* [gentoo-user] emerge of glibc and gcc fails
@ 2007-10-27 19:10 Yoav Luft
2007-10-28 4:04 ` Yoav Luft
2007-10-28 5:32 ` Matan Peled
0 siblings, 2 replies; 8+ messages in thread
From: Yoav Luft @ 2007-10-27 19:10 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 5130 bytes --]
hello,
during an emerge -uDN process, the compilation for gcc-4.2.1 failed, as well
as for glibc, with same errors.
I have run revdep-rebuilt, and found out about a broken
libexpat.so.0thingy, which I solved following the instruction of the
gentoo irc bot.
after that, compiling gcc still fails.
insn-emit.c: In function 'gen_leave':
insn-emit.c:1123: 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]: *** [insn-emit.o] 1 הלקת
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2
/work/build/gcc'
make[1]: *** [stageprofile_build] 2 הלקת
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2
/work/build/gcc'
make: *** [profiledbootstrap] 2 הלקת
*
* ERROR: sys-devel/gcc-4.1.2 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1334: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1546: Called gcc_do_make
* toolchain.eclass, line 1420: Called die
*
* emake failed with profiledbootstrap
* 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.1.2
/temp/build.log'.
*
* Messages for package sys-devel/gcc-4.1.2:
*
* ERROR: sys-devel/gcc-4.1.2 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1334: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1546: Called gcc_do_make
* toolchain.eclass, line 1420: Called die
*
* emake failed with profiledbootstrap
* 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.1.2
/temp/build.log'.
*
the callstack for the glibc failed compile looks the same.
emerge --info
Portage 2.1.3.9 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0,
2.6.19-gentoo-r5 i586)
=================================================================
System uname: 2.6.19-gentoo-r5 i586 AMD-K6(tm) 3D processor
Timestamp of tree: Fri, 26 Oct 2007 12:20:01 +0000
app-shells/bash: 3.2_p17
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python: 2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.18-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.22-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i586-pc-linux-gnu"
CFLAGS="-O2 -march=k6-2 -pipe"
CHOST="i586-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -march=k6-2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans
userfetch"
GENTOO_MIRRORS="http://mirror.hamakor.org.il/pub/mirrors/gentoo/ "
LANG="he_IL.utf-8"
LC_ALL="he_IL.utf-8"
LINGUAS="he en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --delete-after --stats
--timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X alsa arts berkdb bidi bitmap-fonts cairo cdr cli cracklib crypt
cups dbus dri dvd dvdr eds emboss encode esd fam firefox fortran gdbm gif
gnome gpm gstreamer gtk hal iconv ipv6 isdnlog jpeg kde ldap mad midi mikmod
mmx mp3 mpeg mudflap ncurses nls nptl nptlonly nvidia ogg opengl openmp oss
pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection sdl
session spell spl ssl tcpd truetype truetype-fonts type1-fonts unicode
vorbis win32codecs x86 xml xorg xv zlib" ALSA_CARDS="ens1371"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file
hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate
route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse
joystick" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780
lb216 lcdm001 mtxorb ncurses text" LINGUAS="he en" USERLAND="GNU"
VIDEO_CARDS="vesa nvidia"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS,
PORTDIR_OVERLAY
I'm clueless about it, but do feel that not being able to updaate gcc or
glibc is bad, and will probably mean that I will not be able to update
other things as well.
[-- Attachment #2: Type: text/html, Size: 6421 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] emerge of glibc and gcc fails
2007-10-27 19:10 [gentoo-user] emerge of glibc and gcc fails Yoav Luft
@ 2007-10-28 4:04 ` Yoav Luft
2007-10-28 16:49 ` Dan Farrell
2007-10-28 5:32 ` Matan Peled
1 sibling, 1 reply; 8+ messages in thread
From: Yoav Luft @ 2007-10-28 4:04 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 5133 bytes --]
hello,
during an emerge -uDN process, the compilation for gcc-4.2.1 failed, as well
as for glibc, with same errors.
I have run revdep-rebuilt, and found out about a broken
libexpat.so.0thingy, which I solved following the instruction of the
gentoo irc bot.
after that, compiling gcc still fails.
insn-emit.c: In function 'gen_leave':
insn-emit.c:1123: 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]: *** [insn-emit.o] 1 הלקת
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc- 4.1.2
/work/build/gcc'
make[1]: *** [stageprofile_build] 2 הלקת
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2
/work/build/gcc'
make: *** [profiledbootstrap] 2 הלקת
*
* ERROR: sys-devel/gcc- 4.1.2 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1334: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1546: Called gcc_do_make
* toolchain.eclass, line 1420: Called die
*
* emake failed with profiledbootstrap
* 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.1.2
/temp/build.log'.
*
* Messages for package sys-devel/gcc-4.1.2:
*
* ERROR: sys-devel/gcc-4.1.2 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1334: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1546: Called gcc_do_make
* toolchain.eclass, line 1420: Called die
*
* emake failed with profiledbootstrap
* 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.1.2
/temp/build.log'.
*
the callstack for the glibc failed compile looks the same.
emerge --info
Portage 2.1.3.9 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.5-r0,
2.6.19-gentoo-r5 i586)
=================================================================
System uname: 2.6.19-gentoo-r5 i586 AMD-K6(tm) 3D processor
Timestamp of tree: Fri, 26 Oct 2007 12:20:01 +0000
app-shells/bash: 3.2_p17
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python: 2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.18-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.22-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i586-pc-linux-gnu"
CFLAGS="-O2 -march=k6-2 -pipe"
CHOST="i586-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -march=k6-2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans
userfetch"
GENTOO_MIRRORS=" http://mirror.hamakor.org.il/pub/mirrors/gentoo/ "
LANG="he_IL.utf-8"
LC_ALL="he_IL.utf-8"
LINGUAS="he en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --delete-after --stats
--timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X alsa arts berkdb bidi bitmap-fonts cairo cdr cli cracklib crypt
cups dbus dri dvd dvdr eds emboss encode esd fam firefox fortran gdbm gif
gnome gpm gstreamer gtk hal iconv ipv6 isdnlog jpeg kde ldap mad midi mikmod
mmx mp3 mpeg mudflap ncurses nls nptl nptlonly nvidia ogg opengl openmp oss
pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection sdl
session spell spl ssl tcpd truetype truetype-fonts type1-fonts unicode
vorbis win32codecs x86 xml xorg xv zlib" ALSA_CARDS="ens1371"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file
hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate
route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse
joystick" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780
lb216 lcdm001 mtxorb ncurses text" LINGUAS="he en" USERLAND="GNU"
VIDEO_CARDS="vesa nvidia"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS,
PORTDIR_OVERLAY
I'm clueless about it, but do feel that not being able to updaate gcc or
glibc is bad, and will probably mean that I will not be able to update
other things as well.
[-- Attachment #2: Type: text/html, Size: 6684 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge of glibc and gcc fails
2007-10-28 4:04 ` Yoav Luft
@ 2007-10-28 16:49 ` Dan Farrell
2007-10-28 17:40 ` Yoav Luft
0 siblings, 1 reply; 8+ messages in thread
From: Dan Farrell @ 2007-10-28 16:49 UTC (permalink / raw
To: gentoo-user
On Sun, 28 Oct 2007 06:04:43 +0200
"Yoav Luft" <yoav.luft@gmail.com> wrote:
> hello,
> during an emerge -uDN process, the compilation for gcc-4.2.1 failed,
> as well as for glibc, with same errors.
> I have run revdep-rebuilt, and found out about a broken
> libexpat.so.0thingy, which I solved following the instruction of the
> gentoo irc bot.
> after that, compiling gcc still fails.
>
> insn-emit.c: In function 'gen_leave':
> insn-emit.c:1123: internal compiler error: Segmentation fault
> . . .
> I'm clueless about it, but do feel that not being able to updaate gcc
> or glibc is bad, and will probably mean that I will not be able to
> update other things as well.
Have you done a memtest-86, and waited for a few days, or at least a
few error-free complete passes?
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge of glibc and gcc fails
2007-10-28 16:49 ` Dan Farrell
@ 2007-10-28 17:40 ` Yoav Luft
2007-10-28 19:35 ` Dan Farrell
0 siblings, 1 reply; 8+ messages in thread
From: Yoav Luft @ 2007-10-28 17:40 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On 10/28/07, Dan Farrell <dan@spore.ath.cx> wrote:
>
> On Sun, 28 Oct 2007 06:04:43 +0200
> "Yoav Luft" <yoav.luft@gmail.com> wrote:
>
> > hello,
> > during an emerge -uDN process, the compilation for gcc-4.2.1 failed,
> > as well as for glibc, with same errors.
> > I have run revdep-rebuilt, and found out about a broken
> > libexpat.so.0thingy, which I solved following the instruction of the
> > gentoo irc bot.
> > after that, compiling gcc still fails.
> >
> > insn-emit.c: In function 'gen_leave':
> > insn-emit.c:1123: internal compiler error: Segmentation fault
> > . . .
> > I'm clueless about it, but do feel that not being able to updaate gcc
> > or glibc is bad, and will probably mean that I will not be able to
> > update other things as well.
>
> Have you done a memtest-86, and waited for a few days, or at least a
> few error-free complete passes?
> --
> gentoo-user@gentoo.org mailing list
>
>
I have waited for a few days, and tried different versions of gcc and glibc,
all failed.
I did had an overheating problem a couple of months ago, right around the
time the problem started. So, it could be that the CPU is semi-toasted? How
do I run memtest-86? Is there anything else that's worth checking?
[-- Attachment #2: Type: text/html, Size: 1693 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge of glibc and gcc fails
2007-10-28 17:40 ` Yoav Luft
@ 2007-10-28 19:35 ` Dan Farrell
2007-11-01 18:55 ` Yoav Luft
0 siblings, 1 reply; 8+ messages in thread
From: Dan Farrell @ 2007-10-28 19:35 UTC (permalink / raw
To: gentoo-user
On Sun, 28 Oct 2007 19:40:01 +0200
"Yoav Luft" <yoav.luft@gmail.com> wrote:
> On 10/28/07, Dan Farrell <dan@spore.ath.cx> wrote:
> >
> > On Sun, 28 Oct 2007 06:04:43 +0200
> > "Yoav Luft" <yoav.luft@gmail.com> wrote:
> >
> > > hello,
> > > during an emerge -uDN process, the compilation for gcc-4.2.1
> > > failed, as well as for glibc, with same errors.
> > > I have run revdep-rebuilt, and found out about a broken
> > > libexpat.so.0thingy, which I solved following the instruction of
> > > the gentoo irc bot.
> > > after that, compiling gcc still fails.
> > >
> > > insn-emit.c: In function 'gen_leave':
> > > insn-emit.c:1123: internal compiler error: Segmentation fault
> > > . . .
> > > I'm clueless about it, but do feel that not being able to updaate
> > > gcc or glibc is bad, and will probably mean that I will not be
> > > able to update other things as well.
> >
> > Have you done a memtest-86, and waited for a few days, or at least a
> > few error-free complete passes?
> > --
> > gentoo-user@gentoo.org mailing list
> >
> >
>
> I have waited for a few days, and tried different versions of gcc and
> glibc, all failed.
did you remember to emerge --sync, maybe even emerge --metadata ?
frankly, I am not sure what the last one does, but I believe it could
update data concerning the ebuilds themselves, which could be a
potential source of problems.
> I did had an overheating problem a couple of months ago, right around
> the time the problem started. So, it could be that the CPU is
> semi-toasted? How do I run memtest-86?
there are 2 ways I know of:
1) simply reboot on a gentoo boot cd and type 'memtest' or some such
at the boot: line. (Refer to the on-disc documentation for help
concerning what exactly to type)
2) a)emerge memtest86+;
b) find memtest.bin and move it to /boot/memtest86plus
c)add a grub line that looks like this:
title=Memtest86Plus
root (hd0,1) # this refers to my boot partition. you may have
# to change this setting.
kernel /boot/memtest86plus/memtest.bin
d) reboot and use memtest from the hard drive.
If, when you emerge memtest86+, you have /boot mounted, the emerge will
plop the .bin file down right where it needs to be. If not, the output
from the emerge should giveyou the info you need.
Of course, memtest.bin doesn't have to be on your boot partition, if
grub can read the root partition. In fact, you might not even have
a /boot partition. Just make sure the root line for memtest in grub is
proper.
> Is there anything else that's
> worth checking?
You could try a CPU stress test. If the cpu isn't working properly,
using it at 100% capacity for a little while ought to make that
apparent. But your results may vary. A rudimentary query on google
points me in the direction of:
http://users.bigpond.net.au/cpuburn/
However, i don't know if it's source and if not, there's always a valid
security concern when running others' binaries. something to keep in
mind...
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge of glibc and gcc fails
2007-10-28 19:35 ` Dan Farrell
@ 2007-11-01 18:55 ` Yoav Luft
0 siblings, 0 replies; 8+ messages in thread
From: Yoav Luft @ 2007-11-01 18:55 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 3552 bytes --]
On 10/28/07, Dan Farrell <dan@spore.ath.cx> wrote:
>
> On Sun, 28 Oct 2007 19:40:01 +0200
> "Yoav Luft" <yoav.luft@gmail.com> wrote:
>
> > On 10/28/07, Dan Farrell <dan@spore.ath.cx> wrote:
> > >
> > > On Sun, 28 Oct 2007 06:04:43 +0200
> > > "Yoav Luft" <yoav.luft@gmail.com> wrote:
> > >
> > > > hello,
> > > > during an emerge -uDN process, the compilation for gcc-4.2.1
> > > > failed, as well as for glibc, with same errors.
> > > > I have run revdep-rebuilt, and found out about a broken
> > > > libexpat.so.0thingy, which I solved following the instruction of
> > > > the gentoo irc bot.
> > > > after that, compiling gcc still fails.
> > > >
> > > > insn-emit.c: In function 'gen_leave':
> > > > insn-emit.c:1123: internal compiler error: Segmentation fault
> > > > . . .
> > > > I'm clueless about it, but do feel that not being able to updaate
> > > > gcc or glibc is bad, and will probably mean that I will not be
> > > > able to update other things as well.
> > >
> > > Have you done a memtest-86, and waited for a few days, or at least a
> > > few error-free complete passes?
> > > --
> > > gentoo-user@gentoo.org mailing list
> > >
> > >
> >
> > I have waited for a few days, and tried different versions of gcc and
> > glibc, all failed.
>
> did you remember to emerge --sync, maybe even emerge --metadata ?
> frankly, I am not sure what the last one does, but I believe it could
> update data concerning the ebuilds themselves, which could be a
> potential source of problems.
>
> > I did had an overheating problem a couple of months ago, right around
> > the time the problem started. So, it could be that the CPU is
> > semi-toasted? How do I run memtest-86?
>
> there are 2 ways I know of:
> 1) simply reboot on a gentoo boot cd and type 'memtest' or some such
> at the boot: line. (Refer to the on-disc documentation for help
> concerning what exactly to type)
> 2) a)emerge memtest86+;
> b) find memtest.bin and move it to /boot/memtest86plus
> c)add a grub line that looks like this:
> title=Memtest86Plus
> root (hd0,1) # this refers to my boot partition. you may have
> # to change this setting.
> kernel /boot/memtest86plus/memtest.bin
> d) reboot and use memtest from the hard drive.
>
> If, when you emerge memtest86+, you have /boot mounted, the emerge will
> plop the .bin file down right where it needs to be. If not, the output
> from the emerge should giveyou the info you need.
>
> Of course, memtest.bin doesn't have to be on your boot partition, if
> grub can read the root partition. In fact, you might not even have
> a /boot partition. Just make sure the root line for memtest in grub is
> proper.
>
>
> > Is there anything else that's
> > worth checking?
>
> You could try a CPU stress test. If the cpu isn't working properly,
> using it at 100% capacity for a little while ought to make that
> apparent. But your results may vary. A rudimentary query on google
> points me in the direction of:
>
> http://users.bigpond.net.au/cpuburn/
>
> However, i don't know if it's source and if not, there's always a valid
> security concern when running others' binaries. something to keep in
> mind...
> --
> gentoo-user@gentoo.org mailing list
>
>
I had run memtest, and returned no errors. In all occurrences of this
problem I had emerge --sync before I updated, as I was about the update
the whole system, and eventually emerge -UD world. I would try a cpu stress,
but that would have to wait for next week. Thanks fo rthe help so far.
[-- Attachment #2: Type: text/html, Size: 4940 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge of glibc and gcc fails
2007-10-27 19:10 [gentoo-user] emerge of glibc and gcc fails Yoav Luft
2007-10-28 4:04 ` Yoav Luft
@ 2007-10-28 5:32 ` Matan Peled
1 sibling, 0 replies; 8+ messages in thread
From: Matan Peled @ 2007-10-28 5:32 UTC (permalink / raw
To: gentoo-user
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1486 bytes --]
On 27/10/2007, Yoav Luft <yoav.luft@gmail.com> wrote:
> hello,
> during an emerge -uDN process, the compilation for gcc-4.2.1 failed, as well
> as for glibc, with same errors.
> I have run revdep-rebuilt, and found out about a broken libexpat.so.0
> thingy, which I solved following the instruction of the gentoo irc bot.
> after that, compiling gcc still fails.
This has nothing to do with libexpat - this is an ICE (Internal
Compiler Error). There are two things that cause ICEs:
* Bad RAM
* Bad compilers
A bad compiler can be due to a bug in the compiler code, or excessive
CFLAGS. Your CFLAGS look fine, though. Its unlikely to be bad RAM if
it consistently fails in the same spot.
You might want to file a bug at http://bugs.gentoo.org.
Otherwise, your only option is to get a rescue compiler (I don't
remember the address by heart but I'm sure someone will mention it.
Also, Google).
> insn-emit.c: In function 'gen_leave':
> insn-emit.c:1123: 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]: *** [insn-emit.o] 1 הלקת
<snip>
> I'm clueless about it, but do feel that not being able to updaate gcc or
> glibc is bad, and will probably mean that I will not be able to update
> other things as well.
>
בהצלחה!
=)
- Matan Peled
éí¢‹¬z¸\x1ežÚ(¢¸&j)bž b²
^ permalink raw reply [flat|nested] 8+ messages in thread
[parent not found: <9iZmz-3eP-3@gated-at.bofh.it>]
* Re: [gentoo-user] emerge of glibc and gcc fails
[not found] <9iZmz-3eP-3@gated-at.bofh.it>
@ 2007-10-28 13:32 ` David W Noon
0 siblings, 0 replies; 8+ messages in thread
From: David W Noon @ 2007-10-28 13:32 UTC (permalink / raw
To: gentoo-user
On Saturday 27 Oct 2007 20:20 in article <9iZmz-3eP-3@gated-at.bofh.it>
of linux.gentoo.user, Yoav Luft(yoav.luft@gmail.com) wrote:
[snip]
> insn-emit.c:1123: 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.
[snip]
> CFLAGS="-O2 -march=k6-2 -pipe"
I had this problem with an AMD K6-III system. The MMU in the
motherboard's bus control chipset was fried. The system remains dead,
as they don't make Super Socket 7 motherboards any more.
--
Regards
Dave [RLU#314465]
======================================================
dwnoon@ntlworld.com (David W Noon)
======================================================
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2007-11-01 19:01 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-27 19:10 [gentoo-user] emerge of glibc and gcc fails Yoav Luft
2007-10-28 4:04 ` Yoav Luft
2007-10-28 16:49 ` Dan Farrell
2007-10-28 17:40 ` Yoav Luft
2007-10-28 19:35 ` Dan Farrell
2007-11-01 18:55 ` Yoav Luft
2007-10-28 5:32 ` Matan Peled
[not found] <9iZmz-3eP-3@gated-at.bofh.it>
2007-10-28 13:32 ` David W Noon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox