-
Notifications
You must be signed in to change notification settings - Fork 45
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
Error in opening compiled module files #407
Comments
Sorry - just back from vacation. It looks like there are missing |
OK - I see now that your The usual cause of these sorts of things is that your environment is using a different Fortran compiler/version that what was used to build pFUnit. E.g., it is clear you are using ifort for compiling your test, but is it possible that pFUnit itself was built with gFortran? If you save the output from the initial CMake command that may shed some light on the matter. |
Hi, and sorry for the late response. PFUNIT_INSTALL_DIR is a full path I have redacted. Its not a variable at all. pFUnit was built with the same version of ifort. From the file
And asking ifort its version from the terminal,
|
Hello, Quick update: things appear to work as intended as of commit 253ef29. Might be helpful to investigate what has changed since then. |
Hello, I have tried installing pFUnit 4.6 in my workplace in a path accessible to my colleagues.
The build process went smoothly,
make tests
reports that all tests were passed, andmake install
did not report any errors either.But when I actually try to compile a test against my fortran application, the compilation fails, complaining about not being able to find compiled modules and asking me to check include paths.
This is the exact command the makefile executes :
And I get lots of errors of this type :
I have already checked that all the include paths in the command are valid, and seem to contain expected files. Here is the output for
$ls PFUNIT_INSTALL_DIR/PFUNIT-4.6/include
Please advise.
The text was updated successfully, but these errors were encountered: