[PATCH] Move gdbserver to top level
Maciej W. Rozycki
macro@wdc.com
Mon Feb 17 14:21:00 GMT 2020
On Mon, 17 Feb 2020, Luis Machado wrote:
> Should --disable-gdb also imply --disable-gdbserver? Or should we be
> able to build gdbserver without building gdb (sounds a bit more complex)?
Nope, `--disable-gdb --enable-gdbserver' is typical for a cross-debug
environment, where you want to configure and build cross-GDB with
`--host=foo --target=bar' and `gdbserver' with `--host=bar'. Sometimes
your build environment may not even be capable to build native GDB with
`--host=bar', or your target system to run it, and in any case building
GDB takes a lot of processing time compared to `gdbserver'. So it would
be a waste of resources if we forced people to do that.
I build `gdbserver' by itself routinely, although I only did the minimum
to convert from the old layout, that is rather than calling `configure'
from gdb/gdbserver/ I now call it from gdbserver/. So far it has worked,
although with the new arrangement it probably qualifies as a hack, and may
stop working sometime.
Maciej
More information about the Gdb-patches
mailing list