subversion 1.6.0 stubbornly linking against python25-apple?

[macports.org@…]

I can't seem to get the subversion python bindings to link against the correct python:

$ sudo python_select none
Selecting version "none" for python
$ sudo python_select python25
Selecting version "python25" for python
$ sudo port uninstall subversion-python25bindings; sudo port clean subversion-python25bindings; sudo port install subversion-python25bindings
--->  Deactivating subversion-python25bindings @1.6.0_1
--->  Uninstalling subversion-python25bindings @1.6.0_1
--->  Cleaning subversion-python25bindings
--->  Fetching subversion-python25bindings
--->  Verifying checksum(s) for subversion-python25bindings
--->  Extracting subversion-python25bindings
--->  Configuring subversion-python25bindings
--->  Building subversion-python25bindings
--->  Staging subversion-python25bindings into destroot
--->  Installing subversion-python25bindings @1.6.0_1
--->  Activating subversion-python25bindings @1.6.0_1
--->  Cleaning subversion-python25bindings
$ otool -L /opt/local/lib/svn-python2.5/libsvn/_core.so | grep Python
	/Library/Frameworks/Python.framework/Versions/2.5/Python (compatibility version 2.5.0, current version 2.5.0)

[danielluke (Daniel J. Luke)]

Can you attach the -dv output of the build?

(sudo port clean subversion-python25bindings && sudo port -dv build subversion-python25bindings)

Thanks.

[danielluke (Daniel J. Luke)]

Oh, actually that's where the python25 framework gets installed:

$port provides /Library/Frameworks/Python.framework/Versions/2.5/Python /Library/Frameworks/Python.framework/Versions/2.5/Python is provided by: python25

[macports.org@…]

Replying to dluke@…:

Oh, actually that's where the python25 framework gets installed:

$port provides /Library/Frameworks/Python.framework/Versions/2.5/Python /Library/Frameworks/Python.framework/Versions/2.5/Python is provided by: python25

Does it really?

$ /Library/Frameworks/Python.framework/Versions/2.5/bin/python -V
Python 2.5
$ /Library/Frameworks/Python.framework/Versions/2.5/bin/python
Python 2.5 (r25:51918, Sep 19 2006, 08:49:13) 
[GCC 4.0.1 (Apple Computer, Inc. build 5341)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> 
$ /opt/local/bin/python2.5 -V
Python 2.5.4
$ /opt/local/bin/python2.5
Python 2.5.4 (r254:67916, Apr  6 2009, 16:57:21) 
[GCC 4.0.1 (Apple Inc. build 5490)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> ^D

More importantly:

$ /opt/local/bin/python2.5 -c "import svn.core; print svn.core.SVN_VER_MINOR"
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort trap
$ /Library/Frameworks/Python.framework/Versions/2.5/bin/python -c "import svn.core; print svn.core.SVN_VER_MINOR"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named svn.core

I'll attach the -dv output.

[macports.org@…]

Output of port -vd install subversion-python25bindings > /tmp/pysvn.log 2>&1 after a port clean --all subversion-python25bindings

[danielluke (Daniel J. Luke)]

It depends on frameworks_dir in macports.conf (and it looks like frameworks_dir is set to /Library/Frameworks in the current macports.conf).

I've got two 10.5 machines, one with frameworks_dir in the conf and one with out, on the one with it set to /Library/Frameworks, that's where the python framework is installed, on the other it's in ${prefix}/Library/Frameworks

Of course, there's not a /Library/Frameworks/Python.framework on my machine that doesn't have frameworks_dir in macports.conf, but on that machine _core.so is linked (incorrectly) to the /System/Library/Frameworks/Python.framework, so there is definitely a build problem here.

[tome@…]

Cc Me!

[tome@…]

I have the same problem, attached my -dv output of the build.

• my frameworks_dir is /opt/local/Library/Frameworks
  
• I did a proper select_python before installing

otool -L /opt/local/lib/svn-python2.5/libsvn/_fs.so  returns these:
----
	/System/Library/Frameworks/Python.framework/Versions/2.5/Python (compatibility version 2.5.0, current version 2.5.1)
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 34102.0.0)
	/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 32.0.0)
----

[jmroot (Joshua Root)]

Replying to dluke@…:

It depends on frameworks_dir in macports.conf (and it looks like frameworks_dir is set to /Library/Frameworks in the current macports.conf).

The default frameworks_dir was /Library/Frameworks for a while on pre-1.7 trunk, but it has always been ${prefix}/Library/Frameworks in actual releases.

[macports.org@…]

Replying to dluke@…:

It depends on frameworks_dir in macports.conf (and it looks like frameworks_dir is set to /Library/Frameworks in the current macports.conf).

frameworks_dir was not set for me, but setting it exlicitely to /opt/local/Library/Frameworks made no difference in the outcome. The default is ${prefix}/Library/Frameworks, according to man macports.conf.

[danielluke (Daniel J. Luke)]

So, the libtool link lines in both build logs have: -F/opt/local/Library/Frameworks -framework Python, which should cause the correct Python framework to be chosen, so at this point I'm unsure why it's not working correctly.

I can reproduce this on both of my boxes, now, so hopefully I'll be able to figure out a fix (but if someone wants to beat me too it, that's fine too :) ).

[danielluke (Daniel J. Luke)]

Fixed in r49375

(Thanks to Ranier for the idea of doing a 'normal' link instead of a framework one).

[(none)]

Milestone Port Bugs deleted