#6758: [with spkg, needs review] fix messed up libgcrypt package
--------------------------+-------------------------------------------------
 Reporter:  drkirkby      |       Owner:  somebody                     
     Type:  defect        |      Status:  new                          
 Priority:  major         |   Milestone:  sage-4.1.2                   
Component:  cryptography  |    Keywords:                               
 Reviewer:                |      Author:  David Kirkby, Minh Van Nguyen
   Merged:                |  
--------------------------+-------------------------------------------------

Comment(by mvngu):

 Replying to [comment:6 drkirkby]:
 > Something is wrong here. Your revised version will not build with the
 Sun compiler. It gives the errors:
 >
 {{{
 "visibility.c", line 702: void function cannot return value
 "visibility.c", line 851: void function cannot return value
 }}}
 >
 > as it does not contain my fixes.

 Greatly appreciated that you caught this issue!
 [[BR]][[BR]]


 > (I appreciate I screwed up the package first).

 I believe you didn't mess up the package. It was messed up even before the
 start of the 4.x series.
 [[BR]][[BR]]


 > 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.

 Yes, that sounds reasonable. I usually go for the license file in the
 source tarball myself and also check on the project website.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6758#comment:8>
Sage <http://sagemath.org/>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to