This should handle modifying his LD_LIBRARY_PATH correctly
but doing a intel setvars.sh
How are you doing 'intel setvars.sh'? I believe you need to source that
rather than execute it. Also, there might be other files you need to
source. I have access to 2019.u3, and in the install_root, I see these 3
files:
./bin/ifortvars.sh
./bin/iccvars.sh
./bin/compilervars.sh
I don't see a setvars.sh, so things have probably changed in the latest
version from 2019.u3, but I would check the documentation and make sure
your sourcing/executing everything you need to. Some of those scripts
require arguments, too, if I remember right. We set up environment
modules to make these changes, and someone else does that now, so I
don't remember the details.
Prentice
On 3/30/21 1:25 PM, Pritchard Jr., Howard via users wrote:
Hi Ben,
You're heading down the right path....
On our HPC systems, we use modules to handle things like setting
LD_LIBRARY_PATH etc. when using Intel 21.x.y and other Intel compilers.
For example, for the Intel/21.1.1 the following were added to LD_LIBRARY_PATH
(edited to avoid posting explicit paths on our systems)
prepend-path LD_LIBRARY_PATH /path_to_compiler_install
/x86_64/oneapi/2021.1.0.2684/compiler/2021.1.1/linux/lib:path_to_compiler_install
/x86_64/oneapi/2021.1.0.2684/compiler/2021.1.1/linux/compiler/lib/intel64_lin
prepend-path PATH
/path_to_compiler_install/x86_64/oneapi/2021.1.0.2684/compiler/2021.1.1/linux/bin
prepend-path LD_LIBRARY_PATH /path_to_compiler_install
/x86_64/oneapi/2021.1.0.2684/compiler/2021.1.1/linux/lib/emu
prepend-path LD_LIBRARY_PATH /path_to_compiler_install
/x86_64/oneapi/2021.1.0.2684/compiler/2021.1.1/linux/lib/x64
prepend-path LD_LIBRARY_PATH /path_to_compiler_isnstall
/x86_64/oneapi/2021.1.0.2684/compiler/2021.1.1/linux/lib
You should check which intel compiler libraries you installed and make sure
you're prepending the relevant folders to LD_LIBRARY_PATH.
We have tested building Open MPI with the Intel OneAPI compilers and except for
ifx, things went okay.
Howard
On 3/30/21, 11:12 AM, "users on behalf of bend linux4ms.net via users"
<users-boun...@lists.open-mpi.org on behalf of users@lists.open-mpi.org> wrote:
I think I have found one of the issues. I took the check c program from
openmpi
and tried to compile and got the following:
[root@jean-r8-sch24 benchmarks]# icc dummy.c
ld: cannot find -lstdc++
[root@jean-r8-sch24 benchmarks]# cat dummy.c
int
main ()
{
;
return 0;
}
[root@jean-r8-sch24 benchmarks]#
Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS,
39212
"Never attribute to malice, that which can be adequately explained by
stupidity"
- Hanlon's Razor
________________________________________
From: users <users-boun...@lists.open-mpi.org> on behalf of bend linux4ms.net
via users <users@lists.open-mpi.org>
Sent: Tuesday, March 30, 2021 12:00 PM
To: Open MPI Users
Cc: bend linux4ms.net
Subject: Re: [OMPI users] Newbie With Issues
Thanks Mr Heinz for responding.
It maybe the case with clang, but doing a intel setvars.sh then issuing
the following
compile gives me the message:
[root@jean-r8-sch24 openmpi-4.1.0]# icc
icc: command line error: no files specified; for help type "icc -help"
[root@jean-r8-sch24 openmpi-4.1.0]# icc -v
icc version 2021.1 (gcc version 8.3.1 compatibility)
[root@jean-r8-sch24 openmpi-4.1.0]#
Would lead me to believe that icc is still available to use.
This is a government contract and they want the latest and greatest.
Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS,
39212
"Never attribute to malice, that which can be adequately explained by
stupidity"
- Hanlon's Razor
________________________________________
From: Heinz, Michael William <michael.william.he...@cornelisnetworks.com>
Sent: Tuesday, March 30, 2021 11:52 AM
To: Open MPI Users
Cc: bend linux4ms.net
Subject: RE: Newbie With Issues
It looks like you're trying to build Open MPI with the Intel C compiler.
TBH - I think that icc isn't included with the latest release of oneAPI, I
think they've switched to including clang instead. I had a similar issue to
yours but I resolved it by installing a 2020 version of the Intel HPC software.
Unfortunately, those versions require purchasing a license.
-----Original Message-----
From: users <users-boun...@lists.open-mpi.org> On Behalf Of bend
linux4ms.net via users
Sent: Tuesday, March 30, 2021 12:42 PM
To: Open MPI Open MPI <users@lists.open-mpi.org>
Cc: bend linux4ms.net <b...@linux4ms.net>
Subject: [OMPI users] Newbie With Issues
Hello group, My name is Ben Duncan. I have been tasked with installing
openMPI and Intel compiler on a HPC systems. I am new to the the whole HPC and
MPI environment so be patient with me.
I have successfully gotten the Intel compiler (oneapi version from
l_HPCKit_p_2021.1.0.2684_offline.sh installed without any errors.
I am trying to install and configure the openMPI version 4.1.0 however
trying to run configuration for openmpi gives me the following error:
============================================================================
== Configuring Open MPI
============================================================================
*** Startup tests
checking build system type... x86_64-unknown-linux-gnu checking host
system type... x86_64-unknown-linux-gnu checking target system type...
x86_64-unknown-linux-gnu checking for gcc... icc checking whether the C
compiler works... no
configure: error: in `/p/app/openmpi-4.1.0':
configure: error: C compiler cannot create executables See `config.log'
for more details
With the error in config.log being:
configure:6499: $? = 0
configure:6488: icc -qversion >&5
icc: command line warning #10006: ignoring unknown option '-qversion'
icc: command line error: no files specified; for help type "icc -help"
configure:6499: $? = 1
configure:6519: checking whether the C compiler works
configure:6541: icc -O2 conftest.c >&5
ld: cannot find -lstdc++
configure:6545: $? = 1
configure:6583: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "Open MPI"
| #define PACKAGE_TARNAME "openmpi"
| #define PACKAGE_VERSION "4.1.0"
| #define PACKAGE_STRING "Open MPI 4.1.0"
| #define PACKAGE_BUGREPORT
"https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.open-mpi.org%2Fcommunity%2Fhelp%2F&data=04%7C01%7Cmichael.william.heinz%40cornelisnetworks.com%7C452071550e3c40842a6008d8f39b1ab4%7C4dbdb7da74ee4b458747ef5ce5ebe68a%7C0%7C0%7C637527194795401887%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=MqdORKp%2Fbf6mS7NQ51RjPUe0WVVcBITwP0HpxpYyBjI%3D&reserved=0";
| #define PACKAGE_URL ""
| #define OPAL_ARCH "x86_64-unknown-linux-gnu"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:6588: error: in `/p/app/openmpi-4.1.0':
configure:6590: error: C compiler cannot create executables See
`config.log' for more details
My configure line looks like:
./configure --prefix=/p/app/compilers/openmpi-4.1.0/openmpi-4.1.0.intel
--enable-wrapper-rpath --disable-libompitrace
--enable-mpirun-prefix-by-default --enable-mpi-fortran
SO what am I doing wrong , or is it something else ?
Thanks
Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS, 39212
"Never attribute to malice, that which can be adequately explained by stupidity"
- Hanlon's Razor
