Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue Encountered While Installing NCEPLIBS-ip with intel #267

Open
met-sree opened this issue Dec 31, 2024 · 3 comments
Open

Issue Encountered While Installing NCEPLIBS-ip with intel #267

met-sree opened this issue Dec 31, 2024 · 3 comments

Comments

@met-sree
Copy link

Dear Sir,

I tried to install the NCEPLIBS-ip with intel as per the previous suggestions using the following steps:

tar xvf v5.1.0.tar.gz
mv NCEPLIBS-ip-5.1.0 ip510
cd ip510
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/home/centos/model_build/build_iola/external_libs/ip510/build/install ../../ip510
make
make test

However, I encountered the following errors, which are attached in the log.make file (make log) and the log.maketest file (make test log).

Could you please help me resolve these issues?

Thankyou,
Sree

log.make.txt
log.make_test.txt

@met-sree met-sree changed the title ssue Encountered While Installing NCEPLIBS-ip with intel Issue Encountered While Installing NCEPLIBS-ip with intel Dec 31, 2024
@AlexanderRichert-NOAA
Copy link
Contributor

Hi Sree-- Can you please 1) send the output of your CMake step (which will show me what compiler versions you're using, etc.), and 2) for the test step, run "ctest --output-on-failure" so that I can see the error messages for each failed job?

@met-sree
Copy link
Author

met-sree commented Jan 1, 2025

Sir,
Please find the below attached error log files of cmake and ctest.

log.cmake.txt
log.ctest.txt

@AlexanderRichert-NOAA
Copy link
Contributor

Hm darn, yeah these are segfaults that I was seeing on my personal machine when using Intel+CentOS (I think I was using CentOS 8). You might try fixing it by setting ulimit -s unlimited, but other than that, I think it was a bug somewhere in the Intel compiler that I don't think I ever got to the bottom of. If you're able to test on another OS (e.g., Ubuntu) that might also help to confirm that it's a compiler issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants