LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Aaron Thompson (aaron.p.thompson_at_[hidden])
Date: 2007-07-22 22:16:34


Brian,
        Thank you for your response. I was indeed compiling with the --
without-memory-manager option and that's the error I get. This is
how I configure:
./configure --with-f77 --with-f90 CC=gcc CXX=g++ F77=xlf FC=xlf90 --
with-rsh=/usr/bin/ssh --prefix=/usr/local/lammpi --enable-shared --
without-memory-manager

Is there anything else that could possibly be causing this? I'd
really like to use XLF instead of GCC. We're using IBM XLF version
8.1. I know IBM has officially dropped Tiger support, but it still
seems to work for other programs.

Thank you,

Aaron Thompson
Vanderbilt University
aaron.p.thompson_at_[hidden]

On Jul 22, 2007, at 8:29 PM, Brian Barrett wrote:

> On Jul 13, 2007, at 1:00 PM, Aaron Thompson wrote:
>
>> Per Brian's advice, I'm trying to compile LAM with XLF as the
>> Fortran compiler and GCC 3.3 as the C compiler. I'm getting some
>> linker errors when compiling LAM with or without shared libs, this is
>> on a Mac G5 with Tiger. Here's the error:
>>
>> mkdir .libs
>> /usr/bin/g++ -O3 -o .libs/laminfo laminfo.o -Wl,-
>> bind_at_load ../../
>> share/libmpi/.libs/libmpi.dylib ../../share/liblam/.libs/
>> liblam.dylib -ldl
>> ld: Undefined symbols:
>> __ZNSaIcED4Ev
>> __ZNSs20_S_empty_rep_storageE
>> __ZNSsD4Ev
>> make[2]: *** [laminfo] Error 1
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all-recursive] Error 1
>> XLF is able to compile other, pure Fortran programs without error.
>> Has anyone used XLF with GCC? Is there a particular version of GCC
>> that does or doesn't work?
>
> Sorry about the slow reply -- this got lost in my inbox somehow.
> That's a really odd error from GCC. I seem to recall there being
> something funny with G++ when you try to force flat namespaces for
> some of the recent versions of the XCode toolchain. If you aren't
> already, I'd recommend trying to configure LAM with the --without-
> memory-manager option. LAM's memory hacks to deal with networks like
> InfiniBand and Myrinet/GM force a flat namespace, so disabling that
> might help.
>
>
> Good luck,
>
> Brian
>
> --
> Brian Barrett
> LAM/MPI Developer
> Make today a LAM/MPI day!
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/