Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 67141 - sys-devel/libperl-5.8.2 failed to compile due to a gcc internal error
Summary: sys-devel/libperl-5.8.2 failed to compile due to a gcc internal error
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: PPC Linux
: High blocker
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-11 12:19 UTC by Robert Sigler
Modified: 2004-12-04 01:32 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Sigler 2004-10-11 12:19:40 UTC
When trying to do the first emerge system on a stage 2 install (2004.1), sys-devel/libperl-5.8.2 fails to compile.  I get the following output:
make[2]: Entering directory `/var/tmp/portage/libperl-5.8.2/work/perl-5.8.2/x2p'
echo Makefile.SH cflags.SH | tr ' ' '\n' >.shlist
make[2]: Leaving directory `/var/tmp/portage/libperl-5.8.2/work/perl-5.8.2/x2p'
Updating makefile...
make[1]: Leaving directory `/var/tmp/portage/libperl-5.8.2/work/perl-5.8.2/x2p'
`sh  cflags "optimize='-O3 -pipe -mcpu=750'" perl.o` -fPIC perl.c
`sh  cflags "optimize='-O3 -pipe -mcpu=750'" gv.o` -fPIC gv.c
          CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -pipe -mcpu=750  -Wall
          CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -pipe -mcpu=750  -Wall
`sh  cflags "optimize='-O3 -pipe -mcpu=750'" toke.o` -fPIC toke.c
          CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -pipe -mcpu=750  -Wall
`sh  cflags "optimize='-O3 -pipe -mcpu=750'" perly.o` -fPIC perly.c
          CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -pipe -mcpu=750  -Wall
`sh  cflags "optimize='-O3 -pipe -mcpu=750'" op.o` -fPIC op.c
          CCCMD =  gcc -DPERL_CORE -c -fno-strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -pipe -mcpu=750  -Wall
gcc: Internal error: Terminated (program cc1)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
make: *** [toke.o] Error 1
make: *** Waiting for unfinished jobs....
{standard input}: Assembler messages:
{standard input}:790: Warning: partial line at end of file ignored

!!! ERROR: sys-devel/libperl-5.8.2 failed.
!!! Function src_compile, Line 208, Exitcode 2
!!! Unable to make libperl.so

I have stripped out all features from my /etc/make.conf file include all USE flags and non-essential cflags.  I am using a Mac G3.

Reproducible: Always
Steps to Reproduce:
1. PPC G3 stage 2 install (2004.1)
2. chroot into new envrionment
3. emerge sync
4. emerge system

Actual Results:  
all works well until sys-devel/libperl-5.8.2 attempts to compile.  It fails with
the results detailed in the 'details' field.

Expected Results:  
sys-devel/libperl-5.8.2 should compile sucessfully.

Portage 2.0.50-r5 (default-ppc-2004.1, gcc-3.2.3, glibc-2.3.2-r9, 2.6.5-gentoo-G4)
=================================================================
System uname: 2.6.5-gentoo-G4 ppc 0
Gentoo Base System version 1.4.3.13
Autoconf:
Automake:
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CFLAGS="-O3 -pipe -mcpu=750"
CHOST="powerpc-unknown-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache"
GENTOO_MIRRORS="http://gentoo.osuosl.org ftp://ftp.lug.ro/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="dvd f77 gif jpeg nls png ppc truetype"
Comment 1 Joe Jezak (RETIRED) gentoo-dev 2004-12-04 01:32:56 UTC
PPC's stable compiler is now GCC 3.4, if this is still a problem, please file a new bug.