[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie
Fixed upstream via https://github.com/ibm-s390-linux/s390-tools/commit/5e46632767cb95afbf867cded150a4b2326f47f3 -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Fix Released -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
This bug was fixed in the package s390-tools - 2.15.1-0ubuntu6 --- s390-tools (2.15.1-0ubuntu6) hirsute; urgency=medium * debian/patches/s390-tools-lp1903984-hirsute.patch zcryptstats: Fix handling of partial results with many domains Thanks to Ingo Franzki (LP: #1903984) -- Frank Heimes Tue, 19 Jan 2021 18:58:26 +0100 ** Changed in: s390-tools (Ubuntu) Status: In Progress => Fix Released -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
Proposed to drop the -no-pie flag at upstream s390-tools: https://github.com/ibm-s390-tools/s390-tools/pull/106 -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Changed in: s390-tools (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: s390-tools (Ubuntu) Status: New => In Progress -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: New Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
This bug was fixed in the package qemu - 1:5.2+dfsg-2ubuntu1 --- qemu (1:5.2+dfsg-2ubuntu1) hirsute; urgency=medium * Merge with Debian unstable - includes fix for CVE-2020-17380 - includes a fix for s390x PCI device reset (LP: #1907656) Remaining changes: - qemu-kvm to systemd unit - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm, hugepages and architecture specifics - d/qemu-system-common.qemu-kvm.service: systemd unit to call qemu-kvm-init - d/qemu-system-common.install: install helper script - d/qemu-system-common.qemu-kvm.default: defaults for /etc/default/qemu-kvm - d/rules: call dh_installinit and dh_installsystemd for qemu-kvm - Distribution specific machine type (LP: 1304107 1621042) - d/p/ubuntu/define-ubuntu-machine-types.patch: distro machine types - d/qemu-system-x86.NEWS Info on fixed machine type definitions for host-phys-bits=true (LP: 1776189) - add an info about -hpb machine type in debian/qemu-system-x86.NEWS - provide pseries-bionic-2.11-sxxm type as convenience with all meltdown/spectre workarounds enabled by default. (LP: 1761372). - ubuntu-q35 alias added to auto-select the most recent q35 ubuntu type - Enable nesting by default - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default in qemu64 on amd [ No more strictly needed, but required for backward compatibility ] - improved dependencies - Make qemu-system-common depend on qemu-block-extra - Make qemu-utils depend on qemu-block-extra - let qemu-utils recommend sharutils - tolerate ipxe size change on migrations to >=18.04 (LP: 1713490) - d/p/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch: old machine types reference 256k path - d/control-in: depend on ipxe-qemu-256k-compat-efi-roms to be able to handle incoming migrations from former releases. - d/control-in: Disable capstone disassembler library support (universe) - d/qemu-system-x86.README.Debian: add info about updated nesting changes - d/control*, d/rules: disable xen by default, but provide universe package qemu-system-x86-xen as alternative [includes compat links changes of 5.0-5ubuntu4] - allow qemu to load old modules post upgrade (LP 1847361) - Drop d/qemu-block-extra.*.in, d/qemu-system-gui.*.in - d/rules: Drop generating package version into maintainer scripts - d/qemu-system-gui.prerm: add no-op prerm to overcome upgrade issues on the bad old prerm (LP 1906245 1905377) * Dropped Changes: - d/control, d/rules: build with gcc-9 on armhf as workaround until resolved in gcc-10 (LP: 1890435) [it is flaky still, but no more 100% fails] * Added Changes: - Refreshed ubuntu machine types for hirsute@5.2 - d/control: regenerated from d/control-in - d/p/ubuntu/lp-1907789-build-no-pie-is-no-functional-liker-flag.patch: fix ld usage of -no-pie (LP: #1907789) qemu (1:5.2+dfsg-2) unstable; urgency=medium * move ui-opengl.so module from qemu-system-gui to qemu-system-common, as other modules want it (Closes: #976996, #977022) * do not install dropped ppc64abi32 binfmt for qemu-user[-static] (Closes: #977015) qemu (1:5.2+dfsg-1) unstable; urgency=medium * new upstream release Closes: #965978, CVE-2020-15859 (22dc8663d9fc7baa22100544c600b6285a63c7a3) Closes: #970539, CVE-2020-25084 (21bc31524e8ca487e976f713b878d7338ee00df2) Closes: #970540, CVE-2020-25085 (dfba99f17feb6d4a129da19d38df1bcd8579d1c3) Closes: #970541, CVE-2020-25624 (1328fe0c32d5474604105b8105310e944976b058) Closes: #970542, CVE-2020-25625 (1be90ebecc95b09a2ee5af3f60c412b45a766c4f) Closes: #974687, CVE-2020-25707 (c2cb511634012344e3d0fe49a037a33b12d8a98a) Closes: #975276, CVE-2020-25723 (2fdb42d840400d58f2e706ecca82c142b97bcbd6) Closes: #975265, CVE-2020-27616 (ca1f9cbfdce4d63b10d57de80fef89a89d92a540) Closes: #973324, CVE-2020-27617 (7564bf7701f00214cdc8a678a9f7df765244def1) Closes: #972864, CVE-2020-27661 (bea2a9e3e00b275dc40cfa09c760c715b8753e03) Closes: CVE-2020-27821 (1370d61ae3c9934861d2349349447605202f04e9) Closes: #976388, CVE-2020-28916 (c2cb511634012344e3d0fe49a037a33b12d8a98a) * remove obsolete patches * refresh use-fixed-data-path.patch and debian/get-orig-source.sh * bump minimum meson version required for build to 0.55.3 * update build rules for several components * remove deprecated lm32 and unicore32 system emulators * remove deprecated ppc64abi32 and tilegx linux-user emulators * install ui-spice-core.so & chardev-spice.so in qemu-system-common * install ui-egl-headless.so in qemu-system-common * install hw-display-virtio-*.so in qemu-system-common * install ui-opengl.so in qemu-system-gui * install qemu-pr-helper.8 in qemu-system-common * qemu-pr-helper moved to usr/bin/ again * qboot.ro
[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie
This bug was fixed in the package binutils - 2.35.50.20201210-0ubuntu2 --- binutils (2.35.50.20201210-0ubuntu2) hirsute; urgency=medium * Revert linker options parsing patch. LP: #1907789. -- Matthias Klose Fri, 11 Dec 2020 11:29:47 +0100 ** Changed in: binutils (Ubuntu) Status: Fix Committed => Fix Released -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
FYI - fix submitted to qemu upstream and for now added to the qemu package. If upstream eventually prefers a different solution I can refresh it accordingly. => https://lists.gnu.org/archive/html/qemu-devel/2020-12/msg03684.html -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
Launchpad has imported 11 comments from the remote bug at https://sourceware.org/bugzilla/show_bug.cgi?id=27050. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-12-11T10:05:19+00:00 Matthias Klose wrote: works with the 2.35 branch, fails with the trunk: $ ld.gold -pie ld.gold: fatal error: no input files $ ld.gold -no-pie ld.gold: fatal error: no input files $ ld.bfd -pie ld.bfd: no input files $ ld.bfd -no-pie ld.bfd: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/3 On 2020-12-11T13:13:48+00:00 Hjl-tools wrote: It is caused by commit 983d925db6a09ac90f6bed90be16eb69267b58e0 Author: Nick Clifton Date: Mon Oct 5 13:53:59 2020 +0100 Update the BFD linker so that it deprecates grouped short options. * lexsup.c (parse_args): Generate an error or warning message when multiple short options are used together. Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/4 On 2020-12-11T13:18:48+00:00 Hjl-tools wrote: $ valgrind ./ld/ld-new -no-pie ==290969== Memcheck, a memory error detector ==290969== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==290969== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info ==290969== Command: ./ld/ld-new -no-pie ==290969== ==290969== Conditional jump or move depends on uninitialised value(s) ==290969==at 0x409A96: parse_args (lexsup.c:749) ==290969==by 0x403DC6: main (ldmain.c:370) ==290969== ./ld/ld-new: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?) ==290969== ==290969== HEAP SUMMARY: ==290969== in use at exit: 21,161 bytes in 10 blocks ==290969== total heap usage: 72 allocs, 62 frees, 43,232 bytes allocated ==290969== ==290969== LEAK SUMMARY: ==290969==definitely lost: 0 bytes in 0 blocks ==290969==indirectly lost: 0 bytes in 0 blocks ==290969== possibly lost: 0 bytes in 0 blocks ==290969==still reachable: 21,161 bytes in 10 blocks ==290969== suppressed: 0 bytes in 0 blocks ==290969== Rerun with --leak-check=full to see details of leaked memory ==290969== ==290969== Use --track-origins=yes to see where uninitialised values come from ==290969== For lists of detected and suppressed errors, rerun with: -s ==290969== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0) Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/5 On 2020-12-11T13:48:11+00:00 Hjl-tools wrote: longind may not be set by getopt_long_only: diff --git a/ld/lexsup.c b/ld/lexsup.c index 0d10bc6fba..60e3f7d8b5 100644 --- a/ld/lexsup.c +++ b/ld/lexsup.c @@ -735,6 +735,7 @@ parse_args (unsigned argc, char **argv) /* getopt_long_only is like getopt_long, but '-' as well as '--' can indicate a long option. */ opterr = 0; + longind = -1; last_optind = optind; optc = getopt_long_only (argc, argv, shortopts, longopts, &longind); if (optc == '?') Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/6 On 2020-12-11T13:55:31+00:00 Hjl-tools wrote: LONGIND returns the index in LONGOPT of the long-named option found. It is only valid when a long-named option has been found by the most recent call. Since the long option isn't found, LONGIND is undefined. Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/7 On 2020-12-11T15:26:17+00:00 Nickc wrote: Not to be facetious but did we ever really support -no-pie ? It does not appear to be documented, and it looks like it is treated internally as two options: -n and -o-pie. I have a patch that fixes the uninitialised memory problem detected by valgrind, but I am wondering whether it is better to add explicit support for -no-pie as an option to turn off -pie, or else keep the linker's error message, and maybe add a --no-pie option instead. Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/comments/8 On 2020-12-11T15:44:44+00:00 Hjl-tools wrote: (In reply to Nick Clifton from comment #5) > Not to be facetious but did we ever really support -no-pie ? > ld/testsuite/config/default.exp: set NOPIE_LDFLAGS "-no-pie" Reply at: https:/
[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => In Progress ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: qemu (Ubuntu) Importance: Undecided => High -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Unknown Status in binutils package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Bug watch added: Sourceware.org Bugzilla #27050 https://sourceware.org/bugzilla/show_bug.cgi?id=27050 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=27050 Importance: Unknown Status: Unknown -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Unknown Status in binutils package in Ubuntu: Fix Committed Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Changed in: binutils (Ubuntu) Status: New => Fix Committed -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils package in Ubuntu: Fix Committed Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Attachment added: "linuxboot.o - build artifact to re-create the issue" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+attachment/5442724/+files/linuxboot.o -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils package in Ubuntu: New Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Attachment added: "flat.lds - build artifact to re-create the issue" https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+attachment/5442723/+files/flat.lds -- 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/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils package in Ubuntu: New Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1%3A5.2%2Bdfsg-2&stamp=1607598738&raw=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+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