[nucci]

I am running into issues building SU2 version 8.0.1 "Harrier" using the Intel oneAPI 2021 release.

I entered the following build command:

./meson.py build -Dwith-mpi=enabled -Denable-mkl=true

but meson failed with the following:

Command line: icpc /storage/group/RISE/nucci/SU2/build/meson-private/tmpxgsw5rj
l/testfile.cpp -o /storage/group/RISE/nucci/SU2/build/meson-private/tmpxgsw5rjl/
output.obj -c -D_FILE_OFFSET_BITS=64 -O0 -fpermissive -diag-error 10006 -diag-er
ror 10148 -diag-error 10155 -diag-error 10156 -diag-error 10157 -diag-error 1015
8 -Wclass-memaccess -Wno-class-memaccess

Code:
extern int i;
int i;

Compiler stdout:

Compiler stderr:
icpc: command line error: option '-Wclass-memaccess' not supported

Compiler for C++ supports arguments -Wno-class-memaccess: NO
icc binary missing from cross or native file, or env var undefined.
Trying a default icc fallback at icc
icc found: YES (/swst/apps/intel-oneapi-compilers/2021.4.0_gcc-8.5.0/compiler/2021.4.0/linux/bin/intel64/icc)
Could not generate link and compile args for icc.
icc: command line warning #10006: ignoring unknown option '-show'
icc: command line error: no files specified; for help type "icc -help"

Run-time dependency MPI for c found: NO (tried system)

meson.build:60:2: ERROR: Could not generate link and compile args for icc.
icc: command line warning #10006: ignoring unknown option '-show'
icc: command line error: no files specified; for help type "icc -help"

--

I tried using Intel oneAPI 2024 but that was even worse, with meson not even finding the compiler.

I checked the build notes and didn't see anything specific regarding any other options to try for the 2021 oneAPI suite.

Has anyone else run into this, wand what was the fix?

Thanks.

[CleverBoy]

I am not sure about the solution since I do not use Oneapi. Did you put setvars.sh location as source in your bash profile? Something like this:

source your_directory/intel/oneapi-2021/setvars.sh

After running source on your bash file it should start openmpi and maybe this could work.

[nucci]

Unfortunately I still get the same error when I try to build even after sourcing setvars

Note that the Intel oneAPI suite works normally for building other applications without performing this extra source step.

There's something in whatever recipe the meson script follows that is making some kind of mistake. I'm unfamiliar with it, so perhaps someone who has more experience using meson can guide me through the process.

Here's the output which appears the same as before:

```
$ ./meson.py build -Dwith-mpi=enabled -Denable-mkl=true
update CoolProp
/storage/group/RISE/nucci/SU2/subprojects/CoolProp
/storage/group/RISE/nucci/SU2
CoolProp updated
The Meson build system
Version: 0.61.1
Source dir: /storage/group/RISE/nucci/SU2
Build dir: /storage/group/RISE/nucci/SU2/build
Build type: native build
Project name: SU2
Project version: 8.0.1 "Harrier"
C compiler for the host machine: icc (intel 2021.4.0 "icc (ICC) 2021.4.0 20210910")
C linker for the host machine: icc ld.bfd 2.30-123
C++ compiler for the host machine: icpc (intel 2021.4.0 "icpc (ICC) 2021.4.0 20210910")
C++ linker for the host machine: icpc ld.bfd 2.30-123
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program python3 found: YES (/storage/icds/RISE/sw8/anaconda/anaconda3/bin/python3)
WARNING: Python files installed by Meson might not be found by python interpreter.
This warning can be avoided by setting "python.platlibdir" option.
WARNING: Python files installed by Meson might not be found by python interpreter.
This warning can be avoided by setting "python.purelibdir" option.
Compiler for C++ supports arguments -Wno-ignored-qualifiers: NO
Compiler for C++ supports arguments -Wno-unused-parameter: YES
Compiler for C++ supports arguments -Wno-deprecated-declarations: YES
Compiler for C++ supports arguments -Wno-error=cast-function-type: YES
Compiler for C++ supports arguments -Wno-cast-function-type: NO
Compiler for C++ supports arguments -Wno-error=stringop-truncation: YES
Compiler for C++ supports arguments -Wno-stringop-truncation: NO
Compiler for C++ supports arguments -Wno-error=missing-field-initializers: YES
Compiler for C++ supports arguments -Wno-missing-field-initializers: YES
Compiler for C++ supports arguments -Wno-error=class-memaccess: YES
Compiler for C++ supports arguments -Wno-class-memaccess: NO
icc found: YES (/swst/apps/intel-oneapi-compilers/2021.4.0_gcc-8.5.0/compiler/2021.4.0/linux/bin/intel64/icc)
Run-time dependency MPI for c found: NO (tried system)

meson.build:60:2: ERROR: Could not generate link and compile args for icc.
icc: command line warning #10006: ignoring unknown option '-show'
icc: command line error: no files specified; for help type "icc -help"
```

[nucci]

I solved the problem. It appears the meson step is particular about which -Dwith-mpi option.

I was using "enabled" and apparently this was the root of the issue. I switched to "auto" and everything proceeded.

I then ran into an issue with ninja, with a build step failing because it was using the C compiler rather then the MPI C compiler invocation.

This is what I did to render a successful build with the Intel oneAPI 2021.04 suite:

First I loaded my site-dependent modules for the cmake3, the Intel compiler, Intel MPI, and IntelMKL:

module load intel/2024.0
module load mpi/2021.11
module load mkl/2024.0
module load anaconda/2021.11
module load cmake/3.25.2-intel-2021.4

This is a hack to fix compilation issues, I set these after loading the modules abve, which define the $MPICX and $MPICXX env vars:

export CC=$MPICX
export CXX=$MPICXX

Run the meson build script:

./meson.py build -Dwith-mpi=auto -Denable-mkl=true -Denable-tecio=true

A couple of warnings get thrown, but no show-stoppers. The ninja build and install steps proceed normally at this point.

I have not tried this yet with the Intel oneAPI 2024 suite. There are changes to the C compiler in this release, but hopefully those are non-issues.

[CleverBoy]

I am glad you solved it. Thanks for detailed explanation