Re: new libxml2 / libxslt packages?

[Robert Collins <rbcollins at cygwin dot com>]

On Sat, 2003-02-08 at 15:09, Alex Lancaster wrote:


> RC> Check the changelog :]. Yes, I'm on the libx* lists, and routinely
> RC> feed some patches back after each cygwin release.
> 
> Mea culpa.  I should have checked the ChangeLog before I suggested
> that... :-{ I actually did download the source w/ Cygwin patches as
> you suggested below, but I guess I wondered why those patches weren't
> already in the source package if you had been feeding them back.  I
> suppose those patches have been rolled into the current versions?

The bulk of the patches are cygwin-specific *AND* not HEAD appropriate.
For instance:
Fixing VPATH builds because Daniel (IMO foolishly) distributes configure
generated files.
Fixing Makefile.am code to be compatible with the needed libtool and
automake for cygwin.

The rest I send in.


> I did that, but I was wondering whether you had patches against the
> current xmlsoft.org released versions that you need to test.  

Nope. I need to forward port the patches.

> In the case of libxslt, would you expect the patches against 1.0.13 to
> apply cleanly to 1.0.25?  I'm confused Wouldn't those patches already
> be well and truly rolled back into libxslt itself by now?

See above. In short, we won't ever get a OOTB build for cygwin until the
libxml versions of autotools gets updated to autoconf 2.5x, automake
1.6/1.7 and libtool 1.5.

> RC> The problem is that libxml and libxslt need very recent autotools,
> RC> and daniel doesn't like autotools - thus updates rarely. In fact,
> RC> until recently the libtool we need wasn't even in pre-release
> RC> mode.
> 
> I'm confused, does he need the newer autotool(s) to build the
> packages, or does Cygwin need them?  Are there autoconf/automake
> macros that he should be using in configure.in/Makefile.am that are
> required for Cygwin?

Cygwin needs them for the library support. No extra macros are needed.

> >> Does the building libxslt with Python bindings simply not work, or
> >> are these bugs that show up after it's built and installed.
> 
> RC> I don't think the libxslt python bindings existed when I last
> RC> updated the package :/.
> 
> I see.  OK, to just get the damn things to compile under Cygwin,
> should I even attempt to apply the old patches against the new sources
> and try and compile that, or is that just a non-starter?

Here's a recipe:
Start with the xmlsoft tarballs and my patches.
Use difftools to separate out the unified patches into one patch per
file.
Remove all the Makefile.in patches.
Now apply all the other patches.

Rob
-- 
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part