Opened 12 years ago
Closed 5 months ago
#4821 closed enhancement (invalid)
[with spkg, needs work] Experimental scilab-5.0.3.spkg
Reported by: | jsp | Owned by: | mabshoff |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | packages: experimental | Keywords: | scilab, matlab |
Cc: | mkoeppe | Merged in: | |
Authors: | Reviewers: | Matthias Koeppe | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
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 (10)
comment:1 follow-up: ↓ 2 Changed 12 years ago by
- 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 12 years ago by
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
comment:3 Changed 7 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:4 Changed 7 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:5 Changed 6 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:6 Changed 6 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:7 Changed 5 years ago by
- Description modified (diff)
- Report Upstream set to N/A
comment:8 Changed 5 months ago by
- Cc mkoeppe added
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Status changed from needs_work to needs_review
Maybe we can close this ancient ticket now ?
comment:9 Changed 5 months ago by
- Reviewers set to Matthias Koeppe
- Status changed from needs_review to positive_review
comment:10 Changed 5 months ago by
- Resolution set to invalid
- Status changed from positive_review to closed
thx
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