From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-2.5.2-r7 build problems
Date: Wed, 11 Feb 2009 18:40:20 -0800 [thread overview]
Message-ID: <5bdc1c8b0902111840j275fdd8eg429460bb979a2b08@mail.gmail.com> (raw)
In-Reply-To: <499388B5.80105@gmail.com>
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
next prev parent reply other threads:[~2009-02-12 2:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 1:58 [gentoo-user] python-2.5.2-r7 build problems Mark Knecht
2009-02-12 2:25 ` Joshua D Doll
2009-02-12 2:40 ` Mark Knecht [this message]
2009-02-12 3:04 ` Joshua D Doll
2009-02-12 4:18 ` Mark Knecht
2009-02-12 4:22 ` Mark Knecht
2009-02-12 4:22 ` Mark Knecht
2009-02-12 8:58 ` Neil Bothwick
2009-02-12 14:20 ` Mark Knecht
2009-02-12 14:52 ` Mark Knecht
2009-02-12 17:34 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0902111840j275fdd8eg429460bb979a2b08@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox