View previous topic :: View next topic |
Author |
Message |
gir n00b
Joined: 02 Sep 2002 Posts: 37
|
Posted: Tue Jun 24, 2003 8:30 pm Post subject: Python (and, therefore, portage) hosed |
|
|
I spent a good hour or so yesterday cleaning up my system by going through /var/db/pkg/* and removing the packages that I no longer used or needed. Since I was fairly liberal in what I removed, I wanted to `emerge -e world` to make sure that everything on my system would remain happy. The rebuild of my system started last night without a hitch, and when I went to bed my system was in the process of building something like package #17 out of 157. When I got back from work today I figured that the rebuild would be finished but instead I see the following:
Quote: | >>> emerge (41 of 157) dev-perl/MIME-Base64-2.12-r2 to /
>>> md5 src_uri ;-) MIME-Base64-2.12.tar.gz
>>> Unpacking source...
>>> Unpacking MIME-Base64-2.12.tar.gz to /logout/scratch/nielser/portage/MIME-Ba
se64-2.12-r2/work
>>> Source unpacked.
/usr/sbin/ebuild.sh: line 1178: 13195 Segmentation fault perl Makefile.PL $
{myconf} PREFIX=${D}/usr
make: *** No targets specified and no makefile found. Stop.
!!! ERROR: dev-perl/MIME-Base64-2.12-r2 failed.
!!! Function perl-module_src_compile, Line 36, Exitcode 2
!!! compilation failed |
I was a little miffed that the rebuild didn't complete but that's nothing new. Before looking into the problem further, I wanted to sync my portage tree but I ran into a little issue:
Quote: | gir ~ # emerge sync
Segmentation fault |
Cute.
A little investigation reveals that python (somehow) got hosed last night.
Quote: | gir ~ # python
Segmentation fault |
I have no idea how that could have happened... at least, I have no idea how that could have happened in the middle of a rebuild when python was number 13 on the list of packages to rebuild. After other critical packages such as glibc and gcc. For what it's worth, perl also no longer works (which is the cause of my original error) and it was number 21 on the list.
How did perl and python (and probably some other packages) break, esp in the middle of a system rebuild, well after they themselves had been sucessfully built?
More importantly, is there any way to repair my system without reinstalling? I really don't want to sit through another two day long build process. |
|
Back to top |
|
|
Pindrop Apprentice
Joined: 09 Jul 2002 Posts: 165 Location: Virginia, USA
|
Posted: Tue Jun 24, 2003 10:49 pm Post subject: |
|
|
You could untar the stage2*etc.tar.bz2 on your / drive and get all your system files back, emerge sync, emerge -u system, emerge -e world. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|