public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chilakaravikumar at yahoo dot co.in" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52007] configure: error: installation or configuration problem: C compiler cannot create executables
Date: Thu, 26 Jan 2012 10:41:00 -0000	[thread overview]
Message-ID: <bug-52007-4-DG1WDhDN3Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52007-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52007

--- Comment #2 from chilaka <chilakaravikumar at yahoo dot co.in> 2012-01-26 10:28:52 UTC ---
(In reply to comment #1)
> You should look into config.log to find out why it fails.  Also don't build in
> the source directory.  I bet you don't have all the right packages installed to
> use gcc.

config.log content

configure:630: checking host system type
configure:651: checking target system type
configure:669: checking build system type
configure:724: checking for a BSD compatible install
configure:777: checking whether ln works
configure:801: checking whether ln -s works
configure:1866: checking for gcc
configure:1979: checking whether the C compiler (gcc  ) works
configure:1995: gcc -o conftest    conftest.c  1>&5
./configure: line 1994: gcc: command not found
configure: failed program was:

#line 1990 "configure"
#include "confdefs.h"


  parent reply	other threads:[~2012-01-26 10:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 10:37 [Bug c/52007] New: " chilakaravikumar at yahoo dot co.in
2012-01-26 10:40 ` [Bug bootstrap/52007] " pinskia at gcc dot gnu.org
2012-01-26 10:41 ` chilakaravikumar at yahoo dot co.in [this message]
2012-01-26 10:41 ` pinskia at gcc dot gnu.org
2012-01-26 10:45 ` chilakaravikumar at yahoo dot co.in
2012-01-26 10:49 ` jakub at gcc dot gnu.org
2012-01-26 10:56 ` redi at gcc dot gnu.org
2012-01-26 11:01 ` redi at gcc dot gnu.org
2012-01-26 11:14 ` chilakaravikumar at yahoo dot co.in
2012-01-27 12:49 ` chilakaravikumar at yahoo dot co.in
2012-01-28  4:35 ` chilakaravikumar at yahoo dot co.in
2012-01-28  4:42 ` pinskia at gcc dot gnu.org
2012-01-28  9:52 ` chilakaravikumar at yahoo dot co.in
2012-05-31 18:59 ` bkoz at gcc dot gnu.org
2012-05-31 19:01 ` bkoz at gcc dot gnu.org
2012-05-31 19:40 ` bkoz at gcc dot gnu.org

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=bug-52007-4-DG1WDhDN3Y@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).