Differences between revisions 5 and 7 (spanning 2 versions)
Revision 5 as of 2017-07-31 09:41:41
Size: 1092
Editor: vdelecroix
Comment:
Revision 7 as of 2017-07-31 09:45:38
Size: 1134
Editor: vdelecroix
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 2. Do
{{{
 2. Do {{{
Line 20: Line 19:
$ pari_apply_patches # optional patch applications
Line 24: Line 22:
}}}

 3. Recompile cysignals
{{{
Line 25: Line 27:
$ sage -f cypari # recompile cypari2
$ sage -br # recompiles what need to be
}}}

 4. Compile the last version of cypari
{{{
$ sage -pip install git+https://github.com/defeo/cypari2
}}}

 5. Recompile what needs to be
{{{
$ sage -br

Step by step tutorial on how to use PARI/GP development version in Sage

This tutorial explains how to use a PARI/GP development version inside Sage.

Prerequisites

  1. We assume that your PARI/GP source code is at $PARI_ROOT
  2. You need to use a version of Sage compiled from source located at $SAGE_ROOT

Procedure

  1. Download the script pari_sage.sh

  2. Do

    $ cd $PARI_ROOT
    $ sage -sh                # starts Sage environment
    $ source pari_build.sh    # reading pari_build.sh
    $ pari_set_environment    # setting properly environment variables for compilation
    $ pari_build              # building pari
    $ pari_install            # installing pari
  3. Recompile cysignals

$ sage -f cysignals       # recompile cysignals (to be linked correctly against pari)
  1. Compile the last version of cypari

$ sage -pip install git+https://github.com/defeo/cypari2
  1. Recompile what needs to be

$ sage -br

Procedure to restore the standard PARI package in Sage

$ sage -f pari
$ sage -f cysignals
$ sage -f cypari
$ sage -br

PariDevInSage (last edited 2017-08-03 08:15:11 by vdelecroix)