I used the following commands to test this out on seneca:

cd /d1/projects/MET/MET_pull_requests/met-12.1.0/beta1/
runas met_test
git clone https://github.com/dtcenter/MET MET-feature_3047_dev_env_seneca_oneapi
cd MET-feature_3047_dev_env_seneca_oneapi/
git checkout feature_3047_dev_env_seneca_oneapi
source internal/scripts/environment/development.seneca_intel_oneapi
./configure --prefix=`pwd` --enable-all

However, config.log indicates that autoconf chose the GNU compilers:

CC='gcc'
CXX='g++'
F77='gfortran'

I'm thinking we should explicitly set these to the Intel compilers instead in development.seneca_intel_openapi since the default choice of GNU does not suffice.

@JohnHalleyGotway Right! Great point! Thank you for catching that. I just modified the file to include the appropriate values. I also added a new file (internal/scripts/installation/config/install_met_env.seneca_intel_oneapi), which I used for compiling MET and its external libraries on seneca.

Thanks for the updates @jprestop!

I retested this morning and got a lot further... but it did fail with a -lgrib2c linker error. Please see below:

cd /d1/projects/MET/MET_pull_requests/met-12.1.0/beta1/
runas met_test
git clone https://github.com/dtcenter/MET MET-feature_3047_dev_env_seneca_oneapi
cd MET-feature_3047_dev_env_seneca_oneapi/
git checkout feature_3047_dev_env_seneca_oneapi
source internal/scripts/environment/development.seneca_intel_oneapi
./configure --prefix=`pwd` --enable-all
make install test

Here's the error when compiling ensemble_stat which is the first application to be linked:

/bin/ld: cannot find -lgrib2c: No such file or directory

Looks like it's named /d1/projects/MET/intel/external_libs/lib/libg2c.a instead.

Ah! Thanks, @JohnHalleyGotway. I have added the following:

export BUFRLIB_NAME=-lbufr_4
export GRIB2CLIB_NAME=-lg2c

which should resolve the problem.

@jprestop, the next error is for hdf with lidar2nc:

lidar2nc.cc:40:10: fatal error: 'hdf.h' file not found
#include "hdf.h"
         ^~~~~~~
1 error generated.
make[4]: *** [Makefile:507: lidar2nc-lidar2nc.o] Error 1

Has this actually worked for you on seneca? Or am I testing this here for the first time?

Please see this comment on the issue.

@jprestop, thanks for clarifying. Instead of configuring with --enable-all, I switched to using:
--enable-grib2 --enable-python --enable-ugrid --enable-mode_graphics
Note that this excludes --enable-lidar2nc --enable-modis.

Here's the commands:

./configure --prefix=`pwd` --enable-grib2 --enable-python --enable-ugrid --enable-mode_graphics
make clean install test >& make.log

The next failure is due to the absence of the ifx compiler:

ifx  -g -O2 -c -o calcape.o calcape.f
/bin/bash: line 1: ifx: command not found

Checking on seneca, I don't see it:

ls /var/autofs/mnt/linux-amd64/debian/bookworm/local/intel-2023.2.0.49397/compiler/2023.2.1/linux/bin/ifx
ls: cannot access '/var/autofs/mnt/linux-amd64/debian/bookworm/local/intel-2023.2.0.49397/compiler/2023.2.1/linux/bin/ifx': No such file or directory

@JohnHalleyGotway
Thanks for switching from --enable-all to --enable-grib2 --enable-python --enable-ugrid --enable-mode_graphics.

I just sent an email to helpdesk and copied you and @hsoh-u. It looks like the latest version is missing 'ifx' and I used a lesser version that had 'ifx'. Thank you @hsoh-u for suggesting I remove the paths to the compilers, which allowed this problem to come to our attention. So that John can proceed with testing, I have added the paths back in, but we can remove them once helpdesk gets 'ifx' added to the latest installation of Intel oneAPI.

@JohnHalleyGotway Perhaps I should have waited until helpdesk responded before adding those paths back in. I didn't expect such a fast response.

To update from the information in the email, Tor is going to have /nrit/ral/intel/setvars.sh point to the newer version of the compiler here: /var/autofs/mnt/linux-amd64/debian/bookworm/local/intel-2024.2.1.100/compiler/2024.2/bin.

We'll see if there are any problems since I compiled with 2023.2.0... or would you prefer I recompile using 2024.2.1.100 before you test it out again? Apologies for not doing that initially, but I did not realize it was available. It looks like it was added in October 2024.

Please install an updated version of the Intel compilers to include the ifx Fortran compiler needed to install MET.

This action was completed by Tor. Is there anything you need me to do before requesting a re-review?

@jprestop I figured you'd need to recompile the libraries upon which MET depends using the updated compiler version so that MET links to them smoothly. And that you'd ping me once you're confident that this setup is working as you'd like it to.

@JohnHalleyGotway I commented out the sourcing of setvars.sh and added the paths for the older versions of the compilers which I used to install MET and its dependent libraries. Please try testing again. It may be that we need to uncomment the sourcing of setvars.sh, but let's try this and see how it goes.