Using the hardened gcc profile emerging busybox causes an internal compiler error. After switching to the vanilla profile busybox compiler without problems. powerpc-unknown-linux-gnu-gcc -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/include -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/include -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/e2fsprogs -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wstrict-prototypes -Wshadow -Os -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/e2fsprogs/ -c -o /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/shell/cmdedit.o /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/shell/cmdedit.c /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/shell/cmdedit.c: In function `input_tab': /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/shell/cmdedit.c:1123: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. Preprocessed source stored into /var/tmp/portage/busybox-1.00-r4/temp/ccFIGtEW.out file, please attach this to your bugreport. make: *** [/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/shell/cmdedit.o] Error 1 !!! ERROR: sys-apps/busybox-1.00-r4 failed. !!! Function src_compile, Line 144, Exitcode 2 !!! build failed !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1. select the hardened gcc profile 2. emerge busybox-1.00-r4 3. watch it cause an internal compiler error Actual Results: internal compiler error Expected Results: build without error Portage 2.0.51.22-r3 (selinux/2005.1/ppc, gcc-3.4.4, glibc-2.3.4.20041102-r1, 2.6.13-hardened ppc) ================================================================= System uname: 2.6.13-hardened ppc 7447A, altivec supported Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.90.0.3-r5 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CBUILD="powerpc-unknown-linux-gnu" CFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" DISTDIR="/var/tmp/portage/distfiles" FEATURES="autoconfig distlocks sandbox selinux sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://pandemonium.tiscali.de/pub/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/" LC_ALL="en_GB.utf8" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa altivec berkdb cdr crypt cups directfb dlloader dvd dvdread esd fam flac gd gdbm gif gpm gtk hardened imagemagick imlib java jpeg ldap mad motif mpeg ncurses network nls nptl ogg opengl pam perl png ppc python readline real selinux slang sqlite ssl tcpd theora tiff truetype unicode vorbis xine xml2 xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS, MAKEOPTS
Created attachment 70267 [details] Preprocessed source stored "Preprocessed source stored into /var/tmp/portage/busybox-1.00-r4/temp/cc10h9pd.out file, please attach this to your bugreport." As requested
not a bug in busybox
Same bug here. Any recipe to rebuild a clean toolchain on PPC (like bug #79852 for x86) ?
Another ppc/hardened bug? Probably we should keyword and group them...
This is a hardened bug, re-assigning to them.
Looks like another -fno-strict-aliasing problem. Why do ppc people like to put this in their CFLAGS?
(In reply to comment #6) > Looks like another -fno-strict-aliasing problem. No it doesn't. Just confirmed the same behaviour with the hardened compiler with standard make.default settings (busybox-1.1.0; the relevant source file hasn't changed much). The combination that fails is -fstack-protector and -funit-at-a-time (which is enabled at -O2, -Os and higher). It's a start, anyway.
Please reopen with upstream if this is still a problem.
nixnut if still having problems please also file a new hardened+ppc+busybox bug here so we're aware and for tracking against any upstream bug report/URL. Thanks.