Could you test if r1088462 fixes your issue?
The build-outputs.mk macros GEN_SWIG_WRAPPER,CHECKOUT_SWIG,GEN_SWIG_RUNTIME
also use $(SWIG). Even though I haven't touched them, I still trigger the
check-SWIG error immediately when I do './configure --without-swig && make swig-py'.
However, upon code inspection it seems that some of them do attempt to run
$(SWIG), so I'm not sure if they have to be modified too.
Arfrever Frehtes Taifersar Arahesis wrote on Mon, Apr 04, 2011 at 00:25:45 +0200:
> 2011-04-02 04:02:03 Daniel Shahaf napisał(a):
> > Arfrever Frehtes Taifersar Arahesis wrote on Fri, Apr 01, 2011 at 18:33:40 +0200:
> > > 2010-12-31 12:01:57 danielsh_at_apache.org napisał(a):
> > > > Author: danielsh
> > > > Date: Fri Dec 31 11:01:56 2010
> > > > New Revision: 1054087
> > >
> > > Release tarballs contain files pregenerated by SWIG. This revision probably breaks support
> > > for building SWIG-based bindings from release tarballs when SWIG is not available.
> > >
> > Thanks for pointing that out.
> > The problem I attempted to fix was that, in my trunk working copies
> > (which I, most of the time, configure --without-swig), running
> > 'make swig-foo' would attempt to run a command called "none". (This is
> > because configure sets SWIG, which normally points to a 'swig' binary,
> > to 'none'.)
> > I'm sure there is a cleaner solution somewhere, but I don't have any
> > ideas right now. (I could look later for a better place to move this
> > check to, but a quick browse through the Makefile hasn't unearthed it
> > for me.) Do you have any suggestions as to a fix?
> check-SWIG target shouldn't be a dependency of swig-pl, swig-py and swig-rb targets.
> check-SWIG target should be a dependency of targets for individual .c files in
> "Section 4: Rules to build SWIG .c files from .i files" in (generated) build-outputs.mk.
> Arfrever Frehtes Taifersar Arahesis
Received on 2011-04-04 04:30:37 CEST