You can set SAGE_INSTALL_GCC=no and SAGE_ATLAS_LIB=<path>. If you need to customize it further you'll have to edit build/deps.
On Tuesday, February 4, 2014 2:20:15 PM UTC, Aaron Zauner wrote: > > Dear People of the SAGE tribe, > > I work as a freelance HPC systems administrator and are somewhat involved > with the EasyBuild project (http://hpcugent.github.io/easybuild). Now > looking through how SAGE builds itself I've noticed that you wrote an > amalgamation of shell and Python scripts to build all dependencies and > ATLAS/BLAS libraries. In HPC systems we build our own toolchains that are > optimized to processing hardware, memory and interconnects. As such the > whole SAGE build toolkit does not make sense for us. We'd really like to > have SAGE easily available on HPC sites/Clusters for scientific and > developmental use. This is close to impossible unless we use your provided > defaults. > > My question basically is: How do I properly build SAGE without using your > own dependency and buildkit as provided via the Makefiles and build/ > directory? > > Thank you for your time, > Aaron Zauner > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
