Indeed, this is quite bizarre. I can think of a few reasons why the
7.1.1 dir kept showing up (pardon if some of these are mundane -- I
have to ask):
- are you sure what you were executing the "right" mpic++? i.e., what
does "which mpic++" tell you? Can you try executing the mpic++ in
tools/wrappers, just to be absolutely 100% sure that you're running the
right one?
- do you have the LAMHOME environment variable set? If so, unset it
(it definitely affects the outcome of running the wrapper compilers).
- double check that the wrapper compilers are compiled properly -- do
any one or more of the following:
- remove your LAM 7.1 source tree and un-tar it from a tarball
- "make clean" in the source tree before re-running "make all
install" (can be before or after re-running ./configure, but you must
have had to have run configure at least once)
- ensure that the wrappers are recompiled after you re-run configure;
e.g., "cd tools/wrappers; make clean all"
- you can verify which directory is built into the wrappers two ways:
- run laminfo; the prefix dir is shown at the top of the output
- look at the individual compilation lines when the wrappers are
compiled; the default prefix, libdir, and incdir are all passed in on
the command line via -D flags.
-----
If you have time for these tests (and I thank you for your continued
patience!), the following configure flags may speed things up a bit for
testing porpoises:
--without-romio --without-profiling --without-fc --with-debug
The effects of the wrappers in terms of the -I and -L flags that it
passes will be the same with and without these flags (note that they
won't look for liblammpio anymore, since that's the ROMIO library).
On Oct 17, 2004, at 10:57 PM, Joseph Hope wrote:
> OK, this is getting downright bizarre. My guess was that it was the
> explicit act of setting PREFIX that was breaking the install, so I
> tried a second installation with no prefix command, expecting it to
> install into /usr/local.
>
> autoconf didn't want to forget about the old installation
> (/usr/local/lam-7.1.1)
> It found lamclean and went for the old directory, so everything worked
> fine. So I uninstalled the working version, and then tried again.
> This time it said at the top of the configure output that it was going
> to install into /usr/local, and in the end broke the C++ example
> compilation with the same error message as before. Doing a mpic++
> --showme gave:
>
> WARNING: mpic++ expected to find liblammpio.* in
> /usr/local/lam-7.1.1/lib
> WARNING: MPI-2 IO support will be disabled
> WARNING: mpic++ expected to find liblammpi++.* in
> /usr/local/lam-7.1.1/lib
> WARNING: MPI C++ support will be disabled
> xlc++ -I/usr/local/lam-7.1.1/include -D_REENTRANT
> -L/usr/local/lam-7.1.1/lib -lmpi -llam -ldl
>
> Note the reappearance of the /usr/local/lam-7.1.1 directory! It just
> won't give up.
>
> Tried again with an actual prefix of /usr/local.
>
> This time it installed happily into /usr/local, but again the old
> directory has some life:
>
> starone:~/Applications/testlam/lam-7.1.1$ which mpic++
> /usr/local/bin/mpic++
> starone:~/Applications/testlam/lam-7.1.1$ mpic++ --showme
> xlc++ -I/usr/local/lam-7.1.1/include -D_REENTRANT
> -L/usr/local/lam-7.1.1/lib -llammpio -llammpi++ -lmpi -llam -ldl
>
> And this time the C++ examples compile fine. Note that the theory
> that setting the prefix explicitly does indeed make it execute cleanly
> is working out.
>
> Last attempt. I'm going to uninstall both, and then nuke the damn
> /usr/local/lam-7.1.1 directory before trying one last time with no
> prefix.
>
> It did it again. This time there was no such directory, never mind no
> suggestions to use it:
>
> WARNING: mpic++ expected to find liblammpio.* in
> /usr/local/lam-7.1.1/lib
> WARNING: MPI-2 IO support will be disabled
> WARNING: mpic++ expected to find liblammpi++.* in
> /usr/local/lam-7.1.1/lib
> WARNING: MPI C++ support will be disabled
> xlc++ -I/usr/local/lam-7.1.1/include -D_REENTRANT
> -L/usr/local/lam-7.1.1/lib -lmpi -llam -ldl
> starone:~/Applications/testlam/lam-7.1.1$ ls /usr/local/lam-7.1.1
> ls: /usr/local/lam-7.1.1: No such file or directory
> starone:~/Applications/testlam/lam-7.1.1$ ls /usr/local
> bin etc include info lib man share teTeX
> starone:~/Applications/testlam/lam-7.1.1$ grep "/usr/local/lam-7.1.1"
> config.log
> PATH: /usr/local/lam-7.1.1/bin
>
> The only existence it had was in the PATH environment variable. mpicc
> had a similar problem, but one that seemed to have softer
> consequences:
>
> starone:~/Applications/testlam/lam-7.1.1$ mpicc --showme
> WARNING: mpicc expected to find liblammpio.* in
> /usr/local/lam-7.1.1/lib
> WARNING: MPI-2 IO support will be disabled
> xlc -I/usr/local/lam-7.1.1/include -D_REENTRANT
> -L/usr/local/lam-7.1.1/lib -lmpi -llam -ldl
>
> At this point, I shall delete this test directory after doing an
> uninstall, reinstall my "good" version, and back away slowly, careful
> to make no sudden movements.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
