From: Heiko Wundram <heiko@xencon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Still getting calls to gcc-i486
Date: Tue, 14 Jul 2009 16:09:15 +0200 [thread overview]
Message-ID: <d3c54b1cda14c6260d27afec9c90ab49@localhost> (raw)
In-Reply-To: <87vdlv1ixo.fsf@newsguy.com>
On Tue, 14 Jul 2009 08:40:51 -0500, Harry Putnam <reader@newsguy.com>
wrote:
> I've lost track of where all the guff was located but apparently I
> missed something.... can anyone tell me where to look?
>
> emerge error:
> [...]
> building 'cairo._cairo' extension
> creating build/temp.linux-i686-2.6
> creating build/temp.linux-i686-2.6/cairo
> i486-pc-linux-gnu-gcc -pthread -DNDEBUG -O2 -march=i686 -pipe -fPIC
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2
> -I/usr/include/libpng12 -I/usr/include/python2.6 -c cairo/cairomodule.c
-o
> build/temp.linux-i686-2.6/cairo/cairomodule.o
> unable to execute i486-pc-linux-gnu-gcc: No such file or directory
> error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1
> [...]
Re-merge python. Python keeps the compiler that was used to compile it in a
separate "Makefile" that's used to compile Python packages (with
distutils), and that's what you're hitting here (as you haven't updated
that).
--
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
prev parent reply other threads:[~2009-07-14 14:09 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
2009-07-16 6:46 ` Harry Putnam
2009-07-14 14:09 ` Heiko Wundram [this message]
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=d3c54b1cda14c6260d27afec9c90ab49@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