ab00aea1ff
use the new Automake "silent rules" if available.
If you are using an Automake prior to v1.11, you won't see the new
silent rules -- it will automatically default back to the "verbose"
rules.
Note, too, that even with these changes, you can enable the verbose
"make all" output in one of two ways:
1. Add "V=1" to your "make" command line
{{{
shell$ make all V=1
}}}
2. Add "--disable-silent-rules" to your "configure" command line:
{{{
shell$ ./configure --disable-silent-rules ...
}}}
The one down side of using the silent rules by default is that we'll
get less diagnostic information when users send their build logs. I
think we should update the web page to request that users send build
logs of "make V=1", but I'm guessing that not everyone will do it.
Note that I did ''not'' silent-ize the libltdl build (which is a dozen
or so files in the beginning of the build) because we wholly import
libltdl at autogen time. I therefore didn't want to patch libltdl
(further) after importing it a) to remain as forward- compatible as
possible, and b) patching the imported libltdl build system might be
tricky in terms of timestamps / dependencies. So those dozen-or-so
files will still be "verbose", but the rest of the files in OMPI will
be "silent".
This commit was SVN r22189.
This is the OMPI contrib system. It is (far) less functional and
flexible than the OMPI MCA framework/component system.
Each contrib package must have either both a configure.params and a
configure.m4 file, or it must have an autogen.subdirs file.
If it has (configure.params, configure.m4), configure.params can be
just like any MCA component's: specify a list of files to create
during AC_OUTPUT. The configure.m4 file will be slurped up into the
main configure script, just like other MCA components. Note that
there is currently no "no configure" option for contrib packages --
you *must* have a configure.m4 (even if all it does it call $1).
Feel free to fix this situation if you want -- see:
https://svn.open-mpi.org/trac/ompi/ticket/1162
:-)
If it has an autogen.subdirs file, then it needs to be a subdirectory
that is autogen-able (see the vt project for an example).