Description of problem: While trying to build thunderbird-lightning for EPEL 5 I'm getting: /usr/bin/python /builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/mozilla/config/pythonpath.py -I../../../mozilla/config /builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/mozilla/config/expandlibs_exec.py --depend .deps/libcalbasecomps.pp --target libcalbasecomps.so --uselist -- c++ -pedantic -Wall -Wpointer-arith -Woverloaded-virtual -Wno-ctor-dtor-privacy -Wno-invalid-offsetof -Wno-variadic-macros -Wcast-align -Wno-long-long -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -fpermissive -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -finline-limit=50 -fomit-frame-pointer -fPIC -shared -Wl,-z,defs -Wl,--gc-sections -Wl,-h,libcalbasecomps.so -o libcalbasecomps.so calBaseModule.o -lpthread -Wl,-rpath,/usr/lib/thunderbird-lightning-2 -Wl,-rpath-link,/builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/objdir-tb/mozilla/dist/bin:/usr/lib:/usr/local/lib:/lib -Wl,-rpath-link,/usr/lib ../../../calendar/base/src/libcalbase_s.a ../../../calendar/libical/src/libical/libmozical.a -L/builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/objdir-tb/mozilla/dist/bin -lxpcom -lmozalloc -lxul -L../../../mozilla/dist/bin -L../../../mozilla/dist/lib -L/usr/lib -lplds4 -lplc4 -lnspr4 /builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/objdir-tb/mozilla/dist/lib/libxpcomglue_s.a -L/builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/objdir-tb/mozilla/dist/bin -lxpcom -lmozalloc -Wl,--version-script -Wl,/builddir/build/BUILD/thunderbird-lightning-1.9.1/comm-esr17/mozilla/build/unix/gnu-ld-scripts/components-version-script -Wl,-Bsymbolic -ldl -lm collect2: ld terminated with signal 11 [Segmentation fault], core dumped The build completes fine on i386 and x86_64. Version-Release number of selected component (if applicable): 2.17.50.0.6-20.el5_8.3
This could well end up being the same bug as 855163. Both are linker faults that are specific to ppc/ppc64 builds -- and both show up building components of the mozilla/thunderbird suites.
Orion, We need a reasonable way to be able to test this. I've tried without success to set up an environment where I can build thunderbird-lightning on RHEL 5. At the minimum this environment needs to allow for installing an updated binutils linker. That would allow us to test if the fix for 855163 will fix this bug as well. If you've got a suitable srpm and a koji instance where I can throw builds, that would be a huge step forward.
Jeff, I'm afraid I don't have any special access to ppc machines, I'm just using the standard Fedora/EPEL builders. If you have access to the Fedora builders you should be able submit build there. I've added ExcludeArch: ppc for now to the EL5 build, so you'd need to remove that before building. You should be able to check out the el5 branch from the Fedora git repo for thunderbird-lightning.
When I try to fire off a ppc koji build, it claims not to know about the epel target. [law@stumpy thunderbird-lightning]$ ppc-koji build --scratch el5 thunderbird-lightning-1.9.1-1.el5.src.rpm Usage: koji build [options] target <srpm path or scm url> (Specify the --help global option for a list of other help options) koji: error: Unknown build target: el5 [law@stumpy thunderbird-lightning]$ ppc-koji list-targets Name Buildroot Destination --------------------------------------------------------------------------------------------- dist-f12 dist-f12-build dist-f12 dist-f12-updates-candidate dist-f12-build dist-f12-updates-candidate dist-f13-updates-candidate dist-f13-build dist-f13-updates-candidate dist-f14 dist-f14-build dist-f14 dist-f15 dist-f15-build dist-f15 dist-f15-updates-candidate dist-f15-build dist-f15-updates-candidate dist-f16 f16-build f16 f17 f17-build f17 f17-candidate f17-build f17-updates-candidate f18 f18-build f18-updates-candidate f18-candidate f18-build f18-updates-candidate f19 f19-build f19-updates-candidate f19-candidate f19-build f19-updates-candidate f19-rebuild f19-build f19-rebuild f20 f20-build f20 f20-candidate f20-build f20 rawhide f20-build f20 rawhide-repo-holder rawhide rawhide How precisely are you throwing ppc builds into koji?
I would use koji, not ppc-koji koji build --scratch --arch-override=ppc dist-5E-epel ...
I got it to fail after some hacking late last night. Right now it appears to be a different problem than was fixed for 855163. I'll be debugging today. Hopefully it's something already fixed upstream with an associated testcase :-)
Created attachment 734934 [details] Self-contained test Extract on a ppc box. sh doit If the test segfaults, then it failed. Anything else is a pass.
Upstream fix identified. Doing a full build of lightning with a patched up binutils.
Created attachment 735109 [details] Patch from upstream
Created attachment 735963 [details] Testcase for related ppc64 issue Extract on a ppc64 machine and run ./doit Segfault is a failure, anything else is a success.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1306.html