[mpich-discuss] Mpich2 1.5a2

[Dave Goodell]

On Dec 21, 2011, at 6:53 AM CST, Torquil Macdonald Sørensen wrote:

> A few questions about MPICH 1.5a2:
> 
> 1) Have the manpages disappeared?

Hmm... they don't appear to be in the tarball.  That's not intended.  I'll figure out why that is and either update the tarball or cut a new 1.5a3 release.

> 2) It seems that the PDF file user.pdf is not installed into /usr/share/doc/mpich2 anymore? Same for files in www/. Were they previously installed automatically into /usr/share/doc/mpich2 ?

I think this issue is related to question (1).

> 3) If I remember correctly, in previous versions, there were bin/, lib/ and include/ which contained all the necessary files to compile and run the test-suite prior to "make install", by going to test/mpi, and running ./configure --with-mpi=../../ and so on.
> 
> This doesn't seem to work the same way anymore, since compiled library files now seem to be spread out in different hidden .libs/ directories after "make" finishes. It now seems necessary to set a lot of environment variables (LD_LIBRARY_PATH and CPPFLAGS with different added .libs/ subdirectories) when one is about to run the ./configure in test/mpi.
> 
> Perhaps the test-suite is now intended to be run after "make install".

This is now the case.  Try just running "make testing" after running "make install".  It should basically work.  The old approach was difficult to maintain and even harder to make work when using properly-built shared libraries.

There is currently a bug in the way that "test/mpi/configure.in" works, so there might be some weirdness there from "make testing".  Basically it will sometimes pick up characteristics of an MPI implementation that is in your path/environment rather than the one that you just built.  I'm working on it, but we decided to push out 1.5a2 before the new year despite the bug.  The "cd test/mpi && ./configure --with-mpi=..." approach should be a serviceable workaround for now.

-Dave