sci-libs/umfpack-5.2.0 compile dies with: ... /gcc/x86_64-pc-linux-gnu/4.3.2 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../../../x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/../../.. -lgfortranbegin -lgfortran -lm checking for dummy main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... lower case, underscore, no extra underscore checking for sgemm_ in -lblas -latlas ... no checking for sgemm_... no checking for ATL_xerbla in -latlas... yes checking for sgemm_ in -lf77blas... no checking for sgemm_ in -lblas... no checking for sgemm_ in -lcxml... no checking for sgemm_ in -ldxml... no checking for sgemm_ in -lscs... no checking for sgemm_ in -lcomplib.sgimath... no checking for sgemm_ in -lblas... (cached) no checking for sgemm_ in -lblas... (cached) no configure: error: Cannot find blas libraries Reproducible: Always Steps to Reproduce: 1. eselect list blas # Check that you have a blas installed 2. emerge sci-libs/umfpack Actual Results: umfpack doesn't get past configure Expected Results: umfpack compiles I've tried with the atlas-threaded, atlas and acml-mp blas libraries selected with eselect and I get the same results. My fortran compiler is gfortran 4.3.2-r3 p1.6, pie-10.1.5. It looks like it's failing while looking for the sgemm_ symbol, but that symbol is clearly in /usr/lib/blas (see below), on the the default locations ./configure looks for it in. Sorry I'm just submitting a bug and not a patch, but I'm not a fan of ac and libtool and configure and the link, so hopefully someone else will bother to figure it out. # eselect blas list Installed BLAS for library directory lib64 [1] acml-gfortran [2] acml-gfortran-openmp * [3] atlas [4] atlas-threads # eselect blas set 3 # nm /usr/lib/libblas.a |grep sgemm_ 0000000000000000 T atl_f77wrap_sgemm_ 00000000000002c0 t __sgemm_END U atl_f77wrap_sgemm_ 0000000000000000 T sgemm_
Please post your "emerge --info" and attach the config.log file of the failed emerge to this bug.
Reopen this bug when you provide the requested information.
