-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
MAINT: fix licence path win #24793
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
MAINT: fix licence path win #24793
Conversation
@@ -880,7 +880,7 @@ Public License instead of this License. But first, please read | |||
<http://www.gnu.org/philosophy/why-not-lgpl.html>. | |||
|
|||
Name: libquadmath | |||
Files: numpy\.libs\libopenb*.dll | |||
Files: numpy.libs\libopenb*.dll |
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.
Are we statically linking a .dll
? Or should it be .a
for Windows? And we're sure it should be an OpenBLAS library name for quadmath instead of a quadmath-specific lib? Is it an indirect link to quadmath via OpenBLAS then?
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.
I guess that's what's in the wheel, although maybe the static linking line below this line is less clear to me via DLL.
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.
I think this is correct. The one file that is vendored is libopenblas64*.dll
, and that DLL also contains statically linked libgcc
and libquadmath
.
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.
@@ -880,7 +880,7 @@ Public License instead of this License. But first, please read | |||
<http://www.gnu.org/philosophy/why-not-lgpl.html>. | |||
|
|||
Name: libquadmath | |||
Files: numpy\.libs\libopenb*.dll | |||
Files: numpy.libs\libopenb*.dll |
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.
I think this is correct. The one file that is vendored is libopenblas64*.dll
, and that DLL also contains statically linked libgcc
and libquadmath
.
Yes, that is permitted. I looked at those details when reviewing gh-24753; there's no substantial difference in dynamic vs static linking. |
Thanks Andrew. |
just a comment: (windows) a statically linked and stripped libquadmath.dll doesn't include any libquadmath code. This can be easily proven with linker maps. |
@carlkl I don't understand the comment. The source code is still compiled into the resulting OpenBLAS dll. |
Or are you saying that the windows DLL does not actually use any of the libquad code, since it does not call any 128-bit float routines, so the linker will not pull in the code? |
Ahh, I found this discussion of libquadmath on an openblas-libs issue MacPython/openblas-libs#82 (comment). It would be nice to upstream that patch. |
I tested this last year or so with te help of linker maps. The symbol |
@charris, I think there's a mistake in the licence path on windows.
Also, is it permitted to statically link a LGPL libquadmath into the libopenblas that we bundle?