Repository navigation
[3.11] libpython: drop the unused C++ compiler - #954
Merged
conda-forge-admin merged 2 commits intoOct 13, 2026
Merged
conda-forge-admin merged 2 commits into
conda-forge-admin merged 2 commits into
Conversation
Backport of conda-forge#950. The shared library links no C++ runtime (libpython3.11.so.1.0 needs only libc, libm, libpthread, libdl and libutil), but the compiler's run-exports made every libpython build require libstdcxx >=15 on Linux and libcxx on macOS. Because python pins libpython exactly, environments capped below libstdcxx 15 (e.g. Julia 1.10 and 1.12 via CondaPkg) cannot install current python 3.11 builds. Co-authored-by: Miles Cranmer <miles.cranmer@gmail.com>
libpython has no host requirements on this branch, so on macOS the host prefix was only populated through the C++ compiler's libcxx run-export. Without it, lib/ does not exist and cp fails (as seen on conda-forge#950). Co-authored-by: Miles Cranmer <miles.cranmer@gmail.com>
MilesCranmerBot
requested review from
chrisburr,
isuruf,
jakirkham,
katietz,
mbargull,
msarahan,
ocefpaf,
pelson,
scopatz and
xhochy
as code owners
October 13, 2026 15:21
Contributor
|
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/38421435489. Examine the logs at this URL for more detail. |
Contributor
|
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
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
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.
Why
Backport of #950 (3.14) and #949 (main), for #951.
libpythonon this branch depends onlibstdcxx >=15through the C++ compiler's run-export, but the library links no C++ runtime:objdump -ponlibpython3.11.so.1.0from the current linux-64 build lists only libc, libm, libpthread, libdl, libutil (and ld-linux). Becausepythonpinslibpythonexactly, environments that cap libstdc++ below 15 (Julia 1.10 and 1.12 via CondaPkg) cannot install current python 3.11 builds.Scope
The same two commits as #950: drop
{{ compiler('cxx') }}from thelibpythonoutput's build requirements, create$PREFIX/libbefore copying the library (on macOS that directory was only created by the compiler'slibcxxrun-export), and bump the build number.Verification
#950 is the same change and passed CI on all platforms; the fixed 3.14.8 build (
hd51c5da_102_cp314) is published withoutlibstdcxx.