Hi,

what about putting the "-static-intel" into a configuration file for the Intel 
compiler. Besides the default configuration, one can have a local one and put 
the path in an environment variable IFORTCFG (there are other ones for C/C++).

$ cat myconf 
--version
$ export IFORTCFG=/home/reuti/myconf
$ ifort
ifort (IFORT) 19.0.5.281 20190815

-- Reuti


> Am 22.01.2021 um 15:49 schrieb Alvaro Payero Pinto via users 
> <users@lists.open-mpi.org>:
> 
> Dear Open MPI support team,
> 
> I am trying to install Open MPI with Intel compiler suite for the Fortran 
> side and GNU compiler suite for the C side. For factors that don’t depend 
> upon me, I’m not allowed to change the C compiler suite to Intel one since 
> that would mean an additional license.
> 
> Problem arises with the fact that the installation should not dynamically 
> depend on Intel libraries, so the flag “-static-intel” (or similar) should be 
> passed to the Fortran compiler. I’ve seen in the FAQ that this problem is 
> solved by passing an Autotools option “-Wc,-static-intel” to the variable 
> LDFLAGS when invoking configure with Intel compilers. This works if both 
> C/C++ and Fortran compilers are from Intel. However, it crashes if the 
> compiler suite is mixed since GNU C/C++ does not recognise the 
> “-static-intel” option.
> 
> Is there any way to bypass this crash and to indicate that such option should 
> only be passed when using Fortran compiler?
> 
> Configure call to reproduce the crash is made as follows:
> 
> ./configure --prefix=/usr/local/ --libdir=/usr/local/lib64/ 
> --includedir=/usr/local/include/ CC=gcc CXX=g++ 'FLAGS=-O2 -m64' 'CFLAGS=-O2 
> -m64' 'CXXFLAGS=-O2 -m64' FC=ifort 'FCFLAGS=-O2 -m64' 
> LDFLAGS=-Wc,-static-intel
> 
> Please, find attached the output from configure and config.log.
> 
> Additional data:
> 
> ·         Operating system SLES12 SP3.
> ·         Open MPI version 4.0.5
> ·         Intel Fortran compiler version 17.0.6
> ·         GNU C/C++ compiler version 4.8.5.
> 
> I’ll very much appreciate any help provided to solve this problem.
> 
> Kind regards,
> 
> Álvaro
> 
>  
> <outputs.tar.bz2>

Reply via email to