Closed Bug 79771 Opened 25 years ago Closed 25 years ago

Libraries linked against two libstdc++ in 0509 nightly

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.1

People

(Reporter: tenthumbs, Assigned: cls)

Details

In a 050908 Linux nightly, mozilla, as well as regxpcom, fails with a large number of error messages like this: ************************************************** nsNativeComponentLoader: SelfRegisterDll(/tmp/moz/mozilla/components/libxpconnect.so) Load FAILED with error: /tmp/moz/mozilla/components/libxpconnect.so: undefined symbol: __pure_virtual ************************************************** It turns out that most, if not all, of the components/lib*.so are linked against two distinct libstdc++ libs. For example, ldd mozilla-050908/components/libxpconnect.so libxpcom.so => /tmp/moz/mozilla-050908/libxpcom.so (0x4003d000) libplds4.so => /tmp/moz/mozilla-050908/libplds4.so (0x40105000) libplc4.so => /tmp/moz/mozilla-050908/libplc4.so (0x40108000) libnspr4.so => /tmp/moz/mozilla-050908/libnspr4.so (0x4010c000) libpthread.so.0 => /lib/libpthread.so.0 (0x4013b000) libdl.so.2 => /lib/libdl.so.2 (0x4014d000) libmozjs.so => /tmp/moz/mozilla-050908/libmozjs.so (0x40150000) libc.so.6 => /lib/libc.so.6 (0x401b9000) libstdc++-libc6.1-2.so.3 => /usr/lib/libstdc++-libc6.1-2.so.3 (0x402a4000) libm.so.6 => /lib/libm.so.6 (0x402ec000) libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2 (0x40308000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) Yes, I have all sorts of libstdc++ libs lying around for compatibility. This can't possibly be right.
I think this is a variant of bug 79711
Target Milestone: --- → mozilla0.9.1
Extremely bad timing on reverting compiler installation.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.