On Wed, 30 May 2007, David James wrote:
> On 5/28/07, Joe Swatosh <email@example.com> wrote:
> >On 5/27/07, Masaru Tsuchiyama <firstname.lastname@example.org> 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
> >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
> >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.
Masaru, can you test this out for us? If it works, David's suggestion
sounds like a better general approach.
Received on Thu May 31 20:28:34 2007
- application/pgp-signature attachment: stored