Hi, I get the following link error in libraptorhtml.so: ld: fatal: symbol `kISupportsIID' is multiply defined: (file ../../dist/lib/libraptorxmldoc_s.a(nsXMLContentSink.o) and file ../../dist/lib/libraptorlayout_s.a(nsGenericElement.o)); ld: fatal: symbol `kIContentIID' is multiply defined: (file ../../dist/lib/libraptorxmldoc_s.a(nsXMLContentSink.o) and file ../../dist/lib/libraptorlayout_s.a(nsGenericElement.o)); ld: fatal: File processing errors. No output written to libraptorhtml.so collect2: ld returned 1 exit status This problem has not been there on Wednesday, just checked out with date and verified, layout passed with no problems. The funny thing is, that I don't find any changes either in nsGenericElement.cpp or nsXMLContentSink.cpp, that would make up for this. This has been reported by daa in the xslt newsgroup as well, so I don't think it's my configuration. Axel
not positive , but i think I saw this before last wed changed to OS-ALL , I see this on linux also
OS: Solaris → All
Hardware: Sun → All
I saw that too over the weekend, after removing the two declarations it was building again. Index: nsXMLContentSink.cpp =================================================================== RCS file: /cvsroot/mozilla/layout/xml/document/src/nsXMLContentSink.cpp,v retrieving revision 1.108 diff -r1.108 nsXMLContentSink.cpp 103c103 < static NS_DEFINE_IID(kIContentIID, NS_ICONTENT_IID); --- > /*static NS_DEFINE_IID(kIContentIID, NS_ICONTENT_IID);*/ 105c105 < static NS_DEFINE_IID(kISupportsIID, NS_ISUPPORTS_IID); --- > /*static NS_DEFINE_IID(kISupportsIID, NS_ISUPPORTS_IID);*/ Don't ask me why this broke ....
Reassigning to nisheeth
Assignee: clayton → nisheeth
Axel, I am re-assigning this to you. I've sent you comments about your patch via email. Once you get a chance to check this in, please close out this bug. Thanks!
Assignee: nisheeth → axel
I have some free time today. Will check in the fix today. Re-assigning to myself.
Assignee: axel → nisheeth
The fix is checked in.
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Not seeing this problem in the July 14th builds. Marking verified fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.