From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: drow@mvista.com
Cc: bgat@billgatliff.com, Keith.Walker@arm.com,
crossgcc@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Patch for arm-linux gdbserver
Date: Fri, 01 Feb 2002 10:34:00 -0000 [thread overview]
Message-ID: <200202011833.g11IXoZ15188@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <20020201103605.B14977@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 1 Feb 2002 10:36:05 -0500)
>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)
next prev parent reply other threads:[~2002-02-01 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 9:36 William A. Gatliff
[not found] ` <4.1.20020131181535.00b40f00@mhsun1.maidenhead.arm.com>
2002-01-31 13:36 ` William A. Gatliff
2002-01-31 15:10 ` Daniel Jacobowitz
2002-01-31 15:21 ` Peter Barada
2002-02-01 7:36 ` Daniel Jacobowitz
2002-02-01 10:34 ` Peter Barada [this message]
2002-02-01 11:03 ` William A. Gatliff
2002-02-01 11:30 ` Daniel Jacobowitz
2002-02-01 12:02 ` William A. Gatliff
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=200202011833.g11IXoZ15188@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=Keith.Walker@arm.com \
--cc=bgat@billgatliff.com \
--cc=crossgcc@sources.redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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