public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexander Wieder <eidotter@tempel.dynamischer-diskord.de>
To: gcc-help@gcc.gnu.org
Subject: Building GCC 4.2.0 fails on Linux x86-64
Date: Fri, 25 May 2007 11:38:00 -0000	[thread overview]
Message-ID: <4656C7AF.2070702@tempel.dynamischer-diskord.de> (raw)

Hi!

I tried to build GCC 4.2 (core and g++) on my linux box (Ubuntu 7.04,
amd64). Except a program-suffix and an install prefix, I used no
configure options. Building failed with the following messages:

> [...]
> checking for x86_64-unknown-linux-gnu-gcc... /home/alexx/tmp/gcc-build/./gcc/xgcc -B/home/alexx/tmp/gcc-build/./gcc/ -B/home/alexx/local/gcc/x86_64-unknown-linux-gnu/bin/ -B/home/alexx/local/gcc/x86_64-unknown-linux-gnu/lib/ -isystem /home/alexx/local/gcc/x86_64-unknown-linux-gnu/include -isystem /home/alexx/local/gcc/x86_64-unknown-linux-gnu/sys-include  -m32
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
> make[1]: *** [configure-target-libmudflap] Error 1
> make[1]: Leaving directory `/home/alexx/tmp/gcc-build'
> make: *** [all] Error 2

Has anyone an idea why GCC is obviously unable to produce runnable C
programs in my configuration?


Best regards,

Alexander Wieder


             reply	other threads:[~2007-05-25 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25 11:38 Alexander Wieder [this message]
2007-05-25 11:40 ` Andrew Haley
2007-05-25 14:13   ` Alexander Wieder
2007-05-25 14:49     ` Andrew Haley
2007-05-25 11:57 ` Thomas Mittelstaedt
2007-05-25 13:03 ` John Love-Jensen
2007-05-25 14:36   ` Alexander Wieder
2007-05-25 21:37 ` Brian Dessent
2007-05-26 11:14   ` Alexander Wieder

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=4656C7AF.2070702@tempel.dynamischer-diskord.de \
    --to=eidotter@tempel.dynamischer-diskord.de \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).