Probably means this was a problem in some ancient version of our
environment and it never got changed. It looks reasonable, so I'll
make it so. Which platforms will barf with the './config'? Trying
to figure out which branches this needs to be committed to...
Thanks,
Brian
On May 6, 2006, at 6:29 PM, Ralf Wildenhues wrote:
Hi there,
A very minor nit in OpenMPI, concerning autotools: I think it's
better to specify the arguments to AC_CONFIG_AUX_DIR and _MACRO_DIR
without leading "./", since if those name end up in Makefile targets,
BSD make won't have problems with VPATH lookup. (Maybe this should be
noted in the Autoconf documentation.)
Conversely, if that has been done on purpose, say, to fix some issue,
then I'd like to know about it. FWIW, it's present in LAM as well.
Cheers,
Ralf
Index: configure.ac
===================================================================
--- configure.ac (revision 9831)
+++ configure.ac (working copy)
@@ -33,8 +33,8 @@
[m4_normalize(esyscmd([config/ompi_get_version.sh VERSION
--base]))],
[http://www.open-mpi.org/community/help/], [openmpi])
AC_PREREQ(2.58)
-AC_CONFIG_AUX_DIR(./config)
-AC_CONFIG_MACRO_DIR(./config)
+AC_CONFIG_AUX_DIR(config)
+AC_CONFIG_MACRO_DIR(config)
# Get our platform support file. This has to be done very, very
early
# because it twiddles random bits of autoconf
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
