libcxx 17.0.6 #131
Merged
libcxx 17.0.6 #131
Conversation
This file contains 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
This reverts commit 7a836a5.
…nda-forge-pinning 2023.07.19.16.49.37
libcxx 17.0.0.rc1
automerged PR by conda-forge/automerge-action
…da-forge#129) automerged PR by conda-forge/automerge-action
h-vetinari
requested review from
SylvainCorlay,
beckermr,
inducer,
isuruf,
jakirkham and
timsnyder
as code owners
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Closed
9 tasks
h-vetinari
force-pushed
the
17
branch
2 times, most recently
from
247f56c
to
c3092fd
Compare
|
The error here does not make sense to me: as the package in question is definitely in the main channel. |
|
This is running into conda-forge/python-symengine-feedstock#50 |
This was referenced Mar 6, 2024
10 tasks
…nda-forge-pinning 2024.04.20.22.12.53
14 tasks
|
With the imminent merge of conda-forge/conda-forge-pinning-feedstock#5829, this is not a draft anymore - please feel free to review @conda-forge/libcxx :) I feel this PR is in a good shape though, so planning to merge after Monday EOD AoE unless there are comments. |
14 tasks
beenje
added a commit
to beenje/fisx-feedstock
that referenced
this pull request
May 14, 2024
osx-64 build failed when merging into main because libcxx was updated from 16.x.x to 17.x.x between the time of the MR and the merge. libcxx 17.x.x requires MacOS >=10.13 (see conda-forge/libcxx-feedstock#131) My understanding is that a re-render should fix it due to conda-forge/conda-forge-pinning-feedstock#5829
4 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Biggest change is that libcxx now hard-requires MacOS >=10.13, see #110 (particularly for the dylib, but a simple
# includealso fails if the SDK is too old). Since libcxx has such a central role in our MacOS stack (i.e. we always pull in newest libcxx), this will effectively mandate a move to 10.13 (as all packages having libcxx in host will generate a run-export on >=17.0.1, which effectively moves all compiled osx-packages to >=10.13), see conda-forge/conda-forge.github.io#1844.libcxx on linux now also requires glibc >=2.24, which we cannot yet satisfy because our sysroots are too old (and 2_28 hasn't materialized yet); this doesn't seem too big of an issue though, as libcxx-on-linux is not our default C++ stdlib and is used very little.
I've kept the compatibility with old clang by again rebasing the revert of llvm/llvm-project@21f73d5; we're already far beyond the upstream support policy of "last 2 clang versions" by going back all the way to clang 11. This remains on a best-effort basis.
Closes #110