Closed FabioLolix closed 3 years ago
This is because clang pretends to be GCC 4.2.1 for compatibility purposes. We could rework the build info to properly detect this and it should be easy, but it isn't because the build info is hard-coded.
Thank you, I was completely unware of this
Fell free to edit the issue title as needed
We could rework the build info to properly detect this and it should be easy, but it isn't because the build info is hard-coded.
A pull request would be welcome.
We could rework the build info to properly detect this and it should be easy, but it isn't because the build info is hard-coded.
A pull request would be welcome.
I'm already working on it :). It's taking a second because I had to rebuild everything because I switched compilers.
By the way Version:
and Installation Prefix:
have always been empty
Thank you, I was completely unware of this
I think others may also run into this, because they assume that the version is indeed incorrect. It may be best to include additional information in this regard, either the "real" assumed version, or perhaps some additional information about that situation.
I read the explanation about clang in the past, but I also forgot it meanwhile, so ... may be best to improve on the version-reporting situation in this regard, in order to avoid confusion of others in the future.
Guidelines
Version/Commit hash
dce03bae1
Describe the bug.
I don't have GCC 4.2.1 installed
Expected behavior
Compiler report currently used compiler (Clang 12.0.1)
OS
Manjaro Linux stable
Additional context
This issue is not a duplicate