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

Re: Build Error when compiling python binding on Windows with VC6 at r25159 or later

From: David James <james_at_cs.toronto.edu>
Date: 2007-05-30 16:12:27 CEST

On 5/28/07, Joe Swatosh <joe.swatosh@gmail.com> wrote:
> Hi
>
> On 5/27/07, Masaru Tsuchiyama <m.tmatma@gmail.com> wrote:
> > Hi
> >
> > > I'm no expert, but it sounds like it may be a SWIG version issue? I
> > > had a lot of long long issues building the Ruby bindings with a SWIG
> > > versions later than 1.3.24.
> > I'm using swig 1.3.31. It is not Ruby bindings but Python bindings
> > what I mention.
> >
> I understood, I was just mentioning I got the same error when I first started
> trying to get the Ruby bindings to build.
>
> > r25158 is the revision at which merge-sensitive-log branch was merged.
> > I think it breaks building python bindings.
> >
>
> apr_uint64_t is now used in the Subversion headers. The patch below fixes the
> build errors for me, but the tests don't pass.

Hi Joe,

In the Ruby bindings, I see that you used "%clear long long" to clear
out the old SWIG typemaps. Does this work in the Python bindings? If
so, perhaps we should get rid of this hack to python.swg altogether
and just use %clear long long and/or %clear unsigned long long.

Cheers,

David

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 30 16:12:36 2007

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.