Open
Bug 1281627
Opened 8 years ago
Updated 2 years ago
Can no longer have both --enable-debug and --enable-debug-symbols
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(firefox50 affected)
NEW
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: bzbarsky, Unassigned)
References
Details
This used to work; I have --enable-debug-symbols in the overall mozconfig that both debug and opt builds use... Now I get: mozbuild.configure.options.InvalidOptionError: '--enable-debug-symbols=-gdwarf-2' implied by '--enable-debug' conflicts with '--enable-debug-symbols' from the mozconfig
Flags: needinfo?(cmanchester)
Comment 1•8 years ago
|
||
That error message means this is a mozconfig with ac_add_options --enable-debug-symbols ac_add_options --enable-debug=-gdwarf-2 This was intended with bug 1279369, because --enable-debug-symbols has no effect in this case. In the case --enable-debug isn't set, --enable-debug-symbols is the default. An earlier version of that patch emulated the existing behavior, I can post that here if we want to go back to it.
Flags: needinfo?(cmanchester)
Reporter | ||
Comment 2•8 years ago
|
||
Hmm. So my use case is that I basically have three mozconfigs: opt, debug, shared. The first two both include the third. I want debug symbols in all, so have --enable-debug-symbols in the shared. I don't know at this point why I have the -gdwarf-2 thing. Without the --enable-debug thing, is there a difference between --enable-debug-symbols and --enable-debug-symbols=-gdwarf-2? For that matter, is there a practical difference between "--enable-debug=-gdwarf-2" and "--enable-debug --enable-debug-symbols"? I'm pretty happy to change my mozconfigs here; I just want to make sure that both my debug and opt builds end up with the best debug symbols I can get, without sacrificing performance of the opt build.
Comment 3•8 years ago
|
||
I think the thing to do will be to remove --enable-debug-symbols altogether. This is the default, so the opt builds will still end up with symbols (via "-g"), and debug builds will use whatever is passed to --enable-debug. I'm not sure of the practical differences between "-g" (the default) and "-gdwarf-2", but DWARF seems like a common default for debug info.
Reporter | ||
Comment 4•8 years ago
|
||
OK. Can probably just mark this invalid then...
Updated•6 years ago
|
Product: Core → Firefox Build System
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•