Seems that this is the opposite direction of bug #913129 - I had binutils 2.37 as default, sysutils will fail link when it submits the --no-warn-rwx-segments to ld for binutils-2.37. Setting default to binutils-2.39 lets it work fine. Reproducible: Always Steps to Reproduce: 1.have binutils-2.37 installed and set as default (binutils-config) 2.merge syslinux-6.04_pre1-r5 3. Actual Results: build fails with logfile: x86_64-pc-linux-gnu-ld -shared -m elf_i386 --no-warn-rwx-segments -z notext --ha sh-style=gnu -T /var/tmp/portage/sys-boot/syslinux-6.04_pre1-r5/work/syslinux-6. 04-pre1/com32/lib/i386/elf.ld -soname libcom32.c32 -o libcom32.elf zlib/adler32. o zlib/compress.o zlib/crc32.o zlib/uncompr.o zlib/deflate.o zlib/trees.o zlib/z util.o zlib/inflate.o zlib/infback.o zlib/inftrees.o zlib/inffast.o sys/zfile.o sys/zfopen.o libpng/png.o libpng/pngset.o libpng/pngget.o libpng/pngrutil.o libp ng/pngtrans.o libpng/pngwutil.o libpng/pngread.o libpng/pngrio.o libpng/pngwio.o libpng/pngwrite.o libpng/pngrtran.o libpng/pngwtran.o libpng/pngmem.o libpng/pn gerror.o libpng/pngpread.o jpeg/tinyjpeg.o jpeg/jidctflt.o jpeg/decode1.o jpeg/d ecode3.o jpeg/rgb24.o jpeg/bgr24.o jpeg/yuv420p.o jpeg/grey.o jpeg/rgba32.o jpeg /bgra32.o pci/cfgtype.o pci/scan.o pci/bios.o pci/readb.o pci/readw.o pci/readl. o pci/writeb.o pci/writew.o pci/writel.o sys/vesacon_write.o sys/vesaserial_writ e.o sys/vesa/initvesa.o sys/vesa/drawtxt.o sys/vesa/background.o sys/vesa/alphat bl.o sys/vesa/screencpy.o sys/vesa/fmtpixel.o sys/vesa/i915resolution.o syslinux /reboot.o syslinux/keyboard.o syslinux/version.o syslinux/pxe_get_cached.o sysli nux/pxe_get_nic.o syslinux/pxe_dns.o syslinux/video/fontquery.o syslinux/video/r eportmode.o syslinux/addlist.o syslinux/freelist.o syslinux/memmap.o syslinux/mo vebits.o syslinux/shuffle.o syslinux/shuffle_pm.o syslinux/shuffle_rm.o syslinux /biosboot.o syslinux/zonelist.o syslinux/dump_mmap.o syslinux/dump_movelist.o sy slinux/run_default.o syslinux/run_command.o syslinux/cleanup.o syslinux/localboo t.o syslinux/runimage.o syslinux/loadfile.o syslinux/floadfile.o syslinux/zloadf ile.o syslinux/load_linux.o syslinux/initramfs.o syslinux/initramfs_file.o sysli nux/initramfs_loadfile.o syslinux/initramfs_archive.o sys/libansi.o sys/gpxe.o a texit.o onexit.o abort.o x86_64-pc-linux-gnu-ld: unrecognized option '--no-warn-rwx-segments' Expected Results: It should build fine... This has sort of already been fixed because binutils-2.39 and later have been stabilized but was caught off guard since binutils-2.37 is still in portage. I don't know if a fix really is needed but this at least documents a possible issue.
>This has sort of already been fixed because binutils-2.39 and later have been stabilized but was caught off guard since binutils-2.37 is still in portage. Note that <2.40 is masked already, even. But I can see if I can do anything to avoid the error anyway.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e0f0e1c28a7c48434188ca0f60ab21eafa8ba167 commit e0f0e1c28a7c48434188ca0f60ab21eafa8ba167 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-10-18 10:12:08 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-10-18 10:12:08 +0000 sys-boot/syslinux: tweak binutils patch to support <2.39 This makes the upgrade path a bit easier and the option just suppresses a warning, not an error. Bug: https://bugs.gentoo.org/913129 Closes: https://bugs.gentoo.org/915663 Signed-off-by: Sam James <sam@gentoo.org> sys-boot/syslinux/files/syslinux-6.04-binutils-2.41.patch | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
