I am building CVS scipy on OS X 10.3. The build goes fine, and I can import scipy, or do "from scipy import array" w/o problems. I can "import scipy.signal" but if I do "help(scipy.signal)" or "from scipy.signal import buttord" I get Fatal Python error: Interpreter not initialized (version mismatch?) Abort I have python compiled from src in /usr/local/lib/python2.3 and the python framework is also installed. I wonder if the message is arising from the build using part of the framework when I just want to be using the python from src.
From the CVS root, I built scipy with
cd scipy_core sudo python setup.py install # uses /usr/local/bin/python2.3 cd .. sudo python setup.py install
Below is the head of the setup output; if anyone has any suggestions I'm much obliged. Thanks! John Hunter numpy_info: FOUND: define_macros = [('NUMERIC_VERSION', '"\\"23.1\\""')] include_dirs = ['/usr/local/include/python2.3'] SciPy Core Version 0.2.2_alpha_104.1544 **************************************************************** Using fortran_libraries setup option is depreciated --------------------------------------------------- Use libraries option instead. Yes, scipy_distutils now supports Fortran sources in libraries. **************************************************************** running install running build running config_fc running build_src building extension "scipy_base.fastumath" sources adding 'scipy_base/fastumathmodule.c' to sources. building extension "scipy_base._compiled_base" sources running build_py package init file '/Users/jdhunter/python/src/scipy/scipy_core/scipy_distutils/tests/__init__.py' not found (or not a regular file) package init file '/Users/jdhunter/python/src/scipy/scipy_core/scipy_base/tests/__init__.py' not found (or not a regular file) package init file 'weave/tests/__init__.py' not found (or not a regular file) package init file 'weave/tests/__init__.py' not found (or not a regular file) package init file '/Users/jdhunter/python/src/scipy/scipy_core/scipy_distutils/tests/__init__.py' not found (or not a regular file) package init file '/Users/jdhunter/python/src/scipy/scipy_core/scipy_base/tests/__init__.py' not found (or not a regular file) package init file 'weave/tests/__init__.py' not found (or not a regular file) package init file 'weave/tests/__init__.py' not found (or not a regular file) running build_ext customize UnixCCompiler customize UnixCCompiler using build_ext distutils.unixccompiler.UnixCCompiler does not provide version_cmd and version_pattern attributes ******************************************************************************** distutils.unixccompiler.UnixCCompiler compiler_cxx = ['c++'] ranlib = ['ranlib'] linker_exe = ['gcc'] compiler_so = ['gcc', '-fno-strict-aliasing', '-Wno-long-double', '-no-cpp-precomp', '-mno-fused-madd', '-DNDEBUG', '-g', '-O3', '-Wall', '-Wstrict-prototypes'] archiver = ['ar', '-cr'] preprocessor = ['gcc', '-E'] linker_so = ['gcc', '-bundle', '-bundle_loader', '/usr/local/bin/python2.3'] compiler = ['gcc', '-fno-strict-aliasing', '-Wno-long-double', '-no-cpp-precomp', '-mno-fused-madd', '-DNDEBUG', '-g', '-O3', '-Wall', '-Wstrict-prototypes'] libraries = [] library_dirs = [] include_dirs = ['/usr/local/include/python2.3'] ******************************************************************************** running install_lib running install_data /usr/local/bin/python2.3 /Users/jdhunter/python/src/scipy/scipy_core/setup.py install fftw_info: NOT AVAILABLE dfftw_info: NOT AVAILABLE FFTW (http://www.fftw.org/) libraries not found. Directories to search for the libraries can be specified in the scipy_distutils/site.cfg file (section [fftw]) or by setting the FFTW environment variable. djbfft_info: NOT AVAILABLE DJBFFT (http://cr.yp.to/djbfft.html) libraries not found. Directories to search for the libraries can be specified in the scipy_distutils/site.cfg file (section [djbfft]) or by setting the DJBFFT environment variable. blas_opt_info: FOUND: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] define_macros = [('NO_ATLAS_INFO', 3)] extra_compile_args = ['-faltivec', '-framework', 'Accelerate'] lapack_opt_info: FOUND: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] define_macros = [('NO_ATLAS_INFO', 3)] extra_compile_args = ['-faltivec', '-framework', 'Accelerate'] creating build creating build/temp.darwin-7.2.0-Power_Macintosh-2.3 creating build/temp.darwin-7.2.0-Power_Macintosh-2.3/config_pygist ============= begin top level configuration ============= compiling '_configtest.c': /* check whether libm is broken */ #include <math.h> int main(int argc, char *argv[]) { return exp(-720.) > 1.0; /* typically an IEEE denormal */ } gcc options: '-fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes' compile options: '-c' gcc: _configtest.c gcc _configtest.o -lm -o _configtest success! removing: _configtest.c _configtest.o _configtest compiling '_configtest.c': /* check whether libm is broken */ #include <math.h> int main(int argc, char *argv[]) { return exp(-720.) > 1.0; /* typically an IEEE denormal */ }
On Mar 9, 2004, at 1:50 PM, John Hunter wrote:
I am building CVS scipy on OS X 10.3. The build goes fine, and I can import scipy, or do "from scipy import array" w/o problems. I can "import scipy.signal" but if I do "help(scipy.signal)" or "from scipy.signal import buttord" I get
Fatal Python error: Interpreter not initialized (version mismatch?) Abort
You linked the extension against one build of Python, and you're importing it from another.. as the error suggests. If you do otool -L on the extension that is failing, you can see what it's linking to. -bob
"Bob" == Bob Ippolito <bob@redivi.com> writes:
Bob> If you do otool -L on the extension that is failing, you can Bob> see what it's linking to. Yep. Several of the *.so files are linking against /System/Library/Frameworks/Python.framework/Versions/2.3/Python. Maybe I should just stop bucking the tide and go with the framework. Thanks, JDH
On Mar 9, 2004, at 3:30 PM, John Hunter wrote:
"Bob" == Bob Ippolito <bob@redivi.com> writes:
Bob> If you do otool -L on the extension that is failing, you can Bob> see what it's linking to.
Yep. Several of the *.so files are linking against /System/Library/Frameworks/Python.framework/Versions/2.3/Python.
Maybe I should just stop bucking the tide and go with the framework.
Yes, you should. If you have a really good reason not to, I'd like to hear it :) -bob
"Bob" == Bob Ippolito <bob@redivi.com> writes:
Bob> Yes, you should. If you have a really good reason not to, Bob> I'd like to hear it :) Well, I had already succeeded in getting VTK installed on my custom python and that was a fair amount of work so I was hesitant to plow that ground again. But I know VTK will install reasonably well under the framework so that's the route I'm going to take. I just installed scipy under the framework w/o incident. Thanks for all the hard work getting that working properly. JDH
participants (2)
-
Bob Ippolito -
John Hunter