On Sunday 29 January 2006 20:37, Sven Köhler wrote:
You say, that it's the intended behaviour, that bootstrap.sh keeps the
crippled gcc 3.3 intact and as the default compiler.
ive chatted with wolf and the real fix here is to change the 'emerge
clean' at the end of bootstrap.sh into an
I also noticed the --oneshot fix.
i noted this already elsewhere in the thread
dont you read all of the e-mails !?
???
I just wanted to say Thank you for both fixes.
signature.asc
Description: OpenPGP digital signature
On Sunday 29 January 2006 20:50, Sven Köhler wrote:
I also noticed the --oneshot fix.
i noted this already elsewhere in the thread
dont you read all of the e-mails !?
???
I just wanted to say Thank you for both fixes.
sorry i forgot the /joke
-mike
--
gentoo-dev@gentoo.org mailing
On Thursday 26 January 2006 03:40, Sven Köhler wrote:
Seems like a bit ranting to me. Why do you use unsupported installation
method if you want it simple?
I don't know about Sven, but the reasons I prefer the unsupported
installation method is all outlined here:
I have no clue, what
On Thu, 2006-01-26 at 03:40 +0100, Sven Köhler wrote:
Pretty much work for a beginnner!
...and?
You're using a source-based distribution. It is not designed for the
beginner insomuch as you have to perform maintenance tasks that would
otherwise be unnecessary in a binary-only distribution.
On Thu, 2006-01-26 at 14:54 +0100, Sven Köhler wrote:
I think that i clearly explained several times, that bootstrap.sh
installs gcc 3.4 _without_ removing the crippled gcc 3.3 that came with
stage1.
You are absolutely correct. We will need to investigate the best
solution for this. The
On Thursday 26 January 2006 00:14, Homer Parker spammed:
On Wed, 2006-01-25 at 21:06 -0600, Mikey wrote:
Solutions?
And how many have you tested and submitted patches for? Instead of just
complaining, be proactive and help with the problem you perceive is
there. If it's a viable
On Thursday 26 January 2006 08:54, Sven Köhler wrote:
Mike Frysinger is talking about choice and ignores me if i tell him,
that the emerge -e system uses the crippled gcc 3.3 for the first 10
packages until emerge -e system finally rebuilds gcc 3.3 (only due to
some sideeffects!!! namely the
On Thursday 26 January 2006 08:12, Chris Gianelloni spammed:
Something else that *everybody* seems to be missing is that the *first*
method in the GCC upgrading guide, which is the one that would apply
from a fresh-installed system, seems to be completely overlooked by all
the naysayers.
Mike Frysinger is talking about choice and ignores me if i tell him,
that the emerge -e system uses the crippled gcc 3.3 for the first 10
packages until emerge -e system finally rebuilds gcc 3.3 (only due to
some sideeffects!!! namely the dependy of gcc 3.4 on libstdc++-v3 OR gcc
3.3).
i
On Thursday 26 January 2006 13:23, Sven Köhler wrote:
Mike Frysinger is talking about choice and ignores me if i tell him,
that the emerge -e system uses the crippled gcc 3.3 for the first 10
packages until emerge -e system finally rebuilds gcc 3.3 (only due to
some sideeffects!!! namely
On Thursday 26 January 2006 13:23, Sven Köhler wrote:
You say, that it's the intended behaviour, that bootstrap.sh keeps the
crippled gcc 3.3 intact and as the default compiler.
ok, i looked into this some more and ran some tests ...
long and short of it is that the behavior i discussed before
On Wed, 2006-01-25 at 22:09 +0100, Sven Köhler wrote:
I'd like to see, that bootstrap.sh unmerges any old gcc
(emerge -C \${gcc package that we just compiled})
so that a clean system is built with gcc 3.4 only!
Nope. We don't want to remove that choice from the user. We are
working
Sven Köhler wrote:
That's not a problem for me. So excuse me that i wanted
gentoo-installation to be more simple.
Seems like a bit ranting to me. Why do you use unsupported installation
method if you want it simple?
Cheers,
-jkt
--
cd /local/pub more beer /dev/mouth
signature.asc
On Wed, 2006-01-25 at 23:27 +0100, Sven Köhler wrote:
IMHO, i would expect that /usr/portage/scripts/bootstrap.sh; emerge -e
system results in a system, that has a certain integrity with a
minimum of manual steps. (gentoo install being as easy as possible)
That has never been the case. The
On Wednesday 25 January 2006 21:40, Sven Köhler wrote:
I expected the result of these steps to be a clean system.
What do i mean with a clean system?
Actually i thought, that i mean the result of a emerge -e system - but
i know now, that this is not what i mean. For example emerge -e system
On Wed, 2006-01-25 at 21:06 -0600, Mikey wrote:
Solutions?
And how many have you tested and submitted patches for? Instead of just
complaining, be proactive and help with the problem you perceive is
there. If it's a viable solution, it'll probably be at least discussed.
Then there's a
17 matches
Mail list logo
