On Thu, 2006-01-26 at 16:55 -0600, MIkey wrote:
> Jan Kundrát wrote:
>
> > Those are bugs against the revdep-rebuild package.
>
> Which is one of the suggested methods to migrate gcc. Not necessary from
> stage1...
How does the listing of revdep-rebuild bugs have anything to do with
this topic?
On Wednesday 25 January 2006 15:44, Sven Köhler wrote:
> >> I'd like to see, that bootstrap.sh unmerges any old gcc
> >> (emerge -C \<${gcc package that we just compiled})
> >
> > that's a bad idea imo
> > let the user decide which gcc they wish to have
>
> So i understand what you're trying to tel
>> I'd like to see, that bootstrap.sh unmerges any old gcc
>> (emerge -C \<${gcc package that we just compiled})
>
> that's a bad idea imo
> let the user decide which gcc they wish to have
So i understand what you're trying to tell me, but bootstrap.sh makes
the choice already:
bootstrap.sh only
On Wednesday 25 January 2006 11:38, Marius Mauch wrote:
> On Wed, 25 Jan 2006 17:23:20 +0100
> Sven Köhler <[EMAIL PROTECTED]> wrote:
> > >> I'd like to see, that bootstrap.sh unmerges any old gcc
> > >> (emerge -C \<${gcc package that we just compiled})
> > >
> > > that's a bad idea imo
> > >
> >
On Wednesday 25 January 2006 10:38, Marius Mauch spammed:
> that sounds rather unlikely, if gcc-3.4 was installed `emerge -e system`
> would have rebuilt it, not the 3.3 version (unless there is a dep on
> <3.4 in system).
Does this have something to do with it?
gcc-3.4.4-r1.ebuild:
PDEPEND="||
On Wed, 25 Jan 2006 17:23:20 +0100
Sven Köhler <[EMAIL PROTECTED]> wrote:
> >> I'd like to see, that bootstrap.sh unmerges any old gcc
> >> (emerge -C \<${gcc package that we just compiled})
> >
> > that's a bad idea imo
> >
> > let the user decide which gcc they wish to have
>
> But doesn't bo
>> I'd like to see, that bootstrap.sh unmerges any old gcc
>> (emerge -C \<${gcc package that we just compiled})
>
> that's a bad idea imo
>
> let the user decide which gcc they wish to have
But doesn't bootstrap.sh rebuild gcc? I have to take a look again, but i
think bootstrap.sh rebuilt gcc 3
On Wed, 2006-01-25 at 13:30 +0100, Sven Köhler wrote:
> Hi,
>
> bootstrap.sh installs gcc 3.4! So far so good, but gcc 3.3 is not
> unmerged. The consequence is, that "emerge -e system" installs gcc 3.4
> and then afterwards gcc 3.3 instead of libstdc++-v3.
>
> I'd like to see, that bootstrap.sh
On Wednesday 25 January 2006 07:30, Sven Köhler wrote:
> I'd like to see, that bootstrap.sh unmerges any old gcc
> (emerge -C \<${gcc package that we just compiled})
that's a bad idea imo
let the user decide which gcc they wish to have
> so that a clean system is built with gcc 3.4 only!
it wou
Hi,
bootstrap.sh installs gcc 3.4! So far so good, but gcc 3.3 is not
unmerged. The consequence is, that "emerge -e system" installs gcc 3.4
and then afterwards gcc 3.3 instead of libstdc++-v3.
I'd like to see, that bootstrap.sh unmerges any old gcc
(emerge -C \<${gcc package that we just compile
10 matches
Mail list logo
