LAM/MPI logo

LAM/MPI General User's Mailing List Archives

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

From: Ralf Wildenhues (Ralf.Wildenhues_at_[hidden])
Date: 2005-11-09 03:04:53


Hi Alex,

* aas_at_[hidden] wrote on Wed, Nov 09, 2005 at 12:58:34AM CET:
>
> 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'.

I don't think this should be necessary.

> 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

Probably another incarnation of the Libtool bug Brian reported recently.
Should be fixed in Libtool-1.5.22, which is hopefully done very soon.

You should be able to work around it by one of
  LDFLAGS=-m64
  LDFLAGS=-Wl,-64
  LDFLAGS=-64

(sorry, I don't remember how things worked exactly in LAM; correct me if
I'm wrong).

Cheers,
Ralf