[gentoo-user] Problem with Emerge

[gentoo-user] Problem with Emerge

[Bill Six]

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

Hi,

3 days ago I just switched back to Gentoo after not using it for about 6
months.

However, I've been having issues emerging packages.  Frequently, the build
will crap out and I'll get something like the following.  Any idea why this
happens?

Thanks.

ake[2]: [java.stage1] Error 1 (ignored)
mv: cannot stat `objc/*.o': No such file or directory
make[2]: [objc.stage1] Error 1 (ignored)
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/genmodes.c: In function
'main':
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/genmodes.c:1255: internal
compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[2]: *** [build/genmodes.o] Error 1
make[1]: *** [stageprofile_build] Error 2
make: *** [profiledbootstrap] Error 2

!!! ERROR: sys-devel/gcc-4.1.1 failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  ebuild.sh, line 1248:   Called toolchain_src_compile
  toolchain.eclass, line 24:   Called gcc_src_compile
  toolchain.eclass, line 1529:   Called gcc_do_make
  toolchain.eclass, line 1403:   Called die

!!! emake failed with profiledbootstrap

[-- Attachment #2: Type: text/html, Size: 1548 bytes --]

[gentoo-user] Problem with Emerge

[Bill Six]

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

Hi,

3 days ago I just switched back to Gentoo after not using it for about 6
months.

However, I've been having issues emerging packages.  Frequently, the build
will crap out and I'll get something like the following.  Any idea why this
happens?

Thanks.

ake[2]: [java.stage1] Error 1 (ignored)
mv: cannot stat `objc/*.o': No such file or directory
make[2]: [objc.stage1] Error 1 (ignored)
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/genmodes.c: In function
'main':
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/genmodes.c:1255: internal
compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL: http://bugs.gentoo.org/> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[2]: *** [build/genmodes.o] Error 1
make[1]: *** [stageprofile_build] Error 2
make: *** [profiledbootstrap] Error 2

!!! ERROR: sys-devel/gcc-4.1.1 failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  ebuild.sh, line 1248:   Called toolchain_src_compile
  toolchain.eclass , line 24:   Called gcc_src_compile
  toolchain.eclass, line 1529:   Called gcc_do_make
  toolchain.eclass, line 1403:   Called die

!!! emake failed with profiledbootstrap

[-- Attachment #2: Type: text/html, Size: 1597 bytes --]

Re: [gentoo-user] Problem with Emerge

[Dale]

Bill Six wrote:
> Hi,
>
> 3 days ago I just switched back to Gentoo after not using it for about
> 6 months.
>
> However, I've been having issues emerging packages.  Frequently, the
> build will crap out and I'll get something like the following.  Any
> idea why this happens?
>
> Thanks.
>
> ake[2]: [java.stage1] Error 1 (ignored)
> mv: cannot stat `objc/*.o': No such file or directory
> make[2]: [objc.stage1] Error 1 (ignored)
> /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/genmodes.c: In function
> 'main':
> /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/gcc/genmodes.c:1255:
> internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL: http://bugs.gentoo.org/> for instructions.
> The bug is not reproducible, so it is likely a hardware or OS problem.
> make[2]: *** [build/genmodes.o] Error 1
> make[1]: *** [stageprofile_build] Error 2
> make: *** [profiledbootstrap] Error 2
>
> !!! ERROR: sys-devel/gcc-4.1.1 failed.
> Call stack:
>   ebuild.sh, line 1539:   Called dyn_compile
>   ebuild.sh, line 939:   Called src_compile
>   ebuild.sh, line 1248:   Called toolchain_src_compile
>   toolchain.eclass , line 24:   Called gcc_src_compile
>   toolchain.eclass, line 1529:   Called gcc_do_make
>   toolchain.eclass, line 1403:   Called die
>
> !!! emake failed with profiledbootstrap
>
>

What all did you upgrade before this?  Did you upgrade portage?  There
has been a lot of changes in the last six months.

Dale

:-)  :-)
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem with Emerge

[Bill Six]

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]

I wiped Ubuntu off of my machine, and installed a fresh copy of Gentoo from
the 2006.1 release.


>
>
> What all did you upgrade before this?  Did you upgrade portage?  There
> has been a lot of changes in the last six months.
>
> Dale
>
> :-)  :-)
> --
> gentoo-user@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 564 bytes --]

Re: [gentoo-user] Problem with Emerge

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 404 bytes --]

Bill Six wrote:
> Hi,
> 
> 3 days ago I just switched back to Gentoo after not using it for about 6
> months.
> 
> However, I've been having issues emerging packages.  Frequently, the
> build will crap out and I'll get something like the following.  Any idea
> why this happens?

Are they happening in unreproduceable locations? If so, see:
https://bugs.gentoo.org/20600

Thanks,
Donnie


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Problem with Emerge

[Justin Findlay]

On AD 2006 September 07 Thursday 11:11:46 PM -0400, Bill Six wrote:
>Hi,
>
>3 days ago I just switched back to Gentoo after not using it for
>about 6 months.
>
>However, I've been having issues emerging packages.  Frequently,
>the build will crap out and I'll get something like the
>following.  Any idea why this happens?

If you're getting the compiler segmentation fault on many packages at
random times you probably have bad hardware.  The causes I've seen for
this are bad or intermittently bad ram/other hardware, or hardware
failure over a certain temperature.  The first can be easily diagnosed
with memtest86+ as once the probe hits bad sectors you'll know about it.
The second is much more difficult to track down but not impossible.  If
your compiler is segfaulting once the CPU hits a certain temperature,
then you can verify this is going on by emerging a package and watching
the temperature and observe at which temperature the compiler segfaults.
Older Athlons run pretty hot.  If this is your case you may want to buy
the expensive silver heat sink compound.  As for OS problems I don't
know what to say except that this may be a sign not to run -mm or better
patch sets and expect things to be stable. (:  At least all the critical
ebuilds should filter out insanity CFLAGS.


Justin

-- 
You have 1 Moderator Point! Use it or lose it!
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Problem with Emerge

[Richard Broersma Jr]

> > 3 days ago I just switched back to Gentoo after not using it for about 6
> > months.
> > 
> > However, I've been having issues emerging packages.  Frequently, the
> > build will crap out and I'll get something like the following.  Any idea
> > why this happens?
> 
> Are they happening in unreproduceable locations? If so, see:
> https://bugs.gentoo.org/20600

I had this problem also, however I fixed by un-"over clocking" my processor.  Too much heat is not
a good thing.
-- 
gentoo-user@gentoo.org mailing list