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
Python 2 libpython symlink not created correctly on Cygwin #24189
Comments
comment:1
I have a patch for this already--I'm just testing to make sure it works. |
Changed keywords from none to windows cygwin python2 |
Commit: |
New commits:
|
Author: Erik Bray |
Branch: u/embray/cygwin/ticket-24189 |
failure to build fpyll. |
comment:4
Attachment: fpylll-0.3.0dev.log Is your fpylll build fixed by #24191? |
Reviewer: Emmanuel Charpentier |
comment:5
Replying to @tscrim:
Yes and no : fpylll compiles, but Sage does not build. I get an error at Sagelib's compilation :
I think I'm bitten by #24192, which I'll try next. But, as far as I understand, that implies restarting with
|
comment:6
I don't think you need to do a |
Changed branch from u/embray/cygwin/ticket-24189 to |
#23781 introduced a regression that the symlink from
lib/python2.7/config/libpython2.7.dll.a
tolib/libpython2.7.dll.a
is not created properly.On Python 3 this "config" directory name is formatted "config-<PYTHON_LDVERSION>" whereas on Python 2 it should be just "config".
This prevents extension modules from linking to the correct libpython2.7 on Cygwin.
CC: @EmmanuelCharpentier
Component: porting: Cygwin
Keywords: windows cygwin python2
Author: Erik Bray
Branch/Commit:
9873e64
Reviewer: Emmanuel Charpentier
Issue created by migration from https://trac.sagemath.org/ticket/24189
The text was updated successfully, but these errors were encountered: