Re: Patch for Python bindings?

On 4/20/06, David Abrahams <dave@boost-consulting.com> wrote:
> We're having this previously-reported problem building the swig Python
> buildings for SVN 1.3.0
> (http://article.gmane.org/gmane.comp.version-control.subversion.devel/75007)
> and we're reluctant to roll back to an earlier version of SVN. Can
> anyone suggest a patch we can apply to 1.3.0 that will get us around
> this problem?

(I've cc'd the users@ list, because this question is more appropriate
for the users@ list than the dev@ list)

David, could you provide us with a little bit more information about
how you are building Subversion? Please start from a fresh tarball and
list all the commands you run from there.

I'm guessing you might have run autogen.sh without the release flag,
thus accidentally switching to developer mode without clearing out the
pregenerated release mode headers. In general, users building from
tarball should never run autogen.sh. I recommend you start from a
fresh tarball and build and configure from scratch without touching
autogen.sh at all.

We should probably patch Subversion so that users who accidentally run
autogen.sh without clearing out the release mode headers get a clear
error message so that they will know how to avoid it. I'd be very
happy to help out if anyone is interested in fixing this.

Cheers,

David

--
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