Eric Hanchrow wrote:
> I casually tried to build the python bindings (in branches/1.1.x), and
> was surprised when they didn't work. I had to look closely to figure
> out what was going wrong: the symptom was that `make' was complaining
> that there was no command named `-DLINUX=2'. Eventually I figured out
> that the top-level Makefile defined SWIG_PY_COMPILE as the empty
> string, because I'd overlooked a warning from configure:
>
> WARNING: swig versions 1.3.19, 1.3.20 or 1.3.21 are needed for swig
> support.
>
> (I have 1.3.22)
>
> So my suggestion is: initialize SWIG_PY_COMPILE, and other variables
> like it, to "false" rather than letting them default to the empty
> string; it might be a tiny bit easier for someone like me to notice
> what's going on then.
That's an excellent idea.
I've seen "none" used elsewhere for this purpose (deliberately not
/bin/false, because that looks like it just possibly might be meant to be
there).
Even better, would be for the relevant make targets to check for this, and
issue a descriptive error.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 7 17:31:50 2005