1 |
Ok, I decided to to something completely different today, and went on |
2 |
trying to get this working. First I tried to follow your steps: |
3 |
|
4 |
On 14-12-2005 15:21:41 -0800, m h wrote: |
5 |
> ===========Steps for prefix================ |
6 |
> * download toolsbox from http://dev.gentoo.org/~ferringb/portage/prefix/haubi/ |
7 |
> * download portage and prefixed overlay from |
8 |
> http://dev.gentoo.org/~kito/distfiles/ |
9 |
> * cd /data1/portage/dec14/toolsbox-4-20050927 |
10 |
> * export PREFIX=/data1/portage/dec14/prefix |
11 |
> * gmake config PREFIX=$PREFIX |
12 |
> DISTURL=http://www.ibiblio.org/pub/Linux/distributions/gentoo/distfiles |
13 |
> portage_BUILD |
14 |
|
15 |
What is this portage_BUILD? gmake doesn't like it as target. |
16 |
|
17 |
> * mkdir buildroot/distfiles |
18 |
> * cp ../../kito/portage-2.0.53.03.tar.gz buildroot/distfiles/ |
19 |
|
20 |
I took kito's prefixed version instead. Because it's not what the |
21 |
scripts expect, I did some fooling around: |
22 |
|
23 |
% tar -jxf portage-prefix-2.0.54.tar.bz2 |
24 |
% mv portage-prefix-2.0.54 portage-2.0.54 |
25 |
% tar -gcf portage-2.0.54.tar.gz portage-2.0.54 |
26 |
|
27 |
> * touch buildroot/portage/portage.fetched.done |
28 |
> * change portage/portage.build |
29 |
> * change line version to "VERSION=2.0.53.03" |
30 |
|
31 |
I set the version to 2.0.54, at least the unpack phase went fine in |
32 |
gmake portage. |
33 |
|
34 |
> * toolsbox will still fail to install portage... FIXME! |
35 |
> * gmake portage |
36 |
> * wait for a while (3 hours...) |
37 |
|
38 |
hmmm... Could have known, some of the packages don't compile out of the |
39 |
box, because my FC4 system uses gcc4. |
40 |
So I replaced binutils (which bugged) with a never version. Easy, just |
41 |
change binutils/binutils.build and change to the never version. |
42 |
|
43 |
However, after that worked, python didn't want to install, because the |
44 |
linker could not find gcc_s or something. Ok, so I gave up, wondering |
45 |
why I'd need all those tools anyway, and see how hard I would fall, if I |
46 |
would just configure and install kito's portage tar. |
47 |
|
48 |
So I unpacked it, ran configure like this: (where $(prefix) is here for |
49 |
making it generic, and killing lots of long paths) |
50 |
configure \ |
51 |
--sysconfdir=$(prefix)/etc \ |
52 |
--prefix=$(prefix)/usr \ |
53 |
--with-offset-prefix=$(prefix) \ |
54 |
--with-user=fabian \ |
55 |
--with-group=ins \ |
56 |
--with-wheelgroup=ins1 \ |
57 |
--with-rootuser=fabian \ |
58 |
|
59 |
configure, make, make install went all fine, so in my $(prefix), I added |
60 |
an /usr/portage (rsync tree), including distfiles (for fun, from another |
61 |
machine) and a usr/local/portage which contained the prefix overlay |
62 |
files from kito. |
63 |
|
64 |
portage is enormously picky, and creating the make.profile symlink gave |
65 |
me some problems. Making it a relative link, e.g. |
66 |
../usr/portage/profiles... portage assumed the .. was bogus, and thought |
67 |
that the profiles was at /usr/portage/profiles... where it of course |
68 |
wasn't. Solution: use an absolute symlink there. |
69 |
|
70 |
Next stop was emerge dying with some vague permission denied message. |
71 |
Iteratively executing emerge made it work in the end, because it |
72 |
appeared to be creating the /var/cache/... tree, and died each time when |
73 |
a directory didn't exist. So after each run of emerge, my directory |
74 |
tree there was one level deeper, hence after a lot of runs, emerge |
75 |
finally exited cleanly, leaving me with some messages: |
76 |
|
77 |
> (pegasus:~/scratch/programs/gentoo) fabian% usr/bin/emerge info |
78 |
> portage: 'portage' user or group missing. Please update baselayout |
79 |
> and merge portage user(250) and group(250) into your passwd |
80 |
> and group files. Non-root compilation is disabled until then. |
81 |
> Also note that non-root/wheel users will need to be added to |
82 |
> the portage group to do portage commands. |
83 |
> |
84 |
> For the defaults, line 1 goes into passwd, and 2 into group. |
85 |
> portage:x:250:250:portage:/var/tmp/portage:/bin/false |
86 |
> portage::250:portage |
87 |
|
88 |
Ok, I had hoped these numbers would have been set to my user and group |
89 |
IDs by the configure call. Apparently not. Or it is something else I |
90 |
did wrong here. There's no way for me on this system to create or |
91 |
modify users. |
92 |
|
93 |
> *** You are not in the portage group. You may experience cache problems |
94 |
> *** due to permissions preventing the creation of the on-disk cache. |
95 |
> *** Please add this user to the portage group if you wish to use portage. |
96 |
|
97 |
Hmmm... ok. |
98 |
|
99 |
> !!! Problem with sandbox binary. Disabling... |
100 |
|
101 |
Right. It probably doesn't exist. |
102 |
|
103 |
> !!! Relying on the shell to locate gcc, this may break |
104 |
> !!! DISTCC, installing gcc-config and setting your current gcc |
105 |
> !!! profile will fix this |
106 |
> Portage 2.0.54 (default-linux/amd64/2006.0, gcc-4.0.2, unavailable, 2.6.13-1.1526_FC4 x86_64) |
107 |
> ================================================================= |
108 |
> System uname: 2.6.13-1.1526_FC4 x86_64 x86_64 |
109 |
> Unknown Host Operating System |
110 |
> distcc 2.18.3 x86_64-redhat-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] |
111 |
> ccache version 2.4 [disabled] |
112 |
> dev-lang/python: [Not Present] |
113 |
> sys-apps/sandbox: [Not Present] |
114 |
> sys-devel/autoconf: [Not Present] |
115 |
> sys-devel/automake: [Not Present] |
116 |
> sys-devel/binutils: [Not Present] |
117 |
> sys-devel/libtool: [Not Present] |
118 |
> sys-devel/odcctools: [Not Present] |
119 |
> virtual/os-headers: [Not Present] |
120 |
> ACCEPT_KEYWORDS="amd64 x86" |
121 |
> CBUILD="i686-pc-linux-gnu" |
122 |
> CFLAGS="-O2 -pipe" |
123 |
> CHOST="i686-pc-linux-gnu" |
124 |
> CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" |
125 |
[snip] |
126 |
|
127 |
I probably should go and look for some documentation on this... |
128 |
|
129 |
|
130 |
-- |
131 |
Fabian Groffen |
132 |
Gentoo for Mac OS X Project -- Interim Lead |
133 |
-- |
134 |
gentoo-osx@g.o mailing list |