From: Jarry <jarry@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault...
Date: Wed, 15 Feb 2006 19:36:41 +0100 [thread overview]
Message-ID: <43F374B9.20103@gmx.net> (raw)
Hi,
I changed my USE flags (added "hardened hardenedphp lm_sensors)
and tried "emerge --update --deep --newuse world". Emerge wanted
to recompile 8 packages, but crushed during the second one
(glibc) with segmentation fault:
__________________________________________________________
/work/build-default-i686-pc-linux-gnu-linuxthreads/libc.so
/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/libc_nonshared.a
collect2: ld terminated with signal 11 [Segmentation fault]
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../i686-pc-linux-gnu/bin/ld: BFD
2.16.1 assertion fail
/var/tmp/portage/binutils-2.16.1/work/binutils-2.16.1/bfd/elflink.c:2322
make[2]: ***
[/var/tmp/portage/glibc-2.3.5-r2/work/build-default-i686-pc-linux-gnu-linuxthreads/iconvdata/IBM891.so]
Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
`/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5/iconvdata'
make[1]: *** [iconvdata/others] Error 2
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.5-r2/work/glibc-2.3.5'
make: *** [all] Error 2
!!! ERROR: sys-libs/glibc-2.3.5-r2 failed.
!!! Function toolchain-glibc_src_compile, Line 226, Exitcode 2
!!! (no error message)
______________________________________________________________
How can I fix it? Which of those 3 new USE flags could cause it?
Jarry
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-02-15 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 18:36 Jarry [this message]
2006-02-15 19:16 ` [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2) Jarry
2006-02-15 19:34 ` Rumen Yotov
2006-02-15 21:06 ` Jarry
2006-02-15 21:48 ` Rumen Yotov
2006-02-16 18:25 ` Jarry
2006-02-16 18:43 ` Rumen Yotov
2006-02-16 19:54 ` Jarry
2006-02-16 20:59 ` Benno Schulenberg
2006-02-15 21:56 ` Benno Schulenberg
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=43F374B9.20103@gmx.net \
--to=jarry@gmx.net \
--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