From: Frank Schafer <frank.schafer@t-systems.cz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugs in autoconf/automake and python-fchksum
Date: Mon, 12 Sep 2005 14:49:41 +0200 [thread overview]
Message-ID: <1126529381.5947.180.camel@localhost.localdomain> (raw)
In-Reply-To: <1126529271.13466.6.camel@sponge.fungus>
On Mon, 2005-09-12 at 14:47 +0200, Henrik Brix Andersen wrote:
> On Mon, 2005-09-12 at 14:41 +0200, Frank Schafer wrote:
> > During ``emerge system'' python-fchksum failed with a not existing
> > i386-pc-linux-gnu-gcc on a i686 system. I don't know if python hard
> > codes the native compiler to the one it was built with or if this
> > compiler is hard coded in setup.py during python installation. Looking
> > at the ebuild it seems to be ok.
>
> https://bugs.gentoo.org/show_bug.cgi?id=88777
>
> ./Brix
Yes, there I got the workaround from. Be this there this isn't a reason
to fix the bug?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-12 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 12:41 [gentoo-dev] Bugs in autoconf/automake and python-fchksum Frank Schafer
2005-09-12 12:47 ` Henrik Brix Andersen
2005-09-12 12:49 ` Frank Schafer [this message]
2005-09-12 12:56 ` Mike Frysinger
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=1126529381.5947.180.camel@localhost.localdomain \
--to=frank.schafer@t-systems.cz \
--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