From: Branko Badrljica <brankob@avtomatika.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Can not compile gcc
Date: Fri, 14 Nov 2008 20:31:16 +0100 [thread overview]
Message-ID: <491DD204.1010509@avtomatika.com> (raw)
In-Reply-To: <491DC4C0.4000503@j-schmitz.net>
Justin wrote:
> Barry Schwartz schrieb:
>
>> Mansour Al Akeel <mansour.alakeel@gmail.com> skribis:
>>
>>
>>> Any idea ?
>>>
>>>
>> If you use ccache, try emptying it.
>>
>>
>>
>>
>>
> I think there is something else wrong, because it fails in the configure
> phase.
>
> Send us an emerge --info output, please.
>
>
I'm not an expert, but it seems that it was trying to compile 64-bit
test code with -m32 flag:
>The log file:
>checking for x86_64-pc-linux-gnu-gcc...
/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc
-B/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/
-B/usr/x86_64-pc-linux-gnu/bin/ >-B/usr/x86_64-pc-linux-gnu/lib/
-isystem /usr/x86_64-pc-linux-gnu/include -isystem
/usr/x86_64-pc-linux-gnu/sys-include -m32
Perhaps he should check his make.conf for CHOST and CLAGS ?
next prev parent reply other threads:[~2008-11-14 18:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:02 [gentoo-amd64] Can not compile gcc Mansour Al Akeel
2008-11-14 18:26 ` Barry Schwartz
2008-11-14 18:34 ` Justin
2008-11-14 19:31 ` Branko Badrljica [this message]
2008-11-14 18:40 ` Justin
2008-11-14 19:14 ` Mansour Al Akeel
2008-11-14 19:24 ` Beso
2008-11-14 19:30 ` [gentoo-amd64] " Duncan
2008-11-14 19:54 ` Mansour Al Akeel
2008-11-14 21:16 ` [gentoo-amd64] " Tonko Mulder
2008-11-14 21:23 ` Mansour Al Akeel
2008-11-14 23:44 ` [gentoo-amd64] " Duncan
2008-11-15 2:58 ` Mansour Al Akeel
2008-11-15 6:41 ` Duncan
2008-11-14 21:48 ` [gentoo-amd64] " Christoph Mende
2008-11-14 22:22 ` Mansour Al Akeel
2008-11-14 23:19 ` Branko Badrljica
2008-11-14 22:31 ` Beso
2008-11-14 23:10 ` Mansour Al Akeel
2008-11-14 23:26 ` Beso
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=491DD204.1010509@avtomatika.com \
--to=brankob@avtomatika.com \
--cc=gentoo-amd64@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