Installation de Scilab sous LINUX

Salut,
En tant que root

./configure
make all

Par contre ça sert à rien de le mettre dans /usr/local, par défaut le produit
va s'installer dans /usr en fin de compil. Lis le fichier README_Unix dans
le dossier scilab-3.1.1.

Pour ta seconde question, il faut que le produit soit bien conçu.
Habituellement tu fais un './configure' et un 'make' avec un compte
développeur. Ensuite en root tu fais un 'make install'. Attention toutes les
options de type dossier d'installation des binaires, des bibliothèques, ... sont
à préciser lors du './configure'.

Dans tous les cas il faut lire les fichier README et/ou INSTALL fournis
avec l'archive.

A+, crabs

Merci,

/usr/local/Scilab/scilab-3.1.1

Lancement du shell:
su
Mot de passe

./configure
execution ....
....

checking for g77... no
checking for f2c... no
configure: error: Unable to configure: no Fortran compiler found

make: *** Pas de règle pour fabriquer la cible « all ». Arrêt.
[root@TUX scilab-3.1.1]# make
make: *** Pas de cibles spécifiées et aucun makefile n'a été trouvé. Arrêt.
[root@TUX scilab-3.1.1]# make install
make: *** Pas de règle pour fabriquer la cible « install ». Arrêt.

Ou executer le make ???

Ca c'est quoi ???

checking for g77... no
checking for f2c... no
configure: error: Unable to configure: no Fortran compiler found

=> installer Fortran, soit le compilateur g77 ou le machin f2c qui traduit Fortran vers C et apres recommencer.

Je vous donne le détail du ./configure

[root@TUX scilab-3.1.1]# ./configure
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
configuration of libtool
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fl32... no
checking for af77... no
checking for fort77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for lf95... no
checking for g95... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
end of configuration of libtool
checking for main in -lieee... yes
checking for g77... no
checking for f2c... no
configure: error: Unable to configure: no Fortran compiler found
[root@TUX scilab-3.1.1]#

Tu as la reponse (-> <3>).

Bonjour,

Version actuelle 4.0 : http://www.scilab.org/download/index_download.php?page=release.html

Bonjour,

Version actuelle 4.0 : http://www.scilab.org/download/index_download.php?page=release.html