Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Problems compiling 1.2.4 using Intel Compiler 10.1.006 on Leopard
From: Warner Yuen (wyuen_at_[hidden])
Date: 2007-12-11 21:32:00


Has anyone gotten Open MPI 1.2.4 to compile with the latest Intel
compilers 10.1.007 and Leopard? I can get Open MPI-1.2.4 to to build
with GCC + Fortran IFORT 10.1.007. But I can't get any configuration
to work with Intel's 10.1.007 Compilers.

The configuration completes, but the compilation fails fairly early,

My compiler settings are as follows:

For GCC + IFORT (This one works):
export CC=/usr/bin/cc
export CXX=/usr/bin/c++
export FC=/usr/bin/ifort
export F90=/usr/bin/ifort
export F77=/usr/bin/ifort

For using all Intel compilers (The configure works but the compilation
fails):

export CC=/usr/bin/icc
export CXX=/usr/bin/icpc
export FC=/usr/bin/ifort
export F90=/usr/bin/ifort
export F77=/usr/bin/ifort
export FFLAGS=-no-multibyte-chars
export CFLAGS=-no-multibyte-chars
export CXXFLAGS=-no-multibyte-chars
export CCASFLAGS=-no-multibyte-chars

_defined,suppress -o libasm.la asm.lo atomic-asm.lo -lutil
libtool: link: ar cru .libs/libasm.a .libs/asm.o .libs/atomic-asm.o
ar: .libs/atomic-asm.o: No such file or directory
make[2]: *** [libasm.la] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Warner Yuen
Scientific Computing Consultant
Apple Computer
email: wyuen_at_[hidden]
Tel: 408.718.2859
Fax: 408.715.0133

On Nov 22, 2007, at 2:26 AM, users-request_at_[hidden] wrote:

> ------------------------------
>
> Message: 2
> Date: Wed, 21 Nov 2007 15:15:00 -0500
> From: Mark Dobossy <mdobossy_at_[hidden]>
> Subject: Re: [OMPI users] Problems compiling 1.2.4 using Intel
> Compiler 10.1.006 on Leopard
> To: Open MPI Users <users_at_[hidden]>
> Message-ID: <99CA0551-9BF4-47C0-85C2-6B2126A83651_at_[hidden]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> Thanks for the suggestion Jeff.
>
> Unfortunately, that didn't fix the issue.
>
> -Mark
>
> On Nov 21, 2007, at 7:55 AM, Jeff Squyres wrote:
>
>> Can you try also adding CCASFLAGS=-no-multibyte-chars?
>>
>