-
Notifications
You must be signed in to change notification settings - Fork 245
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
Minimal compiler versions #2127
Comments
Also, on the same line of thought, should we try to consolidate |
For inclusions of headers, we require that GNU compatible compilers is able to utilize attributes and macros from We can still solve the issue by pushing something like #if defined(__GNUC__) && __GNUC__ > SOME_NUMBER
and this goes for everything. We could support GCC 3 if we'd like to. However, as a general note, I do not like the idea of having to support old compilers. If you build the newest release of a package, I think it is reasonable to expect that you have software that is somewhat new (say, at most two years old). |
But, it would be good to document or clarify in the documentation. |
Though it's not clear that two years is a reasonable cutoff. Lots of people are on LTS distros way older than that, and there are institutional HPC clusters where the installed GCC version dates back to the geologic era of the volcanic sediments under the ground of the building where the computers are housed. In my experience new compiler versions are more problematic anyway. The old versions have a known list of limitations; new versions always introduce creative new issues :-) |
In #2054 we noted that GCC 8 is no longer supported.
What is the minimal version required to build flint?
What about clang?
Or better, what features do we need?
Given this, where should we add this to the documentation?
Can we add this to the configure?
The text was updated successfully, but these errors were encountered: