Open
Conversation
m-fol
pushed a commit
to m-fol/common.bits
that referenced
this pull request
Mar 18, 2026
Readme: fix mentions of gcc33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Building the metapackage LCG, containing the Python package as a requirement, led to an SSL validation error when uploading symlinks to s3 on some of our platforms (all of them on x86_64 and el9 with these compilers: clang16-dbg, clang16-opt, clang19-opt, gcc13-dbg, gcc13-opt, gcc14fp-opt), more detail below under "Typical build failure".
Other build platforms uploaded the symlink successfully (all of them on x86_64 with OS and compilers: el9-clang19-dgb, el9-gcc14-dbg, el9-gcc14-opt, el9-gcc15-dbg, el9-gcc15-opt, el10-gcc15-opt), more detail below under "Typical success".
In the python recipe of common.bits,
SSL_CERT_FILEis exported here. This happened just before the last upload of symlinks in each of our build logs:Certifi was downgraded to version 2022.12.17 when executing this line of the python recipe.
After applying the commit in this PR, all our builds ran without SSL validation errors. The SSL_CERT_FILE variable was set to a local installation of certifi, because this satisfied the version requirement. Should certifi just be installed under INSTALLROOT instead of relying on the local path of python?
#Typical build failure:
#Typical build success: