On Thu, 2006-09-21 at 13:11 -0400, Umar Farooq wrote:
> Hi,
>
> Thanks for pointing out the incorrect configure line. I still ran
> into the same problems though. I have finally been able to compile
> static programs, after noticing that the conflict was between
> /usr/lib64/libmpi and libc. By default, LAM was installing its
> libraries into /usr/lib, so the lib64/ library was never getting
> updated with the new LAM configuration.
>
> This configure line did the trick:
> ./configure --with-shared=no --with-memory-manager=none --libdir=/usr/lib64
Ah, yes, there are frequently issues with lib and lib64. This is
(unfortunately) one of the nastier side effects of the way most unix
platforms handle multilib scenarios.
One quick nitpick. --with-shared / --without-shared actually don't do
anything. The options that control whether LAM builds shared or static
are --enable-static / --disable-static and --enable-shared /
--disable-shared. Note that it is possible to build *BOTH* static and
shared libraries for LAM. By default, LAM only builds static libraries,
which is why you didn't run into problems with the options...
Brian
|
