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

Re: Second try at build system changes

From: Branko Čibej <brane_at_wandisco.com>
Date: Fri, 21 Dec 2012 16:16:42 +0100

On 21.12.2012 15:55, Philip Martin wrote:
> Branko Čibej <brane_at_wandisco.com> writes:
>
>> Please take time to review these changes and test them. I did my best to
>> test on Mac OS and Linux, but as we saw in the previous iteration,
>> autoconf isn't exactly obvious. As usual, I can't build swig-db and
>> swig-py, but did touch their configury.
> A plain 'make' works as does 'make swig-pl', 'make swig-py' and 'make
> javahl'. 'make swig-py' is better than trunk where it fails due to
> passing -Werror=implicit-function-declaration.

Good! Thanks for taking time to look into that.

> 'make swig-rb' fails so is worse than trunk where it works. The error is
>
> /usr/lib/ruby/1.8/x86_64-linux/ruby.h:709:1: error: unknown type name 'inline'
> /usr/lib/ruby/1.8/x86_64-linux/ruby.h:711:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'rb_class_of'
> /usr/lib/ruby/1.8/x86_64-linux/ruby.h:726:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int'
> /usr/lib/ruby/1.8/x86_64-linux/ruby.h:743:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int'
> In file included from /usr/lib/ruby/1.8/x86_64-linux/ruby.h:756:0,
> from subversion/bindings/swig/ruby/svn_client.c:832:
>
> The code in question is:
>
> 709 static inline VALUE
> 710 #if defined(HAVE_PROTOTYPES)
> 711 rb_class_of(VALUE obj)
> 712 #else
> 713 rb_class_of(obj)
> 714 VALUE obj;
> 715 #endif

Can you post the actual compiler-via-libtool invocation, so that I can
see which options came through to confuse the compiler?

(I sure hope -DHAVE_PROTOTYPES was one of them.)

-- Brane

-- 
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Received on 2012-12-21 16:17:20 CET

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.