Thanks!
I'm missing a number of things (including now most of my marbles :-)...
I was trying to build using ../../configure arm-linux-elf which as
I understand it, should configure the arm target to talk with Linux, right?
Then I used 'make CC=arm-elf-gcc'
I did pull down the latest 5.0 sources already. I had already gotten
v20000314 to compile and more-or-less work (I could source-line
single step under emacs on Linux/x86 targeting the arm,
but I couldn't get the gui to work), and somebody suggested
I go to the latest, maybe that would fix problems I saw with the gui.
When you say arm-*-* is obsolete as host, it should still be OK for
target, right?
I'm pretty sure the DECR_PC... is wrong for ARM and so if nobody
changes that, I don't see any way that what's there would work for ARM.
Where I'm at now is stuck in the morass of spagetti header files,
unable to get a good build with V5. Many header files are missing from
the gdb tree, but are required by remote-utils.c .
So I add in the normal Linux include paths manually to the Makefile
(yes, I know if I do another configure they'll get stepped on) but
that doesn't work either, lots of missing symbols and then
multiply-defined symbols (thereby balancing each other out :-).
I tried copying and editing the few header files that are called,
but each one of those points to 5 other ones so it's a complete
mess. There's got to be a better way to do this.
I somehow stumbled into making insight-20000314 work, but
evidently I'm doing something different, or else more stuff has
been changed and broken things since that release. I'll go back
to see what the difference is between that build that worked and
what I'm going for V5. But getting 20000314 to build right was
no cake-walk either for similar reasons. I remember having to
copy header files and make edits in them.
Any help would be appreciated.
-PaulK
Andrew Cagney wrote:
> Paul Kinzelman wrote:
> >
> > I found that somebody inserted the string "# OBSOLETE" in the
> > .../gdb/config/arm/arm.mt and .mh files, thereby breaking the
> > build for ARM.
> >
> > Also, there are lots of header files missing when I do a standard
> > config and build, the -I path probably needs fixing:
> > stdio.h, errno.h, unistd.h, stdlib.h, setjmp.h, string.h, endian.h
> >
> > And lastly (at least as far as I've gotten), the
> > DECR_PC_AFTER_BREAK definition needs to be 4 in tm-arm.h
> > -PaulK
>
> Which OS? I believe ARM Linux works for instance.
>
> In the NEWS file is the information:
>
> * OBSOLETE configurations
>
> Altos 3068 m68*-altos-*
> Convex c1-*-*, c2-*-*
> Pyramid pyramid-*-*
> ARM RISCix arm-*-* (as host)
> Tahoe tahoe-*-*
>
> Configurations that have been declared obsolete will be commented out,
> but the code will be left in place. If there is no activity to revive
> these configurations before the next release of GDB, the sources will
> be permanently REMOVED.
>
> No one has been activly maintaining ARM on RISCix for some time and the
> code is known to have suffered serious bit rot.
>
> Could I strongly encourage you to pull in the latest GDB snapshot (see
> http://sources.redhat.com/gdb/) and look at reviving this target.
>
> Andrew
