public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Heiko Wundram <heiko@xencon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Still getting calls to gcc-i486
Date: Wed, 15 Jul 2009 23:39:41 +0200	[thread overview]
Message-ID: <25a71da1aca9f5cb2b1e716bb9f44c54@localhost> (raw)
In-Reply-To: <87fxcxodk2.fsf@newsguy.com>


On Wed, 15 Jul 2009 16:13:01 -0500, Harry Putnam <reader@newsguy.com>
wrote:
> <snip>
> So far I haven't found any instance of i486 files remaining on the
> system... what else might evoke that output?

As I said: some Python makefile retains the reference to the (former) i486
compiler. That Makefile is used when building packages using distutils
(that's what's happening here). If remerging Python itself didn't help, how
about grepping /usr/lib/python2.6 for "i486", and replacing the matching
string by hand?

grep -R "i486" /usr/lib/python2.6

On my system (i686), it's /usr/lib/python2.6/config/Makefile that matches.
And that should also be what's used by distutils.

-- 
Heiko Wundram
Gehrkens.IT GmbH

FON 0511-59027953 | http://www.gehrkens.it
FAX 0511-59027957 | http://www.xencon.net

Gehrkens.IT GmbH
Strasse der Nationen 5
30539 Hannover

Registergericht: Amtsgericht Hannover, HRB 200551
Geschäftsführer: Harald Gehrkens, Daniel Netzer



  reply	other threads:[~2009-07-15 21:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 13:40 [gentoo-user] Still getting calls to gcc-i486 Harry Putnam
2009-07-14 14:02 ` Volker Armin Hemmann
2009-07-14 15:32   ` [gentoo-user] " Harry Putnam
2009-07-14 15:36     ` Volker Armin Hemmann
2009-07-14 23:33       ` Harry Putnam
2009-07-15 21:13         ` Harry Putnam
2009-07-15 21:39           ` Heiko Wundram [this message]
2009-07-16  6:46             ` Harry Putnam
2009-07-14 14:09 ` [gentoo-user] " Heiko Wundram

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=25a71da1aca9f5cb2b1e716bb9f44c54@localhost \
    --to=heiko@xencon.net \
    --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