From: "Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>
To: kleine-budde@gmx.de
Cc: gdb mailing list <gdb@sources.redhat.com>, crossgcc@sources.redhat.com
Subject: Re: newbie question: need arm9 native gdb; how to compile gdb source for arm9?
Date: Mon, 27 Oct 2003 20:21:00 -0000 [thread overview]
Message-ID: <200310271423.13383.ken.wolcott@med.ge.com> (raw)
In-Reply-To: <20031027164136.GA21818@timberwolf.dyndns.org>
On Monday 27 October 2003 10:41, Marc Kleine-Budde wrote:
> On Mon, Oct 27, 2003 at 10:03:17AM -0600, Wolcott, Ken (MED, Compuware)
wrote:
> > I have an arm9 cross compiler tool chain created by Dan Kegel's
> > crosstool (http://www.kegel.com/crosstool/). My developers want a gdb
> > that can grok an arm9 coredump. They think that they need an arm9 gdb.
> > How do I compile an arm9 gdb from source? I know how to compile a native
> > gdb from source.
> >
> > configure --with-gcc=/mumble/../gcc where this is the path to the arm9
> > gcc doesn't result in an arm9 gdb.
>
> You need to compile your gdb on your host system by hand with:
>
> GNU_HOST=i686-unknown-linux-gnu \ (your host system touple)
> GNU_TARGET=arm-linux \ (or whatever your target touple is)
> ./configure \
> --build=$GNU_HOST \
> --host=$GNU_HOST \
> --target=$GNU_TARGET
>
> or use a sophisticated tool like (is here tool advertising allowed :)
> ptxdist...(http://ptxdist.sf.net) that can also be used with an external
> toolchain from dan's crosstool....please use the CVS version of ptxdist
>
> hth - Marc
Hi Marc;
Thanks for your help.
First tried the following:
../gdb-6.0/configure \
--host=i686-unknown-linux-gnu \
--build=i686-unknown-linux-gnu \
--target=arm-arm9-linux-gnu
But this failed due to the fact that my native gcc and friends are simplly
named "gcc", not "i686-unknown-linux-gnu"...
then I tried:
../gdb-6.0/configure --target=arm-arm9-linux-gnu
which seemed to work fine for a native gdb which (hopefully) understands arm9
corefiles, a crossgdb...
Then I tried:
../gdb-6.0/configure \
--host=arm-arm9-linux-gnu \
--build=i686-unknown-linux-gnu \
--target=arm-arm9-linux-gnu
because I want a native arm9 gdb they can run on the board itself.
This failed due to:
***********************************************************************************************
arm-arm9-linux-gnu-ar rc libiberty.a \
regex.o cplus-dem.o cp-demangle.o md5.o alloca.o argv.o choose-temp.o
concat.o dyn-string.o fdmatch.o fibheap.o floatformat.o fnmatch.o getopt.o
getopt1.o getpwd.o getruntime.o hashtab.o hex.o lbasename.o lrealpath.o
make-relative-prefix.o make-temp-file.o objalloc.o obstack.o partition.o
physmem.o pex-unix.o safe-ctype.o sort.o spaces.o splay-tree.o strerror.o
strsignal.o ternary.o xatexit.o xexit.o xmalloc.o xmemdup.o xstrdup.o
xstrerror.o mkstemps.o
make[1]: arm-arm9-linux-gnu-ar: Command not found
make[1]: *** [libiberty.a] Error 127
make[1]: Leaving directory
`/tuba_local/gdb_6.0/build_arm9_gdb_6.0_try2/libiberty'
make: *** [all-libiberty] Error 2
***********************************************************************************************
I don't have an arm-arm9-linux-gnu-ar executeable as a result of running
crosstool :-(
So, I guess I will try to get a cross compiler built via LSF (Linux From
Scratch at http://www.fr.linuxfromscratch.org/view/lfs-4.1/index.html) and
look further into crosstool scripts...
Ken
next prev parent reply other threads:[~2003-10-27 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 16:01 Wolcott, Ken (MED, Compuware)
2003-10-27 16:37 ` Dan Kegel
2003-10-27 16:41 ` Marc Kleine-Budde
2003-10-27 20:21 ` Wolcott, Ken (MED, Compuware) [this message]
2003-10-27 20:26 ` Dan Kegel
2003-10-27 20:50 ` Wolcott, Ken (MED, Compuware)
2003-10-27 21:12 ` Dan Kegel
2003-10-27 21:26 ` Wolcott, Ken (MED, Compuware)
2003-10-27 22:19 ` Dan Kegel
2003-10-27 22:40 ` Wolcott, Ken (MED, Compuware)
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=200310271423.13383.ken.wolcott@med.ge.com \
--to=ken.wolcott@med.ge.com \
--cc=crossgcc@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kleine-budde@gmx.de \
/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