weechat @0.4.0 +python: build cannot find Python

[amdt (Alastair M. D. Touw)]

Building on Mac OS X 10.8.3 with Xcode 4.6.2 results in:

Error: org.macports.build for port weechat returned: command execution failed

Relevant section of log file could be lines 604 and 605 as follows:

:info:build Linking C shared module python.so
:info:build clang: error: no such file or directory: 'Python.framework/Versions/2.7/Python'

However, python27 @2.7.5_0+universal is active.

[cooljeanius (Eric Gallager)]

Have you used port select to choose a default python at all? What does port select python return for you?

[larryv (Lawrence Velázquez)]

Please Cc relevant port maintainers in the future.

[mf2k (Frank Schima)]

The python chosen via port select should never affect the installation of a port.

[amdt (Alastair M. D. Touw)]

port select python returned the following:

Available versions for python:
        none (active)
        python25-apple
        python26-apple
        python27
        python27-apple

sudo port select --set python python27 returned the following:

Selecting 'python27' for 'python' failed: symlink: /opt/local/etc/select/python/
current -> python27: file already exists

I then ran sudo rm /opt/local/etc/select/python/current.

At this point, sudo port select --set python python27 succeeded with:

Selecting 'python27' for 'python' succeeded. 'python27' is now active.

However, the build continues to fail with:

Error: org.macports.build for port weechat returned: command execution failed

Python can still not be found (main2.log, lines 574-575, to be attached):

:info:build clang: error: no such file or directory: 'Python.framework/Versions/2.7/Python'
:info:build make[2]: *** [src/plugins/python/python.so] Error 1

[cooljeanius (Eric Gallager)]

Cc Me!

[amdt (Alastair M. D. Touw)]

I had a related problem with Vim not being able to find Python, and reinstalled MacPorts. I now have no problems installing this port.

I do not know the exact reason for the problem with my Python port installation, but even if reproducible it would not be related to this port.

I dot not appear to be able to modify the status of this ticket, so I hereby request it be closed.

[larryv (Lawrence Velázquez)]

This looks like #39357.

[larryv (Lawrence Velázquez)]

Replying to larryv@…:

This looks like #39357.

nvm, actually #39223.

[dcecchin@…]

Cc Me!

[dcecchin@…]

Cc Me!

[dcecchin@…]

Cc Me!

[dcecchin@…]

I'm not sure if that bug is actually a duplicate

I did notice this ​https://github.com/mxcl/homebrew/issues/21013

Seems to be an issue with that version of python? I wonder what we can do to resolve this?

[jmroot (Joshua Root)]

The python version chosen with port select does affect weechat even though it shouldn't, that's #37048. The other problem here is that, as discussed in #39223, LINKFORSHARED is only useful when building python itself and is not a valid way for other programs to find out how to link with python. For that, you have to use pythonX.Y-config --ldflags.

[anddam (Andrea D'Amore)]

Cc Me!

[anddam (Andrea D'Amore)]

Should be fixed in r111398, it could probably be done better by passing appropriate arguments to cmake at configure phase rather than patching link.txt afterwards, any cmake-savvy person welcome to adjust it.