** 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 /<<PKGBUILDDIR>>/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
