From: "Bill Six" <billsix@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Problem with Emerge
Date: Thu, 7 Sep 2006 23:11:46 -0400 [thread overview]
Message-ID: <692017ac0609072011h39b594d7h933916a5e814a6a5@mail.gmail.com> (raw)
[-- 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 --]
next reply other threads:[~2006-09-08 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 3:11 Bill Six [this message]
2006-09-08 5:07 ` [gentoo-user] Problem with Emerge Justin Findlay
-- strict thread matches above, loose matches on Subject: below --
2006-09-08 2:54 Bill Six
2006-09-08 3:12 ` Dale
2006-09-08 3:36 ` Bill Six
2006-09-08 4:03 ` Donnie Berkholz
2006-09-08 5:07 ` Richard Broersma Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=692017ac0609072011h39b594d7h933916a5e814a6a5@mail.gmail.com \
--to=billsix@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox