This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Patch for arm-linux gdbserver



>Simply configure with --host=powerpc-linux.  Then run configure
>separately in the gdbserver directory if it did not get done, and make.
>
>Note that to do that first step $CC must be a cross compiler.
>
>Also note that PPC support for gdbserver is not currently available,
>and may go in in a few days depending on some other factors.

Ok, I built a m68k-linux compiler, and attempted:

CC=m68k-linux-gcc AR=m68k-linux-ar RANLIB=m68k-linux-ranlib LD=m68k-linux-ld /home/pbarada/work/cvs-wavemark/cross-linux-tools/gdb-5.0.93/configure --host=m68k-linux

To configure a m68k-linux version of gdbserver to be built on my x86
box.  Unfortunately configure fails.  From gleaning over the output, I
see two things, the first I'm not sure about and the second is a problem:

Created "Makefile" in /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-linux/m68k-linux/build-gdb using "mt-frag"
/home/pbarada/work/cvs-wavemark/cross-linux-tools/gdb-5.0.93/configure: ./if1747: cannot execute binary file
Configuring intl...
creating cache ../config.cache

I don't think configure should try to run a cross-compiled
executable...

checking compiler warning flags...  -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized
checking for cygwin... no
checking for tgetent in -lncurses... (cached) no
checking for tgetent in -lHcurses... no
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... (cached) no
checking for tgetent in -lcurses... (cached) no
checking for tgetent in -lterminfo... no
configure: error: Could not find a term library
Configure in /home/pbarada/work/cvs-wavemark/cross-linux-tools/obj-crap-linux/m68k-linux/build-gdb/gdb failed, exiting.

Since I'm not trying to run *gdb* on the target, but just *gdbserver*,
how can I get configure to ignore the missing term library and produce
a proper configuration?  This is the problem I had the last time I did
this, and ended up resorting to configureing it by *hand*.

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]