>
> Back in December of 2001, Nish Deodhar reported the same problem with gdb
> 5.1, and talked about the changes he made to get it to compile. Jim Blandy
> from Red Hat/Cygnus asked him a few questions about what he'd done, but the
> gdb 5.2.1, and 5.3 source doesn't reflect those changes. So, I have to
> assume that they weren't considered a good fix by the gdb maintainers.
>
> I manually re-compiled the module with --save-temps. If anyone could help
> me figure out what needs to be done to get this to compile, I would
> appreciate it.
>
> Thanks,
>
> Mark Post
>
Mark,
The problem is that one of the opaque types isn't quite as opaque
as it should be.
We've sent several gdb fixes into the gdb maintainers for the 390
and z/Series gdb... they actually have incorporated many of them
(but, there is a significant legal hurdle to overcome, which makes
gdb progress quite slow.) However, as I understand it, the gdb
maintainers have not changed this one... they view it as a
deficiency in the s390 and z/Series Linux implementation (some type
defined by the kernel which is defined differently on mainframe
linux than other linuxes.)
So - for us, to get gdb to compile cleanly, we had to make many
local modifications... if you just go grab the gdb sources,
it won't compile on mainframe linux.
- Dave Rivers -
--
[EMAIL PROTECTED] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
