From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
Date: Sun, 20 Jun 2010 16:50:37 +0100 [thread overview]
Message-ID: <201006201650.49949.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4C1E2E56.7000203@wonkology.org>
[-- Attachment #1: Type: Text/Plain, Size: 1908 bytes --]
On Sunday 20 June 2010 16:05:58 Alex Schuster wrote:
> meino.cramer@gmx.de writes:
> > Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:
> >> How about putting dev-python/setuptools into
> >> /etc/portage/package.keywords, and trying to emerge 0.6.13?
> >
> > I tried to re-emerge setuptools 0.6.10 and it fails the same way.
> > So I believe (=not knowing) that this problem is caused by something
> > outside setuptools, which gets screwed up.
>
> Probably python itself, as Arttu pointed out.
>
> > Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
> > (current version) is gone and cannot get back due to the same problem
> > (see above). And then I have a "unstable" version, which may pull in
> > other unstable versions of something else, which pull in....
>
> Maybe, but at least in the ebuild itself there are no such dependencies.
> If you'd need to keyword this package only, it should do no harm. If
> more things need to be keyworded, I agree that this tends to make things
> complicated. But at least you can quickpkg the existing version, and get
> it back when needed without compiling with emerge -k.
> But when 0.6.10 also fails, the problem is likely to be somewhere else.
>
> > This way I have corrupted my last installed gentoo system...
>
> I'm at ~amd64 now, and things are easier now :) At least for me.
>
> If you are desperate: Maybe removing setuptools would at least make
> python-updater run through, unless something would pull it in again.
> Emerge -k setuptools back. You may be missing stuff for python 3.1, but
> maybe this does not harm too much.
>
> And report a bug at bugs.gentoo.org, so the maintainers know what's
> going on.
I'd have another go but after setting MAKEOPTS="-j1" (although I have to admit
the error you posted does not look like this would make any difference).
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-20 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 7:37 [gentoo-user] Compilation aborted for setuptools-0.6.12 meino.cramer
2010-06-19 14:43 ` [gentoo-user] " walt
2010-06-19 14:55 ` meino.cramer
2010-06-20 17:07 ` walt
2010-06-20 17:34 ` meino.cramer
2010-06-20 10:25 ` [gentoo-user] " Arttu V.
2010-06-20 10:48 ` meino.cramer
2010-06-20 11:59 ` Arttu V.
2010-06-20 12:23 ` meino.cramer
2010-06-20 13:13 ` Alex Schuster
2010-06-20 13:31 ` meino.cramer
2010-06-20 15:05 ` Alex Schuster
2010-06-20 15:46 ` meino.cramer
2010-06-20 15:50 ` Mick [this message]
2010-06-20 16:41 ` meino.cramer
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=201006201650.49949.michaelkintzios@gmail.com \
--to=michaelkintzios@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