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 <dj...@collab.net> on 2006/01/30 04:55:39 UTC
Re: [Swig-devel] SWIG-1.3.28 release candidate
On 1/29/06, William S Fulton <ws...@fultondesigns.co.uk> wrote:
> A release candidate for SWIG-1.3.28 is online at
>
> http://www.swig.org/swig-1.3.28rc1.tar.gz (Unix source)
> http://www.swig.org/swigwin-1.3.28rc1.zip (Windows)
SWIG 1.3.28rc1 breaks compatibility with with Subversion 1.3.0. With
SWIG 1.3.25, the Python, Perl, and Ruby bindings all pass tests. With
SWIG 1.3.28, the Python bindings segfault, the Perl bindings throw
exceptions, and the Ruby bindings fail to compile. Perhaps it would be
a good idea to fix this before release?
Instructions to build Subversion 1.3.0 with SWIG 1.3.28:
- Download subversion-1.3.0.tar.gz
- Run make extraclean (to clean out the SWIG 1.3.25 headers shipped
with Subversion)
- Run make (to build Subversion)
To test Python bindings, type: make check-swig-py
To test Perl bindings, type: make check-swig-pl
To test Ruby bindings, type: make check-swig-rb
Cheers,
David
P.S. See http://svn.haxx.se/dev/archive-2005-11/0578.shtml for a patch
which works around bugs in SWIG 1.3.27, so that it can work with
Subversion. This fix does not help for SWIG 1.3.28, but it will be
released with Subversion 1.3.1.
--
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: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Marcelo Matus <mm...@acms.arizona.edu>.
Kouhei Sutou wrote:
>Hi Marcelo,
>
>I'm a maintainer of the Ruby bindings.
>
>In <43...@acms.arizona.edu>
> "Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate" on Thu, 02 Feb 2006 14:51:50 -0700,
> Marcelo Matus <mm...@acms.arizona.edu> wrote:
>
>
>
>>Ok, please try again, it seems perl and python are ok now. Ruby also
>>compiles but I am not
>>sure about the runtime test. I just get:
>>
>>
>
>
>
>>Loaded suite test
>>Started
>>........................................
>>/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/ruby/svn/util.rb:58:
>>[BUG] Segmentation fault
>>
>>
>
>Could you pass "---with-ruby-test-verbose=verbose" option to
>the configure script to get more information, re-run the
>configure script and re-run the runtime test for Ruby
>bindings?
>
>
>Regards,
>--
>kou
>
>
as David reported, the error occurs here:
....
test_prop(SvnFsTest): .
test_root(SvnFsTest): .
test_transaction(SvnFsTest): .
test_version(SvnFsTest): .
test_changed(SvnInfoTest):
/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/ruby/svn/util.rb:58:
[BUG] Segmentation fault
which somehow dispatchs the function svn_repos_node_from_baton defined
in node_tree.c
svn_repos_node_t *
svn_repos_node_from_baton (void *edit_baton)
{
struct edit_baton *eb = edit_baton;
return eb->node;
}
with a valid (from swig point of view) null value, resulting in the seg
fault observed.
Marcelo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Kouhei Sutou <ko...@cozmixng.org>.
Hi Marcelo,
I'm a maintainer of the Ruby bindings.
In <43...@acms.arizona.edu>
"Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate" on Thu, 02 Feb 2006 14:51:50 -0700,
Marcelo Matus <mm...@acms.arizona.edu> wrote:
> Ok, please try again, it seems perl and python are ok now. Ruby also
> compiles but I am not
> sure about the runtime test. I just get:
> Loaded suite test
> Started
> ........................................
> /home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/ruby/svn/util.rb:58:
> [BUG] Segmentation fault
Could you pass "---with-ruby-test-verbose=verbose" option to
the configure script to get more information, re-run the
configure script and re-run the runtime test for Ruby
bindings?
Regards,
--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
SWIG/Perl Status was: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Johannes Holzer <hl...@arcor.de>.
Am Donnerstag, 2. Februar 2006 09:36 schrieb Marcelo Matus:
> Any subversion/perl guru around?
>
Are the SWIG/Perl bindings really usable now? I tried to write small perl
scripts, but failed.... I was not able to use the SVN::Client Object
properly, e.g. $ctx->update2 (update more than one file) did not work, and
locking files in the repository (get the lock Token - svn lock) seems to be
broken too...
johannes
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Jason Stewart <ja...@gmail.com>.
Hey,
On 2/2/06, Marcelo Matus <mm...@acms.arizona.edu> wrote:
> - Perl keeps showing a strange error when loading SVN::Core, which is
> not swig generated:
>
> Failed 1/1 tests, 0.00% okay
> ../../../../../subversion/bindings/swig/perl/native/t/8lock............Use
> of uninitialized value in string eq at
> /home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
> line 410.
> (in cleanup) Undefined subroutine &SVN::Pool::apr_pool_destroy
> called at
> /home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
> line 417.
> Can't use an undefined value as a SCALAR reference at
> /home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
> line 376.
>
> Any subversion/perl guru around?
Well the cleanup code is having trouble after there was an error. It
looks like the first error was in Core.pm line 376 - I don't have the
code with me, so I'd need to see it to figure out more than that.
Cheers, jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by John Peacock <jp...@rowman.com>.
Marcelo Matus wrote:
> Failed 1/1 tests, 0.00% okay
> ../../../../../subversion/bindings/swig/perl/native/t/8lock............Use
> of uninitialized value in string eq at
> /home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
> line 410.
> (in cleanup) Undefined subroutine &SVN::Pool::apr_pool_destroy
> called at
> /home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
> line 417.
Install the new Perl bindings then rerun the tests. The Perl bindings can get
into a state that during testing the previously installed compiled XS files are
loaded, not the new in-process lib files. This may be what you are seeing...
HTH
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Marcelo Matus <mm...@acms.arizona.edu>.
Ok, last news on subversion 1.3.0 + swig 1.3.28:
- Python works fine, passes all the tests.
- Ruby passes almost all the tests, four or so fails
- Perl keeps showing a strange error when loading SVN::Core, which is
not swig generated:
Failed 1/1 tests, 0.00% okay
../../../../../subversion/bindings/swig/perl/native/t/8lock............Use
of uninitialized value in string eq at
/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
line 410.
(in cleanup) Undefined subroutine &SVN::Pool::apr_pool_destroy
called at
/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
line 417.
Can't use an undefined value as a SCALAR reference at
/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
line 376.
(in cleanup) Undefined subroutine &SVN::Pool::apr_pool_destroy
called at
/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
line 417.
Compilation failed in require at
../../../../../subversion/bindings/swig/perl/native/t/8lock.t line 6.
# Looks like your test died before it could output anything.
../../../../../subversion/bindings/swig/perl/native/t/8lock............dubious
Any subversion/perl guru around?
Marcelo
David James wrote:
>>I'll need some more historical context here, do you now if any other
>>SWIG version ever worked with subversion 1.3.0?, swig 1.3.26 for example?.
>>
>>
>The Python and Perl bindings build fine with SWIG 1.3.24, 1.3.25,
>1.3.26 and 1.3.27. The Ruby bindings build fine with 1.3.24 and 1.3.25
>but fail to compile with 1.3.26 and 1.3.27 due to a bug in SWIG's
>-external-runtime option. I have attached a patch to
>build/generator/swig/external_runtime.py in Subversion which works
>around this SWIG bug.
>
>SWIG 1.3.28rc1 does not work with any version of Subversion,
>unfortunately, even with this patch.
>
>On 1/30/06, Marcelo Matus <mm...@acms.arizona.edu> wrote:
>
>
>>Also, is there anyway to debug subversion + swig without having to
>>rebuild the
>>entire universe?, something just like
>>
>> make extraclean-swig
>>
>>
>
>Yes. Type the following:
> make extraclean-swig-py extraclean-swig-rb extraclean-swig-pl
>
>After this, rerun ./autogen.sh && ./configure. If you've already run
>make all, you don't need to do it again. Test the three sets of
>bindings using:
>1) make check-swig-py
>2) make check-swig-pl
>3) make check-swig-rb
>
>Cheers,
>
>David
>
>
>
>
>--
>David James -- http://www.cs.toronto.edu/~james
>
>
>------------------------------------------------------------------------
>
>--- build/generator/swig/external_runtime.py 2006/01/19 20:04:31 18174
>+++ build/generator/swig/external_runtime.py 2006/01/19 20:09:43 18175
>@@ -32,6 +32,8 @@
> self.checkout("perl5","perlrun.swg")
> self.checkout("ruby","rubydef.swg")
> self.checkout("ruby", "rubyhead.swg")
>+ if self.version() >= 103026:
>+ self.checkout("ruby", "rubytracking.swg")
>
> # Runtime library names
> runtime_library = {
>@@ -52,6 +54,18 @@
> out_file.close()
> else:
> _exec.run("%s -%s -external-runtime %s" % (self.swig_path, lang, out))
>+
>+ if lang == "ruby" and self.version() >= 103026:
>+ # SWIG 1.3.26-27 should include rubytracking.swg in their
>+ # external runtime, but they don't.
>+ # TODO: Find out whether this bug will be fixed in later versions
>+ # of SWIG.
>+ runtime = open(out, "r").read()
>+ tracking = open("%s/rubytracking.swg" % self.proxy_dir,"r").read()
>+ out_file = open(out, "w")
>+ out_file.write(tracking)
>+ out_file.write(runtime)
>+ out_file.close()
>
> # SWIG 1.3.25 and earlier use the wrong number of arguments in calls to
> # SWIG_GetModule. We fix this below.
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Marcelo Matus <mm...@acms.arizona.edu>.
Ok, please try again, it seems perl and python are ok now. Ruby also
compiles but I am not
sure about the runtime test. I just get:
Loaded suite test
Started
........................................
/home/mmatus/srcs/subversion-1.3.0/subversion/bindings/swig/ruby/svn/util.rb:58:
[BUG] Segmentation fault
which is the same when running with swig-1.3.27+patch. Note the
swig-1.3.28 doesn't need the patch.
Marcelo
David James wrote:
>>I'll need some more historical context here, do you now if any other
>>SWIG version ever worked with subversion 1.3.0?, swig 1.3.26 for example?.
>>
>>
>The Python and Perl bindings build fine with SWIG 1.3.24, 1.3.25,
>1.3.26 and 1.3.27. The Ruby bindings build fine with 1.3.24 and 1.3.25
>but fail to compile with 1.3.26 and 1.3.27 due to a bug in SWIG's
>-external-runtime option. I have attached a patch to
>build/generator/swig/external_runtime.py in Subversion which works
>around this SWIG bug.
>
>SWIG 1.3.28rc1 does not work with any version of Subversion,
>unfortunately, even with this patch.
>
>On 1/30/06, Marcelo Matus <mm...@acms.arizona.edu> wrote:
>
>
>>Also, is there anyway to debug subversion + swig without having to
>>rebuild the
>>entire universe?, something just like
>>
>> make extraclean-swig
>>
>>
>
>Yes. Type the following:
> make extraclean-swig-py extraclean-swig-rb extraclean-swig-pl
>
>After this, rerun ./autogen.sh && ./configure. If you've already run
>make all, you don't need to do it again. Test the three sets of
>bindings using:
>1) make check-swig-py
>2) make check-swig-pl
>3) make check-swig-rb
>
>Cheers,
>
>David
>
>
>
>
>--
>David James -- http://www.cs.toronto.edu/~james
>
>
>------------------------------------------------------------------------
>
>--- build/generator/swig/external_runtime.py 2006/01/19 20:04:31 18174
>+++ build/generator/swig/external_runtime.py 2006/01/19 20:09:43 18175
>@@ -32,6 +32,8 @@
> self.checkout("perl5","perlrun.swg")
> self.checkout("ruby","rubydef.swg")
> self.checkout("ruby", "rubyhead.swg")
>+ if self.version() >= 103026:
>+ self.checkout("ruby", "rubytracking.swg")
>
> # Runtime library names
> runtime_library = {
>@@ -52,6 +54,18 @@
> out_file.close()
> else:
> _exec.run("%s -%s -external-runtime %s" % (self.swig_path, lang, out))
>+
>+ if lang == "ruby" and self.version() >= 103026:
>+ # SWIG 1.3.26-27 should include rubytracking.swg in their
>+ # external runtime, but they don't.
>+ # TODO: Find out whether this bug will be fixed in later versions
>+ # of SWIG.
>+ runtime = open(out, "r").read()
>+ tracking = open("%s/rubytracking.swg" % self.proxy_dir,"r").read()
>+ out_file = open(out, "w")
>+ out_file.write(tracking)
>+ out_file.write(runtime)
>+ out_file.close()
>
> # SWIG 1.3.25 and earlier use the wrong number of arguments in calls to
> # SWIG_GetModule. We fix this below.
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by David James <dj...@collab.net>.
> I'll need some more historical context here, do you now if any other
> SWIG version ever worked with subversion 1.3.0?, swig 1.3.26 for example?.
The Python and Perl bindings build fine with SWIG 1.3.24, 1.3.25,
1.3.26 and 1.3.27. The Ruby bindings build fine with 1.3.24 and 1.3.25
but fail to compile with 1.3.26 and 1.3.27 due to a bug in SWIG's
-external-runtime option. I have attached a patch to
build/generator/swig/external_runtime.py in Subversion which works
around this SWIG bug.
SWIG 1.3.28rc1 does not work with any version of Subversion,
unfortunately, even with this patch.
On 1/30/06, Marcelo Matus <mm...@acms.arizona.edu> wrote:
> Also, is there anyway to debug subversion + swig without having to
> rebuild the
> entire universe?, something just like
>
> make extraclean-swig
Yes. Type the following:
make extraclean-swig-py extraclean-swig-rb extraclean-swig-pl
After this, rerun ./autogen.sh && ./configure. If you've already run
make all, you don't need to do it again. Test the three sets of
bindings using:
1) make check-swig-py
2) make check-swig-pl
3) make check-swig-rb
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Marcelo Matus <mm...@acms.arizona.edu>.
Also, is there anyway to debug subversion + swig without having to
rebuild the
entire universe?, something just like
make extraclean-swig
Marcelo
David James wrote:
>On 1/29/06, William S Fulton <ws...@fultondesigns.co.uk> wrote:
>
>
>>A release candidate for SWIG-1.3.28 is online at
>>
>> http://www.swig.org/swig-1.3.28rc1.tar.gz (Unix source)
>> http://www.swig.org/swigwin-1.3.28rc1.zip (Windows)
>>
>>
>
>SWIG 1.3.28rc1 breaks compatibility with with Subversion 1.3.0. With
>SWIG 1.3.25, the Python, Perl, and Ruby bindings all pass tests. With
>SWIG 1.3.28, the Python bindings segfault, the Perl bindings throw
>exceptions, and the Ruby bindings fail to compile. Perhaps it would be
>a good idea to fix this before release?
>
>Instructions to build Subversion 1.3.0 with SWIG 1.3.28:
>- Download subversion-1.3.0.tar.gz
>- Run make extraclean (to clean out the SWIG 1.3.25 headers shipped
>with Subversion)
>- Run make (to build Subversion)
>
>To test Python bindings, type: make check-swig-py
>To test Perl bindings, type: make check-swig-pl
>To test Ruby bindings, type: make check-swig-rb
>
>Cheers,
>
>David
>
>P.S. See http://svn.haxx.se/dev/archive-2005-11/0578.shtml for a patch
>which works around bugs in SWIG 1.3.27, so that it can work with
>Subversion. This fix does not help for SWIG 1.3.28, but it will be
>released with Subversion 1.3.1.
>
>
>--
>David James -- http://www.cs.toronto.edu/~james
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems? Stop! Download the new AJAX search engine that makes
>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmdÿk&kid3432&bid#0486&dat1642
>_______________________________________________
>Swig-user mailing list
>Swig-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/swig-user
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Swig-user] Re: [Swig-devel] SWIG-1.3.28 release candidate
Posted by Marcelo Matus <mm...@acms.arizona.edu>.
Hello David:
I'll need some more historical context here, do you now if any other
SWIG version
ever worked with subversion 1.3.0?, swig 1.3.26 for example?.
Marcelo
David James wrote:
>On 1/29/06, William S Fulton <ws...@fultondesigns.co.uk> wrote:
>
>
>>A release candidate for SWIG-1.3.28 is online at
>>
>> http://www.swig.org/swig-1.3.28rc1.tar.gz (Unix source)
>> http://www.swig.org/swigwin-1.3.28rc1.zip (Windows)
>>
>>
>
>SWIG 1.3.28rc1 breaks compatibility with with Subversion 1.3.0. With
>SWIG 1.3.25, the Python, Perl, and Ruby bindings all pass tests. With
>SWIG 1.3.28, the Python bindings segfault, the Perl bindings throw
>exceptions, and the Ruby bindings fail to compile. Perhaps it would be
>a good idea to fix this before release?
>
>Instructions to build Subversion 1.3.0 with SWIG 1.3.28:
>- Download subversion-1.3.0.tar.gz
>- Run make extraclean (to clean out the SWIG 1.3.25 headers shipped
>with Subversion)
>- Run make (to build Subversion)
>
>To test Python bindings, type: make check-swig-py
>To test Perl bindings, type: make check-swig-pl
>To test Ruby bindings, type: make check-swig-rb
>
>Cheers,
>
>David
>
>P.S. See http://svn.haxx.se/dev/archive-2005-11/0578.shtml for a patch
>which works around bugs in SWIG 1.3.27, so that it can work with
>Subversion. This fix does not help for SWIG 1.3.28, but it will be
>released with Subversion 1.3.1.
>
>
>--
>David James -- http://www.cs.toronto.edu/~james
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems? Stop! Download the new AJAX search engine that makes
>searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmdÿk&kid3432&bid#0486&dat1642
>_______________________________________________
>Swig-user mailing list
>Swig-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/swig-user
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org