Gentoo Archives: gentoo-alt

From: Fabian Groffen <grobian@g.o>
To: gentoo-alt@l.g.o
Subject: Re: [gentoo-alt] Mock up Linux bootstrap guide
Date: Sat, 01 Dec 2007 14:22:28
Message-Id: 20071201142216.GM24771@gentoo.org
In Reply to: Re: [gentoo-alt] Mock up Linux bootstrap guide by Matt Michalowski
1 On 02-10-2007 18:45:42 +1000, Matt Michalowski wrote:
2 > Without a C++ compiler, ncurses and Python will fail to compile during the
3 > bootstrap. I see a couple of potential options here:
4 > - The "As prerequisite, you need a GCC compiler" line could clarify that
5 > you need both gcc and g++ from GCC.
6
7 Added this now.
8
9 > - Code listings 1.7 & 1.13 could have USE="nocxx" emerge bash / python.
10 > - Perhaps an instruction or (bootstrap_tree could do this) to:
11 > $ echo 'sys-libs/ncurses nocxx' >> $EPREFIX/etc/portage/package.use
12 > $ echo 'dev-lang/python nocxx' >> $EPREFIX/etc/portage/package.use
13 > with an instruction to clear them later.
14
15 I prefer you to do this if you understand the implications of not having
16 a C++ compiler ;)
17
18 > The autoconf-2.13 ebuild has texinfo as a dependency, and will fail to
19 > emerge unless the system provides makeinfo. I think Code Listing 1.10
20 > ("emerge --oneshot --nodeps texinfo") should be moved before Code Listing
21 > 1.8 (emerge autotools).
22
23 I think Rabbe's patches basically changed this order.
24
25 > Similarly, the libtool ebuild calls automake-wrapper's aclocal, which in
26 > turn executes gawk. Hence the emerge libtool in Code Listing 1.11 ("emerge
27 > --oneshot --nodeps libtool") will fail unless the system also provides
28 > gawk, so perhaps Code Listing 1.15 ("emerge --oneshot gawk") should come
29 > before this.
30
31 Hmmm... a Linux system without gawk? In that case bootstrap gawk
32 first...
33
34 > So apart from these minor hiccups, all went well, great work Fabian. :)
35
36 Thanks :)
37
38 --
39 Fabian Groffen
40 Gentoo on a different level
41 --
42 gentoo-alt@g.o mailing list