Jarry wrote:
> So now (I hope!) my system is in consistent state, as it was
> before my little "experiment"
Well, you have had a kernel oops, and it looks like you may have had
another (the emerge of gcc that did nothing for 4 hours), so...
something doesn't seem quite right. Keep watching you
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 /et
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
>
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-
Jarry wrote:
> Rumen Yotov wrote:
> > switch to vanilla. Hope your toolchain isn't recompiled too.
>
> All I know is that I'm pretty stuck: with those hardened flags or
> without them, I can not fix my system...
You have tried switching to the vanilla compiler? (gcc-config 5, in
your case) Have
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 w
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
On Wed, 2006-02-15 at 20:16 +0100, Jarry wrote:
> Jarry wrote:
>
> > 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 fau
Jarry wrote:
> 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:
> __
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-de
10 matches
Mail list logo
