LAM/MPI General User's Mailing List Archives

From: Tim Prince (tprince_at_[hidden])
Date: 2004-12-05 01:52:56

• Next message: Jeff Squyres: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"
• Previous message: Tim Prince: "Re: LAM: lam and intel"
• In reply to: Kamaraju Kusumanchi: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"
• Next in thread: Jeff Squyres: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"
• Reply: Jeff Squyres: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"

At 03:22 PM 12/4/2004, Kamaraju Kusumanchi wrote:

>So there is no libc.so.6 offered by intel. I have no idea why a.out
>should even depend on it in the first place.

lam has explicit calls to libc functions. In order to provide gcc
compatibility, Intel run-time libraries also must employ libc consistently
with gcc. FSF doesn't call it gnu linux for nothing.

Tim Prince

• Next message: Jeff Squyres: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"
• Previous message: Tim Prince: "Re: LAM: lam and intel"
• In reply to: Kamaraju Kusumanchi: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"
• Next in thread: Jeff Squyres: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"
• Reply: Jeff Squyres: "Re: LAM: unable to compile the lam-mpi libraries with ifort +{gcc|icc}"