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