-
-
Notifications
You must be signed in to change notification settings - Fork 656
build/pkgs/nauty
: Handle SAGE_FAT_BINARY
#36707
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
Conversation
883e05f
to
e349b00
Compare
ditto for build/pkgs/sage_conf/install-requires.txt and other |
I know; this is actually all coming from Volker's force pushes to develop. I'll rebase again once stabilized |
hmm, why does then e.g. #36699 branch look fine? |
@vbraun 10.2.rc2 is still pointing to a commit not on the develop branch
|
Rebased onto 10.2.rc1 until there's clarity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Thanks! |
Documentation preview for this PR (built with commit df67f19; changes) is ready! 🎉 |
For the record, the correct rc2 is:
|
Thanks, Volker, it's all good now |
Handling
SAGE_FAT_BINARY
as suggested by @tornaria in #36696 (comment)Disabling popcnt is consistent with the handling of SAGE_FAT_BINARY in our
primesieve
install script.Bumping the patch level so it gets recompiled when applied as a CI hotfix.
📝 Checklist
⌛ Dependencies