| 1 |
I seem to be having some wierd problems with portage. Here is an |
| 2 |
example when I try to re-emerge portage: |
| 3 |
|
| 4 |
---------------------------------------------------------- |
| 5 |
|
| 6 |
root@kruhft:/var/db/pkg/dev-libs# emerge portage |
| 7 |
Calculating dependencies ...done! |
| 8 |
>>> emerge sys-apps/portage-2.0.5 to / |
| 9 |
>>> Unpacking source... |
| 10 |
>>> Source unpacked. |
| 11 |
gcc -O2 -march=i486 -pipe sandbox.c -o sandbox |
| 12 |
gcc -O2 -march=i486 -pipe -c -o libsandbox.o libsandbox.c |
| 13 |
gcc -O2 -march=i486 -pipe libsandbox.o -o libsandbox.so -ldl --shared |
| 14 |
|
| 15 |
>>> Install portage-2.0.5 into /var/tmp/portage/portage-2.0.5/image/ |
| 16 |
category sys-apps |
| 17 |
running install |
| 18 |
running build |
| 19 |
running build_ext |
| 20 |
building 'missingos' extension |
| 21 |
creating build |
| 22 |
creating build/temp.linux-i686-2.2 |
| 23 |
gcc -DNDEBUG -march=i686 -mcpu=i686 -O3 -pipe -fforce-addr |
| 24 |
-frerun-cse-after-loop -frerun-loop-opt -malign-functions=4 |
| 25 |
-funroll-loops -fomit-frame-pointer -fexpensive-optimizations |
| 26 |
-fPIC -I/usr/include/python2.2 -c missingos.c -o |
| 27 |
build/temp.linux-i686-2.2/missingos.o -march=i686 -mcpu=i686 -O3 |
| 28 |
-pipe -fforce-addr -frerun-cse-after-loop -frerun-loop-opt |
| 29 |
-malign-functions=4 -funroll-loops -fomit-frame-pointer |
| 30 |
-fexpensive-optimizations |
| 31 |
creating build/lib.linux-i686-2.2 |
| 32 |
gcc -shared build/temp.linux-i686-2.2/missingos.o -o |
| 33 |
build/lib.linux-i686-2.2/missingos.so |
| 34 |
running install_lib |
| 35 |
creating /var/tmp/portage/portage-2.0.5/image/usr |
| 36 |
creating /var/tmp/portage/portage-2.0.5/image/usr/lib |
| 37 |
creating /var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2 |
| 38 |
creating |
| 39 |
/var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages |
| 40 |
copying build/lib.linux-i686-2.2/missingos.so -> |
| 41 |
/var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages |
| 42 |
warning: install: modules installed to |
| 43 |
'/var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages/', |
| 44 |
which is not in Python's module search path (sys.path) -- you'll |
| 45 |
have to change the search path yourself |
| 46 |
strip: |
| 47 |
/var/tmp/portage/portage-2.0.5/image/usr/lib/python2.2/site-packages/missingos.so/var/tmp/portage/portage-2.0.5/image/usr/lib/portage/bin/tbz2tool |
| 48 |
/var/tmp/portage/portage-2.0.5/image/usr/lib/portage/bin/sandbox |
| 49 |
/var/tmp/portage/portage-2.0.5/image/lib/libsandbox.so |
| 50 |
>>> Completed installing into /var/tmp/portage/portage-2.0.5/image/ |
| 51 |
|
| 52 |
>>> Merging sys-apps/portage-2.0.5 to / |
| 53 |
Traceback (most recent call last): |
| 54 |
File "/usr/bin/emerge", line 1233, in ? |
| 55 |
mydepgraph.merge(mydepgraph.altlist()) |
| 56 |
File "/usr/bin/emerge", line 610, in merge |
| 57 |
retval=portage.doebuild(y,"merge",myroot,edebug) |
| 58 |
File "/usr/lib/python2.2/site-packages/portage.py", line 1212, in |
| 59 |
doebuild |
| 60 |
return |
| 61 |
merge(settings["CATEGORY"],settings["PF"],settings["D"],settings["BUILDDIR"]+"/build-info",myroot,myebuild=settings["EBUILD"]) |
| 62 |
File "/usr/lib/python2.2/site-packages/portage.py", line 1436, in |
| 63 |
merge |
| 64 |
mylink.merge(pkgloc,infloc,myroot,myebuild) |
| 65 |
File "/usr/lib/python2.2/site-packages/portage.py", line 3340, in |
| 66 |
merge |
| 67 |
self.treewalk(mergeroot,myroot,inforoot,myebuild) |
| 68 |
File "/usr/lib/python2.2/site-packages/portage.py", line 3016, in |
| 69 |
treewalk |
| 70 |
packagecounter=long(globalcounterfile.readline()) |
| 71 |
ValueError: invalid literal for long(): |
| 72 |
|
| 73 |
--------------------------------------------------------- |
| 74 |
|
| 75 |
Basically emerge has become useless. Anybody have this problem |
| 76 |
before, or is there a way to reinstall just portage from a package if |
| 77 |
it's screwed up like this? |
Archives