I see the confusion, Jonas. You started from stage 1 but the directions you followed at this step were for installing from stage 2:
<quote from="http://www.gentoo.org/doc/en/gentoo-x86-install.xml#doc_chap12";> The stage2 tarball already has the bootstrapping done for you. All that you have to do is install the rest of the system: Note: If you are starting from a pre-built stage2 and want to ensure that your compiler toolchain is fully up-to-date, add the -u option to the commands below. If you don't know what this means, it's safe to skip this suggestion. </quote> This only applies if you are starting from stage 2 which includes an entirely prebuilt gentoo build environment. At this stage, since stage 2 contains things prebuilt and thus could have older, buggy code in it, you are given the ability to update what it had already built. Since you are starting from a stage 1 build, the build environment is still uninstalled...so there is nothing to update. Reading the instructions a little more closely would have prevented this. :-) Maybe the install guide should make it a bit more plain by saying that the note is only for stage2 installs. The update portage that you are seeing is nothing to worry about. You can do that *after* you build the system. The final portage that will be on your system isn't even built yet so there is no need to worry about the update to portage. The install step *really* should be followed as a recipe and doing everything exactly as it says. Good luck! :-) --Jason On Thu, 2003-11-20 at 10:47, Jonas Widarsson wrote: > OOOh! > Interresting. > What you suggest is actually in the installation guide here: > http://www.gentoo.org/doc/en/gentoo-x86-install.xml#doc_chap12 > > But if what you are suggesting is the solution, it tells me there is a > "bug" in the guide. > Because when "emerge sync" is done, the system suggests I should "update > portage". > I read this: > http://www.gentoo.org/doc/en/portage-user.xml > ...which told me to do the "emerge -u system". > If it is not the preferred procedure to do that at that moment, > there should be a "red" note in the guide saying "don't do that right now." > Put it in the end of this chapter, I think: > http://www.gentoo.org/doc/en/gentoo-x86-install.xml#doc_chap9 > > The bootstrap process is not finished, so I can't really verify if > things work yet. > > I'll be ba-ack. > Jonas > > Jason A. Pfeil wrote: > > >Hold the phone a minute. > > > >I think that we are all looking past the problem. This problem occurred > >*during* installation. Installation was not finished, so there is no > >system to *upgrade*. The system was not installed yet...so I believe > >that the correct step would be to run > > emerge -p system > >followed by > > emerge system > > > >I think that will go to the root of the problem and fix it. :-) > > > >Good Luck! > > > >--Jason > > > >On Thu, 2003-11-20 at 07:21, Jonas Widarsson wrote: > > > > > >>Jason Stubbs wrote: > >> > >> > >> > >>>On Thursday 20 November 2003 20:33, Jonas Widarsson wrote: > >>> > >>> > >>> > >>> > >>>>I'm not completely sure what emerge does, but I guess: > >>>>* searches for packages and downloads them and their dependend packages, > >>>>if they are not available locally or there is an update available on the > >>>>internet. > >>>>* compiles, builds and installs them > >>>> > >>>>So this leaves me another question. > >>>>Before "emerge -u system" i did "emerge sync". > >>>>So after "emerge gcc-config" is finished, should I have to "emerge sync" > >>>>again before I "emerge -u system"? > >>>> > >>>> > >>>> > >>>> > >>>In /usr/portage is what is known as the portage tree. It has three basic > >>>levels. > >>>- package group > >>>\- package name > >>> \- package version > >>> > >>>Each package version is defined by an ebuild that says where to download > >>>source code, how to compile and install the source code, a stability rating > >>>against various architectures and other stuff. > >>> > >>>When you run "emerge sync" it updates /usr/portage to match what is on the > >>>Gentoo servers. It is in this way that you get "notified" of all the latest > >>>packages. > >>> > >>>So, to answer your question, an "emerge sync" is probably not necessary. If > >>>"emerge -u system" still doesn't work, you can try "emerge sync; emerge > >>>gcc-config; emerge -u system" but that should only fix it if the problem was > >>>with the ebuild - which is very unlikely. > >>> > >>>Jason > >>> > >>> > >>> > >>> > >>Thanks for that reply. Nice. > >> > >># emerge sync; emerge gcc-config; emerge -u system > >>Nothing different. same error. > >> > >>Interresting though that the library version is ncurses-5.3-r2 > >>In my judgement, r2 means it is some kind of not yet stable version. > >>Is it safe to proceed with installation? > >>What can one do to correct this later? > >> > >>Of course, I'll get back to this thread if I can't (or gentoo can't) sort it out. > >> > >>I guess I'll try to proceed as if no error occured. The worst thing that can > >>happen is to start over from scratch, but I think gentoo is such a well thought of > >>distribution that you don't need to do it again when hitting errors. Fix it and > >>proceed, is what I expect it to be capable of... > >> > >>Thanks. > >> > >> > >>-- > >>[EMAIL PROTECTED] mailing list > >> > >> > > -- > [EMAIL PROTECTED] mailing list -- Jason A. Pfeil [EMAIL PROTECTED] Senior Open Systems Engineer http://www.10East.com 10East, Inc. (904)220-DOCS -- [EMAIL PROTECTED] mailing list
