[Pkg-octave-devel] Octave3.0 compiled using gfortran

Thomas Weber thomas.weber.mail at gmail.com
Sat Jan 19 13:29:28 UTC 2008


Am Samstag, den 19.01.2008, 11:57 +0100 schrieb Pascal A. Dupuis:
> On Fri, Jan 18, 2008 at 06:37:55PM +0100, Rafael Laboissiere wrote:
> > * depuis <pascal.dupuis at worldonline.be> [2008-01-18 18:02]:
> > 
> > > I recently tested a patch on octave3.0, and noticed the dependency to f77.
> > > After searching a bit, I found the page about the gfortran transition at 
> > > http://wiki.debian.org/GfortranTransition
> > > 
> > > The main dependencies are:
> > > 1) atlas and lapack: Cam Maguire has already recompiled those libs, packages
> > > at http://people.debian.org/~camm/
> > > 2) suitesparse-3.0.0: I recompiled locally a version, changing the control
> > > file to reflect the names change of atlas to libatlas
> > > 
> > > I then updated the debian files for octave3.0. Compilation is in progress...
> > > I enclose the debian specific files, could you check ? Could you also forward
> > > the info to the relevant mailing lists, if relevant ?
> > 
> > Could you please send a patch instead of the debian/* files in a tarball?
> > Send the patches pkg-octave-devel at lists.alioth.debian.org and
> > pkg-scicomp at lists.alioth.debian.org.
> > 
> 
> Patchs enclosed. The version of octave compiled with gfortran ran all
> his tests, except 4. Two of those failures are known. The list of
> failed test is:
> src/DLD-FUNCTIONS/rand.cc .............................. PASS   56/57   FAIL 1
> scripts/optimization/sqp.m ............................. PASS    0/1    FAIL 1
> test_sparse.m .......................................... PASS 1182/1184 FAIL 2

Test failures not withstanding, what should we do now? Camm's private
archive is not acessible to the buildds.

	Thomas




More information about the Pkg-octave-devel mailing list