Thanks for the response, but I found the problem... I was an idiot.
*blush*
It turns out a previous admin had left a partial installation of lammpi
on the system, and the wrong one was coming up first in the path.
Sorry for the bother,
Leigh
On Apr 21, 2005, at 5:36 PM, Brian Barrett wrote:
> It looks like there is something wrong with your build, specifically
> with the wrapper compilers. can you send the output of 'laminfo' and
> 'mpicc -showme'? They should shed some light on the problem.
>
> Thanks,
>
> Brian
>
>
> On Apr 12, 2005, at 8:18 AM, Leigh Hausman wrote:
>
>> I'm trying to compile lam from scratch on OS X (10.3.8) because I
>> need support for fortran compilers. I've installed the gnu compilers
>> collection v. 3.4.3, including g77. I compiled lam 7.1.1 and the
>> compile seemed entirely normal. I was able to lamboot several
>> machines and proceeded to work through the lamtest suite. I
>> immediately ran into difficulties during the configure process:
>>
>> $ ./configure
>> Configuring LAM test suite version 7.1.1
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for gawk... no
>> checking for mawk... no
>> checking for nawk... no
>> checking for awk... awk
>> checking whether make sets $(MAKE)... yes
>> checking build system type... powerpc-apple-darwin7.8.0
>> checking host system type... powerpc-apple
>> -darwin7.8.0
>> checking for mpicc... yes
>> checking for gcc... mpicc
>> checking for C compiler default output file name... a.out
>> checking whether the C compiler works... yes
>> checking whether we are cross compiling... no
>> checking for suffix of executables...
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether mpicc accepts -g... yes
>> checking for mpicc option to accept ANSI C... none needed
>> checking for style of include used by make... GNU
>> checking dependency style of mpicc... gcc3
>> checking for mpic++... yes
>> checking whether we are using the GNU C++ compiler... yes
>> checking whether mpic++ accepts -g... yes
>> checking dependency style of mpic++... gcc3
>> checking for mpif77... yes
>> checking whether we are using the GNU Fortran 77 compiler... yes
>> checking whether mpif77 accepts -g... yes
>> checking for ranlib... ranlib
>> checking for mpi.h... yes
>> checking for MPI_Initialized in -lmpi... yes
>> checking if have Fortran MPI bindings... no
>> checking if supposed to have Fortran MPI bindings... yes
>> configure: error: Cannot continue
>>
>> This does not appear to be the FLIBS problem described in the manual,
>> but I could be wrong. It looked similar (at least in symptom) to a
>> problem experienced by another user with IBM's XLF compilers, and
>> I've tried recompiling lam using --with-memory-manager=none and I've
>> also tried compiling the most recent beta version. The problem was
>> persistent.
>>
>> I have attached the config.log from both the lam installation and the
>> failed lamtests configure command; I would be happy to provide
>> additional information. If anyone has any suggestions, I'd appreciate
>> the help.
>>
>> <lam-config.log><lamtests-config.log>
>>
>> _______________________________________________
>> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
> --
> Brian Barrett
> LAM/MPI developer and all around nice guy
> Have a LAM/MPI day: http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|
