Building dev-util/boost-build-1.34.0 with sys-devel/gcc-4.2.0 segfaults reproducible, while it can be build with sys-devel/gcc-4.1.2. I know 4.2.0 is hardmasked and no bugs shall be submited, but I am unsure if and how this bug should be reported to upstream. Reproducible: Always Steps to Reproduce: 1. gcc-config i686-pc-linux-gnu-4.2.0 2. emerge =dev-util/boost-build-1.34.0 Actual Results: >>> Unpacking source... >>> Unpacking boost_1_34_0.tar.bz2 to /var/tmp/portage/dev-util/boost-build-1.34.0/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/dev-util/boost-build-1.34.0/work/boost_1_34_0/tools ... ### ### Using 'cc' toolset. ### rm -rf bootstrap mkdir bootstrap i686-pc-linux-gnu-gcc -o bootstrap/jam0 -march=athlon-xp -O2 -pipe -fomit-frame-pointer command.c compile.c debug.c execunix.c expand.c fileunix.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c ./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= clean ./build.sh: line 13: 2428 Segmentation fault $@ !!! ERROR: dev-util/boost-build-1.34.0 failed. Call stack: ebuild.sh, line 1621: Called dyn_compile ebuild.sh, line 973: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile boost-build-1.34.0.ebuild, line 55: Called die !!! building bjam failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/dev-util/boost-build-1.34.0/temp/build.log'. # emerge --info Portage 2.1.2.9 (default-linux/x86/2007.0/desktop, gcc-4.2.0, glibc-2.6-r0, 2.6.21-gentoo-r1 i686) ================================================================= System uname: 2.6.21-gentoo-r1 i686 AMD Athlon(tm) XP 2600+ Gentoo Base System release 1.12.10 Timestamp of tree: Wed, 06 Jun 2007 21:20:01 +0000 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer parallel-fetch prelink sandbox sfperms strict userfetch userpriv usersandbox" GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo/ http://ftp.romnet.org/gentoo/" LANG="en_US.UTF-8" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="3dnow 3dnowext X a52 aac acl acpi alsa apache2 avahi bash-completion berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dbus doc dri dvb dvd dvdr dvdread eds emboss encode evo fam firefox foomaticdb fortran gdbm gif gpm gtk hal iconv ipod ipv6 isdnlog jpeg kde kdeenablefinal kdehiddenvisibility ldap libg++ mad midi mikmod mmx mmxext mp3 mp4 mpeg mplayer mudflap mysql ncurses nls nptl nptlonly nsplugin ogg openal openexr opengl openmp pam pch pcre pdf perl php png ppds pppd python qt3 qt3support qt4 quicktime readline real reflection samba sasl sdl session speex spell spl sse ssl subversion svg tcpd tetex theora threads tiff truetype truetype-fonts type1-fonts unicode usb visualization vorbis win32codecs x264 x86 xcomposite xml xorg xv xvid zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" LIRC_DEVICES="userspace" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
hmm, in bug #178743 some users noted similar errors. Please try with -O0 instead of -O2, this might help...
There are a couple of workarounds listed in Bug #173703 (it also results in a segfault in jam0). Adding -fno-strict-aliasing worked for me.
yep, same bug. i'm waiting for a reply from upstream. Tiziano, you can add -fno-strict-aliasing to the ebuild in the meantime if you want.
err, no ... dont go blindly adding append-flags to work around a gcc bug
it's a jam bug, not a gcc bug, and you had no problem with it in bug #173703
i thought we were discussing an upstream bug report about a gcc-4.2 regression that causes crashes with some C++ code in this case if you're talking about jam having strict aliasing violations, then yes, you'd be correct ... but this would simply be a dupe bug report at any rate *** This bug has been marked as a duplicate of bug 173703 ***
Fixed.