-
Notifications
You must be signed in to change notification settings - Fork 57
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
Support gcc 11 #169
Comments
Dear David, |
thumbs up |
(sharpy_env) [buttermelted@thinkpad sharpy]$ python -m unittest changed my issues to this, will try to compile with less threads |
changing from -j6 to -j2 |
Dear x3oo, This issue sometimes happens when you have not checkout the same branch in SHARPy and the submodules (xbeam and UVLM). Can you doublecheck that? I highly doubt chaning the number of cores will make a difference. Best regards |
git submodule update --remote |
running unittest still testing whoooo |
Ran 52 tests in 1004.682s OK (skipped=4) |
thanks for programming and releasing sharpy, thanks for the fast support. |
@DavidAnderegg how did you find the solution? i am asking so i can solve it next time myself |
Basically I googled the error code until I figured out that a certain GLIBC - Version corresponds to a certain gcc version. Then it was only putting the knowledge and the error message together. |
Describe the bug
It is not possible to use sharpy with gcc11 because the required scipy(1.3.2) version was built using gcc9. It might be possible to force scipy to compile locally with gcc11.
I just wanted to let you know, may be add a little note to the install instructions?
Anyways, thank you for making this all open source!
To Reproduce
First build it using gcc11. Then, run the tests.
Expected behavior
I am not sure? Maybe upgrade scipy or mention it somewhere?
System Info (please complete the following information):
Additional context
I fixed it on arch with installing the aur-packages
gcc9
,gcc9-fortran
,gcc9-libs
and this cmake command:FC=gfortran-9 CXX=g++-9 CC=gcc-9 cmake ..
The text was updated successfully, but these errors were encountered: