-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
jfalcou-eve/v2021.10.0 #7744
jfalcou-eve/v2021.10.0 #7744
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ok, so this is blocked by #7529 (waiting for conan-io/conan-docker-tools#320 to be deployed) |
@ericLemanissier Do you mean we need to update CLang 10 too? That PR was related to Clang 11 only. This PR here is failing with Clang 10. |
err, no, I just misread the version number. some more investigation is needed then! |
ok, so clang 10 support for concepts seems to be limited: https://groups.google.com/g/compiler-explorer-discussion/c/gwkLj-o-R_8?pli=1 |
it does not support the library part of concepts
This comment has been minimized.
This comment has been minimized.
Thank you for checking! ❤️ |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave some infos on the minimal setup required.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@jfalcou do you have an idea about this error https://c3i.jfrog.io/c3i/misc/logs/pr/7744/8-configs/windows-visual_studio/jfalcou-eve/cci.20210823/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9-test.txt ? (it's cci.20210823, not v2021.10.0) |
It makes literally no sense. I suspect MSVC is getting confused. My surprise is that the recipe even worked with MSVC at all as we don't really support it yet. |
Well, windows and mac builds were never tested on conan center index: https://c3i.jfrog.io/c3i/misc/summary.html?json=https://c3i.jfrog.io/c3i/misc/logs/pr/6902/14-production/jfalcou-eve/cci.20210823//summary.json |
Seems the safest. We will have msvc-clang support soonish but it'll be for 2021.11.x at least. Not sure CCI test this setup. |
This comment has been minimized.
This comment has been minimized.
😆 all builds are INVALID_CONFIGURATION, I messed up something ! EDIT: EVE supports only gcc 11 and clang 12,which are not yet on CCI (https://github.com/conan-io/conan-center-index/blob/master/docs/supported_platforms_and_configurations.md), this explains that. It's quite risky to put an untested package on CCI, what do you (approvers) think ? |
So question: how does it ended up there first then ? |
gcc 10 passed for falcou-eve/cci.20210823 (https://c3i.jfrog.io/c3i/misc/summary.html?json=https://c3i.jfrog.io/c3i/misc/logs/pr/6902/14-production/jfalcou-eve/cci.20210823//summary.json) but you said gcc 10 is not compatible with jfalcou-eve/v2021.10.0 |
It probably works. clang before 12 is a clear no-no as all the concepts and some std like bit_cast are not there properly (same for libc++ based clang that still lacks some basic things). So, letting the GCC requirement down to 10 is probably OK. So, I feel bad now to have let you spend all this time on this. Maybe we should lt the recipes "as it is" for now and try again when the CCI uses newer compilers ? I'm unsure of what to do. |
no problem, don't worry. the bot successfully tested both versions of eve on GCC 10, so I guess we're good to go ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking it, just to consider if we should change the version name.
@@ -2,3 +2,6 @@ sources: | |||
"cci.20210823": | |||
url: "https://github.com/jfalcou/eve/archive/30e7a7f6bcc5cf524a6c2cc624234148eee847be.tar.gz" | |||
sha256: "c267135f7215197ef6859b2aa1c5b6a7fc45ca8333933beda56c96b0d0400ef1" | |||
"v2021.10.0": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we get rid of the v
, it will follow semver and version ranges would work here. Do we know if it is semver?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Asked here: jfalcou/eve#1027 (comment)
Confirmed, they will follow pattern |
I don't mind much, but I think it's simpler to maintain and consume if we use upsteam version names as-is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably the version ranges algorithm is something to revisit, it's not the first time something related to it appears in some comment (related #5651). To be honest, I thought we usually remove the leading v
from this kind of version pattern. But, me too, I prefer to use upstream version names as-is.
Don't forget that adding v has strong consequences in downstream recipes (don't forget all the mess with spirv-tools). |
* jfalcou-eve/v2021.10.0 fixes conan-io#7743 * Update conandata.yml * Update conandata.yml * disable clang 10 it does not support the library part of concepts * Update conanfile.py * Update conanfile.py * Update conanfile.py * Update conanfile.py * Update conanfile.py
fixes #7743
Specify library name and version: jfalcou-eve/v2021.10.0
conan-center hook activated.