> > Host machine: RH 6.2 i386
> > Target Machine: Cirrus EDB7211 arm evaluation board running Linux.
>
> Ok. Is that an ARM 7500FE based board?
I don't recognize that number. The Cirrus manual says EP7211 chip, is that
what you're asking?
> arm-linux-gcc v2.95.2 is preferable.
Hopefully my arm-linux-gcc v2.91.66 will work? I'd rather tackle that some
other day.
> > The gdb and insight 5.0 I have is different (in the areas patched by
> > your patch file). Please send me a pointer to your 5.0 (gdb and insight) so
> > I can start from there with gdb then insight (which will hopefully match
> > your patch file). It sounds like redhat may have
> > their own different V5.0 floating around. That's very confusing.
>
> I get my source from the mainline CVS tree at sources.redhat.com for both gdb
> and insight. I update frequently. The patches I sent were against source
> updated on July 31 I believe.
I just grabbed the CVS tree now and the patch you sent still does not work.
It fails immediately (Hunk #1 FAILED at 1014.) I tried it in various place with
various -pN numbers just in case. I think if I'm in the gdb50/gdb area and use
-p0 it should work, right? I used "patch -p0 < ../gdbserv.patch"
But if I look at the patch file, if I'm interpreting it right, it's saying that at
line 1014 in gdb/configure.in, it should
find "if test "${target}" = ...", but in my copy of gdb/configure.in (including what
I just downloaded), line 1014 of gdb/configure.in is blank. The line it seems to
want to refer to is 952 in both what I just downloaded from CVS as well
as in the tar.gz file I downloaded before. Isn't that why the patch is failing?
> You shouldn't have to. What kernel and libc are on the Linux system? Is it ELF
> or a.out?
The server I'm using to build is 2.2.12-20smp.
The host debug i386 box is 2.2.14-5.0
The target arm board is 2.2.1
I'm using elf for everything.
How do I find the libc version?
-PaulK
