On Fri, Jun 26, 2015 at 7:04 PM, Todd Gamblin <tgamb...@llnl.gov> wrote: > 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.
And what about the case where the user wants a compiler loaded to compile some software himself? Is that handled by rpath's? Ward
