-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Fix libgcc.so symlink in sysroot #112
Conversation
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 ( |
Hi! This is the friendly conda-forge automerge bot! Commits were made to this PR after the |
is this still necessary? all red. |
Yes, need to fix this for clang. |
@conda-forge-admin, please rerender (local rerender seemed to hang; no progress after ~20+ min) |
Rerender is broken, removed. |
I remember that rerendering this takes about 40 mins ;) tmux + go do something else! |
I did see a bug in smithy where you have to rerender twice and it alternates between a good one and a bad if I remember correctly. I never tracked it down. That might have been for this feedstock. I am not sure. |
The CHOST-variant only gets created in install-gcc.sh, so pull that forward
@isuruf, I may have fixed this now. 🙃 |
Thanks |
So the cross-compiled s390x targets are failing with
but the native s390x compilers passed, so this should sort itself out upon restart I guess... IMO we should merge and see (not least given the lack of usage of s390x compilers) - WDYT? |
Come on. What's the hurry? You are not even a maintainer of this repository. |
I'm removing this commit and resending the PR. |
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)