Opened 11 years ago
Closed 11 years ago
#40287 closed defect (invalid)
MacVim , vim: Python support does not work
Reported by: | wichert@… | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.0 |
Keywords: | Cc: | ||
Port: | MacVim vim |
Description
I noticed that for both binary and source installs of MacVim the python variant does not work. When trying to compile with +python27 I see the following in the debug output:
checking Python version... 2.7 checking Python is 1.4 or better... yep checking Python's install prefix... /opt/local/Library/Frameworks/Python.framework/Versions/2.7 checking Python's execution prefix... /opt/local/Library/Frameworks/Python.framework/Versions/2.7 checking Python's configuration directory... /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config checking if -pthread should be used... no checking if compile and link flags for Python are sane... no: PYTHON DISABLED
Attachments (4)
Change History (19)
comment:1 Changed 11 years ago by wichert@…
comment:2 Changed 11 years ago by wichert@…
Looking at config.log shows why it fails:
configure:5285: checking Python's install prefix configure:5294: result: /opt/local/Library/Frameworks/Python.framework/Versions/2.7 configure:5297: checking Python's execution prefix configure:5306: result: /opt/local/Library/Frameworks/Python.framework/Versions/2.7 configure:5328: checking Python's configuration directory configure:5345: result: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config configure:5399: checking if -pthread should be used configure:5438: result: no configure:5442: checking if compile and link flags for Python are sane configure:5459: /usr/bin/clang -o conftest -pipe -Os -arch x86_64 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -DPYTHON_HOME=\"/opt/local/Library/Frameworks/Python.framework/Versions/2.7\" -I/opt/local/include -DMACOS_X_UNIX -no-cpp-precomp -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 -L/usr/local/lib conftest.c -L/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -lpython2.7 -ldl -framework CoreFoundation -u _PyMac_Error Python.framework/Versions/2.7/Python >&5 clang: error: no such file or directory: 'Python.framework/Versions/2.7/Python'
Which suggests that this is related to #39223
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | raimue@… removed |
---|---|
Owner: | changed from macports-tickets@… to raimue@… |
Port: | vim added |
Summary: | Python support does not work → MacVim , vim: Python support does not work |
comment:4 Changed 11 years ago by larryv (Lawrence Velázquez)
Resolution: | → invalid |
---|---|
Status: | new → closed |
This was fixed in r110123. Clean, run selfupdate, and build again.
comment:5 Changed 11 years ago by wichert@…
That did not seem to improve things:
wichert@zephyr ~ $ vim -v Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault: 11
comment:6 Changed 11 years ago by larryv (Lawrence Velázquez)
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Please attach your main.log
and config.log
:
% sudo port clean vim % sudo port configure vim % echo $(port logfile vim) % echo $(port work vim)/vim*/config.log
Changed 11 years ago by wichert@…
Changed 11 years ago by wichert@…
Attachment: | config.log added |
---|
comment:7 follow-up: 9 Changed 11 years ago by wichert@…
Attached. Both vim and MacVim show the same segfault.
comment:8 follow-up: 10 Changed 11 years ago by wichert@…
I also noticed the existing binary builds for vim were made before r110123 landed and are thus missing python support.
comment:9 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to wichert@…:
Attached. Both vim and MacVim show the same segfault.
Sorry, I gave you the wrong command. You need to run this.
sudo port configure vim +python27
comment:10 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to wichert@…:
I also noticed the existing binary builds for vim were made before r110123 landed
No, they were not. r110123 bumped vim to @7.3.762_3, which has been built.
and are thus missing python support.
We only generate binary archives for default variants, which do not include any of the Python variants.
comment:11 Changed 11 years ago by wichert@…
The segfaults appears to be related to the variants. Install vim +python27
works correctly now, but vim +python27 +ruby
will segfault immediately on startup.
comment:15 Changed 11 years ago by larryv (Lawrence Velázquez)
Port: | MacVim, vim → MacVim vim |
---|---|
Resolution: | → invalid |
Status: | reopened → closed |
Okay, please open a new ticket specifically about the Ruby issue.
The exact same problem occurs with the vim port as well.