On Wed, Feb 11, 2009 at 6:25 PM, Joshua D Doll <joshua.d...@gmail.com> wrote: > Mark Knecht wrote: >> >> Hi, >> I had two machine that for some reason wouldn't build the 2.5 slot >> for python. I've waited weeks for the possibility that something would >> get cleaned up in portage or on a server somewhere but as of yet it >> hasn't happened. For kicks today I cleaned out distfiles and did an >> emerge -e @system but it failed the same way. I'm wondering what to >> try next? >> >> Is it allowable to remove ebuilds by hand? Will an eix-sync get new >> versions if ebuilds are missing and I change the servers that the >> machine is pointing to? >> >> Looking for ideas about how to move forward. >> >> Thanks, >> Mark >> >> >> > > What's the error message? > > --Joshua Doll
Not much unfortunately: Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xml/sax/xmlreader.py ... Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmllib.py ... Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmlrpclib.py ... Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/zipfile.py ... make: *** [libinstall] Error 1 ^[[31;01m*^[[0m ^[[31;01m*^[[0m ERROR: dev-lang/python-2.5.2-r7 failed. ^[[31;01m*^[[0m Call stack: ^[[31;01m*^[[0m ebuild.sh, line 49: Called src_install ^[[31;01m*^[[0m environment, line 3469: Called die ^[[31;01m*^[[0m The specific snippet of code: ^[[31;01m*^[[0m make DESTDIR="${D}" altinstall maninstall || die; ^[[31;01m*^[[0m The die message: ^[[31;01m*^[[0m (no error message) ^[[31;01m*^[[0m ^[[31;01m*^[[0m If you need support, post the topmost build error, and the call stack if relevant. ^[[31;01m*^[[0m A complete build log is located at '/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/build.log'. ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/environment'. ^[[31;01m*^[[0m