Hello all,

Are you using the builtin python? If so, you will need to set your PYTHONPATH to point to the directory where numpy 1.0.4 is installed. The reason is that the builtin python comes with python 1.0.1, which won't build scipy with the gfortran you have.

I'm not using Leopard, but if I recall from the discussion on python- mac, there's the added difficulty that the environment isn't preserved through 'sudo' -- so just setting the PYTHONPATH environment variable won't work if you need to 'sudo python setup.py install' to install a given library to a system directory. I don't recall what the recommended solution, if any, was. I think it involved some .pth file trickery that looked relatively, um, ugly. Alternately, one could select a non-system directory as your local site-packages, via a .pth or PYTHONPATH, so sudo is not needed to install. This doesn't work for system admins supporting multiple users though. Finally, on the horizon were some options for setting up "virtual" python installs that would act like separate installs from the system one for the purpose of installing packages, but would use the system python and its libs under the covers. Is there yet any set of simple, newbie-friendly instructions that covers how best to install things like numpy/scipy on leopard? Zach On Nov 9, 2007, at 4:47 PM, Brian Granger wrote:

Are you using the builtin python? If so, you will need to set your PYTHONPATH to point to the directory where numpy 1.0.4 is installed. The reason is that the builtin python comes with python 1.0.1, which won't build scipy with the gfortran you have.

There is a somewhat odd issue on Leopard. If you look at sys.path:

python -c "import sys; print sys.path"

You will see that the directory where the builtin numpy is (I think it is something like */Extras/*) is before the site-packages directory where your numpy 1.0.4 would be installed (unless you used to --home or --prefix options when running python setup.py install). This means that unless you set PYTHONPATH you will always get Leopards older numpy, which will cause scipy to fail on building.

Note, this is very different than on Tiger where the builtin python did not include many third party packages. Leopard includes quite a few (for better or worse).

Brian

On Nov 9, 2007 2:33 PM, Daniel Yarlett <yarlett@psych.stanford.edu> wrote:

...

hi,

apologies if this is not the appropriate forum for posting this, but i am having some trouble building and installing scipy 0.6.0 on a PPC Mac that i have just upgraded to OS X 10.5 (this version of scipy previously worked fine on the same machine under OS X 10.4).

numpy 1.0.4 seems to install fine with "python setup.py install".

however, when i try to install scipy 0.6.0 i get the output (tail only) included at the end of this email.

here are my compiler versions:

gcc -- version gcc (GCC) 4.3.0 20071026 (experimental)

gfortran -- version GNU Fortran (GCC) 4.3.0 20071026 (experimental)

i remember that on previous versions of OS X you could use gcc_select to specify v3.4 of gcc to make the build go through. unfortunately gcc_select seems to have been deprecated in Leopard so i haven't been able to try that. don't know if that's a red herring or not.

also, fwiw, i just upgraded an intel macbook prop from OS X 10.4 to 10.5 and had no problems at all with the pre-existing versions of numpy and scipy.

anyway, any help would be greatly appreciated!

best,

dan.

--

END OF OUTPUT FROM "python setup.py install" for scipy 0.6.0:

Could not locate executable f95 customize AbsoftFCompiler Could not locate executable f90 Could not locate executable f77 customize IBMFCompiler Could not locate executable xlf90 Could not locate executable xlf customize IntelFCompiler Could not locate executable ifort Could not locate executable ifc customize GnuFCompiler Found executable /usr/local/bin/g77 gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found customize GnuFCompiler gnu: no Fortran 90 compiler found gnu: no Fortran 90 compiler found customize GnuFCompiler using build_clib building 'superlu_src' library compiling C sources C compiler: gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/ MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp- precomp - mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3

compile options: '-DUSE_VENDOR_BLAS=1 -c' gcc: scipy/linsolve/SuperLU/SRC/colamd.c gcc: unrecognized option '-no-cpp-precomp' cc1: error: unrecognized command line option "-arch" cc1: error: unrecognized command line option "-arch" cc1: error: unrecognized command line option "-Wno-long-double" gcc: unrecognized option '-no-cpp-precomp' cc1: error: unrecognized command line option "-arch" cc1: error: unrecognized command line option "-arch" cc1: error: unrecognized command line option "-Wno-long-double" error: Command "gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/ MacOSX10.4u.sdk -fno-strict-aliasing -Wno-long-double -no-cpp- precomp - mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 - DUSE_VENDOR_BLAS=1 -c scipy/linsolve/SuperLU/SRC/colamd.c -o build/ temp.macosx-10.3-fat-2.5/scipy/linsolve/SuperLU/SRC/colamd.o" failed with exit status 1 _______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user

_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user