Gentoo Archives: gentoo-user

From: Matan Peled <chaosite@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] emerge of glibc and gcc fails
Date: Sun, 28 Oct 2007 05:38:07
Message-Id: 7624268b0710272232g4b74c708pac1dd618de3168cf@mail.gmail.com
In Reply to: [gentoo-user] emerge of glibc and gcc fails by Yoav Luft
1 On 27/10/2007, Yoav Luft <yoav.luft@×××××.com> wrote:
2 > hello,
3 > during an emerge -uDN process, the compilation for gcc-4.2.1 failed, as well
4 > as for glibc, with same errors.
5 > I have run revdep-rebuilt, and found out about a broken libexpat.so.0
6 > thingy, which I solved following the instruction of the gentoo irc bot.
7 > after that, compiling gcc still fails.
8
9 This has nothing to do with libexpat - this is an ICE (Internal
10 Compiler Error). There are two things that cause ICEs:
11 * Bad RAM
12 * Bad compilers
13
14 A bad compiler can be due to a bug in the compiler code, or excessive
15 CFLAGS. Your CFLAGS look fine, though. Its unlikely to be bad RAM if
16 it consistently fails in the same spot.
17
18 You might want to file a bug at http://bugs.gentoo.org.
19
20 Otherwise, your only option is to get a rescue compiler (I don't
21 remember the address by heart but I'm sure someone will mention it.
22 Also, Google).
23
24 > insn-emit.c: In function 'gen_leave':
25 > insn-emit.c:1123: internal compiler error: Segmentation fault
26 > Please submit a full bug report,
27 > with preprocessed source if appropriate.
28 > See <URL:http://bugs.gentoo.org/> for instructions.
29 > The bug is not reproducible, so it is likely a hardware or OS problem.
30 > make[2]: *** [insn-emit.o] 1 הלקת
31 <snip>
32 > I'm clueless about it, but do feel that not being able to updaate gcc or
33 > glibc is bad, and will probably mean that I will not be able to update
34 > other things as well.
35 >
36
37
38 בהצלחה!
39
40 =)
41
42 - Matan Peled
43 éí¢‹¬z¸žÚ(¢¸&j)bž b²