In case this will help, I have the framework implemented (and committed) for handling pre-compioled binaries for tool dependencies for a supported set of architectures. Dave B has updated a lot of tool dependency definitions on both the test and main tool sheds to use this enhancement - those that he has updated are currently all owned by the devteam in preparation for a tool migration stage that he will soon be committiing. Perhaps the atlas tool dependency can be updated to proved a pre-compiled binary installation.
Greg Von Kuster On Sep 26, 2013, at 11:10 AM, Peter Cock <p.j.a.c...@googlemail.com> wrote: > Hi Bjoern, > > Is there anything else we (the Galaxy community) can do to help > sort out the ATLAS installation problems? > > Another choice might be to use OpenBLAS instead of ATLAS, e.g. > http://stackoverflow.com/questions/11443302/compiling-numpy-with-openblas-integration > > However, I think we build NumPy without using ATLAS or any > BLAS library. That seems like the most pragmatic solution > in the short term - which I think is what Dan tried here: > http://testtoolshed.g2.bx.psu.edu/view/blankenberg/package_numpy_1_7 > > Thanks, > > Peter > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > http://lists.bx.psu.edu/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/ ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/