effects versions 1.0.0,1.1.0,1.1.2 with CFLAGS="-march=i686 -O2 -pipe -fstack-check" /var/tmp/portage/busybox-1.1.2/work/busybox-1.1.2/coreutils/mv.c: In function `mv_main': /var/tmp/portage/busybox-1.1.2/work/busybox-1.1.2/coreutils/mv.c:129: error: label 'RET_1' used before containing binding contour make: *** [/var/tmp/portage/busybox-1.1.2/work/busybox-1.1.2/coreutils/mv.o] Error 1 !!! ERROR: sys-apps/busybox-1.1.2 failed. !!! Function src_compile, Line 129, Exitcode 2 !!! build failed !!! If you need support, post the topmost build error, NOT this status message.
So remove that flag from your make.conf?
-fstack-check is not a supported flag.
(In reply to comment #2) > -fstack-check is not a supported flag. was in 2005.0, gentoo hardened and other flavours of linux included check page 90 http://dev.gentoo.org/~spyderous/articles/linux_development_platform/CH03.pdf
what's your point ? there are a ton of flags provided by gcc
(In reply to comment #5) > what's your point ? there are a ton of flags provided by gcc There was no problem with this flag in 2005.0 as I had it set in the make.conf as it provides some protection against stack smash attacks. This was a flaw that was open to attack from badly written software in 2.4 and earlier kernels. Busybox should handle any compiler flags gracefully - even if it just ignores it.
The problem relates to the "Basic" type use of goto's in mv.c - this is why the complier borks as it does not where the heck the stack is going
(In reply to comment #3) > (In reply to comment #2) > > -fstack-check is not a supported flag. > > was in 2005.0, gentoo hardened and other flavours of linux included > hardened uses -fstack-protector{,-all} http://www.gentoo.org/proj/en/hardened/ (I'm one of the maintainers..)
