Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 298676 - sys-devel/gcc-4.3.4: cc1: internal compiler error: Illegal instruction (SYSCALLS.c)
Summary: sys-devel/gcc-4.3.4: cc1: internal compiler error: Illegal instruction (SYSCA...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-28 13:17 UTC by Sergey Klyaznik
Modified: 2009-12-29 06:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log and additional log files (additional.tgz,114.08 KB, application/octet-stream)
2009-12-28 13:19 UTC, Sergey Klyaznik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Klyaznik 2009-12-28 13:17:22 UTC
Failed to emerge sys-devel/gcc-4.3.4

Reproducible: Always

Steps to Reproduce:
emerge gcc

Actual Results:  
cp /var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../fixincludes/README-fixinc include-fixed/README                                                                          
chmod a+r include-fixed/README                                                                                                                                                        
echo timestamp > stmp-int-hdrs                                                                                                                                                        
rm -f SYSCALLS.c tmp-SYSCALLS.s                                                                                                                                                       
sed -e s/TARGET_GETGROUPS_T/gid_t/ \                                                                                                                                                  
          /var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/sys-types.h /var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/sys-protos.h > SYSCALLS.c                       
/var/tmp/portage/sys-devel/gcc-4.3.4/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.3.4/work/build/./gcc/ -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include -isystem /usr/i686-pc-linux-gnu/sys-include -O2 -g -march=prescott -O2 -pipe   -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wno-strict-prototypes -Wno-error -isystem ./include  -I. -I. -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libcpp/include  -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libdecnumber -I/var/tmp/portage/sys-devel/gcc-4.3.4/work/gcc-4.3.4/gcc/../libdecnumber/bid -I../libdecnumber    \              
          -aux-info SYSCALLS.c.X -S -o tmp-SYSCALLS.s SYSCALLS.c                                                                                                                      
cc1: internal compiler error: Illegal instruction                                                                                                                                     
Please submit a full bug report,                                                                                                                                                      
with preprocessed source if appropriate.                                                                                                                                              
See <http://bugs.gentoo.org/> for instructions.                                                                                                                                       
make[3]: *** [SYSCALLS.c.X] Error 1                                                                                                                                                   
rm gcc.pod                                                                                                                                                                            
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build/gcc'                                                                                                      
make[2]: *** [all-stage2-gcc] Error 2                                                                                                                                                 
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build'                                                                                                          
make[1]: *** [stage2-bubble] Error 2                                                                                                                                                  
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.3.4/work/build'                                                                                                          
make: *** [bootstrap-lean] Error 2
 *
 * ERROR: sys-devel/gcc-4.3.4 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4884:  Called toolchain_src_compile
 *             environment, line 5446:  Called gcc_src_compile
 *             environment, line 3087:  Called gcc_do_make
 *             environment, line 2877:  Called die
 * The specific snippet of code:
 *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
 *  The die message:
 *   emake failed with bootstrap-lean
 *
 * 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/sys-devel/gcc-4.3.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.3.4/temp/environment'.
 *



Portage 2.1.6.13 (hardened/linux/x86/10.0, gcc-3.4.6, glibc-2.9_p20081201-r2, 2.6.28-hardened-r9 i686)             
=================================================================                                                  
System uname: Linux-2.6.28-hardened-r9-i686-Intel-R-_Celeron-R-_CPU_1.70GHz-with-gentoo-1.12.11.1                  
Timestamp of tree: Wed, 23 Dec 2009 08:00:15 +0000                                                                 
app-shells/bash:     4.0_p35                                                                                       
dev-lang/python:     2.5.4-r3, 2.6.4
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:    1.6-r2
sys-devel/autoconf:  2.63-r1
sys-devel/automake:  1.5, 1.7.9-r1, 1.9.6-r2, 1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6b
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib/fax /var/spool/fax/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles"
LANG="en_en"
LC_ALL=""
LDFLAGS="-Wl,-O1"
LINGUAS="ru en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage/layman/voip"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="acl bash-completion berkdb bzip2 cli cracklib crypt cups cxx dri gdbm hardened iconv logrotate modules mudflap ncurses nls nptl nptlonly openmp pam pcre perl pic pppd python readline reflection session spl ssl sysfs syslog tcpd threads unicode urandom x86 zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1        emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m     maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ru en" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 intel        mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage      siliconmotion sis sisusb tdfx tga trident tseng v4l vesa via vmware   voodoo"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 1 Sergey Klyaznik 2009-12-28 13:19:37 UTC
Created attachment 214380 [details]
build.log and additional log files
Comment 2 Patrick Lauer gentoo-dev 2009-12-28 21:08:30 UTC
Illegal instruction usually means you built code for a CPU that has more features than the one the code runs on - are you sure that Celery is a prescott-compatible CPU?
Comment 3 Sergey Klyaznik 2009-12-29 06:20:53 UTC
(In reply to comment #2)
> Illegal instruction usually means you built code for a CPU that has more
> features than the one the code runs on - are you sure that Celery is a
> prescott-compatible CPU?
> 

You are right, Thank you.