From: "Rakesh Kumar" <hkrakeshkumar@hotmail.com>
To: gdb@sourceware.org
Subject: Configuring GDB for ARM ELF
Date: Thu, 15 Feb 2007 11:51:00 -0000 [thread overview]
Message-ID: <BAY137-F1101B6BAAAF02EA4A78457AA960@phx.gbl> (raw)
Hi,
I used the above command to configure GDB for ARM
./configure --host=i686-pc-linux-gnu --target=arm-elf
But i get the following after running the command....
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... arm-unknown-elf
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for gnatbind... gnatbind
checking whether compiler driver understands Ada... yes
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1
$$f
2
checking for correct version of gmp.h... yes
checking for correct version of mpfr.h... no
checking for bison... bison -y
checking for bison... bison
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for expect... expect
checking for runtest... runtest
checking for i686-pc-linux-gnu-ar... no
checking for ar... ar
checking for i686-pc-linux-gnu-as... no
checking for as... as
checking for i686-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking for i686-pc-linux-gnu-ld... no
checking for ld... ld
checking for i686-pc-linux-gnu-lipo... no
checking for lipo... no
checking for i686-pc-linux-gnu-nm... no
checking for nm... nm
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for i686-pc-linux-gnu-windres... no
checking for windres... no
checking for i686-pc-linux-gnu-objcopy... no
checking for objcopy... objcopy
checking for i686-pc-linux-gnu-objdump... no
checking for objdump... objdump
checking for arm-elf-cc... no
checking for arm-elf-gcc... no
checking for arm-elf-c++... no
checking for arm-elf-g++... no
checking for arm-elf-cxx... no
checking for arm-elf-gxx... no
checking for arm-elf-gcc... no
checking for arm-elf-gcj... no
checking for arm-elf-gfortran... no
checking for ar... no
checking for arm-elf-ar... no
checking for as... no
checking for arm-elf-as... no
checking for dlltool... no
checking for arm-elf-dlltool... no
checking for ld... no
checking for arm-elf-ld... no
checking for lipo... no
checking for arm-elf-lipo... no
checking for nm... no
checking for arm-elf-nm... no
checking for objdump... no
checking for arm-elf-objdump... no
checking for ranlib... no
checking for arm-elf-ranlib... no
checking for strip... no
checking for arm-elf-strip... no
checking for windres... no
checking for arm-elf-windres... no
checking where to find the target ar... pre-installed
checking where to find the target as... pre-installed
checking where to find the target cc... pre-installed
checking where to find the target c++... pre-installed
checking where to find the target c++ for libstdc++... pre-installed
checking where to find the target dlltool... pre-installed
checking where to find the target gcc... pre-installed
checking where to find the target gcj... pre-installed
checking where to find the target gfortran... pre-installed
checking where to find the target ld... pre-installed
checking where to find the target lipo... pre-installed
checking where to find the target nm... pre-installed
checking where to find the target objdump... pre-installed
checking where to find the target ranlib... pre-installed
checking where to find the target strip... pre-installed
checking where to find the target windres... pre-installed
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether -fkeep-inline-functions is supported... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
As you have observed I'm getting NO for most of the dependencies......
How do i get the dependencies?
Thanks and regards,
Rakesh Kumar H.K.
_________________________________________________________________
Spice up your IM conversations. New, colorful and animated emoticons. Get
chatting! http://server1.msn.co.in/SP05/emoticons/
next reply other threads:[~2007-02-15 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 11:51 Rakesh Kumar [this message]
2007-02-15 13:52 ` Daniel Jacobowitz
2007-02-15 15:46 ` Inder
2007-02-16 12:54 ` Rakesh Kumar
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-F1101B6BAAAF02EA4A78457AA960@phx.gbl \
--to=hkrakeshkumar@hotmail.com \
--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