From: Blakawk <blakawk@gentooist.com>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] unable to compile gcc 4.5.3-r1
Date: Fri, 02 Sep 2011 12:44:36 +0200 [thread overview]
Message-ID: <be94762792ffd1b41e2b30496ba57420@parizet.com> (raw)
In-Reply-To: <30529.1314958583@ccs.covici.com>
On 02.09.2011 12:16, covici@ccs.covici.com wrote:
> Dale <rdalek1967@gmail.com> wrote:
>
>> covici@ccs.covici.com wrote:
>> > Hi. I am unable to compile gcc 4.5.3-r1 -- I get the following
>> error
>> > when doing so:
>> >
>> > mkdir -p -- x86_64-pc-linux-gnu/libgomp
>> > Checking multilib configuration for libgomp...
>> > Configuring stage 1 in x86_64-pc-linux-gnu/libgomp
>> > configure: loading site script /usr/share/config.site
>> > configure: loading site script
>> /usr/share/crossdev/include/site/linux
>> > configure: loading site script
>> > /usr/share/crossdev/include/site/x86_64-linux-gnu
>> > configure: creating cache ./config.cache
>> > checking for --enable-version-specific-runtime-libs... no
>> > checking for --enable-generated-files-in-srcdir... no
>> > checking build system type... x86_64-pc-linux-gnu
>> > checking host system type... x86_64-pc-linux-gnu
>> > checking target system type... x86_64-pc-linux-gnu
>> > checking for a BSD-compatible install... /usr/bin/install -c
>> > checking whether build environment is sane... yes
>> > checking for a thread-safe mkdir -p... /bin/mkdir -p
>> > checking for gawk... gawk
>> > checking whether make sets $(MAKE)... yes
>> > checking for
>> > x86_64-pc-linux-gnu-gcc...
>> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./gcc/xgcc
>> > -B/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./gc\c/
>> > -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
>> > checking for C compiler default output file name...
>> > configure: error: in
>> >
>> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/x86_64-pc-linux-gnu/libgomp':
>> > configure: error: C compiler cannot create executables
>> > See `config.log' for more details.
>> >
>> > I have searched google and looked at bugs.gentoo.org, but no joy.
>> >
>> > I am running unstable amd64 gentoo.
>> >
>> > Any assistance would be appreciated.
>> >
>>
>> Google worked here for me but usually when I have a problem, it
>> fails.
>> I guess Google treats you the same as me. lol I found this:
>>
>> http://forums.gentoo.org/viewtopic-t-294109.html
>>
>> That help any?
> Nope, this only happens in that specific situation, most things
> compile
> normally. I didn't see that post for that reason -- I was looking
> for
> something more specific.
Please provide the so-called config.log to see what happened (normally
located in
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/x86_64-pc-linux-gnu/libgomp/config.log).
--
Blog: http://gentooist.com
Twitter: http://twitter.com/blakawk
next prev parent reply other threads:[~2011-09-02 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 9:53 [gentoo-user] unable to compile gcc 4.5.3-r1 covici
2011-09-02 10:05 ` Dale
2011-09-02 10:16 ` covici
2011-09-02 10:44 ` Blakawk [this message]
2011-09-02 12:11 ` covici
2011-09-02 12:20 ` Blakawk
2011-09-02 14:46 ` covici
2011-09-02 14:05 ` Dale
2011-09-02 14:22 ` covici
2011-09-02 11:15 ` Dale
2011-09-02 11:56 ` Pandu Poluan
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=be94762792ffd1b41e2b30496ba57420@parizet.com \
--to=blakawk@gentooist.com \
--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