From: Wolfgang Illmeyer <wolfgang.illmeyer@gmx.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Python stuff and CHOST Change don't agree
Date: Thu, 28 Apr 2005 23:32:44 +0200 [thread overview]
Message-ID: <4271567C.9080907@gmx.net> (raw)
Hi,
A few months ago I changed my CHOST in make.conf from i386-pc-linux-gnu
to i686-pc-linux-gnu. Everything went ok until I had to install some
python package; the old chost was hardcoded somewhere in
/usr/lib/python2.3 or similar and therefore it still wanted to use the
i386-toolchain when building python stuff. remerging python didn't help.
revdep-rebuild didn't help. then I manually replaced the i386 by i686
and it went well for a while.
Today i wanted to emerge solfege with gnome useflag and it stopped at
dev-python/pyorbit due to a missing "i386-pc-linux-gnu-gcc"
what can i do?
greetings
Wolfgang
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-04-28 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 21:32 Wolfgang Illmeyer [this message]
2005-04-28 21:37 ` [gentoo-dev] Python stuff and CHOST Change don't agree Ciaran McCreesh
2005-04-28 22:08 ` Mike Frysinger
2005-04-28 22:19 ` Robin H. Johnson
2005-04-29 22:28 ` Wolfgang Illmeyer
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=4271567C.9080907@gmx.net \
--to=wolfgang.illmeyer@gmx.net \
--cc=gentoo-dev@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