[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: r8368 and SWIG version requirements.

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2004-01-19 03:28:40 CET

On Sun, 18 Jan 2004, Ben Reser wrote:

> I'm going to veto r8368 to force us to discuss the version requirements
> of SWIG.
> Last night I worked with David to figure out some perl bindings issues
> he had on RedHat. He was having trouble getting SWIG 1.3.16 to build
> with perl binding support. It works fine for him with 1.3.19. But I'm
> not convinced we really require 1.3.19.
> Right now the configure script is accepting 1.3.16, 1.3.17 and 1.3.19.
> There's a change pending to accept 1.3.20 and 1.3.21. The configure
> script however, recommends 1.3.19 and so does our documentation.
> So if we really require 1.3.19 then we need to make the configure
> scripts say that. In that case I consider r8368 incomplete.
> If 1.3.19 is not required than r8368 is just wrong.
> I'll try to find some time tonight or tomorrow to play with 1.3.16 and
> see if we really work with it or not.
> If we really need 1.3.19 then I'll merge r8368 into the #1690 issue and
> update the patch to accept only 1.3.19. And remove my veto.

Fair enough. I'll just note that this is the first time I've tried to
add the perl bindings to the RPM packages, and SWIG 1.3.16 builds the
python bindings fine. I'm just currently encountering compile problems
when I try to add the perl bindings.

David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 19 03:40:24 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.