| 1 |
Mark Knecht wrote: |
| 2 |
> On Wed, Feb 11, 2009 at 6:25 PM, Joshua D Doll <joshua.doll@×××××.com> wrote: |
| 3 |
> |
| 4 |
>> Mark Knecht wrote: |
| 5 |
>> |
| 6 |
>>> Hi, |
| 7 |
>>> I had two machine that for some reason wouldn't build the 2.5 slot |
| 8 |
>>> for python. I've waited weeks for the possibility that something would |
| 9 |
>>> get cleaned up in portage or on a server somewhere but as of yet it |
| 10 |
>>> hasn't happened. For kicks today I cleaned out distfiles and did an |
| 11 |
>>> emerge -e @system but it failed the same way. I'm wondering what to |
| 12 |
>>> try next? |
| 13 |
>>> |
| 14 |
>>> Is it allowable to remove ebuilds by hand? Will an eix-sync get new |
| 15 |
>>> versions if ebuilds are missing and I change the servers that the |
| 16 |
>>> machine is pointing to? |
| 17 |
>>> |
| 18 |
>>> Looking for ideas about how to move forward. |
| 19 |
>>> |
| 20 |
>>> Thanks, |
| 21 |
>>> Mark |
| 22 |
>>> |
| 23 |
>>> |
| 24 |
>>> |
| 25 |
>>> |
| 26 |
>> What's the error message? |
| 27 |
>> |
| 28 |
>> --Joshua Doll |
| 29 |
>> |
| 30 |
> |
| 31 |
> Not much unfortunately: |
| 32 |
> |
| 33 |
> Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xml/sax/xmlreader.py |
| 34 |
> ... |
| 35 |
> Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmllib.py |
| 36 |
> ... |
| 37 |
> Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/xmlrpclib.py |
| 38 |
> ... |
| 39 |
> Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/zipfile.py |
| 40 |
> ... |
| 41 |
> make: *** [libinstall] Error 1 |
| 42 |
> ^[[31;01m*^[[0m |
| 43 |
> ^[[31;01m*^[[0m ERROR: dev-lang/python-2.5.2-r7 failed. |
| 44 |
> ^[[31;01m*^[[0m Call stack: |
| 45 |
> ^[[31;01m*^[[0m ebuild.sh, line 49: Called src_install |
| 46 |
> ^[[31;01m*^[[0m environment, line 3469: Called die |
| 47 |
> ^[[31;01m*^[[0m The specific snippet of code: |
| 48 |
> ^[[31;01m*^[[0m make DESTDIR="${D}" altinstall maninstall || die; |
| 49 |
> ^[[31;01m*^[[0m The die message: |
| 50 |
> ^[[31;01m*^[[0m (no error message) |
| 51 |
> ^[[31;01m*^[[0m |
| 52 |
> ^[[31;01m*^[[0m If you need support, post the topmost build error, |
| 53 |
> and the call stack if relevant. |
| 54 |
> ^[[31;01m*^[[0m A complete build log is located at |
| 55 |
> '/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/build.log'. |
| 56 |
> ^[[31;01m*^[[0m The ebuild environment file is located at |
| 57 |
> '/var/tmp/portage/dev-lang/python-2.5.2-r7/temp/environment'. |
| 58 |
> ^[[31;01m*^[[0m |
| 59 |
> |
| 60 |
> |
| 61 |
> |
| 62 |
|
| 63 |
I might be mistaken, but I don't think that is make error message. You |
| 64 |
might want to check further up in the build.log for more information. |
| 65 |
|
| 66 |
--Joshua Doll |
Archives