From mboxrd@z Thu Jan  1 00:00:00 1970
From: Philip Blundell <philb@gnu.org>
To: gdb@sources.redhat.com
Subject: gdbserver in configure scripts
Date: Sat, 09 Sep 2000 13:40:00 -0000
Message-id: <E13XrSH-0006lh-00@kings-cross.london.uk.eu.org>
X-SW-Source: 2000-09/msg00093.html

It doesn't currently work to build a cross GDB targeting, say, m68k-linux (or 
any other gdbserver-enabled platform).  The configure script fails with:

linking /usr/src/sourceware/src/gdb/gdbserver/../config/nm-empty.h to nm.h
configure: error: /usr/src/sourceware/src/gdb/gdbserver/../config/nm-empty.h: File not found
configure: error: /usr/src/sourceware/src/gdb/gdbserver/configure failed for gdbserver

This would be prevented by the following commented-out code in configure.in:

# else
# GDBserver is only useful in a "native" enviroment
# configdirs=`echo $configdirs | sed 's/gdbserver//'`

Does anybody know of a reason why this code should not be enabled?

(I'm not sure what the story is with nm-empty.h.  I don't have one in my tree; 
the ChangeLog suggests that it used to exist, but I didn't see anything 
referring to its removal.)

Thanks

p.