[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10
I'm looking into moving the section headers to the end of the object file for ld.bfd. It doesn't look too hard, but there will likely be some testsuite tweaking needed. It looks like gold puts section headers last. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1365664 Title: gdb source test suites are failing in Ubuntu14.10 Status in “gdb” package in Ubuntu: Confirmed Bug description: ---Problem Description--- gdb source test suites are failing in Ubuntu14.10 Machine Type = P8 ---Steps to Reproduce--- Install a P8 system with Power KVM and then install Ubuntu 14.10 guest. Then try to build and execute the gdb source test suites as below. root@ubuntu:~# apt-get source gdb root@ubuntu:~# cd gdb-7.8/ root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 21 | tee gdblog === gdb Summary === # of expected passes25009 # of unexpected failures287 # of unexpected successes 2 # of expected failures 66 # of unknown successes 1 # of known failures 59 # of unresolved testcases 3 # of untested testcases 19 # of unsupported tests 100 ---uname output--- Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 VM provided by Pavaman and the number of failures curiously increased to 250 (in comparison to less than 140 on 14.04), which leads me to believe that there is something in the environment of Ubuntu 14.10 compromising gdb functionality in several testcases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1365664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371636] Re: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs
It looks like the overlapping FDE error is caused by a bunch of zero address range FDEs in /usr/lib/llvm-3.5/lib/libclangCodeGen.a(CGStmtOpenMP.o). These do have the potential to cause an exception handling problem at runtime, so ld is correct to complain. (It might also be reasonable for ld to discard these FDEs.) I haven't looked into why they are being generated, I'll leave that to someone familiar with that library. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs Status in The ARB phylogenetic analysis suite: Confirmed Status in binutils: Unknown Status in Mesa: Confirmed Status in “binutils” package in Ubuntu: Confirmed Bug description: Since today mesa fails to build on Ubuntu 14.10 (both i386 and amd64) while it still builds fine on Ubuntu 14.04. Nothing relevant changed in mesa since previous build in my PPA (indeed just some vc4 code only built on arm), the bug is reported by ld which I noticed just got updated with binutils package. Full PPA build log: https://launchpadlibrarian.net/185286922/buildlog_ubuntu-utopic-i386.mesa_10.4~git1409190730.195891~gd~u_FAILEDTOBUILD.txt.gz Error: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crti.o /usr/lib/gcc/i686-linux-gnu/4.9/crtbeginS.o -Wl,--whole-archive ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_client.a ../../../../src/gallium/state_trackers/clover/.libs/libclover.a ../../../../src/gallium/auxiliary/.libs/libgallium.a ../../../../src/util/.libs/libmesautil.a ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a ../../../../src/gallium/winsys/sw/xlib/.libs/libws_xlib.a -Wl,--no-whole-archive -L/usr/lib/llvm-3.5/lib /usr/lib/i386-linux-gnu/libexpat.so -lX11 -lXext -lXfixes -lxcb-dri2 -lxcb -ldrm -ldl -lclangFrontendTool -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangAnalysis -lclangAST -lclangEdit -lclangLex -lclangBasic -lLLVM-3.5.0 -L/usr/lib/gcc/i686-linux-gnu/4.9 -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-linux-gnu/4.9/crtendS.o /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crtn.o -O2 -march=pentium3 -Wl,--gc-sections -Wl,--no-undefined -Wl,--version-script=../../../../../../src/gallium/targets/opencl/opencl.sym -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-soname -Wl,libMesaOpenCL.so.1 -o .libs/libMesaOpenCL.so.1.0.0 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs. /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:636: recipe for target 'libMesaOpenCL.la' failed To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371636]
Build libOpenCL.so.1 with -Wl,-noinhibit-exec,-Map,libOpenCl.map and look at the mapfile entries for .eh_frame. Try to match up with addresses given for the overlapping FDE. This should give you the object file(s) at fault. My guess is that further analysis will point at an llvm bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs Status in The ARB phylogenetic analysis suite: Confirmed Status in binutils: Unknown Status in Mesa: Confirmed Status in “binutils” package in Ubuntu: Confirmed Status in “llvm-toolchain-3.5” package in Ubuntu: Confirmed Bug description: Since today mesa fails to build on Ubuntu 14.10 (both i386 and amd64) while it still builds fine on Ubuntu 14.04. Nothing relevant changed in mesa since previous build in my PPA (indeed just some vc4 code only built on arm), the bug is reported by ld which I noticed just got updated with binutils package. Full PPA build log: https://launchpadlibrarian.net/185286922/buildlog_ubuntu-utopic-i386.mesa_10.4~git1409190730.195891~gd~u_FAILEDTOBUILD.txt.gz Error: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crti.o /usr/lib/gcc/i686-linux-gnu/4.9/crtbeginS.o -Wl,--whole-archive ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_client.a ../../../../src/gallium/state_trackers/clover/.libs/libclover.a ../../../../src/gallium/auxiliary/.libs/libgallium.a ../../../../src/util/.libs/libmesautil.a ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a ../../../../src/gallium/winsys/sw/xlib/.libs/libws_xlib.a -Wl,--no-whole-archive -L/usr/lib/llvm-3.5/lib /usr/lib/i386-linux-gnu/libexpat.so -lX11 -lXext -lXfixes -lxcb-dri2 -lxcb -ldrm -ldl -lclangFrontendTool -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangAnalysis -lclangAST -lclangEdit -lclangLex -lclangBasic -lLLVM-3.5.0 -L/usr/lib/gcc/i686-linux-gnu/4.9 -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-linux-gnu/4.9/crtendS.o /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crtn.o -O2 -march=pentium3 -Wl,--gc-sections -Wl,--no-undefined -Wl,--version-script=../../../../../../src/gallium/targets/opencl/opencl.sym -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-soname -Wl,libMesaOpenCL.so.1 -o .libs/libMesaOpenCL.so.1.0.0 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs. /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:636: recipe for target 'libMesaOpenCL.la' failed To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371636]
I don't believe trunk binutils is the source of the problem. Trunk binutils (commit ae6c7e33 and aa8f4d1e) is merely letting you know about a case where previous versions of ld silently created binaries with potential runtime failures during exception handling. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs Status in The ARB phylogenetic analysis suite: Confirmed Status in binutils: Unknown Status in Mesa: Confirmed Status in “binutils” package in Ubuntu: Confirmed Status in “llvm-toolchain-3.5” package in Ubuntu: Confirmed Bug description: Since today mesa fails to build on Ubuntu 14.10 (both i386 and amd64) while it still builds fine on Ubuntu 14.04. Nothing relevant changed in mesa since previous build in my PPA (indeed just some vc4 code only built on arm), the bug is reported by ld which I noticed just got updated with binutils package. Full PPA build log: https://launchpadlibrarian.net/185286922/buildlog_ubuntu-utopic-i386.mesa_10.4~git1409190730.195891~gd~u_FAILEDTOBUILD.txt.gz Error: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crti.o /usr/lib/gcc/i686-linux-gnu/4.9/crtbeginS.o -Wl,--whole-archive ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_client.a ../../../../src/gallium/state_trackers/clover/.libs/libclover.a ../../../../src/gallium/auxiliary/.libs/libgallium.a ../../../../src/util/.libs/libmesautil.a ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a ../../../../src/gallium/winsys/sw/xlib/.libs/libws_xlib.a -Wl,--no-whole-archive -L/usr/lib/llvm-3.5/lib /usr/lib/i386-linux-gnu/libexpat.so -lX11 -lXext -lXfixes -lxcb-dri2 -lxcb -ldrm -ldl -lclangFrontendTool -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangAnalysis -lclangAST -lclangEdit -lclangLex -lclangBasic -lLLVM-3.5.0 -L/usr/lib/gcc/i686-linux-gnu/4.9 -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-linux-gnu/4.9/crtendS.o /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crtn.o -O2 -march=pentium3 -Wl,--gc-sections -Wl,--no-undefined -Wl,--version-script=../../../../../../src/gallium/targets/opencl/opencl.sym -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-soname -Wl,libMesaOpenCL.so.1 -o .libs/libMesaOpenCL.so.1.0.0 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs. /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:636: recipe for target 'libMesaOpenCL.la' failed To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371636]
It looks like the overlapping FDE error is caused by a bunch of zero address range FDEs in /usr/lib/llvm-3.5/lib/libclangCodeGen.a(CGStmtOpenMP.o). These do have the potential to cause an exception handling problem at runtime, so ld is correct to complain. (It might also be reasonable for ld to discard these FDEs.) I haven't looked into why they are being generated, I'll leave that to someone familiar with that library. So, not a mesa bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs Status in The ARB phylogenetic analysis suite: Confirmed Status in binutils: Unknown Status in Mesa: Confirmed Status in “binutils” package in Ubuntu: Confirmed Status in “llvm-toolchain-3.5” package in Ubuntu: Confirmed Bug description: Since today mesa fails to build on Ubuntu 14.10 (both i386 and amd64) while it still builds fine on Ubuntu 14.04. Nothing relevant changed in mesa since previous build in my PPA (indeed just some vc4 code only built on arm), the bug is reported by ld which I noticed just got updated with binutils package. Full PPA build log: https://launchpadlibrarian.net/185286922/buildlog_ubuntu-utopic-i386.mesa_10.4~git1409190730.195891~gd~u_FAILEDTOBUILD.txt.gz Error: libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crti.o /usr/lib/gcc/i686-linux-gnu/4.9/crtbeginS.o -Wl,--whole-archive ../../../../src/gallium/auxiliary/pipe-loader/.libs/libpipe_loader_client.a ../../../../src/gallium/state_trackers/clover/.libs/libclover.a ../../../../src/gallium/auxiliary/.libs/libgallium.a ../../../../src/util/.libs/libmesautil.a ../../../../src/gallium/winsys/sw/null/.libs/libws_null.a ../../../../src/gallium/winsys/sw/dri/.libs/libswdri.a ../../../../src/gallium/winsys/sw/xlib/.libs/libws_xlib.a -Wl,--no-whole-archive -L/usr/lib/llvm-3.5/lib /usr/lib/i386-linux-gnu/libexpat.so -lX11 -lXext -lXfixes -lxcb-dri2 -lxcb -ldrm -ldl -lclangFrontendTool -lclangFrontend -lclangDriver -lclangSerialization -lclangCodeGen -lclangParse -lclangSema -lclangAnalysis -lclangAST -lclangEdit -lclangLex -lclangBasic -lLLVM-3.5.0 -L/usr/lib/gcc/i686-linux-gnu/4.9 -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.9/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-linux-gnu/4.9/crtendS.o /usr/lib/gcc/i686-linux-gnu/4.9/../../../i386-linux-gnu/crtn.o -O2 -march=pentium3 -Wl,--gc-sections -Wl,--no-undefined -Wl,--version-script=../../../../../../src/gallium/targets/opencl/opencl.sym -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-soname -Wl,libMesaOpenCL.so.1 -o .libs/libMesaOpenCL.so.1.0.0 /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs. /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:636: recipe for target 'libMesaOpenCL.la' failed To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833237]
This is due to a horrible linker script breaking a new GOT indirect to GOT relative optimisation (git commit 066f4018ae78). ld does a preliminary layout to see whether various optimisations can be done. In this case the preliminary layout indicates that code using a GOT indirect address can be replaced with code calculating a GOT relative address (saving a GOT entry and load from memory). The trouble is that skiboot.lds puts a bunch of dynamic sections between .got and the address in question. Those dynamic sections are not filled out for the preliminary layout, nor can they be since one of the aims of the ppc64 linker optimisation is to reduce dynamic relocations. With the dynamic sections adding over 150kb, the optimisation is no longer valid but ld has already removed the GOT entry. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1833237 Title: skiboot ftbfs in eoan Status in binutils: In Progress Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833237]
Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1833237 Title: skiboot ftbfs in eoan Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Status in binutils source package in Eoan: Confirmed Status in skiboot source package in Eoan: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479]
Well, yes, but patches can be posted to binut...@sourceware.org without a bugzilla open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Confirmed Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479]
(In reply to Balint Reczey from comment #2) > Did I miss something? You did. By subtracting off_adjust from the value written to p_offset you potentially have p_offset mod page_size != p_vaddr mod page_size. This will fail the glibc test in elf/dl-load.c resulting in "ELF load command address/offset not properly aligned" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Won't Fix Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479]
It looks to me like your fix ignores the following comment, and will therefore cause problems with other loaders. /* We shouldn't need to align the segment on disk since the segment doesn't need file space, but the gABI arguably requires the alignment and glibc ld.so checks it. So to comply with the alignment requirement but not waste file space, we adjust p_offset for just this segment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in binutils: Won't Fix Status in binutils package in Ubuntu: In Progress Status in gzip package in Ubuntu: In Progress Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845190]
Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1845190 Title: binutils nm wrong output format breaks i386 nm work Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Bug description: discovered with diffoscope autopkgregression, looks like a real bug, based on https://salsa.debian.org/reproducible-builds/diffoscope/issues/69 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1845190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844119]
Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1844119 Title: readelf crash on 32bit, leading to abi-monitor testsuite regression Status in binutils: Fix Released Status in binutils package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Bug description: readelf --debug-dump=info libjsoncpp.so.1.8.1 to reproduce dpkg -l |grep binut ii binutils2.32.51.20190905-0ubuntu1 i386 GNU assembler, linker and binary utilities ii binutils-common:i3862.32.51.20190905-0ubuntu1 i386 Common files for the GNU assembler, linker and binary utilities ii binutils-i686-linux-gnu 2.32.51.20190905-0ubuntu1 i386 GNU binary utilities, for i686-linux-gnu target ii libbinutils:i3862.32.51.20190905-0ubuntu1 i386 GNU binary utilities (private shared library) To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1844119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479]
Closing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1843479
Title:
gzip in Ubuntu Eoan results in Exec format error on WSL1
Status in binutils:
Fix Released
Status in binutils package in Ubuntu:
Fix Released
Status in gzip package in Ubuntu:
Fix Released
Status in binutils source package in Eoan:
Fix Released
Status in gzip source package in Eoan:
Fix Released
Bug description:
[Impact]
* Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
* The error occurs frequently in package updates and makes gzip inoperable
on WSL1
* The problem is caused by PT_LOAD offset pointing past the end of file and
the fix is fixing strip to not generate such ELF files and recompiling gzip
with the fixed strip.
[Test Case]
* Check the gzip binary for wrong offset:
$ FILE=/usr/bin/gzip; readelf -W --program-headers $FILE | awk -v
size=$(stat -c %s $FILE) '/^ LOAD/ {if (strtonum($2) > size) {print "wrong
offset ("$2" ("strtonum($2)") points past EOF:" size; exit 1;}}'
[ Regression Potential ]
* The binutils fix could cause binutils to generate invalid ELF files. The
fix is very small and isolated and has been tested and accepted by upstream,
which makes such problems unlikely.
* Bugs in the toolchain in general can make the rebuilt gzip show new
errors, but this generally applies to many SRUs and security updates. The
testing period in proposed should mitigate this risk.
[Other Info]
* Binutils 2.33.1-6ubuntu1.1 was accidentally built in -proposed
instead of in a PPA. I've rebuilt it in https://launchpad.net/~ci-
train-ppa-service/+archive/ubuntu/3878 for the -security pocket as
2.33-2ubuntu1.2.
[Originial Bug Text]
Summary:
Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
What I expect to happen:
gzip executes correctly on WSL1.
What happens instead:
gzip fails with an Exec format error.
Notes:
I suspect a change in how gzip is being built for Eoan is causing
issues with ELF parsing on the WSL1 translation layer. For example:
On Disco with gzip 1.9-3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped
On Eoan with gzip 1.10-0ubuntu3:
$ file /bin/gzip
/bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0,
stripped
Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
not believe this is an issue in 1.10 because this error does not occur
when building gzip from GNU project source on Ubuntu Eoan.
Justifications:
WSL1 will need to be patched in future Windows builds for this change
in ELF. However that patch will likely not be backported to older
builds of Windows, including Windows Enterprise/Server 2019.
To ensure Eoan can run on current and older builds of Windows Ubuntu
should consider looking at how it's building gzip and see if it can be
made to 'play nice' until WSL1 can be updated.
This was originally reported here:
https://github.com/microsoft/WSL/issues/4461
Details:
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
*** 1.10-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1843479/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40214]
Documented -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/40214 Title: ld checks for libs in wrong order. it should be inline with ld.so and check configured folders first. Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: if one installs a new version of a lib to /usr/local/lib and has an old version from the system in /usr/lib linking fails with gcc. it tries to link the version in /usr/lib removing the version from /usr/lib, linking works. ldd shows the right version in /usr/local/lib since the version of libtool in ubuntu does not include dependency_libs from the .la file, one has to specify the dependency libs manualy or remove the libs from /usr/lib; both merly workarounds that i dont want to use upstream. not sure what the right place for this bug is. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/40214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958389]
HJ, you likely can reproduce the failue with an asan build of binutils, or using MALLOC_PERTURB_. I haven't tested the patch yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: In Progress Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: New Status in xen source package in Jammy: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000]
[Touch-packages] [Bug 1958389]
Created attachment 13937 Likely fix >From the backtrace in https://bugs.debian.org/1004269 it is clear that the problem is triggered by commit e86fc4a5bc37 in which a new extrap field was added to coffcode.h combined_entry_type but is not used on anything except rs6000 coff targets. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: In Progress Status in launchpad-buildd: New Status in binutils package in Ubuntu: New Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: New Status in xen source package in Jammy: Invalid Status in binutils package in Debian: New Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19
[Touch-packages] [Bug 1958389]
Fixed mainline and 2.38 branch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Fix Released Status in launchpad-buildd: New Status in binutils package in Ubuntu: Fix Released Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: Fix Released Status in xen source package in Jammy: Invalid Status in binutils package in Debian: Fix Released Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000] Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]:
[Touch-packages] [Bug 2023437]
When I build clang-16 from your object files (plus my system libraries and startup files) for powerpc64le using gold 2.40.50.20230614 I get exactly the same binary as when using gold 2.39.0.20230101. That's comparing gold from the tip of master and binutils-2_39-branch in sourceware.org/git/binutils-gdb.git. The latter does not have the commit you identify as causing a problem. Very likely the reason why I don't see a problem is that my libz.so.1, libtinfo.so.5, libstdc++.so.6, libm.so.6, libgcc_s.so.1, libc.so.6, ld64.so.2, or startup files are different to yours. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: In Progress Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm
[Touch-packages] [Bug 2023437]
Should now be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move
[Touch-packages] [Bug 2023437]
I've been going down the wrong rabbit hole, I should have asked you at the outset to post the result of your g++ command with -v added. That would have shown your compiler is defaulting to PIEs while mine is not. Adding -pie to the gold command line shows a huge number of relative dynamic relocations are missing from 2.40 and mainline compared to 2.39. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: Fix Released Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument
[Touch-packages] [Bug 2023437]
Linking with your .so files still doesn't give me any difference between gold-2.39 and gold mainline. I'm using my crt*.o, libc_nonshared.a, libgcc.a. From ld -t output it seems nothing from libc_nonshared.a or libgcc.a is extracted, so the only real difference ought to be crt1.o, crti.o, crtn.o, crtbegin.o and crtend.o. Please supply them too. For reference the linker command line I'm using on my x86_64 to powerpc64le cross compiler setup is: ~/build/gas/all/gold/ld-new --sysroot=/home/gnu/powerpc64le-linux-gnu --eh-frame-hdr -m elf64lppc -dynamic-linker /lib64/ld64.so.2 -o bin/clang-16 /home/gnu/powerpc64le-linux-gnu/usr/lib64/crt1.o /home/gnu/powerpc64le-linux-gnu/usr/lib64/crti.o /usr/local/lib/gcc/powerpc64le-linux-gnu/12.2.0/crtbegin.o -L/usr/local/lib/gcc/powerpc64le-linux-gnu/12.2.0 -v -Bsymbolic- functions -z relro --build-id --gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -rpath $ORIGIN/../lib: lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLLVMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse.a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a so/libz.so.1 so/libtinfo.so.6.4 so/libstdc++.so.6.0.32 so/libm.so.6 so/libgcc_s.so.1 -lgcc --start-group so/libc.so.6 /home/gnu/powerpc64le- linux-gnu/usr/lib64/libc_nonshared.a so/ld64.so.2 --end-group so/libgcc_s.so.1 -lgcc /usr/local/lib/gcc/powerpc64le-linux- gnu/12.2.0/crtend.o /home/gnu/powerpc64le-linux-gnu/usr/lib64/crtn.o This is the command line passed to the linker by g++-12 as shown by adding -v to the g++ command line, with unneeded plugin and library path stuff removed and modified to pick up your shared libraries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: In Progress Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move
