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: Wed, 15 Feb 2006 23:48:42 +0200 [thread overview]
Message-ID: <1140040122.12259.14.camel@mach.qrypto.org> (raw)
In-Reply-To: <43F397DB.30100@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Hi again,
On Wed, 2006-02-15 at 22:06 +0100, Jarry wrote:
> Rumen Yotov wrote:
>
> > You shouldn't have used "hardened" unless you running a hardened system.
>
> Now I know, but I think it is too late. I wanted to switch to hardened,
> so I thought I have to add those flag first, and update the whole system.
> I did not thought it would end by reinstalling the system again...
>
> > Check the output of: gcc-config -l (what profile is GCC using) and
>
> obelix ~ # gcc-config -l
> [1] i686-pc-linux-gnu-3.4.4 *
> [2] i686-pc-linux-gnu-3.4.4-hardenednopie
> [3] i686-pc-linux-gnu-3.4.4-hardenednopiessp
> [4] i686-pc-linux-gnu-3.4.4-hardenednossp
> [5] i686-pc-linux-gnu-3.4.4-vanilla
>
> > switch to vanilla. Hope your toolchain isn't recompiled too.
>
Now run: "gcc-config 5" and check again with gcc-config -l that vanilla
is your default gcc profile.
> All I know is that I'm pretty stuck: with those hardened flags or
> without them, I can not fix my system...
>
> Jarry
>
Next try re-emerging GCC-3.4.4.
HTH.Rumen
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3409 bytes --]
next prev parent reply other threads:[~2006-02-15 21:56 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 [this message]
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=1140040122.12259.14.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