I’m trying to put together my own, autoconf’d/libtool’d library that
requires MPI (it’s an MPI tracing library).
Ordinarily, in the configure script, I set CC=mpicc (well, $MPICC,
because I detect where/whether it’s installed), but this poses some
problems with libtool. Specifically, if mpicc is set to use a weird
compiler (for example, IBM’s XL compilers), it requires different
handling for building libraries. For example, you have to use -qpic
instead of -fPIC. My libtool knows about IBM’s XL compilers, but
because mpicc can be a frontend for *any* compiler, I’m reluctant to
edit my libtool to treat mpicc as a synonym for the XL compiler. What
I want is a way to make sure that I tell libtool what compiler mpicc
is *really* using so that the flags are correct.
My solution so far has been to set CC=$( $MPICC -showme ), but this
seems like a poor solution to me (is -showme portable to all mpicc
implementations?). Does anyone know a better way of doing this? I
assume I’m not the first guy to have this problem.
--
Kyle B. Wheeler Scalable Computing Systems (1423)
Student Intern Sandia National Laboratories
kbwheel_at_[hidden] 505-844-7179
MS: 1319 CSRI/237
- application/pgp-signature attachment: stored
|
