I was having a problem trying to build and get running gdbserver 4.18
on i386 host and arm target,
so the redhat folks said try 5.0 and gave me a pointer. I downloaded
it and insight builds fine, but gdbserver does not. Then I tried
following
the gdbserver/README to build a vanilla i386/i386 version which
also didn't work (see below). I thought I posted
something about a week ago and received no response.
Anyway, I'm trying to build for the arm. I'm very disappointed to hear
that not only have you discontinued support for it, but you've actually
ripped some stuff out that used to support it. Somebody probably put
a good bit of time in to get it working, it seems a shame to undo that
effort (as well as it removes support for an important architecture).
Can this decision be reversed?
I did get it compiling and am about to try it on the arm (kludging the
gdbserver/i386 code to possibly work) which is how I got the 4.18
running on the target/arm before (as well as I had to fix some
incorrect arm definitions, for instance DECR_PC_AFTER_BREAK).
I was able to source-line debug with emacs over a serial line, but
I couldn't make it work with Insight nor over tcpip, which is why
the redhat/cygnus folks suggested V5.
I finally got V5 compiling and am about to try running it on the arm.
Ah, I *finally* got it to work with a vanilla compile also.
The gdbserver/README is incorrect, please fix it for next release.
It says to do '../../configure i386-none-lynx' and when I do that,
I get lots of header files missing. But if I do just '../../configure'
it works!
It also talks about 'Lynx', should that be Linux (which was my
assumption
and why I got into problems before)?
PaulK
