bin/ompi_info presents an opportunity to help all us shlubs that
have to do gnu build systems.
It appears it could be extended to include useful bits of info
that are normally classed as build magic.
e.g. gnome-config, xml2-config, etc, etc.
I see lam-config was debated at least briefly back in 2003.
An openmpi-config would be a marvelous thing to have.
To expose some of the evil-user assumptions I have to support:
a) there will be multiple mpis on the system.
b) only some crufty old version noone wants to use will be
in the default path or default shared library path.
and
c) magically,
./configure --with-mpi=$users_favorite_hacked_local_mpi_build
is supposed to work.
or more realistically
d)
./configure --with-mpich=$someplace_particular0
./configure --with-lam=$someplace_particular1
./configure --with-lampi=$someplace_particular2
or
./configure --with-openmpi-config=$someplace_close_to_heaven
is supposed to work.
I realize all this has *nothing* to do with writing an mpi and
everything to do with *packaging*.
Please consider throwing something like this into the initial release.
Ben
On Wed, Jun 15, 2005 at 02:24:24PM -0500, Matthew Knepley wrote:
> I would like to emphasize Ben's point about integration.
> I really could care less whether the implementation works right now
> or not. However, I care very much how the build system functions,
> since that it where the hard work of integration will be. You are
