Closed Bug 25446 Opened 25 years ago Closed 23 years ago

duplicate symbols when building ../xpcom/build/libxpcom.so on AIX-4.3.2

Categories

(SeaMonkey :: Build Config, defect, P3)

Other
AIX

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ciaran.deignan, Assigned: jdunn)

References

Details

On AIX-4.3.2 the build of the shared object "libxpcom.so", using the 
"makeC++SharedLib_r" command fails due to duplicate symbols. Running the command 
manually with the "-bnoquiet" option gives the following detail:
ld: 0711-224 WARNING: Duplicate symbol: .getter_Copies(nsXPIDLCString&)
ld: 0711-228 WARNING: Duplicate symbols were found while resolving symbols.
        The following duplicates were found:
 Symbol                    Source-File(Object) OR Import-File{Shared-object}
 ------------------------- -------------------------------------------------
 .getter_Copies(nsXPIDLCString&) nsComponentManager.cpp(nsComponentManager.o)
    ** Duplicate **        nsNativeComponentLoader.cpp(nsNativeComponentLoader.o
)
ld: 0711-224 WARNING: Duplicate symbol: getter_Copies(nsXPIDLCString&)
 getter_Copies(nsXPIDLCString&) nsComponentManager.cpp(nsComponentManager.o)
    ** Duplicate **        nsNativeComponentLoader.cpp(nsNativeComponentLoader.o
)

I do not believe that this problem was present in the M12 freeze...
accepting.  cc'd cls and jdunn for input.
Status: NEW → ASSIGNED
Target Milestone: M16
Blocks: 18688
punting to jdunn.  Jim - are you seeing this problem?
Assignee: granrose → jdunn
Severity: blocker → major
Status: ASSIGNED → NEW
Yes, this is a warning and there are more than just here.
Right now I am not too worried about them.  I have no
plan to fix these 'duplicates' but I will keep the bug
open (for now).
Status: NEW → ASSIGNED
removing john and cyeh from being copied
QA Contact: cyeh
M16 has been out for a while now, these bugs target milestones need to be 
updated.
Target Milestone: M16 → M30
I would like to close this bug out.
While we are still getting some duplicate error messages,
my change to only export NSGetModule from all components
has helped reduced some of the warnings... and these are
just warnings.

Since the command doesn't fail, I am marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.