Bugzilla – Bug 1215950
QEMU (ipxe): Patch missing to build with current Binutils
Last modified: 2023-10-05 15:46:08 UTC
Actually, that's not QEMU but ipxe but that's part of the QEMU package: (Currently at:) https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:B/qemu/standard/x86_64 [ 2843s] arch/x86/image/bootsector.c: Assembler messages: [ 2843s] arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push' [ 2843s] make[1]: *** [Makefile.housekeeping:956: bin-x86_64-efi/bootsector.o] Error 1 [ 2843s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/qemu-8.1.0/roms/ipxe/src' The upstream issue is: with merged patch/pull request: https://github.com/ipxe/ipxe/pull/1011 and associated issue https://github.com/ipxe/ipxe/pull/1011 Binutils update request: https://build.opensuse.org/request/show/1113885
I am slighty confused: https://build.opensuse.org/package/revisions/openSUSE:Factory/qemu ---------cut------- Ana Guerrero's avatar Ana Guerrero (anag+factory) accepted request 1111408 from Dario Faggioli's avatar Dario Faggioli (dfaggioli) 17 days ago (revision 260) - Fix bsc#1215311: * roms/ipxe: Backport 0aa2e4ec9635, in preparation of binutils 2.41 (bsc#1215311) ---------cut------- I am not quite sure it does contain the patch of interest as _service points to 745b08ecda828f53eb32b73116e41118e30d0ee7 https://github.com/openSUSE/qemu/commit/745b08ecda828f53eb32b73116e41118e30d0ee7 which is not part of any branch and is *not* about Binutils but about python: " [openSUSE][RPM] Make the package buildable on SLE/Leap 15.x " But the currently latest patch at https://github.com/openSUSE/qemu/commits/factory indeed contains has last commit: "roms/ipxe: Backport 0aa2e4ec9635, in preparation of binutils 2.41 (bsc#1215311)" And the latter contains the fix from https://github.com/ipxe/ipxe/pull/1036 (sorry for the wrong pxe pull request in comment 0). * * * Thus, it looks as if another _servicedata update is needed to point to the proper GIT commit!
Mmm... that's a bit weird indeed. Anyway, this was already handled in bug 1215311, which is already mentioned in the changelog, so I'm closing this as a duplicate, and let's continue the discussion there... *** This bug has been marked as a duplicate of bug 1215311 ***