| 1 |
On Wed, April 2, 2008 17:19, Fabian Groffen wrote: |
| 2 |
> On 02-04-2008 16:55:30 +0200, Duft Markus wrote: |
| 3 |
>> Used a) since i'm messing with environment anyway in the bootstrap |
| 4 |
>> script, and i don't know what eprefix i will bootstrap at compile time, |
| 5 |
>> so b) isn't possible. |
| 6 |
>> Now the right python is found, but i have another problem: there is no |
| 7 |
>> rpath hardcoded in python, so it doesn't find python2.5.so...... Need to |
| 8 |
>> mess a little more with the environment :) |
| 9 |
> |
| 10 |
> Then set your LDFLAGS to the appropriate values when you bootstrap |
| 11 |
> python. |
| 12 |
|
| 13 |
LDFLAGS not being appropriately set might be the problem, but I had the |
| 14 |
same problem on amd64-linux due to the missing /usr/lib -> /usr/lib64 |
| 15 |
symlink. Emerging baselayout-prefix isn't able to create the symlink due |
| 16 |
to the directory /usr/lib created by the bootstrapped portage using |
| 17 |
bootstrap-prefix.sh. I've posted a possible patch for bootstrap-prefix.sh |
| 18 |
in https://bugs.gentoo.org/show_bug.cgi?id=183874#c9 |
| 19 |
|
| 20 |
Regards, |
| 21 |
Stefan |
| 22 |
-- |
| 23 |
gentoo-alt@l.g.o mailing list |
Archives