LAM/MPI logo

LAM/MPI General User's Mailing List Archives

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

From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2005-06-21 07:32:11


The issue is GNU Libtool here. The Libtool that ships with LAM 7.1.1
is fairly old; due to some fantastic work from Ralf Wildenhues, recent
versions of Libtool (e.g., 1.5.18) now correctly support the PGI 5.2
compilers.

The latest LAM beta tarball ships with a much newer version of Libtool.
  If you could grab that and give it a whirl, it should build properly
for you:

        http://www.lam-mpi.org/beta/

On Jun 21, 2005, at 6:35 AM, Baker D.J. wrote:

> Hi All,
> A while ago I downloaded the latest version of lam (v7.1.1), and
> did a successful default install on our server. Our server, by the way,
> is a 64bit AMD machine running RH Release 3, Update 2. I then decided
> to
> see if I could build, and use lam built with the Portland group
> compiler
> (v 5.2). The build appeared to go well, however the resulting mpicc
> will
> not work. Trying to do a compile/load yields...
>
> mpicc: relocation error:
> /import/raid1-LG1/local/pgi-5.2.2/linux86-64/5.2/lib/libpthread.so.0:
> symbol _h_errno, version GLIBC_2.2.5 not defined in file libc.so.6 with
> link time reference
>
> As part of the configure I defined the appropriate FC, F77, CC and CXX.
> Does anyone in the lam community have any ideas what might be going
> wrong here, please? Any advice/pointers would be apprecaited.
>
> Thank you -- David.
>
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>

-- 
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/