> On 11 Mar 2015, at 11:25 , Johannes Ring <[email protected]> wrote: > > On Mon, Mar 9, 2015 at 11:30 PM, Terje Kvernes <[email protected]> wrote: >> After installing via fenics-install.sh on linux (RedHat 7) and using a >> custom yaml-file (attached), I am left with the following: >> >> In [2]: numpy.__config__.show() >> lapack_info: >> NOT AVAILABLE >> lapack_opt_info: >> NOT AVAILABLE >> blas_info: >> NOT AVAILABLE >> atlas_threads_info: >> NOT AVAILABLE >> blas_src_info: >> NOT AVAILABLE >> atlas_blas_info: >> NOT AVAILABLE >> lapack_src_info: >> NOT AVAILABLE >> openblas_info: >> NOT AVAILABLE >> atlas_blas_threads_info: >> NOT AVAILABLE >> blas_mkl_info: >> NOT AVAILABLE >> blas_opt_info: >> NOT AVAILABLE >> atlas_info: >> NOT AVAILABLE >> lapack_mkl_info: >> NOT AVAILABLE >> mkl_info: >> NOT AVAILABLE >> >> It has been pointed out to me that modifying numpy.yaml to the following: >> >> build_stages: >> >> - when: platform == 'linux' >> name: create-site.cfg >> before: install >> handler: bash >> bash: | >> cat > site.cfg << EOF >> [blas] >> blas_libs = blas >> library_dirs = ${ARTIFACT}/lib >> [lapack] >> lapack_libs = lapack >> library_dirs = ${ARTIFACT}/lib >> EOF >> >> should solve our problems, and I can certainly script it so this is patched >> in, but this seems a bit harsh. Is there a “proper” way to achieve this >> when using hashstack? > > The numpy.yaml file in hashstack certainly needs improvement. Please > feel free to report a bug about this for hashstack.
Done. Apologies for the delay. -- Terje Kvernes Head sysadmin Department of Mathematics University of Oslo _______________________________________________ fenics-support mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics-support
