In Spack, the compilers don't actually have to be loaded, so your new compilers stay out of the way of the system software. The stuff compiled with Spack gets RPATH'd, so it knows how to find its libraries -- in the gcc build we actually modify gcc's spec to put an RPATH in to each compiler's runtime. That's for compilers Spack actually built -- for system compilers, I'm still working on a way to make the Spack build automatically RPATH in compiler runtime libraries. It *is* possible to do this. CMake actually detects what it calls "implicit link libraries" for each compiler. Most compilers can be coaxed into telling you what these are.
-Todd On 6/26/15, 7:04 AM, "Kenneth Hoste" <kenneth.ho...@ugent.be> wrote: >Well, there are other options, but they're not supported (yet) by >EasyBuild. > >The issue is caused by having an older libstdc++.so in $LD_LIBRARY_PATH >after loading the GCC/4.7.x module. > >If GCC was built with RPATH linking by EasyBuild, there's no need to set >$LD_LIBRARY_PATH (in theory, there still are reasons to do so), and then >wget would break. >Same with static linking (which is a lot more difficult overal, e.g. >when building Python). > > >regards, > >Kenneth
