sys-apps/busybox-1.18.3 fails to build: networking/lib.a(arping.o): In function `arping_main': arping.c:(.text.arping_main+0x442): undefined reference to `__memset_chk' archival/lib.a(tar.o): In function `writeLongname': tar.c:(.text.writeLongname+0x11e): undefined reference to `__memset_chk' archival/lib.a(tar.o): In function `writeFileToTarball': tar.c:(.text.writeFileToTarball+0x21d): undefined reference to `__memset_chk' Reproducible: Always Steps to Reproduce:
Created attachment 262601 [details] build log
Created attachment 262603 [details] emerge --info
*** This bug has been marked as a duplicate of bug 353816 ***
This seems to be another bug than #353816 as I've already tried the fixes that were mentioned there and because the error message is slightly different.
Reopened
Workaround proposal if you have a hardened toolchain. Not ideal, but it gets you moving forward... Add into busybox-1.18.3.ebuild:src_prepare() 'append-cflags -D_FORTIFY_SOURCE=0' and rebuild the manifest
(In reply to comment #6) > Workaround proposal if you have a hardened toolchain. Not ideal, but it gets > you moving forward... Add into busybox-1.18.3.ebuild:src_prepare() > 'append-cflags -D_FORTIFY_SOURCE=0' and rebuild the manifest > Thanks, it worked very well and I guess it's not that important to have a failsafe application like busybox fortified anyway.