I must confess that I don't undestand how this works and so far I've been able to only put brute force into it. I have installed quite a few python versions on my system:
- 3.9.9 with shared library
- 3.9.10 with framework
- 3.10.1 with shared library
- 3.10.2 with framework
I also have through homebrew both python@3.9 and pyt...@3.10.
So far the only thing that works is:
export vi_cv_path_python3=~/.pyenv/versions/3.9.9/bin/python3
export vi_cv_dll_name_python3=~/.pyenv/versions/3.9.9/lib/libpython3.9.dylib
./configure --with-features=huge \
--enable-multibyte \
--enable-terminal \
--enable-cscope \
--enable-pythoninterp=dynamic \
--enable-python3interp=dynamic \
--enable-perlinterp=dynamic \
--enable-rubyinterp=dynamic \
--enable-luainterp=dynamic \
--with-lua-prefix=/opt/homebrew
--prefix=/opt/homebrew
checking --enable-python3interp argument... dynamic
checking --with-python3-command argument... no
checking for python3... /Users/alex/.pyenv/shims/python3
checking Python version... 3.9
checking Python is 3.0 or better... yep
checking Python's abiflags...
checking Python's install prefix... /opt/homebrew/opt/python@3.9/Frameworks/Python.framework/Versions/3.9
checking Python's execution prefix... /opt/homebrew/opt/python@3.9/Frameworks/Python.framework/Versions/3.9
checking Python's configuration directory... /opt/homebrew/opt/python@3.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/config-3.9-darwin
checking Python3's dll name... (cached)
checking if -pthread should be used... no
checking if compile and link flags for Python 3 are sane... yes
What is confusing:
1. why is it looking into the homebrew python@3.9?
2. why is it not working the same with 3.10.x?
I will appreciate any thoughts/suggestions/request for further investigation.
thank you, alex