Error installing pFUnit on WSL(Ubuntu-20.04.5) #382
Comments
rholden813
changed the title
|
My apologies - it has been a busy week. I will take a deeper look over the weekend. |
|
This is a weird error. The initial output you provided from the CMake command itself is much shorter than I would have expected. One guess is that you have installed some of these packages already and CMake is finding old/partial installations? Could you start again from scratch and upload the full output from the CMake command and then the output from a serial build with |
|
Thanks for getting back to me. Here is the result of After running |
|
Hmm. Well there is no error in that output. But it did not complete either. Even more odd, it looks like ExceptionVector.F90 built successfully, despite no record of having built Exception.F90 first. The CMake step is also reporting that it is using FARGPARSE in a manner that suggests it is finding a previous installation, and I suspect this is related to your problems. E.g., you might have conflicting versions of things being built together. CMake is unfortunately too good at searching many places for installs. For completeness, please let me know which version of CMake you are using. But I think the solution will be to find and purge earlier builds. The very latest CMake does have an option to restrict the search path, so if you cannot find/delete the existing packages, we can show you how to modify your CMake command line to force it. |
|
I suspect you are correct and CMake is using conflicting versions during the installation. The CMake version I am using is CMake-3.25.0-rc1. I'll have a look through and delete any old builds. Should I not be able to find them, if you could show me how to modify the CMake command, that would be great. |
|
The CMake option (as of 3.23) is You'll need to add any system paths that CMake may be searching; unfortunately the list is not short, and it is OS dependent. |
|
When building a fresh docker image, the same error as before ( |
|
@tclune FYI we're encountering the exact same problem in our GitHub Actions CI pipeline, just noticed it now. We use We usually cache a successful pFUnit build, approximately a month ago our CI also did a clean build using This indeed looks like an incompatibility between |
|
@mathomp4 - just in case you are not following this ticket. Probably not a fun one to track down. |
|
We are looking a bit more closely at the CI today. At first glance, the problem appears to be that CMake 3.25 is incorrectly processing the dependencies for files that have 2 Fortran modules in them. I usually just have 1 module per file, but for some special cases I do violate that rule. If so, it should be possible to submit a reproducer to the CMake team. So far we don't see anything in the CMake release notes that would point a finger at anything. We know 3.22.1 works and 3.25 fails. |
|
@n-claes This is indeed a CMake 3.25 + pFUnit issue. In #399 I added a fix to "pin" CMake to 3.24.3 until CMake can respond to an issue I opened (see https://gitlab.kitware.com/cmake/cmake/-/issues/24203). For now, you might want to do the same thing in your CI (and I guess locally, don't move to 3.25.0 if possible) |
Hi,
I am trying to install pFUnit on a WSL (Ubuntu-20.04.5) on my Windows laptop. I am using
gfortran-11,gcc-11,g++-11andcmake 3.25.0-rc1I come across an error when using
make installAs per the instructions given to build and install pFUnit, I have used the following:
As a result of
cmake .., the code returns:Using
make tests, the code successfully completes all of the tests, as shown below:But, to complete the installation, using
make install, I receive an error shortly afterfargparseis built:I was unable to find a similar error to this one online and I have spent many hours today, along with my colleagues to find a solution. Any help or guidance would be much appreciated.
The text was updated successfully, but these errors were encountered: