#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: Robert Bradshaw, John Cremona, Jeroen Demeyer, William Stein |
Upstream: N/A
Reviewer: |
Merged:
Work_issues: |
----------------------------------------------------------------------------+
Comment(by drkirkby):
Replying to [comment:102 cremona]:
> For more on the bison issue see the pari-dev thread here:
http://pari.math.u-bordeaux.fr/archives/pari-dev-1007/msg00011.html
>
> It seems that we should not use an svn source grad in our distribution
but a "proper PARI tarball". An explanation of how to create such a thing
is I hope forthcoming on that thread.
>
> Secondly, the thread http://pari.math.u-bordeaux.fr/archives/pari-
dev-1007/msg00015.html makes some releavnt comments (and asks a question)
on Dave's other points.
Bison, like autoconf and automake should not be necessary for end-users.
Often developer additions don't have a 'configure' script - they rely on
other developers making that from configure.ac. It is the same with bison
- some files only need to be geneated and passed to the end users. As long
as the timestamp on the files generated by bison is more recent than the
files they were generated from, bison should not be necessary.
With regard to my own Solaris issue with -fPCI, shared libraries and Pari,
I'm not sure how to observe what is happening, or where I can follow the
Pari bug numbers referenced. Essentially one of the Pari developers
disagreed with me, and said it is not necessary to use -fPIC when
compiling 32-bit shared libraries on Solaris - only 64-bit ones. I
responded that this is not so, and provided a link to something written by
Casper Dik (a very knowledge Sun employee), that -fPIC is necessary. I
gather that was passed on, but I don't see any record of it.
There's also the point I made that Pari is looking for a different version
of GMP to what is in Sage when building a 64-bit version of Pari. The Pari
developer believes it is finding another version before that one in Sage.
'''IF''' that is so, that needs fixing in Sage. Somehow we need to ensure
Pari first looks for the libraries in $SAGE_LOCAL/lib, and not in
/usr/lib, /usr/local, or wherever else Pari may chose to look. The whole
point of shipping a bunch of standard libraries with Sage is we know what
ones are are used by Sage.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9343#comment:103>
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.
