Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Rakesh Kumar" <hkrakeshkumar@hotmail.com>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: Configuring GDB for ARM ELF
Date: Fri, 16 Feb 2007 12:54:00 -0000	[thread overview]
Message-ID: <BAY137-F26C039D3A8B2F2FB773E47AA950@phx.gbl> (raw)
In-Reply-To: <20070215115045.GB26850@caradoc.them.org>


Yeah i tried building it and it exits with the following error status....

make[1]: Entering directory `/home/rhk/gdb-6.6'
Configuring in ./libiberty
configure: loading cache ./config.cache
checking whether to enable maintainer-specific portions of Makefiles... no
checking for makeinfo... makeinfo --split-size=5000000
checking for perl... perl
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-ar... ar
checking for i686-pc-linux-gnu-ranlib... ranlib
checking for i686-pc-linux-gnu-gcc... gcc
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-libiberty] Error 1
make[1]: Leaving directory `/home/rhk/gdb-6.6'
make: *** [all] Error 2

_________________________________________________________________
Crave for a healthier lifestyle? Ask an expert 
http://content.msn.co.in/Lifestyle/AskExpert/Default07.htm


  parent reply	other threads:[~2007-02-16  5:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 11:51 Rakesh Kumar
2007-02-15 13:52 ` Daniel Jacobowitz
2007-02-15 15:46   ` Inder
2007-02-16 12:54   ` Rakesh Kumar [this message]
2007-02-16 15:14     ` Daniel Jacobowitz
2007-02-16 20:12       ` Supriya Sriraman
2007-02-21  1:11         ` Michael Snyder
2007-02-16  4:06 ` Michael Snyder

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=BAY137-F26C039D3A8B2F2FB773E47AA950@phx.gbl \
    --to=hkrakeshkumar@hotmail.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.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