This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: `gdbserver' in cross compiled builds
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Christoph Plattner <christoph dot plattner at gmx dot at>
- Cc: Andrew Cagney <ac131313 at cygnus dot com>, gdb at sources dot redhat dot com
- Date: Sun, 24 Feb 2002 11:37:12 -0500
- Subject: Re: `gdbserver' in cross compiled builds
- References: <3C5B3201.2F2FB670@gmx.at> <3C77D1F6.1020704@cygnus.com> <3C780221.CF27FBDA@gmx.at> <3C7808F9.3080106@cygnus.com> <3C78CDDC.DCEC0237@gmx.at>
On Sun, Feb 24, 2002 at 12:26:20PM +0100, Christoph Plattner wrote:
> Yes, that's clear for me. It is the same for glibc.
> With this point I have NO problems.
>
> The problem is simple in the tree setup !
>
> In my built (objects) tree, there is NO "gdbserver" subdirectory
> created by configuring, in the gdb source tree, the configuration
> cannot be done, because all generated files (configs, header files,
> etc) are written to the build tree (OBJECT tree).
Andrew explained this to you at least twice.... if the build tree is
for a cross debugger, you CAN NOT build gdbserver in it.
> So my problems are not in the config parameters, but simple, where
> (on which path) is called what ?
> And if I do some hacks manually, PPC support (for example) cannot be
> built. Why does the gdbserver directory work so bad ?
Use current CVS instead. I've spent months fixing this.
In fact, if you get current CVS, you can:
mkdir obj
cd obj
../src/gdb/gdbserver/configure
make
And build only the server.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer