LAM/MPI logo

LAM/MPI General User's Mailing List Archives

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

From: Martin Siegert (siegert_at_[hidden])
Date: 2005-11-09 19:47:30


Hi Alex,

the problem is usually that a libtool ignores the -m64 flag; in my
experience even if LDFLAGS include that flag. You can check that by
finding the corresponding libtool line that leads to the make error:

libtool --mode=link gcc -m64 -o ...

usually leads to something like

gcc -shared -o ...

i.e., the gcc command following the libtool line is missing the -m64
flag. The only way that I found to work around this is to edit libtool
directly after you ran configure.

Somewhere there is a line

    compiler_flags=

Change this to

    compiler_flags='-m64'

and then run "make".

This is from my experience with almost any software package that I try
to compile on a 64bit platform (in my case powerpc64). I have not
attempted to compile LAM yet, thus it is possible that this does not
apply to the libtool version distributed with LAM. Nevertheless, it
is worth a try.

Cheers,
Martin

-- 
Martin Siegert
Head, HPC_at_SFU
WestGrid Site Manager
Academic Computing Services                        phone: (604) 291-4691
Simon Fraser University                            fax:   (604) 291-4242
Burnaby, British Columbia                          email: siegert_at_[hidden]
Canada  V5A 1S6
On Wed, Nov 09, 2005 at 09:28:43PM -0300, Alex A. Schmidt wrote:
> Dear Brian,
> 
> (I had to change my e-mail address at the LAM/MPI mailing list
> since my previous webmail was having some trouble with annexed
> files... sic!)
> 
> I'm quite sure that CFLAGS, FFLAGS, and CXXFLAGS were set
> to -m64 before I tried to configure lamtest. In any case I did
> it all over again and got the same warning messages (and error messages
> from 'make check').
> 
> I also tried to set LDFLAGS to "-m64 -L/usr/local/bin/64" following
> Ralf Wildenhues's suggestion but it looks to me that it didn't produce
> any effect at all.
> 
> The complete config.log is annexed to this message.
> 
> Thanks for the help so far,
> 
> Alex
> 
> 
> -----Mensagem original-----
> De:   Brian Barrett <brbarret_at_[hidden]>
> Enviada em: 09/11/2005 14:48:20
> Para: General LAM/MPI mailing list <lam_at_[hidden]>
> Assunto: Re: LAM: 64 bit lamtest-7.1.1 failed for Solaris 9 with gcc-3.4.2
> 
> On Nov 8, 2005, at 6:58 PM, aas_at_[hidden] wrote:
> 
> > Hello,
> >
> > I' m trying to build LAM-7.1.1 for a SunFire V220 machine
> > running recommended patched Solaris 9 with gcc-3.4.2
> > (and everything it needs from sunfreeware).
> >
> > Configuration, making and building of LAM-7.1.1 went just fine with:
> >
> > '.configure --libdir=/usr/local/lib/64'
> >
> > CFLAGS=-m64
> > FFLAGS=-m64
> > CXXFLAGS=-m64
> >
> > and
> >
> > LD_LIBRARY_PATH_32=/usr/lib:/usr/openwin/lib:/usr/local/lib
> > LD_LIBRARY_PATH_64=/usr/lib/64:/usr/openwin/lib/64:/usr/local/lib/64
> >
> > which I got from 'man ld.so.1'.
> >
> > but lamtest configuration says:
> >
> > ld: warning: file /usr/local/lib/64/liblamf77mpi.a(dupfn_f.o):
> > wrong ELF class: ELFCLASS64
> > ld: elf error: file /usr/local/lib/64/libmpi.a(MPI.o): elf_getshdr:
> > Request error: class file/memory mismatch
> > ld: elf error: file /usr/local/lib/64/libmpi.a(MPI.o): elf_getshdr:
> > Request error: class file/memory mismatch
> > ld: elf error: file /usr/local/lib/64/libmpi.a(MPI.o): elf_getshdr:
> > Request error: class file/memory mismatch
> > ld: elf error: file /usr/local/lib/64/libmpi.a(MPI.o): elf_getshdr:
> > Request error: class file/memory mismatch
> > ld: elf error: file /usr/local/lib/64/libmpi.a(MPI.o): elf_getshdr:
> > Request error: class file/memory mismatch
> > ld: warning: file /usr/local/lib/64/libmpi.a(MPI.o): wrong ELF
> > class: ELFCLASS64
> > ld: fatal: File processing errors. No output written to conftest
> > collect2: ld returned 1 exit status
> > mpif77: No such file or directory
> 
> You need to make sure that CFLAGS, FFLAGS, and CXXFLAGS are set to -
> m64 when running the lamtests configure script as well as the LAM/MPI
> configure script.  The wrapper compilers in LAM/MPI do not
> automatically pick up and include the -m64 flag, so it needs to be
> given to the lamtests configure script.
> 
> If that doesn't clean things up, please include the full config.log
> from running the lamtest configure script.
> 
> Thanks,
> 
> Brian
> 
> 
> -- 
>    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/
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/