| 1 |
Fabian Groffen wrote: |
| 2 |
> On 25-03-2008 11:12:36 +1100, Matt Michalowski wrote: |
| 3 |
> |
| 4 |
>>>>> Compiling source in |
| 5 |
>>>>> |
| 6 |
>> /opt/hwbp/var/tmp/portage/sys-apps/portage-2.2.00.9500/work/prefix-portage-2.2.00.9500 |
| 7 |
>> ... |
| 8 |
>> Traceback (most recent call last): |
| 9 |
>> File "<string>", line 1, in <module> |
| 10 |
>> ImportError: No module named portage.const |
| 11 |
>> |
| 12 |
> |
| 13 |
> Looks like python can't find Portage. That is at least "weird". Are |
| 14 |
> you sure Portage uses prefix python, and that prefix python was indeed |
| 15 |
> compiled by the ebuild? |
| 16 |
> |
| 17 |
> I think you suffer from an old bug that aparently is still not yet fixed |
| 18 |
> properly. Or it just is there because you use a long living Prefix |
| 19 |
> install. |
| 20 |
> |
| 21 |
> Check if your $EPREFIX/usr/lib and $EPREFIX/lib are symlinks pointing to |
| 22 |
> the lib64 variants. If you fix that, it may be that python suddenly can |
| 23 |
> find python again. |
| 24 |
> |
| 25 |
It's a reasonably long living install. |
| 26 |
|
| 27 |
It turns out my $EPREFIX/usr/lib and $EPREFIX/usr/lib64 were different |
| 28 |
directories. $EPREFIX/usr/lib had gcc, gentoolkit and portage |
| 29 |
directories inside it, so I moved them all to $EPREFIX/usr/lib64, |
| 30 |
removed the $EPREFIX/usr/lib directory and symlinked $EPREFIX/usr/lib64 |
| 31 |
to $EPREFIX/usr/lib. |
| 32 |
|
| 33 |
Now all is well, and the upgrade to 9500 succeeded, thanks. |
| 34 |
|
| 35 |
Matt. |
| 36 |
-- |
| 37 |
gentoo-alt@l.g.o mailing list |
Archives