Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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? None of those bugs are relevant to either a stage 1 install, stage 3 install, or gcc upgrade. Regards, Paul -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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 tell me, but bootstrap.sh makes
> the choice already:
> bootstrap.sh only rebuilds gcc 3.4
> (i looked that up in my emerge.log)
you're looking at bootstrap wrong ... it forces a few native packages to the
newest version available
in this case, bootstrap emerges gcc and portage picks the best one ...
gcc-3.4.4
> >> so that a clean system is built with gcc 3.4 only!
> >
> > it wouldnt anyways as the version of gcc isnt changed unless the user
> > does so
> >
> > so unless you ran `gcc-config 3.4.4`, your gcc version would still be
> > 3.3.x
>
> Right, and it will be the gcc 3.3 included in the stage1 tarball - even
> if a new gcc 3.3 version is available. So if the user wants to use gcc
> 3.3, he has to manually update gcc (for example to have features not
> included in the gcc from the stage1 tarball).
if a user wants gcc-3.3 but not gcc-3.4, then it's their responsibility to
mask it accordingly via /etc/portage
> So no matter if the user wants gcc 3.3 or gcc 3.4, the user has to do
> something manually to get a "proper" gentoo.
i dont know what you mean by "proper"
at any rate, this will all "fix" itself when 2006.0 is released
> If i may suggest something, then i would recomm that the user is abled
> to specify the gcc installed by bootstrap.sh like this:
> bootstrap.sh --gccspec "=sys-devel/gcc-3.3*"
no, use /etc/portage
-mike
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
>> 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 rebuilds gcc 3.4
(i looked that up in my emerge.log)
gcc 3.3 is only rebuild (and thereby updated) by "emerge -e system".
>> so that a clean system is built with gcc 3.4 only!
>
> it wouldnt anyways as the version of gcc isnt changed unless the user does so
>
> so unless you ran `gcc-config 3.4.4`, your gcc version would still be 3.3.x
Right, and it will be the gcc 3.3 included in the stage1 tarball - even
if a new gcc 3.3 version is available. So if the user wants to use gcc
3.3, he has to manually update gcc (for example to have features not
included in the gcc from the stage1 tarball).
For example my stage1 inclueded gcc 3.3.5* - but 3.3.6 is already stable.
So no matter if the user wants gcc 3.3 or gcc 3.4, the user has to do
something manually to get a "proper" gentoo.
If i may suggest something, then i would recomm that the user is abled
to specify the gcc installed by bootstrap.sh like this:
bootstrap.sh --gccspec "=sys-devel/gcc-3.3*"
The default should be the "newest" gcc.
In the above example, bootstrap.sh installs GCCV="sys-devel/gcc-3.3.6"
After that, bootstrap.sh could unmerge the gcc included in the stage1 by
emerge -C "<$GCCV" ">$GCCV"
Greetings
Sven
signature.asc
Description: OpenPGP digital signature
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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
> > >
> > > 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.4 only - not 3.3.
> > gcc 3.3 was only rebuilt during "emerge -e system".
>
> 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).
the -e system step probably rebuilt both
-mike
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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="|| ( app-admin/eselect-compiler sys-devel/gcc-config ) x86? ( !nocxx? ( !elibc_uclibc? ( !build? ( || ( sys-libs/libstdc++-v3 =sys-devel/gcc-3.3* ) ) ) ) )" pgpDawOTGXPwS.pgp Description: PGP signature
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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 bootstrap.sh rebuild gcc? I have to take a look again,
> but i think bootstrap.sh rebuilt gcc 3.4 only - not 3.3.
> gcc 3.3 was only rebuilt during "emerge -e system".
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).
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
signature.asc
Description: PGP signature
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
>> 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.4 only - not 3.3.
gcc 3.3 was only rebuilt during "emerge -e system".
signature.asc
Description: OpenPGP digital signature
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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 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 now towards the 2006.0 release, which means GCC 3.3 will not be
present in the stage1 tarball. Basically, wait for 2006.0, or follow
the standard steps to switch compilers yourself. It's not like we're
forcing you to keep both compilers. ;]
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
signature.asc
Description: This is a digitally signed message part
Re: [gentoo-dev] bootstrapping since gcc 3.4 is stable
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 wouldnt anyways as the version of gcc isnt changed unless the user does so
so unless you ran `gcc-config 3.4.4`, your gcc version would still be 3.3.x
-mike
--
gentoo-dev@gentoo.org mailing list
[gentoo-dev] bootstrapping since gcc 3.4 is stable
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 compiled})
so that a clean system is built with gcc 3.4 only!
Greetings
Sven
signature.asc
Description: OpenPGP digital signature
