From: Rumen Yotov <rumen@qrypto.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] updating glibc-2.3.5-r2: segmentation fault... (part 2)
Date: Thu, 16 Feb 2006 20:43:02 +0200 [thread overview]
Message-ID: <1140115383.25550.9.camel@mach.qrypto.org> (raw)
In-Reply-To: <43F4C38D.9040703@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Thu, 2006-02-16 at 19:25 +0100, Jarry wrote:
> Rumen Yotov wrote:
>
> > Now run: "gcc-config 5" and check again with gcc-config -l that vanilla
> > is your default gcc profile.
> >
> > Next try re-emerging GCC-3.4.4.
>
> I tried. Changed to vanilla, verified, started re-emerging gcc, but it
> failed without saying anything (frozen, after 4 hours of nothing-doing
> I interrupted it). Then I tried "emerge --sync", that crushed too:
>
> >>> Updating Portage cache: 52%Segmentation fault
>
> I repeated it 3x, always the same: at 52% segfault. Seems my system
> is pretty broken. I really did not know that just adding two use-flags
> (hardened hardenedphp) can be so dangerous, even on "stable-only" system.
> It seems I will spend one more nice weekend by reinstalling... :-(
>
> Jarry
>
Hi,
Have you compiled anything after compiling GCC with 'hardened'? (genlop)
Try with MAKEOPTS="-j1" in /etc/make.conf but not much hope.
Or better boot with install-CD chroot into your existing installation
and remerge GCC with sane CFLAGS. Quicker than complete reinstall.
Or check/search for a binary package for your arch & flags (not easy).
PS:first try recompiling the toolchain in that order:binutils,gcc,glibc.
HTH.Rumen
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3409 bytes --]
next prev parent reply other threads:[~2006-02-16 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 18:36 [gentoo-user] updating glibc-2.3.5-r2: segmentation fault Jarry
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 [this message]
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=1140115383.25550.9.camel@mach.qrypto.org \
--to=rumen@qrypto.org \
--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