-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
fix messed up libgcrypt package #6758
Comments
comment:1
By looking at the latest source code for libgcrypt this code has been changed. It would appear the intension was to just execute the functions _gcry_md_hash_buffer and _gcry_ac_io_init_va, but not return their value. Here are the relevant functions from the latest release (1.4.4):
The code for function gcry_md_hash_buffer has changed a little more, but it is obvious the intension here two was to execute _gcry_md_hash_buffer and not return the value.
So I removed the 'return' from the code in Sage, and made a patch. Since this is just buggy code, and not-Solaris specific, I've made the patch on all platforms. It is only seen on Solaris with the Sun compiler, as the Sun compiler is more fussy than gcc. See: http://sage.math.washington.edu/home/kirkby/Solaris-fixes/libgcrypt-1.4.3.p2/ Sinve there are some license issues here, I have not updated the package. This code currently in Sage is GPL3 - see #6757 Dave |
comment:2
After uncompressing the spkg http://sage.math.washington.edu/home/kirkby/Solaris-fixes/libgcrypt-1.4.3.p2/libgcrypt-1.4.3.p2.spkg I see that it contains two copies of libgcrypt: one in the src (version 1.4.0) directory and another copy in src/libgcrypt-1.4.3. Any reason why we need two different versions in the spkg? |
comment:3
This needs work as the updated libgcrypt spkg is seriously messed up --- it has two different versions of libgcrypt. |
comment:4
An updated spkg is up at http://sage.math.washington.edu/home/mvngu/release/spkg/standard/libgcrypt-1.4.3.p2.spkg This package incorporates David Kirkby's changes in http://sage.math.washington.edu/home/kirkby/Solaris-fixes/libgcrypt-1.4.3.p2/libgcrypt-1.4.3.p2.spkg but leaves out the fixes for the dodgy bits of code since these have been fixed in libgcrypt 1.4.3. I deleted the patches/ directory. Changes have been committed in David's name. |
Author: David Kirkby, Minh Van Nguyen |
comment:6
Minh Something is wrong here. Your revised version will not build with the Sun compiler. It gives the errors:
as it does not contain my fixes. (I appreciate I screwed up the package first). I believe the best solution is to forget about 1.4.3.p2 entirely, and produce a 1.4.4. Despite the web site saying 1.4.4 is GPL3, the code clearly has a GPL2 'COPYING' file. Dave |
comment:7
#7045 has an update to the 1.4.4 release. No changes to the source were necessary for this to build with Sun Studio 12.1 |
comment:8
Replying to @sagetrac-drkirkby:
Greatly appreciated that you caught this issue!
I believe you didn't mess up the package. It was messed up even before the start of the 4.x series.
Yes, that sounds reasonable. I usually go for the license file in the source tarball myself and also check on the project website. |
comment:9
We should upgrade to libgcrypt 1.4.4 and not worry about libgcrypt 1.4.3 any longer. See ticket #7045 for this. |
I tried to use the Sun compiler to build Sage. Since it's more fussy that gcc, it is showing as an error
The dodgy bits of code are:
and
The Sun compiler will not accept this, and so exits, aborting the build of Sage.
Note there are license issues with libgcrypt too - it is GPL 3. See #6757
Dave
CC: @sagetrac-mvngu @sagetrac-drkirkby
Component: cryptography
Author: David Kirkby, Minh Van Nguyen
Issue created by migration from https://trac.sagemath.org/ticket/6758
The text was updated successfully, but these errors were encountered: