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