I found the most sane way to do this on the BG/P was to query the compiler wrappers for C/C++/Fortran. I don't understand why you aren't or are unable to do this within PETSc's configure.
Of course, we still encounter the crazy errors with shared libraries on our Cray XE6 where if we fail to preload a needed MPI library before importing PETSc we get symbol resolution errors... A On Wed, Mar 11, 2015 at 10:26 PM, Jed Brown <[email protected]> wrote: > Barry Smith <[email protected]> writes: > > so that if the basic link fails it automatically tries again here after > adding the -lstdc++ library. > > What if you're building with Clang and need -lc++ instead? >
