Skip to content
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

hoomd-v3.0.0-beta.2 #30

Merged
merged 3 commits into from
Dec 16, 2020
Merged

hoomd-v3.0.0-beta.2 #30

merged 3 commits into from
Dec 16, 2020

Conversation

bdice
Copy link
Contributor

@bdice bdice commented Dec 16, 2020

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@bdice bdice requested a review from joaander as a code owner December 16, 2020 04:05
@bdice
Copy link
Contributor Author

bdice commented Dec 16, 2020

@conda-forge-admin, please rerender

@bdice bdice changed the base branch from master to dev December 16, 2020 04:06
@bdice
Copy link
Contributor Author

bdice commented Dec 16, 2020

@joaander The conda-forge ecosystem recently updated to GCC 9. This breaks CUDA < 11.0 for now. This is a known issue upstream: conda-forge/nvcc-feedstock#51

I'm fine with merging this in its current state with the failing builds, and then making a new build later when the pinnings are fixed to support CUDA 9 with GCC 7, etc. Let me know what you think.

@joaander
Copy link
Contributor

Thanks! I'm also fine merging now.

@joaander joaander merged commit 83f693f into conda-forge:dev Dec 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants