(Unsure to which list this thread response should be sent due to an earlier missing cross-post...) On 06/15/2011 12:20 PM, Peter Simons wrote: >> Now, I wonder what to do about AX_MPI. It seems to me like your >> macros make that older version obsolete. Do you think we should >> deprecate AX_MPI and delete it, eventually? On Wed, Jun 15, 2011 at 1:15 PM, Olaf Lenz <olenz@xxxxxxxxxxxxxxxxxxxx> wrote: > In principle, the macro is still useful if somebody doesn't want to > compile *all* his code using the MPI compiler, but only some files. > However, I have no clear idea why someone would want to do that... > > Does anybody here have an application for the old macros? I do have such a use case. I build an MPI-based application along with some non-MPI, application-related utilities. The two build types are kept in separate subdirectories with only the MPI-related Makefile.am containing CXX = @MPICXX@. Sometimes HPC platform login nodes have policies disallowing using mpiexec outside of a batch job. Some MPI stacks require mpiexec be used for all MPI-enable binaries. My use case allows me to run my non-MPI utilities on such HPC login nodes. - Rhys _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
