Bug 355021 – sys-apps/busybox-1.18.3 - networking/lib.a(arping.o): In function `arping_main':

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description DarkNRG 2011-02-15 13:31:23 UTC]

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:

[Comment 1 DarkNRG 2011-02-15 13:32:09 UTC]

Created attachment 262601 [details]
build log

[Comment 2 DarkNRG 2011-02-15 13:32:36 UTC]

Created attachment 262603 [details]
emerge --info

[Comment 3 Vlastimil Babka (Caster) (RETIRED) 2011-02-15 13:35:49 UTC]

*** This bug has been marked as a duplicate of bug 353816 ***

[Comment 4 DarkNRG 2011-02-15 13:36:41 UTC]

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.

[Comment 5 DarkNRG 2011-02-15 13:37:23 UTC]

Reopened

[Comment 6 Emil Medve 2011-02-17 20:48:25 UTC]

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

[Comment 7 DarkNRG 2011-02-18 11:58:16 UTC]

(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.

[Comment 8 SpanKY 2011-02-21 16:11:57 UTC]

*** This bug has been marked as a duplicate of bug 353816 ***