546454 - gcc 4.2 Linux x86_64 builds fail w/ --enable-debug and --enable-libxul

Status: RESOLVED WONTFIX

(Firefox Build System :: General, defect)

Description

[[e-mail] (:bhearsum)]

While working on bug 512489, Armen discovered that x86_64 linux builds fail with our debug mozconfig with this error:
/usr/bin/ld: ../../staticlib/libxpcom_core.a(nsXPComInit.o): relocation R_X86_64_PC32 against `base::Thread::Options::Options()' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make[4]: *** [libxul.so] Error 1
make[4]: Leaving directory `/builds/slave/tracemonkey-linux64-debug/build/obj-firefox/toolkit/library'
make[3]: *** [libs_tier_toolkit] Error 2
make[3]: Leaving directory `/builds/slave/tracemonkey-linux64-debug/build/obj-firefox'
make[2]: *** [tier_toolkit] Error 2
make[2]: Leaving directory `/builds/slave/tracemonkey-linux64-debug/build/obj-firefox'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/builds/slave/tracemonkey-linux64-debug/build/obj-firefox'

We're building on CentOS 5.0 with a custom gcc-4.3.3 built as described here: https://bugzilla.mozilla.org/show_bug.cgi?id=523365#c3

Comment 1

[[e-mail] (:bhearsum)]

This might block bug 512489, or we might work around it.

Comment 2

[(not currently active) Ted Mielczarek]

This is the same failure mode we saw from landing bug 517097, because the default debug flags had "-g -fno-inline". However, since this doesn't break the 32-bit build, there may be some fiddling with visibility we can do to fix it.

Comment 3

[[e-mail] (:bhearsum)]

fwiw, we ended up working around this for our x86-64 tinderboxes as a result of upgrading to gcc 4.3.3 (used to be gcc 4.2.3)

Comment 4

[(not currently active) Ted Mielczarek]

Doesn't seem like we need to care about GCC 4.2 all that much, then.