Re: [gentoo-user] gcc update failed...

2009-07-07 Thread Jarry 

W.Kenworthy wrote:


Try MAKEOPTS=-j1 - the default is still j2 if you just delete the
variable.

Ive also seen this a lot recently.  Serialising the make process into
one thread helps.


I do not know if -j2 is default, but I just tested it once again:
with -j2 gcc compilation failed. When I commented it in make.conf
out (did not explicitelly define -j1), compilation works. That is
very strange...

I compilled gcc many times, even this version (4.3.2-r3).
The only difference is, gcc wants to be re-compilled with
nptl flag now (that's why portage wants to update gcc).
Could nptl cause this problem?

Jarry

--
___
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Volker Armin Hemmann 
On Montag 06 Juli 2009, Jarry wrote:
 Hi,
 I just tried to update gcc (actually, it is just recompiling with
 new nptl flag), but it failed with this messages:
 __

   Failed to emerge sys-devel/gcc-4.3.2-r3, Log file:
  
'/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'

   * Messages for package sys-devel/gcc-4.3.2-r3:

   *
   * ERROR: sys-devel/gcc-4.3.2-r3 failed.
   * Call stack:
   *   ebuild.sh, line   49:  Called src_compile
   * environment, line 4870:  Called toolchain_src_compile
   * environment, line 5396:  Called gcc_src_compile
   * environment, line 3094:  Called gcc_do_make
   * environment, line 2884:  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.2-r3/temp/build.log'.
   * The ebuild environment file is located at
 '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'.
 __

 What does it mean, and how can I fix it???

 Jarry

that means that you forgot to copy the important part. You just copied the 
pretty useless vanilla portage error. Not the real error some lines above that 
one.

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Dale 
Volker Armin Hemmann wrote:
 On Montag 06 Juli 2009, Jarry wrote:
   
 Hi,
 I just tried to update gcc (actually, it is just recompiling with
 new nptl flag), but it failed with this messages:
 __

   Failed to emerge sys-devel/gcc-4.3.2-r3, Log file:
  
'/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'

   * Messages for package sys-devel/gcc-4.3.2-r3:

   *
   * ERROR: sys-devel/gcc-4.3.2-r3 failed.
   * Call stack:
   *   ebuild.sh, line   49:  Called src_compile
   * environment, line 4870:  Called toolchain_src_compile
   * environment, line 5396:  Called gcc_src_compile
   * environment, line 3094:  Called gcc_do_make
   * environment, line 2884:  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.2-r3/temp/build.log'.
   * The ebuild environment file is located at
 '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'.
 __

 What does it mean, and how can I fix it???

 Jarry
 

 that means that you forgot to copy the important part. You just copied the 
 pretty useless vanilla portage error. Not the real error some lines above 
 that 
 one.


   

And based on a little searching, you may want to post emerge --info as
well.  There appears to be a version of kernel that doesn't like this
gcc version.  Note the word appears. 

Dale

:-)  :-)

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Jarry 

Volker Armin Hemmann wrote:

On Montag 06 Juli 2009, Jarry wrote:

I just tried to update gcc (actually, it is just recompiling with
new nptl flag), but it failed with this messages:
__

  Failed to emerge sys-devel/gcc-4.3.2-r3, Log file:
 
   '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'

  * Messages for package sys-devel/gcc-4.3.2-r3:
  *
  * ERROR: sys-devel/gcc-4.3.2-r3 failed.
  * Call stack:
  *   ebuild.sh, line   49:  Called src_compile
  * environment, line 4870:  Called toolchain_src_compile
  * environment, line 5396:  Called gcc_src_compile
  * environment, line 3094:  Called gcc_do_make
  * environment, line 2884:  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.2-r3/temp/build.log'.
  * The ebuild environment file is located at
'/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'.
__

What does it mean, and how can I fix it???

Jarry


that means that you forgot to copy the important part. You just copied the 
pretty useless vanilla portage error. Not the real error some lines above that 
one.




I do not know how much to include, but above this, everything seemed
to be ok to me:
_
-Wno-overlength-strings-DHAVE_CONFIG_H -I. -I. 
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc 
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/. 
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/ 

../include 
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libcp 

p/include 
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libde 

cnumber 
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libdecnu 


  mber/bid -I../libdecnumberinsn-recog.c -o insn-recog.o
{standard input}: Assembler messages:
{standard input}:36051: Warning: end of file not at end of a line; 
newline inserted

{standard input}:37071: Error: bad register name `%e'
xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://bugs.gentoo.org/ for instructions.
make[3]: *** [insn-attrtab.o] Error 1
make[3]: *** Waiting for unfinished jobs
rm gcc.pod gfortran.pod
make[3]: Leaving directory 
`/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build/gcc'

make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory 
`/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build'

make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory 
`/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build'

make: *** [bootstrap-lean] Error 2
...

emerge --info
Portage 2.2_rc33 (default/linux/amd64/2008.0, gcc-4.3.2, 
glibc-2.9_p20081201-r2, 2.6.22-vs2.2.0.7-gentoo x86_64)

=
System uname: 
Linux-2.6.22-vs2.2.0.7-gentoo-x86_64-AMD_Athlon-tm-_64_X2_Dual_Core_Processor_4800+-with-glibc2.2.5

Timestamp of tree: Mon, 06 Jul 2009 17:00:01 +
app-shells/bash: 3.2_p39
dev-lang/python: 2.5.4-r3
sys-apps/baselayout: 2.0.0
sys-apps/openrc: 0.4.3-r2
sys-apps/sandbox:1.6-r2
sys-devel/autoconf:  2.63
sys-devel/automake:  1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS=amd64
CBUILD=x86_64-pc-linux-gnu
CFLAGS=-march=athlon64 -O2 -pipe
CHOST=x86_64-pc-linux-gnu
CONFIG_PROTECT=/etc /var/bind
CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/gconf 
/etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo 
/etc/udev/rules.d

CXXFLAGS=-march=athlon64 -O2 -pipe
DISTDIR=/usr/portage/distfiles
FEATURES=distlocks fixpackages parallel-fetch preserve-libs 
protect-owned sandbox sfperms strict unmerge-orphans userfetch
GENTOO_MIRRORS=http://distfiles.gentoo.org 
http://distro.ibiblio.org/pub/linux/distributions/gentoo;

LDFLAGS=-Wl,-O1
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
SYNC=rsync://rsync.gentoo.org/gentoo-portage
USE=3dnow acl amd64 berkdb bzip2 cli cracklib crypt cups dri fortran 
gdbm iconv idn ipv6 isdnlog midi mmx mudflap multilib ncurses nls nptl 
nptlonly openmp pam pcre perl pppd python readline reflection session 
spl sse sse2 ssl sysfs tcpd unicode urandom xorg zlib 
ALSA_CARDS=ali5451 als4000 atiixp atiixp-modem bt87x ca0106

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Volker Armin Hemmann 
On Montag 06 Juli 2009, Jarry wrote:
 Volker Armin Hemmann wrote:
  On Montag 06 Juli 2009, Jarry wrote:
  I just tried to update gcc (actually, it is just recompiling with
  new nptl flag), but it failed with this messages:
  __
 
Failed to emerge sys-devel/gcc-4.3.2-r3, Log file:
   
 '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'
 
* Messages for package sys-devel/gcc-4.3.2-r3:
*
* ERROR: sys-devel/gcc-4.3.2-r3 failed.
* Call stack:
*   ebuild.sh, line   49:  Called src_compile
* environment, line 4870:  Called toolchain_src_compile
* environment, line 5396:  Called gcc_src_compile
* environment, line 3094:  Called gcc_do_make
* environment, line 2884:  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.2-r3/temp/build.log'.
* The ebuild environment file is located at
  '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'.
  __
 
  What does it mean, and how can I fix it???
 
  Jarry
 
  that means that you forgot to copy the important part. You just copied
  the pretty useless vanilla portage error. Not the real error some lines
  above that one.

 I do not know how much to include, but above this, everything seemed
 to be ok to me:
 _
  -Wno-overlength-strings-DHAVE_CONFIG_H -I. -I.
 -I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc
 -I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/.
 -I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/

 ../include
 -I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libcp

  p/include
 -I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libde

  cnumber
 -I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libdecnu

mber/bid -I../libdecnumberinsn-recog.c -o insn-recog.o
 {standard input}: Assembler messages:
 {standard input}:36051: Warning: end of file not at end of a line;
 newline inserted
 {standard input}:37071: Error: bad register name `%e'
 xgcc: Internal error: Killed (program cc1)
 Please submit a full bug report.
 See http://bugs.gentoo.org/ for instructions.
 make[3]: *** [insn-attrtab.o] Error 1
 make[3]: *** Waiting for unfinished jobs
 rm gcc.pod gfortran.pod
 make[3]: Leaving directory
 `/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build/gcc'
 make[2]: *** [all-stage2-gcc] Error 2
 make[2]: Leaving directory
 `/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build'
 make[1]: *** [stage2-bubble] Error 2
 make[1]: Leaving directory
 `/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build'
 make: *** [bootstrap-lean] Error 2
 ...
 
 emerge --info
 Portage 2.2_rc33 (default/linux/amd64/2008.0, gcc-4.3.2,
 glibc-2.9_p20081201-r2, 2.6.22-vs2.2.0.7-gentoo x86_64)
 =
 System uname:
 Linux-2.6.22-vs2.2.0.7-gentoo-x86_64-AMD_Athlon-tm-_64_X2_Dual_Core_Process
or_4800+-with-glibc2.2.5 Timestamp of tree: Mon, 06 Jul 2009 17:00:01 +
 app-shells/bash: 3.2_p39
 dev-lang/python: 2.5.4-r3
 sys-apps/baselayout: 2.0.0
 sys-apps/openrc: 0.4.3-r2
 sys-apps/sandbox:1.6-r2
 sys-devel/autoconf:  2.63
 sys-devel/automake:  1.10.2
 sys-devel/binutils:  2.18-r3
 sys-devel/gcc-config: 1.4.1
 sys-devel/libtool:   1.5.26
 virtual/os-headers:  2.6.27-r2
 ACCEPT_KEYWORDS=amd64
 CBUILD=x86_64-pc-linux-gnu
 CFLAGS=-march=athlon64 -O2 -pipe
 CHOST=x86_64-pc-linux-gnu
 CONFIG_PROTECT=/etc /var/bind
 CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/gconf
 /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo
 /etc/udev/rules.d
 CXXFLAGS=-march=athlon64 -O2 -pipe
 DISTDIR=/usr/portage/distfiles
 FEATURES=distlocks fixpackages parallel-fetch preserve-libs
 protect-owned sandbox sfperms strict unmerge-orphans userfetch
 GENTOO_MIRRORS=http://distfiles.gentoo.org
 http://distro.ibiblio.org/pub/linux/distributions/gentoo;
 LDFLAGS=-Wl,-O1
 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
 SYNC=rsync://rsync.gentoo.org/gentoo-portage
 USE=3dnow acl amd64 berkdb bzip2 cli cracklib crypt cups dri fortran
 gdbm iconv idn ipv6 isdnlog midi mmx mudflap multilib ncurses nls nptl
 nptlonly openmp pam pcre perl

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Jarry 

Volker Armin Hemmann wrote:

On Montag 06 Juli 2009, Jarry wrote:

Volker Armin Hemmann wrote:

On Montag 06 Juli 2009, Jarry wrote:

I just tried to update gcc (actually, it is just recompiling with
new nptl flag), but it failed with this messages:
__

  Failed to emerge sys-devel/gcc-4.3.2-r3, Log file:
 
   '/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/build.log'

  * Messages for package sys-devel/gcc-4.3.2-r3:
  *
  * ERROR: sys-devel/gcc-4.3.2-r3 failed.
  * Call stack:
  *   ebuild.sh, line   49:  Called src_compile
  * environment, line 4870:  Called toolchain_src_compile
  * environment, line 5396:  Called gcc_src_compile
  * environment, line 3094:  Called gcc_do_make
  * environment, line 2884:  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.2-r3/temp/build.log'.
  * The ebuild environment file is located at
'/var/tmp/portage/sys-devel/gcc-4.3.2-r3/temp/environment'.
__

What does it mean, and how can I fix it???

Jarry

that means that you forgot to copy the important part. You just copied
the pretty useless vanilla portage error. Not the real error some lines
above that one.

I do not know how much to include, but above this, everything seemed
to be ok to me:
_
 -Wno-overlength-strings-DHAVE_CONFIG_H -I. -I.
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/.
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/

../include
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libcp

 p/include
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libde

 cnumber
-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libdecnu

   mber/bid -I../libdecnumberinsn-recog.c -o insn-recog.o
{standard input}: Assembler messages:
{standard input}:36051: Warning: end of file not at end of a line;
newline inserted
{standard input}:37071: Error: bad register name `%e'
xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://bugs.gentoo.org/ for instructions.
make[3]: *** [insn-attrtab.o] Error 1
make[3]: *** Waiting for unfinished jobs
rm gcc.pod gfortran.pod
make[3]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/build'
make: *** [bootstrap-lean] Error 2
...

emerge --info
Portage 2.2_rc33 (default/linux/amd64/2008.0, gcc-4.3.2,
glibc-2.9_p20081201-r2, 2.6.22-vs2.2.0.7-gentoo x86_64)
=
System uname:
Linux-2.6.22-vs2.2.0.7-gentoo-x86_64-AMD_Athlon-tm-_64_X2_Dual_Core_Process
or_4800+-with-glibc2.2.5 Timestamp of tree: Mon, 06 Jul 2009 17:00:01 +
app-shells/bash: 3.2_p39
dev-lang/python: 2.5.4-r3
sys-apps/baselayout: 2.0.0
sys-apps/openrc: 0.4.3-r2
sys-apps/sandbox:1.6-r2
sys-devel/autoconf:  2.63
sys-devel/automake:  1.10.2
sys-devel/binutils:  2.18-r3
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   1.5.26
virtual/os-headers:  2.6.27-r2
ACCEPT_KEYWORDS=amd64
CBUILD=x86_64-pc-linux-gnu
CFLAGS=-march=athlon64 -O2 -pipe
CHOST=x86_64-pc-linux-gnu
CONFIG_PROTECT=/etc /var/bind
CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/gconf
/etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo
/etc/udev/rules.d
CXXFLAGS=-march=athlon64 -O2 -pipe
DISTDIR=/usr/portage/distfiles
FEATURES=distlocks fixpackages parallel-fetch preserve-libs
protect-owned sandbox sfperms strict unmerge-orphans userfetch
GENTOO_MIRRORS=http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo;
LDFLAGS=-Wl,-O1
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
SYNC=rsync://rsync.gentoo.org/gentoo-portage
USE=3dnow acl amd64 berkdb bzip2 cli cracklib crypt cups dri fortran
gdbm iconv idn ipv6 isdnlog midi mmx mudflap multilib ncurses nls nptl
nptlonly openmp pam pcre perl pppd python readline reflection session
spl sse sse2 ssl sysfs tcpd unicode urandom xorg zlib
ALSA_CARDS=ali5451 als4000

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Mike Edenfield 

On 7/6/2009 2:23 PM, Jarry wrote:


-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libdecnu
mber/bid -I../libdecnumber insn-recog.c -o insn-recog.o
{standard input}: Assembler messages:
{standard input}:36051: Warning: end of file not at end of a line;
newline inserted
{standard input}:37071: Error: bad register name `%e'
xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://bugs.gentoo.org/ for instructions.
make[3]: *** [insn-attrtab.o] Error 1



MAKEOPTS=-j2


Can you try this again without -j2 in the make opts?  The gcc build 
process is enough of a pain to debug when you can see output 
sequentially, running parallel makes makes it worse.


In your case, it failed trying to assemble insn-attrtab.o but the last 
output on screen was from insn-recog.c on a different make branch.  It 
appears that the build process generated an incomplete insn-attrtab.c 
file which cut off in the middle of an opcode, most likely in the middle 
of a register name like %eax.  Its possible that there was another error 
buried up further in the output that got lost in the parallelizing.


--Mike

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Jarry 

Mike Edenfield wrote:

On 7/6/2009 2:23 PM, Jarry wrote:


-I/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/gcc/../libdecnu
mber/bid -I../libdecnumber insn-recog.c -o insn-recog.o
{standard input}: Assembler messages:
{standard input}:36051: Warning: end of file not at end of a line;
newline inserted
{standard input}:37071: Error: bad register name `%e'
xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://bugs.gentoo.org/ for instructions.
make[3]: *** [insn-attrtab.o] Error 1



MAKEOPTS=-j2


Can you try this again without -j2 in the make opts?  The gcc build 
process is enough of a pain to debug when you can see output 
sequentially, running parallel makes makes it worse.


In your case, it failed trying to assemble insn-attrtab.o but the last 
output on screen was from insn-recog.c on a different make branch.  It 
appears that the build process generated an incomplete insn-attrtab.c 
file which cut off in the middle of an opcode, most likely in the middle 
of a register name like %eax.  Its possible that there was another error 
buried up further in the output that got lost in the parallelizing.


Now this is strange: I commented out that MAKEOPTS=-j2 in make.conf
and gcc compilled without any complaint. I did not change anything
else! Can't believe this. I will check it tomorrow again, with -j2
and without...

Jarry

--
___
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread Mike Edenfield 

On 7/6/2009 4:23 PM, Jarry wrote:

Mike Edenfield wrote:

On 7/6/2009 2:23 PM, Jarry wrote:



MAKEOPTS=-j2



Can you try this again without -j2 in the make opts? The gcc build
process is enough of a pain to debug when you can see output
sequentially, running parallel makes makes it worse.



Now this is strange: I commented out that MAKEOPTS=-j2 in make.conf
and gcc compilled without any complaint. I did not change anything
else! Can't believe this. I will check it tomorrow again, with -j2
and without...


I can't explain why this happens but I do know that I've seen a number 
of complex builds (especially gcc/glibc) that just randomly fail when 
using a parallel make.  I see this effect on FreeBSD moreso than Gentoo, 
but I suspect that's only a question of scale.


--Mike

Re: [gentoo-user] gcc update failed...

2009-07-06 Thread W.Kenworthy 
On Mon, 2009-07-06 at 17:53 -0400, Mike Edenfield wrote:
 On 7/6/2009 4:23 PM, Jarry wrote:
  Mike Edenfield wrote:
  On 7/6/2009 2:23 PM, Jarry wrote:
 
  MAKEOPTS=-j2
 
  Can you try this again without -j2 in the make opts? The gcc build
  process is enough of a pain to debug when you can see output
  sequentially, running parallel makes makes it worse.
 
  Now this is strange: I commented out that MAKEOPTS=-j2 in make.conf
  and gcc compilled without any complaint. I did not change anything
  else! Can't believe this. I will check it tomorrow again, with -j2
  and without...
 
 I can't explain why this happens but I do know that I've seen a number 
 of complex builds (especially gcc/glibc) that just randomly fail when 
 using a parallel make.  I see this effect on FreeBSD moreso than Gentoo, 
 but I suspect that's only a question of scale.
 
 --Mike
 

Try MAKEOPTS=-j1 - the default is still j2 if you just delete the
variable.

Ive also seen this a lot recently.  Serialising the make process into
one thread helps.

BillK