Admin at 00:06, 29 May 2013

2013-05-29T00:06:21Z

← Older revision		Revision as of 00:06, 29 May 2013
Line 48:		Line 48:
	$ CFLAGS="-DVIMAGE_H" python setup.py build		$ CFLAGS="-DVIMAGE_H" python setup.py build
	</pre>		</pre>

			When you compile, you'll see a bunch of spew and warnings and whatnot, but it should compile okay.

			Test it out by adding <code>/path/to/scipy/install/lib/python2.7/site-packages</code> to your <code>$PYTHONPATH</code>, then run the following command in Python:

			<pre>
			$ python
			Python 2.7.2 (default, Oct 11 2012, 20:14:37)
			[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)] on darwin
			Type "help", "copyright", "credits" or "license" for more information.
			>>> from scipy import *
			>>>
			</pre>

			You should not see any error messages.

Admin at 23:58, 28 May 2013

2013-05-28T23:58:41Z

← Older revision		Revision as of 23:58, 28 May 2013
Line 1:		Line 1:
			Linked to from this page: [[Mac_OS_X_Lion]]

	While compiling scipy, I ran into a problem with <code>vImage.h</code> not being found:		While compiling scipy, I ran into a problem with <code>vImage.h</code> not being found:

Admin: Created page with "While compiling scipy, I ran into a problem with vImage.h not being found:

 $ python setup.py build  [...]  customize UnixCCompiler customize UnixCCompiler usi..."

2013-05-28T23:57:22Z

Created page with "While compiling scipy, I ran into a problem with <code>vImage.h</code> not being found: <pre> $ python setup.py build [...] customize UnixCCompiler customize UnixCCompiler usi..."

New page

While compiling scipy, I ran into a problem with <code>vImage.h</code> not being found:

<pre>
$ python setup.py build

[...]

customize UnixCCompiler
customize UnixCCompiler using build_clib
customize Gnu95FCompiler
Found executable /usr/local/bin/gfortran
customize Gnu95FCompiler
customize Gnu95FCompiler using build_clib
building 'arpack_scipy' library
compiling C sources
C compiler: clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe

compile options: '-Iscipy/sparse/linalg/eigen/arpack/ARPACK/SRC -I/Users/charlesreid/pkg/numpy/std/lib/python2.7/site-packages/numpy/core/include -c'
clang: scipy/sparse/linalg/eigen/arpack/ARPACK/FWRAPPERS/veclib_cabi_c.c
clang: warning: argument unused during compilation: '-mno-fused-madd'
In file included from scipy/sparse/linalg/eigen/arpack/ARPACK/FWRAPPERS/veclib_cabi_c.c:2:
/System/Library/Frameworks/Accelerate.framework/Headers/Accelerate.h:24:10: fatal error: 'vImage/vImage.h' file not found
#include <vImage/vImage.h>
^
1 error generated.
clang: warning: argument unused during compilation: '-mno-fused-madd'
In file included from scipy/sparse/linalg/eigen/arpack/ARPACK/FWRAPPERS/veclib_cabi_c.c:2:
/System/Library/Frameworks/Accelerate.framework/Headers/Accelerate.h:24:10: fatal error: 'vImage/vImage.h' file not found
#include <vImage/vImage.h>
^
1 error generated.
error: Command "clang -fno-strict-aliasing -fno-common -dynamic -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch i386 -arch x86_64 -pipe -Iscipy/sparse/linalg/eigen/arpack/ARPACK/SRC -I/Users/charlesreid/pkg/numpy/std/lib/python2.7/site-packages/numpy/core/include -c scipy/sparse/linalg/eigen/arpack/ARPACK/FWRAPPERS/veclib_cabi_c.c -o build/temp.macosx-10.8-intel-2.7/scipy/sparse/linalg/eigen/arpack/ARPACK/FWRAPPERS/veclib_cabi_c.o" failed with exit status 1
</pre>

This was resolved by looking in the file <code>/System/Library/Frameworks/Accelerate.framework/Headers/Accelerate.h</code> and seeing that the problematic include statement was wrapped with an ifndef statement:

<pre>
#ifndef VIMAGE_H
#include <vImage/vImage.h>
#endif
</pre>

So, it is possible to bypass the vImage.h include by adding the flag <code>-DVIMAGE_H</code> to the compilation commands that scipy issues. Do this by modifying the <code>CFLAGS</code> environmental variable:

<pre>
$ CFLAGS="-DVIMAGE_H" python setup.py build
</pre>

Scipy vImage.h Problem - Revision history

Admin at 00:06, 29 May 2013

Admin at 23:58, 28 May 2013

Admin: Created page with "While compiling scipy, I ran into a problem with `vImage.h` not being found:
$ python setup.py build [...] customize UnixCCompiler customize UnixCCompiler usi..."

Scipy vImage.h Problem - Revision history

Admin at 00:06, 29 May 2013

Admin at 23:58, 28 May 2013

Admin: Created page with "While compiling scipy, I ran into a problem with vImage.h not being found: $ python setup.py build [...] customize UnixCCompiler customize UnixCCompiler usi..."

Admin: Created page with "While compiling scipy, I ran into a problem with `vImage.h` not being found:
$ python setup.py build [...] customize UnixCCompiler customize UnixCCompiler usi..."