| 1 |
On 03/21/2011 02:19 AM, Helmut Jarausch wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> probably, portage-2.2.0_alpha28 has broken my system. |
| 5 |
> |
| 6 |
> I have reinstalled a binary version of portage-2.2.0_alpha27, but ... |
| 7 |
> |
| 8 |
> For many packages, portage installs libraries into /usr instead of |
| 9 |
> /usr/lib64 or /usr/lib32 |
| 10 |
> |
| 11 |
> Probably, the function get_libdir |
| 12 |
> (defined in /usr/portage/eclass/multilib.eclass) |
| 13 |
> returns an empty string. |
| 14 |
|
| 15 |
Seems that some important definitions are stored in |
| 16 |
/usr/portage/profiles/features/multilib/make.defaults and for some |
| 17 |
reason they are not being honored. |
| 18 |
|
| 19 |
That file should be sourced during every emerge, depending on your |
| 20 |
selected portage profile. What "does eselect profile list" say? |
| 21 |
Is the selected profile the correct one? |
| 22 |
|
| 23 |
Maybe using the -d flag with emerge will give you a hint where things |
| 24 |
are going wrong. |
Archives