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

Re: Building and Testing Python, Perl, and Ruby Bindings

From: David James <djames_at_collab.net>
Date: 2006-07-13 05:35:55 CEST

On 7/12/06, D.J. Heap <djheap@gmail.com> wrote:
> On 7/12/06, D.J. Heap <djheap@gmail.com> wrote:
> > C:\Apps\swig\Lib\exception.i(11): Error: CPP #error ""This version of
> > exception.i should not be used"". Use the -cpperraswarn option to
> > continue swig processing.
> If I manually tweak the project to add -cpperraswarn and get rid of
> $(top_srcdir), then I get down to:
> Compiling...
> core.c
> ..\..\..\subversion\bindings\swig\python\core.c(8285) : fatal error
> C1021: invalid preprocessor command 'warning'
> Is #warning a GCCism? The MS compiler doesn't seem to like it at all.
> Maybe its been longer than I thought since I last tried the bindings.

Have you tried building Subversion with SWIG 1.3.25? These problems
involving the #error and #warning preprocessor directive only occur
with SWIG 1.3.26 or later.



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
Received on Thu Jul 13 05:36:21 2006

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.