-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
ENH add extra sysroot deps to mark builds #32
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
@conda-forge-admin rerender |
…da-forge-pinning 2020.07.17.07.14.20
ok @isuruf @conda-forge/core this is the last PR we need to enable cos7! |
Shouldn't the activation packages also need a conflict with |
Why do the activation packages care about the sysroot stuff? |
@#!$@#!$@#! How did I not know about this?! UGH. Will make a PR and send repodata patches today. :/ |
OK. I have the PR for the depo data patches here: conda-forge/conda-forge-repodata-patches-feedstock#68 We'll have to merge this PR after the repo data patches. We need it to make the pr on the activation scripts. |
Ok @isuruf, I think this one is ready to merge! |
I think this PR is breaking |
fixed in #33 |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)This PR adds a few extra sysroot deps to mark the builds for the C/C++/FORTRAN compilers as belonging to the new sysroots. This enables us to use a repodata patch for the vendored sysroot versions of these compilers (conda-forge/conda-forge-repodata-patches-feedstock#66).