-
Notifications
You must be signed in to change notification settings - Fork 345
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
GEOS compilation fails with Intel compiler #460
Comments
You could strip out those lines, or even just remove astyle from the cmakelists.txt file entirely. It's only used for code formatting so it's not necessary at all. I have no idea why icc chokes on that character string. |
I wonder if it may be an issue with the build environment or compiler flags, e.g. spack/spack#14450 or https://community.intel.com/t5/Intel-C-Compiler/improper-UTF-8-characters-handling-by-ICC-on-Windows/td-p/1099463 Adding a |
Agree, see gh-461 |
I switched from the Autotools build to the CMake build and the problem magically went away! |
Nevermind, I was using GCC that time. Trying again with Intel... |
For what it's worth, I'm unable to reproduce the error using the free Intel oneAPI:
this compiles fine (no errors, no warnings), but fails some of the tests:
With the initial error, it's likely there is something strange going on with non-Latin locales. |
I'm going to guess that the regress fails are related to the |
I might as well catalogue the 10 excerpts from
The bright side of this is that 97% tests passed, only 10 tests failed out of 377. |
Okay, I'm able to build GEOS with Intel with #461 and |
…store the M (because we have nowhere to store it right now). References #460
No, a little too niche. |
I'm trying to compile GEOS 3.9.1 on CentOS 7 with Intel 19.1.1.217 and I'm getting the following compilation error:
Here is the full build log.
Any suggestions for how to resolve this issue?
The text was updated successfully, but these errors were encountered: