Re: [gentoo-user] python-2.5.2-r7 build problems

[Mark Knecht <markknecht@gmail.com>]

On Wed, Feb 11, 2009 at 7:04 PM, Joshua D Doll <joshua.doll@gmail.com> wrote:
> Mark Knecht wrote:
>>
>> On Wed, Feb 11, 2009 at 6:25 PM, Joshua D Doll <joshua.doll@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
>>
>>
>>
>
> I might be mistaken, but I don't think that is make error message. You might
> want to check further up in the build.log for more information.
>
> --Joshua Doll
>

Thanks. I really see nothing else in the file unless I'm just missing
it somehow. I've grepped the file for error/Error/ERROR. The only
thing that shows up is this for 'Error':
mkdir: cannot create directory `Include': File exists
make: [Include/graminit.h] Error 1 (ignored)
Parser/pgen ./Grammar/Grammar ./Include/graminit.h ./Python/graminit.c
mkdir: cannot create directory `Include': File exists
make: [Python/graminit.c] Error 1 (ignored)
Parser/pgen ./Grammar/Grammar ./Include/graminit.h ./Python/graminit.c

and this:

Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/test/test_multibytecodec.py
...
Sorry: UnicodeDecodeError: ('unicodeescape', '\\N{SOFT HYPHEN}', 0,
15, 'unknown Unicode character name')
Compiling /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/test/test_multibytecodec_support.py
...

For kicks I erased the work directory which gets left around when a
build fails. That didn't help.

Mostly I was thinking if I knew what I could safely delete then I
could let emerge download new copies. I'm assuming that this is being
caused by some corrupted file on my machine, or on the server. If I
change servers then maybe I'll get a good copy, etc. It's weak but
this has been hanging around for a month. I've filed a bug. I haven't
heard a word from bugzilla folks. Not like the old days when you'd see
a response from someone within hours.

- Mark