Closed Bug 170975 Opened 23 years ago Closed 23 years ago

RFE: Add configure-option to avoid the usage of intermediate *.a-archives

Categories

(SeaMonkey :: Build Config, enhancement)

Product:
SeaMonkey
Component:
Build Config
Platform:
All
Linux
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 78081

People

(Reporter: roland.mainz, Assigned: netscape)

Details

RFE: Add configure-option to avoid the usage of intermediate *.a-archives. It looks that this is the main issue why Sun Workshop's XIPO(=interprocedural optimizer) and some other stuff doesn't work... ;-(
*** This bug has been marked as a duplicate of 78081 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Christopher Seawood wrote: > *** This bug has been marked as a duplicate of 78081 *** Why do you think that this is a DUPlicate of that bug ? I am asking for an optional switch to pass everything directly to the linker step without creating *.a archives as intermediate steps first (yes, I know, we may run into problems with the "too long commandline"-issue) ...
I picked the wrong bug. The feature you're asking for was already evaluated in bug 11219 and because of the commandline limitations, it falls in the WONTFIX category. Yet another configure option isn't an option. If this were to be implemented, it would be an all or nothing venture.
Christopher Seawood wrote: > I picked the wrong bug. The feature you're asking for was already evaluated > in bug 11219 and because of the commandline limitations, it falls in the > WONTFIX category. Not really. Having this option would produce a testcase for the compiler folks and would help to check whether they can fix this in their code (as I said, this seems to screw some very valuable compiler features like XIPO, confuses some debuggers like "dbx" and is responsible for some other issues, too).
Really, it does. The explanation that you give does not negate that bug 11219 already pointed out the problems of this RFE. If you have a solution for those problems, then we can reconsider the issue. I am NOT going to add another build option *just* so that you can provide a "testcase" for the sun compiler team. You know exactly what triggers the problem so you can provide a static testcase based upon our current tree. The dbx issue sounds like a dbx bug. Please elaborate on "other issues".
v dup.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.