| 1 |
Brandon Lewis wrote: |
| 2 |
> I tried boostrapping a while back on gutsy, but i ran into too many |
| 3 |
> problems. Just curious if anyone has tried bootstrapping on ubuntu |
| 4 |
> lately and whether or not they were successful. If so, what |
| 5 |
> instructions did you follow? Did you have to do anything special? |
| 6 |
> |
| 7 |
> --Brandon |
| 8 |
I bootstrapped on a clean Ubuntu 8.04 Hardy server install. Basically I |
| 9 |
followed all of the Linux instructions, |
| 10 |
http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml - |
| 11 |
with a few deviations. Here are such deviations/notes/tips, if you are |
| 12 |
still interested. |
| 13 |
|
| 14 |
- After the ubuntu server install, I performed an "apt-get install |
| 15 |
build-essential" to easily get gcc, make, etc. This is the only ubuntu |
| 16 |
package I installed. |
| 17 |
|
| 18 |
- Code Listing (CL) 1.4 : I didn't bother bootstrapping python or wget, |
| 19 |
Hardy had up-to-date versions installed. |
| 20 |
|
| 21 |
- Before CL 1.8, perform a "emerge --oneshot bison" as bash requires |
| 22 |
yacc which we don't have. This will also emerge m4-1.4.11. |
| 23 |
|
| 24 |
- CL 1.8 : Instead of "emerge --oneshot bash", perform "emerge --oneshot |
| 25 |
=app-shells/bash-3.2_p17-r1". The latest version in the latest snapshot, |
| 26 |
3.2_p39, now inherits the autotools eclass, causing portage to want to |
| 27 |
install automake, libtool, etc., which is what we are doing in CL 1.9. |
| 28 |
Restricting the version to 3.2_p17-r1 will only emerge ncurses and bash. |
| 29 |
|
| 30 |
- CL 1.9 : Since my bison emerge installed m4, I skipped the emerge |
| 31 |
"emerge --oneshot --nodeps "m4"" command. Before "emerge --oneshot |
| 32 |
--nodeps libtool", perform a "emerge --oneshot gawk". The libtool |
| 33 |
install calls aclocal, and the gentoo aclocal wrapper calls gawk, which |
| 34 |
ubuntu doesn't install out of-the-box, so I made sure that gawk was |
| 35 |
installed before the libtool emerge. |
| 36 |
|
| 37 |
- CL 1.11 : I skipped "emerge --oneshot "<m4-1.4.11"". Not sure why this |
| 38 |
is recommended (possibly older versions of coreutils don't like |
| 39 |
m4-1.4.11?), but skipping it seemed to have no ill-effects, and |
| 40 |
coreutils-6.11 emerged fine. |
| 41 |
|
| 42 |
- CL 1.12 : You will probably hit bug |
| 43 |
http://bugs.gentoo.org/show_bug.cgi?id=220489 during "emerge --oneshot |
| 44 |
--nodeps findutils" (I did). To remedy this, and to make sure this |
| 45 |
doesn't trip up the emerge system later, I masked findutils-4.4.0 by |
| 46 |
performing "mkdir $EPREFIX/etc/portage ; echo =sys-apps/findutils-4.4.0 |
| 47 |
>> $EPREFIX/etc/portage/package.mask". emerge will then install |
| 48 |
findutils-4.3.13 instead. |
| 49 |
|
| 50 |
- CL 1.12 : I also skipped "emerge --oneshot gawk" here as I'd performed |
| 51 |
that earlier. |
| 52 |
|
| 53 |
- During the first "emerge -e system" in CL 1.16, it will eventually |
| 54 |
emerge sandbox. After sandbox is installed you will see a lot of errors |
| 55 |
like "ACCESS DENIED open_wr: /etc/passwd". The system emerge |
| 56 |
finished, but it seems sandbox doesn't work on Ubuntu Hardy server (does |
| 57 |
Ubuntu server have some security features that I don't know about |
| 58 |
perhaps? I wonder if the desktop version does the same thing? This |
| 59 |
doesn't happen on Debian Etch) |
| 60 |
|
| 61 |
- Since sandbox doesn't work, it breaks the next "emerge -e system" in |
| 62 |
CL 1.19 if enabled. To combat this, I disabled sandbox. So after CL |
| 63 |
1.18, perform a "echo 'FEATURES="-sandbox"' >> $EPREFIX/etc/make.conf" |
| 64 |
|
| 65 |
Hope this is helpful. |
| 66 |
|
| 67 |
Matt. |
| 68 |
|
| 69 |
-- |
| 70 |
gentoo-alt@l.g.o mailing list |
Archives