Re: newbie question: need arm9 native gdb; how to compile gdb source for arm9?

["Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>]

Hi Dan;

#!/bin/bash

export
PATH="/tuba_local/crosstool/crosstool-0.24/result/arm-arm9-linux-gnu/gcc-3.2.1-glibc-2.3.2/bin:/sbin:/usr/sbin:/usr/bin:/bin"

...
configure calls
...

Ken


On Monday 27 October 2003 17:08, Dan Kegel wrote:
> Hi Ken,
> that's odd; all that's between the ***'s in your message are aa bunch
> of configure runs.  You didn't actually build anything.
> - Dan
>
> Wolcott, Ken (MED, Compuware) wrote:
> > Hi Dan;
> >
> >   I did "export PATH=stuff:"
> >
> >   The script is between the lines of asterisks...
> >
> >   The most recent run can't find nm either :-(
> >
> > Ken
> >
> > On Monday 27 October 2003 16:00, Dan Kegel wrote:
> >>That all looks fine.  Can't imagine why it didn't find ar.
> >>
> >>Did you also set PATH when doing the 'make'?  All you show
> >>in the script is the 'configure's.
> >>- Dan
> >>
> >>Wolcott, Ken (MED, Compuware) wrote:
> >>>Hi Dan;
> >>>
> >>>  This is my script to build gdb:
> >>>
> >>>**************************************************************
> >>>#!/bin/bash
> >>>
> >>>
> >>>export
> >>>PATH="/tuba_local/crosstool/crosstool-0.24/result/arm-arm9-linux-gnu/gcc
> >>>- 3.2.1-glibc-2.3.2/bin:/sbin:/usr/sbin:/usr/bin:/bin"
> >>>
> >>># This builds an arm9 cross gdb...
> >>># ../gdb-6.0/configure --target=arm-arm9-linux-gnu
> >>>
> >>># This builds a native arm9 gdb using i686-unknown-linux-gnu to build
> >>>it... # ../gdb-6.0/configure --host=arm-arm9-linux-gnu
> >>>--build=i686-unknown-linux-gnu --target=arm-arm9-linux-gnu
> >>>
> >>># only use arm9 tools?
> >>>../gdb-6.0/configure --host=arm-arm9-linux-gnu
> >>> --build=arm-arm9-linux-gnu --target=arm-arm9-linux-gnu
> >>>**************************************************************
> >>>
> >>>This is the output of the ls:
> >>>**************************************************************
> >>>tuba:/tuba_local/gdb_6.0/build_arm9_gdb_6.0_try3> ls
> >>>/tuba_local/crosstool/crosstool-0.24/result/arm-arm9-linux-gnu/gcc-3.2.1
> >>>- glibc-2.3.2/bin arm-arm9-linux-gnu-addr2line 
> >>> arm-arm9-linux-gnu-c++filt arm-arm9-linux-gnu-gccbug 
> >>> arm-arm9-linux-gnu-objcopy
> >>>arm-arm9-linux-gnu-size
> >>>arm-arm9-linux-gnu-ar         arm-arm9-linux-gnu-cpp
> >>>arm-arm9-linux-gnu-gcov    arm-arm9-linux-gnu-objdump
> >>>arm-arm9-linux-gnu-strings
> >>>arm-arm9-linux-gnu-as         arm-arm9-linux-gnu-g++
> >>>arm-arm9-linux-gnu-ld      arm-arm9-linux-gnu-ranlib
> >>>arm-arm9-linux-gnu-strip
> >>>arm-arm9-linux-gnu-c++        arm-arm9-linux-gnu-gcc
> >>>arm-arm9-linux-gnu-nm      arm-arm9-linux-gnu-readelf
> >>>tuba:/tuba_local/gdb_6.0/build_arm9_gdb_6.0_try3>
> >>>**************************************************************
> >>>
> >>>Thanks,
> >>>Ken
> >>>
> >>>On Monday 27 October 2003 15:15, Dan Kegel wrote:
> >>>>Wolcott, Ken (MED, Compuware) wrote:
> >>>>>../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 :-(
> >>>>
> >>>>What *do* you have as a result of running crosstool?
> >>>>Can you do an 'ls' in the bin directory of the toolchain?
> >>>>Sounds like maybe you just have a path set wrong...
> >>>>
> >>>>In other words, don't panic, your toolchain is probably fine...
> >>>>- Da
> >
> > n

-- 
Kenneth A. Wolcott
Consultant, Clinical Systems Engineering
GE Medical Systems Information Technologies
8200 West Tower Avenue, Milwaukee, WI  53223
Phone:  414/362-2720 
Email:  Ken.Wolcott@med.ge.com