Ticket #4821 (needs_work enhancement)
[with spkg, needs work] Experimental scilab-5.0.3.spkg
| Reported by: | jsp | Owned by: | mabshoff |
|---|---|---|---|
| Priority: | minor | Milestone: | sage-5.10 |
| Component: | packages: experimental | Keywords: | scilab, matlab |
| Cc: | Work issues: | ||
| Report Upstream: | Reviewers: | ||
| Authors: | Merged in: | ||
| Dependencies: | Stopgaps: |
Description
I made an experimental scilab-5.0.3.spkg
[ http://sage.math.washington.edu/home/jsp/SPKGS/Scilab/scilab-5.0.3.spkg ]
Please test it by downloading it into $SAGEROOT and type ./sage -f -m scilab-5.0.3.spkg The -m argument keeps the package in the spkg/build directory for further experimentation. See spkg-install: I did a minimal ./configure --without-javasci --without-gui --with-gfortran There are two dependencies left: pcre and matio I don't know how essential they are for a full functional scilab :(
Cheers,
Jaap
For me it worked on Fedora 9 and Fedora 10
real 36m7.756s
user 22m25.173s
sys 9m55.849s
Successfully installed scilab-5.0.3
You can safely delete the temporary build directory
/home/jaap/downloads/sage-3.2.2.alpha0/spkg/build/scilab-5.0.3
Making Sage/Python scripts relocatable...
Making script relocatable
Finished installing scilab-5.0.3.spkg
[jaap@paix sage-3.2.2.alpha0]$
[...]
sage: scilab.console()
graphics module not found.
javasci module not found.
___________________________________________
scilab-5.0.3
Consortium Scilab (DIGITEO)
Copyright (c) 1989-2008 (INRIA)
Copyright (c) 1989-2007 (ENPC)
___________________________________________
Startup execution:
loading initial environment
-->
Change History
comment:1 follow-up: ↓ 2 Changed 4 years ago by mabshoff
- Summary changed from Experimental scilab-5.0.3.spkg [with spkg, needs review] to [with spkg, needs work] Experimental scilab-5.0.3.spkg
comment:2 in reply to: ↑ 1 Changed 4 years ago by jsp
Replying to mabshoff:
This spkg needs at least to attempt to pick the right Fortran runtime at configure time.
Of course you are right, but I don't know how to do that.
Besides there are other dependencies to be resolved.
What I did on Fedora was cycling .configure and installing missing dependencies.
Not very suited for inclusion in spkg-install :-)!
Jaap
Note: See
TracTickets for help on using
tickets.

This spkg needs at least to attempt to pick the right Fortran runtime at configure time.
Cheers,
Michael