On Sat, 2005-09-10 at 23:03 +0200, Volker Armin Hemmann wrote:
> On Saturday 10 September 2005 20:09, Frank Schafer wrote:
> > ... or which distribution to install during less than 4 days?
> >
> > Hi list,
> >
> > as I wrote yesterday I planned to complete installation after work
> > (started ``emerge --emptytree system'' in the morning).
> >
> 
> where did you get the idea that --emptytree is needed or even a wise decision?
> --emptytree is almost NEVER needed and since it is a troublesom procedure, it 
> should not be made, until you are totally sure, that you need it.
> 
> emerge system
> 
> is all you need to do, to get the base system.
> After that, emerge what you like to have, but NEVER use --emptytree, except 
> when you are able to deal with the consequences.
> 
> Obviously you are not, so do not do it. 
> NO
> 
> 
> was that clear enough?
> 

Yes, that WAS clear enough. So we have an even more nasty documentation
bug in the gentoo installation handbook (it tells to ``emerge
--emptytree system'') and a nasty portage (or was it bootstrap?) bug (it
tells me to be aware, that we need to add -e to emerge system now after
finishing.

> For your gcc-problem, there is the fix script, others mentioned - but a lot 
> of 
> times all that is needed is to run gcc-config to set the correct gcc.

gcc-config ran after the installation. (see in one fo my further posts,
there was the "Native compiler changed to ..." amongst the messages.

I've found (with some help of b.g.o.) that these ARE bugs. Here's the
whole success story.

scripts/bootstrap.sh
#to work around the autoconf dependency bug
emerge --oneshot --nodeps autoconf
emerge --oneshot --nodeps aotoconf-wrapper
#to work around the python-fchksum dependency bug
emerge --oneshot --nodeps python
emerge --emptytree system

No fix_libtool_files.sh necessary. Why? There never was an older version
of gcc.

Some words to the autoconf ... will start a new thread.

So much to the ability.

Frank

PS: You're a German? Probably this is the reason for your arrogance.

-- 
gentoo-user@gentoo.org mailing list

Reply via email to