Potential issue with MPI wrapper for ifx

[Glenn_Hammond]

I installed oneAPI on my Ubuntu 22.04 Linux box (compiler version 2025.2, mpi version 2021.16, mkl version 2025.2). When attempting to use the mpiifx wrapper for ifx in a PETSc library configure script, I run into the following error:

--------------

Executing: mpiifx -c -o /tmp/petsc-_6vxwwl5/config.setCompilers/conftest.o -I/tmp/petsc-_6vxwwl5/config.setCompilers /tmp/petsc-_6vxwwl5/config.setCompilers/conftest.F90
stdout: /opt/intel/oneapi/mpi/2021.16/bin/mpiifx: 1: eval: ifxexport: not found
Possible ERROR while running compiler: exit code 127
stderr:
/opt/intel/oneapi/mpi/2021.16/bin/mpiifx: 1: eval: ifxexport: not found
Source:
program main

end

Error testing Fortran compiler: Cannot compile FC with mpiifx.
MPI compiler wrapper mpiifx failed to compile

Executing: mpiifx -show
stdout: ifxexport -I"/opt/intel/oneapi/mpi/2021.16/include/mpi" -I"/opt/intel/oneapi/mpi/2021.16/include" -I"/opt/intel/oneapi/mpi/2021.16/include/mpi" -L"/opt/intel/oneapi/mpi/2021.16/lib" -L"/opt/intel/oneapi/mpi/2021.16/lib" -Xlinker --enable-new-dtags -Xlinker -rpath -Xlinker "/opt/intel/oneapi/mpi/2021.16/lib" -Xlinker -rpath -Xlinker "/opt/intel/oneapi/mpi/2021.16/lib" -lmpifort -lmpi -ldl -lrt -lpthread
MPI compiler wrapper mpiifx is likely incorrect.
Use --with-mpi-dir to indicate an alternate MPI.
Deleting "FC"

--------------

I can confirm independently (outside the PETSc configure script) that ifxexport is being called by the wrapper:

--------------

$ mpiifx -show
ifxexport -I"/opt/intel/oneapi/mpi/2021.16/include/mpi" -I"/opt/intel/oneapi/mpi/2021.16/include" -I"/opt/intel/oneapi/mpi/2021.16/include/mpi" -L"/opt/intel/oneapi/mpi/2021.16/lib" -L"/opt/intel/oneapi/mpi/2021.16/lib" -Xlinker --enable-new-dtags -Xlinker -rpath -Xlinker "/opt/intel/oneapi/mpi/2021.16/lib" -Xlinker -rpath -Xlinker "/opt/intel/oneapi/mpi/2021.16/lib" -lmpifort -lmpi -ldl -lrt -lpthread

--------------

I Google online for "ifxexport" and it does not exist, nor do others report similar issues elsewhere.

Is it possible that a call to "export" within a shell script (e.g., setting an environment variable) is missing a space concatenating ifx+export?

Thank you in advance for any insight.

Glenn