[bug] Is gcc 12.1, 12.2 missing?
See original GitHub issueWhile creating a custom settings.yml
file I noticed that the support for current gcc versions 12.1, 12.2 might be missing.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
GCC 12 Release Series — Changes, New Features, and Fixes
GCC 12.2. This is the list of problem reports (PRs) from GCC's bug tracking system that are known to be fixed in the...
Read more >Bug#1025928: gcc-12: Missing changelog entry for 12.2.0-9.1
Source: gcc-12. Version: 12.2.0-9.1. Dear maintainer, I noticed that the debian/changelog entry for the 12.2.0-9.1 upload is missing from ...
Read more >GCC 12.2 Released. Over 70 bug fixes. : r/linux - Reddit
One way to do that is to start with an assembler (which is reasonably easy to make from scratch if you need to),...
Read more >Bug listing with status RESOLVED with resolution TEST ...
Bug :233 - "Emacs segfaults when merged through the sandbox. ... Bug:30399 - "Gcc failed to build" status:RESOLVED resolution:TEST-REQUEST severity:critical ...
Read more >Clang linking error MacOS Big Sur | Apple Developer Forums
It seems like there is no GCC support in Big Sur (?). I get the same message when I try to build with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @IceflowRE
It is not necessary to update the version manually in every Conan instance, it should be updated (while Conan does not update it) in one settings.yml file and use it everywhere with
conan config install
. Using your own profiles and distributing them withconan config install
is the recommended way for production anyway. Using a new compiler version typically includes installing the compiler in the machines (developers and CI agents), and updating or adding a new profile with the new compiler version.It is not possible to skip this check, it is very deep in Conan, it is not just one simple place that “validates” the value, but it is very hardcoded inside the
settings
model, how assignment, comparison, “contains”, etc. are computed. This was done this way, because as the settings are part of thepackage_id
, it is very important to have a well defined set of values, otherwise the mismatches forpackage_id
are a much bigger pain.I am very sorry that we didn’t manage to add this for 1.54, we are absolutely swamped at the moment. This is why I labeled it as “PR welcome”, thinking that if it was important enough for someone, they could put some time to contribute it.
Conan 2.0 does not change this behavior of Conan, the settings values will still be equally restricted. The release date is still not fully defined for the same reason, it is difficult to estimate with the huge load of work to do. Hopefully before the end of the year.
This is not a blocker, moving it to 1.55. Recall that you can add your own settings to
settings.yml
and also automate it withconan config install