1 |
On 03/21/2011 11:13:36 AM, walt wrote: |
2 |
> On 03/21/2011 02:19 AM, Helmut Jarausch wrote: |
3 |
> > Hi, |
4 |
> > |
5 |
> > probably, portage-2.2.0_alpha28 has broken my system. |
6 |
> > |
7 |
> > I have reinstalled a binary version of portage-2.2.0_alpha27, but |
8 |
> ... |
9 |
> > |
10 |
> > For many packages, portage installs libraries into /usr instead of |
11 |
> > /usr/lib64 or /usr/lib32 |
12 |
> > |
13 |
> > Probably, the function get_libdir |
14 |
> > (defined in /usr/portage/eclass/multilib.eclass) |
15 |
> > returns an empty string. |
16 |
> |
17 |
> Seems that some important definitions are stored in |
18 |
> /usr/portage/profiles/features/multilib/make.defaults and for some |
19 |
> reason they are not being honored. |
20 |
> |
21 |
> That file should be sourced during every emerge, depending on your |
22 |
> selected portage profile. What "does eselect profile list" say? |
23 |
> Is the selected profile the correct one? |
24 |
> |
25 |
> Maybe using the -d flag with emerge will give you a hint where things |
26 |
> are going wrong. |
27 |
|
28 |
Thanks, Walt. |
29 |
|
30 |
/usr/portage/profiles/features/multilib/make.defaults looks OK |
31 |
|
32 |
The selected profile is default/linux/amd64/10.0/desktop |
33 |
which is OK, as well. |
34 |
|
35 |
I should have mentioned that after installing portage-2.2.0_alpha28 |
36 |
the search path included /usr/portage/bin which doesn't exist. |
37 |
I have no idea where this came from. |
38 |
|
39 |
The debugging run revealed that the 'multilib' USE flag got lost. |
40 |
|
41 |
I've just emerged a package both on my machine and a very similar |
42 |
machine but which hasn't been updated the last few days. |
43 |
|
44 |
Diffing the two log files showed that the multilib USE flag isn't in |
45 |
effect on my machine (only). |
46 |
|
47 |
I've compared /etc/make.conf on both machines and there isn't any |
48 |
difference. So, it looks like a broken profile here. |
49 |
What to do about that? |
50 |
|
51 |
Thanks, |
52 |
Helmut. |