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
Linking of Pynac to GMP #19678
Comments
comment:4
The |
Changed keywords from pynac, linking to pynac, underlinking |
comment:5
FWIW, Pynac's In GiNaC's Makefile we still have #The -no-undefined breaks Pynac on OS X 10.4. See #9135
if CYGWIN
libpynac_la_LDFLAGS = -version-info $(LT_VERSION_INFO) -no-undefined
else
libpynac_la_LDFLAGS = -version-info $(LT_VERSION_INFO)
endif though, so it must fail on Cygwin (unless we link to libgmp there). The libtool versioning (0.0.0) IMHO doesn't make sense either. |
Author: Sebastien Gouezel |
comment:6
Added linking to gmp on Cygwin in the makefile. With this, compilation on cygwin works properly. New commits:
|
Branch: u/gouezel/pynac_lgmp |
Commit: |
comment:7
Hmmm, do we want to link with GMP on Cygwin only? It would have been sufficient to add |
comment:8
I agree it is probably safe to link everywhere to GMP. I was scared by the comment |
comment:9
It's an oversight. I have opened pynac/pynac#102. Thanks for the suggestions. |
comment:10
Replying to @rwst:
Should we wait for an upstream patch or merge as is? |
comment:11
Please don't wait. I'm in minimum maintenance mode (accept patches, do urgent releases). |
comment:12
I'd prefer to not just add it on Cygwin; on the other hand, the component is still (just) "Porting: Cygwin", and the current patch doesn't affect other systems (so doesn't need further testing on MacOS X, say). Thoughts (by others than Ralph)? |
Upstream: Reported upstream. Developers acknowledge bug. |
comment:14
Replying to @nexttime:
Fixed :-) |
Changed branch from u/gouezel/pynac_lgmp to u/gouezel/pynac_lgmp3 |
comment:15
New branch linking to gmp on all platforms, adding the proper test in configure. The patch itself is one line
in New commits:
|
comment:16
The change to Is upstream (@RWS) willing to make a new release for this? Then we don't need the patching. |
comment:17
Replying to @sagetrac-gouezel:
Thanks. If I had the time, I would have done the same in a pull request... @jdemeyer: Simply set upstream to "Fixed upstream, but not in a stable release". ;-) |
comment:18
P.S.: Of course a patch using the same autotools versions is preferable. |
comment:19
I already submitted a PR upstream (two actually, the |
comment:20
The search lib command is already merged. I'll add the |
comment:21
Ah that gets generated, so I can do the release today, as well. |
comment:22
Please test #19744 on Cygwin. |
Changed author from Sebastien Gouezel to none |
comment:23
This has been superseded by #19744, correct? |
Changed upstream from Reported upstream. Developers acknowledge bug. to Completely fixed; Fix reported upstream |
Changed branch from u/gouezel/pynac_lgmp3 to none |
Changed commit from |
Reviewer: Travis Scrimshaw |
This comment has been minimized.
This comment has been minimized.
comment:27
Replying to @rwst:
That was not really useful but it doesn't hurt and is consistent with common practise I guess. |
When building on Cygwin32, I get the following error:
This indicated to me there is a linking issue with Pynac to GMP. Full log is here on #19663.
Fixed by the update to Pynac 0.5.3 on #19744.
Upstream: Completely fixed; Fix reported upstream
CC: @sagetrac-gouezel @jpflori @rwst
Component: packages: standard
Keywords: pynac, underlinking
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/19678
The text was updated successfully, but these errors were encountered: