The current scipy-0.7.1 ebuild does not build, due to unprefixed paths set in site.cfg (which is used to find blas and other libraries) The following diff solves this: --- /home/mhulsman/gentoo/usr/portage/sci-libs/scipy/scipy-0.7.1.ebuild 2010-02-28 12:02:57.000000000 +0100 +++ scipy-0.7.1-r00.1.ebuild 2010-04-17 17:40:27.719140721 +0200 @@ -74,14 +74,14 @@ epatch "${FILESDIR}"/${PN}-0.7.1-weave.patch cat > site.cfg <<-EOF [DEFAULT] - library_dirs = /usr/$(get_libdir) - include_dirs = /usr/include + library_dirs = $EPREFIX/usr/$(get_libdir) + include_dirs = $EPREFIX/usr/include [atlas] include_dirs = $(pkg-config --cflags-only-I \ cblas | sed -e 's/^-I//' -e 's/ -I/:/g') library_dirs = $(pkg-config --libs-only-L \ cblas blas lapack| sed -e \ - 's/^-L//' -e 's/ -L/:/g' -e 's/ //g'):/usr/$(get_libdir) + 's/^-L//' -e 's/ -L/:/g' -e 's/ //g'):$EPREFIX/usr/$(get_libdir) atlas_libs = $(pkg-config --libs-only-l \ cblas blas | sed -e 's/^-l//' -e 's/ -l/, /g' -e 's/,.pthread//g') lapack_libs = $(pkg-config --libs-only-l \ @@ -91,13 +91,13 @@ cblas | sed -e 's/^-I//' -e 's/ -I/:/g') library_dirs = $(pkg-config --libs-only-L \ cblas blas | sed -e 's/^-L//' -e 's/ -L/:/g' \ - -e 's/ //g'):/usr/$(get_libdir) + -e 's/ //g'):$EPREFIX/usr/$(get_libdir) libraries = $(pkg-config --libs-only-l \ cblas blas | sed -e 's/^-l//' -e 's/ -l/, /g' -e 's/,.pthread//g') [lapack_opt] library_dirs = $(pkg-config --libs-only-L \ lapack | sed -e 's/^-L//' -e 's/ -L/:/g' \ - -e 's/ //g'):/usr/$(get_libdir) + -e 's/ //g'):$EPREFIX/usr/$(get_libdir) libraries = $(pkg-config --libs-only-l \ lapack | sed -e 's/^-l//' -e 's/ -l/, /g' -e 's/,.pthread//g') EOF Also, the numpy script /usr/lib/python2.6/site-packages/numpy/distutils/system_info.py (which processes site.cfg during the scipy build) contains a couple of hardcoded default paths (line 184-195, 818). As the section [DEFAULT] in the scipy site.cfg overrides these paths this is currently not a problem for building scipy however. Reproducible: Always Steps to Reproduce: 1. Build scipy
Justin, Can you look at this, please.
I will fix that the next days.
ping
(In reply to comment #3) > ping > totally forget that, will take the bug.
Current version do work here. Could you try those?
As of bug 280453 it seems to be fixed.