PARI: STACK_CHECK est incompatible avec les threads

Running xcas:
After unzipping xcas in a directory, click on
xcas.exe (english)
xcasfr.bat (french)
xcases.bat (spanish)
If you want to have print support you should install AsTeX, see
http://www.univ-orleans.fr/EXT/ASTEX
Once AsTeX installed, preview and print should work on windows NT.
On windows 9x, you might need to edit the file
latex.bat with wordpad or notepad and remove the ^ before &latex2e

* Making a giac dll (Jean-Pierre Branchard)
make -f Makefile.win giac.dll
cp giac.dll /bin
ln -sf /bin/giac.dll /usr/local/lib
See also http://cygwin.com/cygwin-ug-net/dll.html#DLL-BUILD
Then you can compile giac applications using e.g. for Ginette
g++ ginette.cc -s -o ginette `gtk-config --cflags --libs` -lgiac

Binary distribution
===================
This binary distribution has been tested with Familiar 0.8.3, with the gpe
tarball.
Copy xcas_ipaq.tgz to the /tmp directory of your ipaq, then as root type
# cd /
# tar xvfz /tmp/xcas_ipaq.tgz
Edit e.g. with vi a file /usr/bin/xcas and change to the correct
export LANGUAGE=es_ES:es or fr_FR:fr
Unfortunately localization does not seem to work right now:-(

Note: it is important that you run xcas from a RAM directory otherwise you
will have speed penalties and/or hardware problems since files
would be saved in flash ROM. See the /usr/bin/xcas file and adapt.

You can of course modify your window manager to include xcas in the menu

Thanks to Pierre Coupard at LINEO, the binary distribution should also work
on the Sharp Zaurus unchanged provided you have installed X11 on it. See
the instructions from http://www.zauruszone.com/, section Downloads,
then Zaurus X11 Applications

Giac/Xcas homepage:
http://www-fourier.ujf-grenoble.fr/~parisse/giac.html (English)
http://www-fourier.ujf-grenoble.fr/~parisse/giac_fr.html (French)
http://www-fourier.ujf-grenoble.fr/~parisse/giac_es.html (Spanish)

***************************************************************************
Build:
======
* install the cross compiler from www.handhelds.org, get ipkg
for developpement and ar x them then tar xvfz data.tar.gz to the
/skiff directory, make a link from /skiff/local to
/usr/local/arm/3.4.1/ and usr to local
* Untar giac.tgz and go to giac directory, edit config.h to suit
your need (include GSL or not, include PARI or not) or
cp config.h.ipaq config.h
then go in the src directory and type
make -f Makefile.ipaq

Running javscript programs with giac CAS support under linux
1/ Install giac-1.1: add the line
deb http://www-fourier.ujf-grenoble.fr/~parisse/debian/ testing main
in the file /etc/apt/sources.list. Then run
  sudo apt-get update
Now you can install or upgrade by running
  sudo apt-get install giac

2/ Install webkit
  sudo apt-get install libwebkit-dev

3/ Copy libgiacjs.so in /usr/lib and run sudo ldconfig or run
  export LD_LIBRARY_PATH=.

4/ Run
  ./javascript -l giacjs giacjs.js
(replace giacjs.js with your javascript)
If it does not work, run ldd javascript and make a link in /usr/lib like this
cd /usr/lib ; sudo ln -s libwebkitgtk-1.0.so.0 libwebkit-1.0.so.2

For details how to make the interface, have a look at giacjs.i

The files in this directory compile JNI version of giac for Mac OS X
10.6 or 10.8. (Maybe other versions will also work, untested.) 10.6 is
preferred since if compiled under 10.8 the JNI cannot be used on earlier
Mac OS X versions.

Prerequisites:

  * Mac OS X 10.6 or 10.8 (either real or running in VirtualBox)
  * Xcode 3.2 (for 10.6) or a recent one (for 10.8)
  * Admin privileges for the current user

Usage:

  * Enter "make" to compile the JNI version. You will be asked to give
    the admin password to install some dependencies into /usr/local.
  * The file libjavagiac.jnilib will be put in giac-1.1.0/src/.
  * You can do some testing by running "make test". You should see
    that the .jnilib file is a 18 MB bundle having no .dylib
    dependencies (i.e. libgmp, libgsl, libmpfr and libgettext are
    statically linked into it).

Authors:

  * Bernard Parisse
  * Zoltan Kovacs

To compile giac for nacl,
0/ run
export NACL_SDK_ROOT=~/nacl_sdk/pepper_31 # (adapt)
export NACL_ARCH=pnacl # for nacl_ports
1/ install naclports
2/ copy for example ports/gsl to ports/gmp and ports/mpfr and adapt, compile gsl gmp and mpfr
by running make gmp; make gsl; make mpfr
You must run sha1sum package_name to get the sha1 files.
3/ copy again ports/gsl to ports/giac and adapt.
To compile giac successfully, once configure is done,
you must change config.h in out/repository/giac-1.1.0 and src:
remove HAVE_LIBPTHREAD and HAVE_PTHREAD_H, add
#define PNACL
At the end, ignore the errors while building icas.pexe and aide.pexe by
  touch icas.pexe aide.pexe
remove the line mv $(DESTDIR)/... at the end of src/Makefile, run
  make install
then you can remove the share/giac directory in pepper.

4/ Test in NACL_SDK_ROOT
unset NACL_ARCH
export TOOLCHAIN=pnacl
# check in index.html data-tools: pnacl must be first
# export CONFIG=Release # or Debug
export CONFIG=Debug # or Release

add giac mpfr gmp gsl gslcblas in Makefile LIBS of getting started
Unfortunately I get a LLVM link error
LLVM ERROR: atomic load/store must be at least naturally aligned, got 0, bytes expected at least 4 bytes, in:   %10 = load volatile i32* %call

giac/KhiCAS sur TI nspire CX
============================
Pour cross-compiler KhiCAS, il faut installer le SDK de ndless
https://hackspire.org/index.php/C_and_assembly_development_introduction

Ensuite installer GMP, MPFR, MPFI les versions importent peu mais autant prendre les plus recentes. Il suffit de prendre les archives standard (https://gmplib.org/, https://www.mpfr.org/, https://gforge.inria.fr/frs/?group_id=157), a cross-compiler, ce qui peut se faire avec les instructions suivantes
    #! /bin/bash
    export CC=nspire-gcc
    export CXX=nspire-g++
    export LD=nspire-ld
    export AR=arm-none-eabi-ar
    export AS=nspire-as
puis pour compiler GMP
    ./configure --host=arm-none-eabi
installer a la main gmp*h dans chemin_vers_ndless-sdk/toolchain/install/include et libgmp.a vers chemin_vers_ndless-sdk/toolchain/install/lib
puis pour compiler MPFR
    ./configure --with-gmp=chemin_vers_ndless-sdk/toolchain/install --host=arm-none-eabi
meme procedure d'install et compilation de MPFI de maniere analogue.

Puis recuperer le source a jour de giac,
https://www-fourier.univ-grenoble-alpes.fr/~parisse/giac/giac-1.6.0.tar.bz2
cp config.h.nspire config.h
editer Makefile.nspire pour s'adapter a votre installation locale et faire
make -f Makefile.nspire

Si vous faites des modifications et que vous voulez executer en pas a pas au debuggueur:
* a faire une fois: installez firebird-emu
https://github.com/nspire-emus/firebird.
Installer sur l'emulateur les fichiers de boot et de flash de votre
nspire CX. Puis envoyez avec firebird-send ndless 4.5.0 pour la nspire
(https://tiplanet.org/forum/viewtopic.php?t=20446), activez ndless.
Faites deux sauvegardes (dont une de snapshot pour redemarrer firebird-emu).
* apres chaque compilation: envoyez l'executable giac.tns sur l'emulateur.
Tapez alors dans un shell la commande
    arm-none-eabi-gdb -ex "target remote localhost:3333" giac.elf
ou dans emacs: Esc x gdb (enter) puis
    arm-none-eabi-gdb -i=mi -ex "target remote localhost:3333" giac.elf
Cela doit interrompre l'emulateur (affichage grise). Mettez un point
d'arret dans votre code source (dans emacs Ctrl-X Ctrl-A Ctrl-B sur
la ligne souhaitee, dans gdb avec la commande b pour break, b nom de fonction
ou b nom de ficher source:numero de ligne) et tapez c (cont).
Ensuite lorsque le point d'arret est atteint vous pouvez executer en pas
a pas comme avec une session gdb normale
(p print, n next, s step into, u until, c continue, etc.).
Dans le repertoire src de giac, il y a un fichier .gdbinit qui contient
une macro fort utile pour afficher des variables de type gen,
c'est v (comme voir) qui s'utilise comme p mais au lieu d'afficher
la variable comme une structure C, il l'affiche comme dans Xcas.

-------------------------------------------------------------------------
ENGLISH
-------------------------------------------------------------------------
Running xcas:
After unzipping xcas in a directory, click on
xcas.exe (english)
xcasfr.bat (french)
xcases.bat (spanish)
If you want to have print support you must have a LaTeX distribution
with pstricks that supports Unix-like LaTeX commands (latex, windvi, dvips)
A good place to get one for Windows is http://www.fptex.org/
If you are using miktex, replace windvi.exe by yap.exe in the xdvi.bat
file.
During the setup, keep the recommended default install *but* you
must also install pstricks, check for custom install and check the
pstricks button in the texlive->tex-pictures->pstricks, as well as
the ghostscript-free and gsview42-nonfree in the win32-support section
After install, check that . is in your current PATH or move latex.bat,
xdvi.bat and dvips.bat in a directory from your PATH e.g. in the
C:\WINDOWS directory
If you want to put xcas in a directory of your PATH and run it from
another directory, you should set the environment variables
XCAS_LOCALE to the directory where the locales are
XCAS_HELP to the file aide_cas
This can be done in the xcasfr.bat or xcases.bat file, e.g. add
set XCAS_LOCALE=/cygdrive/c/xcas/locale/
set XCAS_HELP=/cygdrive/c/xcas/aide_cas
-------------------------------------------------------------------------
FRANCAIS
-------------------------------------------------------------------------
Pour installer xcas
Utilisez un decompresseur (par exemple WinZip) pour desarchiver xcas.zip
dans un repertoire puis cliquez sur
xcasfr.bat
Pour pouvoir imprimer, il vous faut une distribution LaTeX avec pstricks
qui accepte les commandes LaTeX en style Unix (latex, windvi et dvips)
Par exemple, vous pouvez en recuperer sur http://www.fptex.org/
Pendant l'installation, conservez l'install recommendee par defaut *mais*
selectionnez pstricks dans la section texlive->tex-pictures->pstricks et
dans la section win32-support->ghostscript-free et gsview42-nonfree
(vous pouvez aussi rajouter emacs, latex2html, etc. dans cette section)
Si vous utilisez la ditribution miktex, remplacez windvi.exe par yap.exe
dans le fichier xdvi.bat
Apres installation, verifiez que . est dans votre PATH, sinon vous
devrez deplacer latex.bat, xdvi.bat et dvips.bat dans un repertoire de votre
chemin par exemple dans le repertoire C:\WINDOWS
Si vous placez xcas dans un repertoire du PATH et que vous le lancez
depuis un autre repertoire, vous devez donner une valeur aux variables
d'environement
XCAS_LOCALE (vers le repertoire ou les fichiers de locale sont installes)
XCAS_HELP (vers le fichier aide_cas)
Vous pouvez rajouter dans le fichier xcasfr.bat des lignes du genre
set XCAS_LOCALE=/cygdrive/c/xcas/locale/
set XCAS_HELP=/cygdrive/c/xcas/aide_cas