Mail Archives: djgpp/2009/05/02/08:19:35
> From: Rugxulo <rugxulo AT gmail DOT com>
> Date: Sat, 2 May 2009 04:16:34 -0700 (PDT)
>=20
> On May 2, 5:09=A0am, Eli Zaretskii <e DOT DOT DOT AT gnu DOT org> wrote:
> >
> > The last version of GDB ported to DJGPP was 6.1. =A0That was 5 ye=
ars
> > ago. =A0GDB 6.1 also has a couple of nasty bugs (for example, the
> > `finish' command triggers an internal GDB error).
>=20
> It also doesn't like "info all-regs", IIRC.
Yes, for the same reason: it thinks DJGPP supports SSE registers.
> > GDB 7.0 will support Python scripting, a powerful new feature. =
=A0To get
> > that working with DJGPP, I need a working port of libpython. =
=A0The only
> > DOS port of Python I could find was built with DJGPP v2.04, so it=
is
> > incompatible with what I use (v2.03). =A0On top of that, there's =
no
> > libpython.a in that port, only the binary of the Python interpret=
er.
>=20
> Does Python need libpython built to bootstrap itself?
I don't know. But that's not what I meant. GDB needs to be linked
against libpython.a, to support the Python scripting. And the only
DJGPP port of Python does not have the library, only the .exe of the
stand-alone interpreter.
> (BTW, are you willing to use libsupp? It might help.)
I didn't intend doing so, at this stage. I didn't have any real
problems building GDB with the stock djdev203, so this isn't a high
priority.
> > Another set of new features in GDB 7.0 is based on libexpat, a li=
brary
> > for parsing XML files. =A0I couldn't find a DJGPP port of it.
>=20
> Here it is (I think) although I've never used it:
>=20
> http://gd.tuwien.ac.at/pc/dos/djgpp/current/v2tk/expat20s.zip
> http://gd.tuwien.ac.at/pc/dos/djgpp/current/v2tk/expat20b.zip
Oops, I have that on my disk, as part of the mirror of DJGPP packages
I have here. Thanks for pointing that out.
> Python is quite popular, so hopefully somebody will step up to help
> you with it.
I surely hope so.
- Raw text -