#9343: upgrade pari to version 2.4.3
---------------------------+------------------------------------------------
   Reporter:  was          |       Owner:  tbd       
       Type:  enhancement  |      Status:  new       
   Priority:  major        |   Milestone:  sage-4.5.2
  Component:  packages     |    Keywords:            
     Author:               |    Upstream:  N/A       
   Reviewer:               |      Merged:            
Work_issues:               |  
---------------------------+------------------------------------------------

Comment(by drkirkby):

 Hi,
 John or someone else can perhaps convey this to the Pari developers. Would
 it be possible for them to add the -fPIC option on at least all Solaris
 systems. (Both SPARC and x86). If code goes into a shared library, it
 should be compiled position independent. It is unreliable if this is not
 done. There's some relevant information about this here.

 http://gcc.gnu.org/onlinedocs/gcc-4.5.0/gcc/Code-Gen-Options.html#Code-
 Gen-Options
 http://gcc.gnu.org/onlinedocs/gcc-4.5.0/gcc/Link-Options.html#Link-Options

 I believe it would be more reliable to build with -fPIC when the code is
 going into a shared library - irrespective of the platform. What one
 should ensure though is there is not a mixture of PIC and non-PIC code, as
 that can be unreliable too.

 I've not had a chance to look at the other issues, but as far as I can
 see, this update completely breaks a 64-bit build on Solaris or
 !OpenSolaris.

 I've also noticed that Pari reports that ''readline'' is not working on
 Solaris systems. Yet the ''readline'' is definitely working in my Sage
 builds on Solaris. Several parts of Sage link against readline (Pari, gap,
 Singular, ECL, Python ...). None of them believe that ''readline'' is
 broken, but Pari does.

 Dave

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9343#comment:76>
Sage <http://www.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