You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by David James <ja...@gmail.com> on 2005/08/03 14:09:36 UTC

[PATCH] Encourage users to upgrade to SWIG 1.3.24

Currently, the installation documentation recommends first that users
install "SWIG 1.3.19 - 1.3.21, or SWIG 1.3.24 or above." In fact,
Subversion works best with SWIG 1.3.24 or above, but it can deal with
SWIG 1.3.19. As reported on several mailing lists, SWIG does not work
well with SWIG 1.3.20 or SWIG 1.3.21, due to bugs in SWIG_TypeQuery.
Therefore, I have updated the documentation to recommend other
versions of SWIG instead.

[[[

* subversion/bindings/swig/INSTALL:
  (BUILDING SWIG BINDINGS): Encourage users to upgrade to SWIG 1.3.24.
  SWIG 1.3.19 also works, but many users have reported problems with
  SWIG 1.3.20 and SWIG 1.3.21. Secondly, remind users to configure SWIG
  with --enable-static, if they are using SWIG 1.3.19 - 1.3.21.

]]]





-- 
David James -- http://www.cs.toronto.edu/~james

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by David James <ja...@gmail.com>.
On 8/8/05, Branko Čibej <br...@xbc.nu> wrote:> I'm beginning to seriously wonder if any of these shiny new Python> things have been tested on Windows?Not yet! I've tried to fix up the Windows build process in r15635,r15636, r15637, r15644, and r15645 on the python-bindings-improvementsbranch. I'd love to see some bug reports.
Cheers,
David
-- David James -- http://www.cs.toronto.edu/~james

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by Branko Čibej <br...@xbc.nu>.
David James wrote:

>OK, great! I've implemented and documented this new requirement in
>r15620 on the python-bindings-improvements branch. All developers who
>compile the bindings from trunk will now need SWIG 1.3.24 or better.
>  
>
I'm beginning to seriously wonder if any of these shiny new Python 
things have been tested on Windows?

-- Brane


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by David James <ja...@gmail.com>.
On 8/4/05, Daniel L. Rall <dl...@finemaltcoding.com> wrote:
> On Thu, 04 Aug 2005, David James wrote:
> 
> > > > There are also more severe issues with Subversion's support for SWIG
> > > > 1.3.20 and 1.3.21, which have not yet been addressed. See <
> > > > http://svn.haxx.se/dev/archive-2005-08/0053.shtml >. For this reason,
> > > > I think it would be a good idea to encourage users to upgrade to newer
> > > > versions of SWIG, if they can.
> > > I agree with this, though. I think we ought to raise our minimum version to
> > > 1.3.24.
> > Great! If we are moving to SWIG 1.3.24, there is no need to discuss
> > the problems with SWIG 1.3.21 in the INSTALL file. Would you be happy
> > with my patch if I instead deleted the information on older versions
> > of SWIG? I can also patch the swig.m4 file to disallow SWIG 1.3.19
> > through 1.3.21, if you think this is a good idea.
> >
> > On the python-bindings-improvements branch, I had to copy and paste a
> > large section of code from SWIG in order to support new SWIG features
> > on old SWIG versions, such as 1.3.19. If we forced users to upgrade to
> > SWIG 1.3.24, this code would not be necessary.
> 
> This sounds like a reasonable requirement for the 1.3.x line.

OK, great! I've implemented and documented this new requirement in
r15620 on the python-bindings-improvements branch. All developers who
compile the bindings from trunk will now need SWIG 1.3.24 or better.

Further, if you run autogen.sh in release mode, it will generate
standalone "C" files for all of the SWIG files, so that SWIG will not
be a dependency. In order to get this working, I had to run the Perl
"vtable wrapper code generator" from inside autogen.sh, so that the
vtable wrapper code would be included in the standalone "C" files. (I
reimplemented the vtable wrapper code generator in Python so that
users of all the bindings could benefit without adding Perl as a
dependency.)

See the change at:
http://svn.collab.net/viewcvs/svn?view=rev&rev=15620

Please review the change and let me know if you have any feedback.
This change in particular will need to be reviewed carefully because
it makes big changes to our build process.

Cheers,

David

-- 
David James -- http://www.cs.toronto.edu/~james

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by "Daniel L. Rall" <dl...@finemaltcoding.com>.
On Thu, 04 Aug 2005, David James wrote:

> > > There are also more severe issues with Subversion's support for SWIG
> > > 1.3.20 and 1.3.21, which have not yet been addressed. See <
> > > http://svn.haxx.se/dev/archive-2005-08/0053.shtml >. For this reason,
> > > I think it would be a good idea to encourage users to upgrade to newer
> > > versions of SWIG, if they can.
> > I agree with this, though. I think we ought to raise our minimum version to
> > 1.3.24.
> Great! If we are moving to SWIG 1.3.24, there is no need to discuss
> the problems with SWIG 1.3.21 in the INSTALL file. Would you be happy
> with my patch if I instead deleted the information on older versions
> of SWIG? I can also patch the swig.m4 file to disallow SWIG 1.3.19
> through 1.3.21, if you think this is a good idea.
> 
> On the python-bindings-improvements branch, I had to copy and paste a
> large section of code from SWIG in order to support new SWIG features
> on old SWIG versions, such as 1.3.19. If we forced users to upgrade to
> SWIG 1.3.24, this code would not be necessary.

This sounds like a reasonable requirement for the 1.3.x line.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by David James <ja...@gmail.com>.
> > There are also more severe issues with Subversion's support for SWIG
> > 1.3.20 and 1.3.21, which have not yet been addressed. See <
> > http://svn.haxx.se/dev/archive-2005-08/0053.shtml >. For this reason,
> > I think it would be a good idea to encourage users to upgrade to newer
> > versions of SWIG, if they can.
> I agree with this, though. I think we ought to raise our minimum version to
> 1.3.24.
Great! If we are moving to SWIG 1.3.24, there is no need to discuss
the problems with SWIG 1.3.21 in the INSTALL file. Would you be happy
with my patch if I instead deleted the information on older versions
of SWIG? I can also patch the swig.m4 file to disallow SWIG 1.3.19
through 1.3.21, if you think this is a good idea.

On the python-bindings-improvements branch, I had to copy and paste a
large section of code from SWIG in order to support new SWIG features
on old SWIG versions, such as 1.3.19. If we forced users to upgrade to
SWIG 1.3.24, this code would not be necessary.

Cheers,

David

-- 
David James -- http://www.cs.toronto.edu/~james

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by Max Bowsher <ma...@ukf.net>.
David James wrote:
> On 8/4/05, Max Bowsher <ma...@ukf.net> wrote:
>> I _know_ I've had a working python bindings set using SWIG 1.3.21 and
>> *--disable-static* in the past.
> Perhaps the requirements of the Subversion build have changed?
>
> If I build SWIG 1.3.21 without the "--enable-static" flag, it does not
> install "libswigpy.a". On my machine, with default configure settings,
> Subversion needs "libswigpy.a" to build. Newer versions of SWIG do not
> exhibit this problem.

Swig 1.3.21 should be built with:

./configure <stuff>
make
make runtime
make install
make install-runtime


> There are also more severe issues with Subversion's support for SWIG
> 1.3.20 and 1.3.21, which have not yet been addressed. See <
> http://svn.haxx.se/dev/archive-2005-08/0053.shtml >. For this reason,
> I think it would be a good idea to encourage users to upgrade to newer
> versions of SWIG, if they can.

I agree with this, though. I think we ought to raise our minimum version to 
1.3.24.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by David James <ja...@gmail.com>.
On 8/4/05, Max Bowsher <ma...@ukf.net> wrote:
> I _know_ I've had a working python bindings set using SWIG 1.3.21 and
> *--disable-static* in the past.
Perhaps the requirements of the Subversion build have changed?

If I build SWIG 1.3.21 without the "--enable-static" flag, it does not
install "libswigpy.a". On my machine, with default configure settings,
Subversion needs "libswigpy.a" to build. Newer versions of SWIG do not
exhibit this problem.

In many cases, users have a different version of SWIG already
installed on their machine which has "libswigpy.a". If users do not
use the --enable-static flag, then Subversion will skip over the new
version of SWIG that they just installed (because it didn't install
libswigpy.a), and use the older version of libswigpy.a instead. I
experienced this problem on my system.

There are also more severe issues with Subversion's support for SWIG
1.3.20 and 1.3.21, which have not yet been addressed. See <
http://svn.haxx.se/dev/archive-2005-08/0053.shtml >. For this reason,
I think it would be a good idea to encourage users to upgrade to newer
versions of SWIG, if they can.

Cheers,

David


-- 
David James -- http://www.cs.toronto.edu/~james

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: [PATCH] Encourage users to upgrade to SWIG 1.3.24

Posted by Max Bowsher <ma...@ukf.net>.
David James wrote:
> Currently, the installation documentation recommends first that users
> install "SWIG 1.3.19 - 1.3.21, or SWIG 1.3.24 or above." In fact,
> Subversion works best with SWIG 1.3.24 or above, but it can deal with
> SWIG 1.3.19. As reported on several mailing lists, SWIG does not work
> well with SWIG 1.3.20 or SWIG 1.3.21, due to bugs in SWIG_TypeQuery.
> Therefore, I have updated the documentation to recommend other
> versions of SWIG instead.
>
> [[[
>
> * subversion/bindings/swig/INSTALL:
>   (BUILDING SWIG BINDINGS): Encourage users to upgrade to SWIG 1.3.24.
>   SWIG 1.3.19 also works, but many users have reported problems with
>   SWIG 1.3.20 and SWIG 1.3.21. Secondly, remind users to configure SWIG
>   with --enable-static, if they are using SWIG 1.3.19 - 1.3.21.
>
> ]]]

Um?
I _know_ I've had a working python bindings set using SWIG 1.3.21 and 
*--disable-static* in the past.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org