From: Jarry <jarry@gmx.net>
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:54:38 +0100 [thread overview]
Message-ID: <43F4D87E.3040104@gmx.net> (raw)
In-Reply-To: <1140115383.25550.9.camel@mach.qrypto.org>
Rumen Yotov wrote:
> Have you compiled anything after compiling GCC with 'hardened'? (genlop)
Negative, only gcc, then emerge failed trying to compile 2nd package -
glibc-2.3.5-r2. I tried to go back (removed those hardened-flags), and
could not compile gcc-3.4.4
> Try with MAKEOPTS="-j1" in /etc/make.conf but not much hope.
I do not know why, but it helped! I changed it from -j2 to -j1, and
emerge gcc without any problem! Then I switched back to -j2 and updated
my whole system without a problem:
emerge --update --deep --newuse world
Thanks a lot, man!
So now (I hope!) my system is in consistent state, as it was before
my little "experiment" with "hardened" and "hardenedphp" flags.
With one exception. When I now check:
gcc-config -l
[1] i686-pc-linux-gnu-3.4.4 *
[2] i686-pc-linux-gnu-3.4.4-hardened
[3] i686-pc-linux-gnu-3.4.4-hardenednopie
[4] i686-pc-linux-gnu-3.4.4-hardenednopiessp
[5] i686-pc-linux-gnu-3.4.4-hardenednossp
Previously it was:
[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
Do I have to make worry about that missing vanilla-profile?
Jarry
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-16 20:14 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
2006-02-16 19:54 ` Jarry [this message]
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=43F4D87E.3040104@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