Brandon Lewis wrote:
I tried boostrapping a while back on gutsy, but i ran into too many
problems. Just curious if anyone has tried bootstrapping on ubuntu
lately and whether or not they were successful. If so, what
instructions did you follow? Did you have to do anything special?
--Brandon
I bootstrapped on a clean Ubuntu 8.04 Hardy server install. Basically I
followed all of the Linux instructions,
http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml -
with a few deviations. Here are such deviations/notes/tips, if you are
still interested.
- After the ubuntu server install, I performed an "apt-get install
build-essential" to easily get gcc, make, etc. This is the only ubuntu
package I installed.
- Code Listing (CL) 1.4 : I didn't bother bootstrapping python or wget,
Hardy had up-to-date versions installed.
- Before CL 1.8, perform a "emerge --oneshot bison" as bash requires
yacc which we don't have. This will also emerge m4-1.4.11.
- CL 1.8 : Instead of "emerge --oneshot bash", perform "emerge --oneshot
=app-shells/bash-3.2_p17-r1". The latest version in the latest snapshot,
3.2_p39, now inherits the autotools eclass, causing portage to want to
install automake, libtool, etc., which is what we are doing in CL 1.9.
Restricting the version to 3.2_p17-r1 will only emerge ncurses and bash.
- CL 1.9 : Since my bison emerge installed m4, I skipped the emerge
"emerge --oneshot --nodeps "m4"" command. Before "emerge --oneshot
--nodeps libtool", perform a "emerge --oneshot gawk". The libtool
install calls aclocal, and the gentoo aclocal wrapper calls gawk, which
ubuntu doesn't install out of-the-box, so I made sure that gawk was
installed before the libtool emerge.
- CL 1.11 : I skipped "emerge --oneshot "<m4-1.4.11"". Not sure why this
is recommended (possibly older versions of coreutils don't like
m4-1.4.11?), but skipping it seemed to have no ill-effects, and
coreutils-6.11 emerged fine.
- CL 1.12 : You will probably hit bug
http://bugs.gentoo.org/show_bug.cgi?id=220489 during "emerge --oneshot
--nodeps findutils" (I did). To remedy this, and to make sure this
doesn't trip up the emerge system later, I masked findutils-4.4.0 by
performing "mkdir $EPREFIX/etc/portage ; echo =sys-apps/findutils-4.4.0
>> $EPREFIX/etc/portage/package.mask". emerge will then install
findutils-4.3.13 instead.
- CL 1.12 : I also skipped "emerge --oneshot gawk" here as I'd performed
that earlier.
- During the first "emerge -e system" in CL 1.16, it will eventually
emerge sandbox. After sandbox is installed you will see a lot of errors
like "ACCESS DENIED open_wr: /etc/passwd". The system emerge
finished, but it seems sandbox doesn't work on Ubuntu Hardy server (does
Ubuntu server have some security features that I don't know about
perhaps? I wonder if the desktop version does the same thing? This
doesn't happen on Debian Etch)
- Since sandbox doesn't work, it breaks the next "emerge -e system" in
CL 1.19 if enabled. To combat this, I disabled sandbox. So after CL
1.18, perform a "echo 'FEATURES="-sandbox"' >> $EPREFIX/etc/make.conf"
Hope this is helpful.
Matt.
--
[email protected] mailing list
