-
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
[question] No clang 10 configurations? #8913
Comments
Good question and it's a long history. You need to read conan-io/conan-docker-tools#205 to understand all. To summarize: Maintainability is the word. After almost 5 years supporting, patching, fixing, doing all kind of amend, we decided to use a single base Docker image and install the compiler there. Ubuntu releases a new version every 6 months, between this time, we have new compilers available, so we need to install via non-stable ppa, and find out some way to update as soon as available on stable branch. With the time, it's harder and harder to maintain. |
To complement, clang-10 is there and there are packages available built by Clang 10. Also, there are 2 Docker images with Clang 10: |
Faced same issues with openssl-1.1.1m no package for clang-10 which is default for 20.04. 20.04 is LTS version which is end of life in 2030, 22.04 LTS has not been even released yet. I do understand that it's hart do support and maintain everything, but maybe need more socializing on long term support. this is usually coming uunnoticible 😢 ... |
@pgeler it was the same problem for me, but with bzip2. I instructed my team to download |
@barower yes thank you!!! Build image we are using shared across the projects with same clang/gcc version (not all projects using conan). I'm trying to install and use it in parallel/ another way we are looking is to use our own binary packages... but is not this a step back 🤔 |
we have to move forward, and we cannot build for everything - we have limited resources, and supported configuration is always about a balance in build times, maintenance cost, and reasonable coverage. |
|
@uilianries Is it possible that some packages that used to be pre-built with clang 10 have been removed from Conan Center ? I noticed that one of my CI jobs that used to pass last month, is now failing with this error, on the same commit ID : Installing (downloading, building) binaries...
ERROR: Missing binary: xapian-core/1.4.18:a0e99a2fb2badc7066c6de0f5b7d202a5377dbfc
ERROR: Missing binary: zlib/1.2.11:2b1e5ff9df96aaf5924c273e1368c632fcb32dd2
zlib/1.2.11: WARN: Can't find a 'zlib/1.2.11' package for the specified settings, options and dependencies:
- Settings: arch=x86_64, build_type=Release, compiler=clang, compiler.version=10, os=Linux
- Options: fPIC=True, shared=False
- Dependencies:
- Requirements:
- Package ID: 2b1e5ff9df96aaf5924c273e1368c632fcb32dd2
ERROR: Missing prebuilt package for 'xapian-core/1.4.18', 'zlib/1.2.11'
Use 'conan search zlib/1.2.11 --table=table.html -r=remote' and open the table.html file to see available packages
Or try to build locally from sources with '--build=xapian-core --build=zlib'
More Info at 'https://docs.conan.io/en/latest/faq/troubleshooting.html#error-missing-prebuilt-package' I ran this command and saw that there is no more pre-built package for clang 10: conan search zlib/1.2.11@ --table=table.html -r=conancenter |
Forget what I've just said. The root cause of my issue is that I've just enabled the conan revisions. |
That said, I don't fully understand how packages are indexed on Conan Center. Are the outdated packages not listed ? Also, outdated packages seem to be listed in the results of a In regards to the revisions, is there a way to install outdated packages when the revision feature is enabled? In my use case, I had to enable the revision feature in order to use a private conan repository on Artifactory. But since then, I cannot install some packages from Conan Center that I used to install (because they are outdated). Here are the logs of the same operation, with and without the revision feature enabled. With revisions -> failureexport CONAN_REVISIONS_ENABLED=1
conan install zlib/1.2.11@ -s compiler=clang -s compiler.version=10
Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=clang
compiler.libcxx=libstdc++11
compiler.version=10
os=Linux
os_build=Linux
[options]
[build_requires]
[env]
zlib/1.2.11: Not found in local cache, looking in remotes...
zlib/1.2.11: Trying with 'conancenter'...
Downloading conanmanifest.txt completed [0.33k]
Downloading conanfile.py completed [5.36k]
Downloading conan_export.tgz completed [0.33k]
Decompressing conan_export.tgz completed [0.00k]
zlib/1.2.11: Downloaded recipe revision 4b38406da00104befece594b529fd155
Installing package: zlib/1.2.11
Requirements
zlib/1.2.11 from 'conancenter' - Downloaded
Packages
zlib/1.2.11:2b1e5ff9df96aaf5924c273e1368c632fcb32dd2 - Missing
Installing (downloading, building) binaries...
ERROR: Missing binary: zlib/1.2.11:2b1e5ff9df96aaf5924c273e1368c632fcb32dd2
zlib/1.2.11: WARN: Can't find a 'zlib/1.2.11' package for the specified settings, options and dependencies:
- Settings: arch=x86_64, build_type=Release, compiler=clang, compiler.version=10, os=Linux
- Options: fPIC=True, shared=False
- Dependencies:
- Requirements:
- Package ID: 2b1e5ff9df96aaf5924c273e1368c632fcb32dd2
ERROR: Missing prebuilt package for 'zlib/1.2.11'
Use 'conan search zlib/1.2.11 --table=table.html -r=remote' and open the table.html file to see available packages
Or try to build locally from sources with '--build=zlib'
More Info at 'https://docs.conan.io/en/latest/faq/troubleshooting.html#error-missing-prebuilt-package' Without revisions -> successexport CONAN_REVISIONS_ENABLED=0
conan install zlib/1.2.11@ -s compiler=clang -s compiler.version=10
Configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=clang
compiler.libcxx=libstdc++11
compiler.version=10
os=Linux
os_build=Linux
[options]
[build_requires]
[env]
zlib/1.2.11: Not found in local cache, looking in remotes...
zlib/1.2.11: Trying with 'conancenter'...
Downloading conanmanifest.txt completed [0.33k]
Downloading conanfile.py completed [5.36k]
Downloading conan_export.tgz completed [0.33k]
Decompressing conan_export.tgz completed [0.00k]
zlib/1.2.11: Downloaded recipe revision 0
Installing package: zlib/1.2.11
Requirements
zlib/1.2.11 from 'conancenter' - Downloaded
Packages
zlib/1.2.11:2b1e5ff9df96aaf5924c273e1368c632fcb32dd2 - Download
Installing (downloading, building) binaries...
zlib/1.2.11: Retrieving package 2b1e5ff9df96aaf5924c273e1368c632fcb32dd2 from remote 'conancenter'
Downloading conanmanifest.txt completed [0.25k]
Downloading conaninfo.txt completed [0.39k]
Downloading conan_package.tgz completed [86.68k]
Decompressing conan_package.tgz completed [0.00k]
zlib/1.2.11: Package installed 2b1e5ff9df96aaf5924c273e1368c632fcb32dd2
zlib/1.2.11: Downloaded package revision 0
Aggregating env generators We clearly see that conan first says that the package is missing and then installs it, for the same package ID ( Is there a way to force conan to use revision 0 of the recipe ? Or list the revisions ? I tried |
we never remove existing packages, so they should be there, until some data corruption has happened (which to my knowledge didn't).
(attaching the full log, just in case) they should be available for the consumption with command like:
you may use |
Thank you @SSE4 ! 🙏 The However, how do your define the latest revision a configuration exists for ? For instance, in your example, how did you know |
yes, I basically run the script to scan all revisions:
|
All right, thank you! |
I think this issue can be closed? |
I would say yes. Unless conan developers plan to integrate a solution to transparently do this with the resolver. |
Clang 10 has been integrated to CCI |
It is documented here https://github.com/conan-io/conan-center-index/blob/master/docs/supported_platforms_and_configurations.md |
10 is default clang version on Ubuntu 20.04, why has support for it been removed? It complicates building with Conan in environments with no possibility to download sources from Internet
The text was updated successfully, but these errors were encountered: