[SciPy-User] numpy and scipy on mac osx 10.6.4

Massimo Di Stefano massimodisasha@gmail....
Wed Oct 13 16:43:26 CDT 2010


Hi,


things ar going better now,

i used an up to date python 2.7 (i386 + x86_64) available here

 [ http://pub.jbhannah.net/python/2.7/ ]  

file /usr/local/bin/python
/usr/local/bin/python: Mach-O universal binary with 2 architectures
/usr/local/bin/python (for architecture i386):	Mach-O executable i386
/usr/local/bin/python (for architecture x86_64):	Mach-O 64-bit executable x86_64


thanks to the author :-)

to build numpy i forced the flags :

 export LDFLAGS="-arch x86_64 -arch i386 -Wall -undefined dynamic_lookup -bundle"
 export FFLAGS="-arch x86_64 -arch i386"

 sudo python setup.py install


tring to build numpy (your git version) and testing it i have :

Ran 3079 tests in 43.420s

OK (KNOWNFAIL=4, SKIP=1)
<nose.result.TextTestResult run=3079 errors=0 failures=0>

cool! :-)

the full log are :

build log :

http://www.geofemengineering.it/epilog/numpy_build.txt

test log :

http://www.geofemengineering.it/epilog/numpy_test.txt


Now building scipy, 
it build fine without errors, but running test i gote few errors :

Ran 1731 tests in 866.721s

FAILED (KNOWNFAIL=2, SKIP=6, errors=14)
<nose.result.TextTestResult run=1731 errors=14 failures=0>

full log are :

build log :

http://www.geofemengineering.it/epilog/scipy_build.txt

test log : 

http://www.geofemengineering.it/epilog/scipy_test.txt


there are some test that fails :-/

maybe this can give you any clue on what's going wrong in scipy.linalg ?

ld /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scipy/fftpack/_fftpack.so
ld: warning: -arch not specified
ld: warning: in /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/scipy/fftpack/_fftpack.so, file was built for i386 which is not the architecture being linked (x86_64)
ld: could not find entry point "start" (perhaps missing crt1.o) for inferred architecture x86_64
epy:~ epy$ 

 
thanks!




Il giorno 13/ott/2010, alle ore 21.30, Matthew Brett ha scritto:

> Hi,
> 
>> the command :
>> 
>> "git checkout farchs-from-c  "
>> 
>> needs to be run inside the numpy directory ?
> 
> Right - thanks for the correction:
> 
>> there is the full log (chackout, build, test) :
>> 
>> http://http.geofemengineering.it/epilog/numpy_log_test
> 
> I think you meant http://www.geofemengineering.it/epilog/numpy_log_test ?
> 
> You're getting errors like these:
> 
> ======================================================================
> ERROR: test_return_character.TestF90ReturnCharacter.test_all
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>  File "/Library/Python/2.6/site-packages/nose-0.11.4-py2.6.egg/nose/case.py",
> line 367, in setUp
>    try_run(self.inst, ('setup', 'setUp'))
>  File "/Library/Python/2.6/site-packages/nose-0.11.4-py2.6.egg/nose/util.py",
> line 491, in try_run
>    return func()
>  File "/Library/Python/2.6/site-packages/numpy/f2py/tests/util.py",
> line 341, in setUp
>    module_name=self.module_name)
>  File "/Library/Python/2.6/site-packages/numpy/f2py/tests/util.py",
> line 73, in wrapper
>    memo[key] = func(*a, **kw)
>  File "/Library/Python/2.6/site-packages/numpy/f2py/tests/util.py",
> line 156, in build_code
>    module_name=module_name)
>  File "/Library/Python/2.6/site-packages/numpy/f2py/tests/util.py",
> line 73, in wrapper
>    memo[key] = func(*a, **kw)
>  File "/Library/Python/2.6/site-packages/numpy/f2py/tests/util.py",
> line 137, in build_module
>    __import__(module_name)
> ImportError: dlopen(/var/folders/1H/1HF3mbiVFOOWnbfLVKDmc++++TI/-Tmp-/tmp87fgzl/_test_ext_module_5403.so,
> 2): no suitable image found.  Did find:
> 	/var/folders/1H/1HF3mbiVFOOWnbfLVKDmc++++TI/-Tmp-/tmp87fgzl/_test_ext_module_5403.so:
> mach-o, but wrong architecture
> 
>> seems fortran is broken again, i'm using the fortran that comes form the R research site (as suggested on the scipy site)
> 
> I hope that someone who knows what they are doing can help you.
> 
> If no-one offers, then see if you can extract the compilation flags
> from the f2py build process somehow?
> 
> Lacking experience of f2py, I ended up hacking the _installed_ version
> of numpy/f2py/tests/utils.py around line 125 to add
> 
> print 'build stdout: ', out
> 
> to see what flags it was using.
> 
> Best,
> 
> Matthew
> _______________________________________________
> SciPy-User mailing list
> SciPy-User@scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-user



More information about the SciPy-User mailing list