On Mon, Sep 26, 2016 at 2:00 AM, Dima Pasechnik <dimp...@gmail.com> wrote:
surely one can mess everything up with env. vars :-) > Yes, of course, I should have been more specific. I mean 'standard' environment variables (which users like me might use in wrong or 'hackish' ways). e.g., something like module add gcc-6.1.0-x86_64 export PATH=$HOME/bin:/data/local/bin:/opt/gcc-6.1.0/bin:$PATH export LD_LIBRARY_PATH=$HOME/lib:/data/local/lib:$LD_LIBRARY_PATH export LIBRARY_PATH=$HOME/lib:/data/local/lib export C_INCLUDE_PATH=$HOME/include:/data/local/include export CPLUS_INCLUDE_PATH=$HOME/include:/data/local/include export LD_RUN_PATH=$HOME/lib:/data/local/lib export SAGE_ATLAS_LIB=/usr/lib64/atlas-sse3/ export STATIC_LIB_DIR=/data/local/lib/ (Actually, I unset SAGE_ATLAS_LIB before the latest build, since the current development branch has switched to OpenBLAS. (I think I want to say hooray about that, but will at least wait until it doesn't segfault.)) How much attention (if any) does Sage pay to these environment variables? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
