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

Re: svn.collab.net scheduled maintenance downtime

From: Greg Stein <gstein_at_gmail.com>
Date: Tue, 24 Feb 2009 18:13:23 +0100

On Tue, Feb 24, 2009 at 18:06, Mark Phippard <markphip_at_gmail.com> wrote:
> On Sat, Feb 21, 2009 at 8:27 PM, Greg Stein <gstein_at_gmail.com> wrote:
>> Some of the commit-hook scripts now require Python 2.4. It isn't
>> needed for end-user building from tarballs. Just for some of the
>> auxilliary tools that we ship.
>> Core svn doesn't need python at all, tho it does need sqlite 3.4 or newer.
> We have confirmed that you CANNOT build SVN bindings with Python >
> 2.4.  Here is quote from my build engineer:

Later than 2.4? Or versions prior?

*Core svn* doesn't need Python. If you want to build Python bindings,
then yah... you're gonna need Python. As far as the *version* of
Python... different question. And it looks like the general answer is
"you need Python 2.4 or later."

> "In the first place, both autogen.sh and configure both checks for Python
> 2.4 using the build/find_python.sh. If Subversion don't find Python 2.4
> then configure clearly warns
> "Python 2.4 or later is required to run the testsuite
> or to use the Subversion Python bindings"
> If we continue by fooling configure. Next stop is at 'make swig-py'
> while compiling  libsvn_swig_py/swigutil_py.c. This is  because of
> missing 'Py_RETURN_NONE' in python.h."

Eh? I see that symbol in my Python 2.5.

> He mentions autogen.sh but we are not running that, we are just
> running configure from the tarball.
> Comments?  Is this what we want?

No... you shouldn't be running autogen.sh.

Did you get your greater/lesser symbol mixed up, above? It is
*expected* that we're now generally requiring Python 2.4 or later. I
hadn't thought about the bindings, but it appears they need 2.4 or
later, too.


Received on 2009-02-24 18:14:56 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.