Opened 13 years ago
Last modified 10 years ago
#1609 new enhancement
create an octave-3.0.0 optional spkg
Reported by: | was | Owned by: | was |
---|---|---|---|
Priority: | major | Milestone: | sage-wishlist |
Component: | packages: optional | Keywords: | octave |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
Change History (9)
comment:1 Changed 13 years ago by
- Status changed from new to assigned
comment:2 Changed 13 years ago by
- Milestone changed from sage-2.9.2 to sage-wishlist
comment:3 Changed 13 years ago by
I probably won't work on this further, so I hope somebody else will try.
comment:4 Changed 13 years ago by
- Status changed from assigned to new
comment:5 Changed 13 years ago by
> > Looking at the linker failure it indicates that you have a gcc 4.2 > somewhere (maybe installed into $SAGE_LOCAL via my gcc-4.2.1 spkg :)) > and the linker gets confused because it also links against a gcc 4.0.3 > runtime. If that is the case I can have a closer look. It seems that > the build failed right at the end. You're right; it's some sort of conflict like that though I don't think it's gcc-4.2 versus gcc-4.0.3, but gcc-4.2.1 versus gcc 4.0.3 stuff that's coming from the g95 binaries that we ship with Sage. So probably the way to build the Octave package would be to build Sage using gfortran/gcc from your gcc-4.2.1.spkg, then build Octave. I don't know if there is a way around having to do that, which basically means no optional Octave package. I don't think having an optional Octave package is critical since it takes > 1 hour to build, and the Octave developers are extremely good at making it easy to get Octave binaries for a wide range of platforms. -- William
comment:6 Changed 11 years ago by
- Keywords octave added
- Report Upstream set to N/A
Not sure if this helps but I typically do: ./configure F77=gfortran
this seems to compile cleanly.
If needed be, we can get the octave people involved. This is a nice and important package for many people.
comment:7 Changed 10 years ago by
3.4.0 is the latest release, so there's not much point in trying to create a 3.0.0 package.
Dave
comment:8 Changed 10 years ago by
I thought I'd have a quick go at trying to make an Octave package, but I hit a problem pretty early on:
checking for sin in -lm... yes checking whether we are using the GNU Fortran 77 compiler... yes checking whether /export/home/drkirkby/sage-4.7.rc0/local/bin/sage_fortran accepts -g... yes checking how to get verbose linking output from /export/home/drkirkby/sage-4.7.rc0/local/bin/sage_fortran... -v checking for Fortran 77 libraries of /export/home/drkirkby/sage-4.7.rc0/local/bin/sage_fortran... -L/usr/ccs/lib -L/usr/lib -L/export/home/drkirkby/sage-4.7.rc0/local/lib -L/usr/local/gcc-4.6.0/lib/gcc/i386-pc-solaris2.11/4.6.0 -L/usr/local/gcc-4.6.0/lib/gcc/i386-pc-solaris2.11/4.6.0/../../.. -lgfortran -lm -lquadmath checking for dummy main to link with Fortran 77 libraries... unknown configure: error: in `/export/home/drkirkby/sage-4.7.rc0/spkg/build/octave-3.4.0/src': configure: error: linking to Fortran libraries from C fails See `config.log' for more details Error configuring GNU Octave real 0m23.634s user 0m9.304s sys 0m8.385s sage: An error occurred while installing octave-3.4.0
I don't know what BLAS library I'm supposed to configure this with. I have tried:
./configure --prefix="$SAGE_LOCAL" --with-glpk-includedir="$SAGE_LOCAL/include" --with-glpk-libdir="$SAGE_LOCAL/lib" --with-blas="SAGE_LOCAL/lib/libcblas.so" F77="$SAGE_FORTRAN"
but are unsure if the 'libcblas.so' is the right library. I tried another one (libblas.a), but had no luck with that either. If I omit the --with-blas=
option, then it fails with:
configure: error: A BLAS library was detected but found incompatible with your Fortran 77 compiler settings.
I don't know how to get around this BLAS issue.
I think it will need a bit of work to create this package. To get the best from Octave, you need a lot of libraries Sage does not include. It might be worth putting those libraries in an Octave package and building the libraries first.
Dave
comment:9 Changed 10 years ago by
- Component changed from packages to optional packages
OK, I made a first attempt which I've posted here:
http://sage.math.washington.edu/home/was/build/octave-3.0.0.spkg
It builds for 70 minutes then dies with a mysterious C++ error: