0db23b0210
new automake requires subdirs-object directive, to resolve this: 09:43:37 automake: warning: possible forward-incompatibility. 09:43:37 automake: At least a source file is in a subdirectory, but the 'subdir-objects' 09:43:37 automake: automake option hasn't been enabled. For now, the corresponding output 09:43:37 automake: object file(s) will be placed in the top-level directory. However, 09:43:37 automake: this behaviour will change in future Automake versions: they will 09:43:37 automake: unconditionally cause object files to be placed in the same subdirectory 09:43:37 automake: of the corresponding sources. 09:43:37 automake: You are advised to start using 'subdir-objects' option throughout your 09:43:37 automake: project, to avoid future incompatibilities. 09:43:37 tools/otfmerge/Makefile.common:13: warning: source file '$(OTFMERGESRCDIR)/otfmerge.c' is in a subdirectory, 09:43:37 tools/otfmerge/Makefile.common:13: but option 'subdir-objects' is disabled cmr=v1.8.2:reviewer=ompi-rm1.8 This commit was SVN r32225.
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 a configure.m4. It may optionally also have an autogen.subdirs file. If it has a configure.m4 file, it must specify its own relevant files to AC_CONFIG_FILES to create during AC_OUTPUT -- just like MCA components (at a minimum, usually its own Makefile). 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 -- it probably won't not be too difficult to extend autogen.pl to support this scenario, similar to how it is done for MCA components. :-) 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).