Re: [gentoo-alt] Mock up Linux bootstrap guide

[Matt Michalowski]

Fabian Groffen wrote:
> Hi all,
>
> Without internet I have to change my focus of development, as not
> everything is possible at the moment ;)
>
> I quickly wrote an initial version of a Linux bootstrap guide.  It isn't
> linked on the web yet, as I first would like to see some feedback on it.
> I haven't tested it yet myself either.
>
>


I've bootstrapped on a couple of various distros before (adapting the OS 
X instructions), but today I finally got around to testing the Linux 
guide on a fresh Debian Etch x86 install. Pretty smooth overall, but I 
thought I'd share some comments/opinions.

Without a C++ compiler, ncurses and Python will fail to compile during 
the bootstrap. I see a couple of potential options here:
- The "As prerequisite, you need a GCC compiler" line could clarify that 
you need both gcc and g++ from GCC.
- Code listings 1.7 & 1.13 could have USE="nocxx" emerge bash / python.
- Perhaps an instruction or (bootstrap_tree could do this) to:
  $  echo 'sys-libs/ncurses nocxx' >> $EPREFIX/etc/portage/package.use
  $  echo 'dev-lang/python nocxx' >> $EPREFIX/etc/portage/package.use
  with an instruction to clear them later.

The autoconf-2.13 ebuild has texinfo as a dependency, and will fail to 
emerge unless the system provides makeinfo. I think Code Listing 1.10 
("emerge --oneshot --nodeps texinfo") should be moved before Code 
Listing 1.8 (emerge autotools).

Similarly, the libtool ebuild calls automake-wrapper's aclocal, which in 
turn executes gawk. Hence the emerge libtool in Code Listing 1.11 
("emerge --oneshot --nodeps libtool") will fail unless the system also 
provides gawk, so perhaps Code Listing 1.15 ("emerge --oneshot gawk") 
should come before this.

So apart from these minor hiccups, all went well, great work Fabian. :)

Matt.
-- 
gentoo-alt@g.o mailing list