At Thu, 16 Jun 2005 14:44:04 -0700 Zac Medico <[EMAIL PROTECTED]> wrote:
> Allan Gottlieb wrote: >> >> /usr/bin/autoconf did not exist. Indeed as shown below a number of >> files need to be emerged. I have started the emerge and will then >> redo >> emerge --emptytree system >> >> My question now is what went wrong. That is, why didn't I have >> autoconf after the bootstrap or why didn't the >> emerge --emptytree system >> bring it in before it was needed? >> >> thanks again, >> allan >> > > Good question. My best guess is that you deviated from the handbook > or simply borked something somehow. Then again, maybe it's a bug > that can be reproduced. Anyone? I agree that it is most likely operator error. The only thing I (knowingly) did slightly different from the base install is that I am installing on a clean partition but did *not* do a mkfs. The partition to hold my new gentoo (/dev/hdc3, the only hard disk is hdc) is my current "active partition", i.e. grub is in its boot block. I wish to continue using this boot block (I dual boot windows to (shamefully) play diablo II; and have had trouble in the past with windows so try to not affect anything it its path to booting). Note that with this new installation I have *not* yet reached the point of configuring the kernel or installing grub. What I do is remove all the directories (and "hidden" files) except for boot and rename boot to boot-old. Then I bring in stage1 and unpack. When I want to reboot into my old system I move the boot from the stage1 unpack to boot-new and move boot-old to boot. I don't see how this could affect /usr/bin/autoconf but of course finger slips can occur. Anyway I will try again and will check at various points if /usr/bin/autoconf exists. Thanks again for your help. allan -- gentoo-user@gentoo.org mailing list
