-
-
Notifications
You must be signed in to change notification settings - Fork 532
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
Patch pynac to build properly with Cygwin's system GMP #27713
Comments
Author: Erik Bray |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
comment:3
To add, this started of course since #27212. Not sure why I didn't catch the problem before since I have recollection of testing this on Cygwin, but maybe I just never rebuilt everything (including pynac?) from scratch for some reason. |
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, but not in a stable release. |
comment:4
Fixed upstream. rws confirms there will be a new pynac release in a few weeks, so we can possibly wait on that as well. |
Reviewer: Travis Scrimshaw |
comment:5
I think we can add this patch now (in part to get some extra testing through Sage beta releases) and then remove it when we upgrade Pynac (if that does get into the next stable Sage release). |
Changed branch from u/embray/cygwin/build/ticket-27713 to |
comment:7
the update with the patch in has been released, see #28016 |
Changed commit from |
There are some bits in plain GMP not present for some reason in MPIR such that Cygwin gets some configure-time flags set differently than the defaults on Linux. Cygwin's system package for GMP is configured with these different defaults, leading to a build failure in pynac that I don't get on other platforms.
See the upstream PR for more details: pynac/pynac#342
Upstream: Fixed upstream, but not in a stable release.
Component: porting: Cygwin
Keywords: gmp pynac
Author: Erik Bray
Branch:
5816c4b
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/27713
The text was updated successfully, but these errors were encountered: