This is the mail archive of the
mailing list for the Cygwin project.
RE: please update libXML (undefined references)
- From: "Robert Collins" <robert dot collins at syncretize dot net>
- To: "'Jason Tishler'" <jason at tishler dot net>,<cygwin-apps at cygwin dot com>
- Date: Mon, 22 Jul 2002 23:50:06 +1000
- Subject: RE: please update libXML (undefined references)
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Jason Tishler
> Sent: Monday, 22 July 2002 11:45 PM
> To: firstname.lastname@example.org
> Subject: Re: please update libXML (undefined references)
> > I've uploaded libxml regardless of this issue. A because the python
> > bindings are new, and B because cygfoo.dll is the standard
> for cygwin
> > .dll's. libtool is correct, python incorrect.
> Stating that Python is "incorrect" above is a little strong -- I would
> prefer "Python does not work that way" instead. Note that if one uses
> Distutils (i.e., the recommended way to build Python shared
> extension in
> a platform independent way), then the "right thing" will happen.
Granted. Not being a python user, I'm really very dependent on patches
to make libxml do The Right Thing.
It seems to me however, that libfoomod.dll will collide with mingw
pythons - I don't see how the logic for .dll naming should be different
for python than the platform as a whole.
Having said that, I'll happily accept a patch to the cygwin libxml
makefile.am's to get the correct file name, and if it's something that
is truly portable then I'll do what I can to get it included in the
stock libxml distribution as well.