[Pkg-octave-devel] Packaging Octave 3.8
mtmiller at debian.org
Fri Jan 10 14:18:39 UTC 2014
On Fri, Jan 10, 2014 at 10:56:56 +0100, Sébastien Villemot wrote:
> Le vendredi 10 janvier 2014 à 00:29 -0500, Mike Miller a écrit :
> > Build error of octave_3.8.0-1 on mipsel:
> > libinterp/octave-value/ov-int16.cc-tst ................. PASS 6/6
> > libinterp/octave-value/ov-int32.cc-tst ................. PASS 6/6
> > libinterp/octave-value/ov-int64.cc-tst ................. PASS 6/6
> > libinterp/octave-value/ov-int8.cc-tst .................. PASS 6/6
> > libinterp/octave-value/ov-java.cc-tst ..................panic: Bus error -- stopping myself...
> > No idea on this one.
> Isn't it Java-related? Maybe disabling Java would help.
Yeah, I now see that the same error is in the octave-java buildd logs.
For some reason both mips and mipsel failed to build octave-java, but
mips appears to be happy with octave's java support, for now. I'm doing
a test build now with mipsel added to the disable-java list.
> > Build errors of octave_3.8.0-1 on hurd-i386:
> > configure: WARNING: llvm-config utility not found. JIT compiler is disabled.
> > [...]
> > ../libinterp/.libs/liboctinterp.so: undefined reference to `JNI_GetCreatedJavaVMs'
> > ../libinterp/.libs/liboctinterp.so: undefined reference to `JNI_CreateJavaVM'
> > collect2: error: ld returned 1 exit status
> > I disabled Java for hurd-i386 and did a successful build on a porterbox.
> > The error detecting LLVM is due to #734735. With that bug fixed locally
> > Octave detects LLVM properly and passes all JIT tests. I think the
> > reason Java is not working is because default-jdk is gcj on hurd. I can
> > commit my changes to disable Java for hurd if that sounds appropriate.
> Yes, please do.
Done (and maybe adding mipsel to the list if test build succeeds).
> > Do we want to leave LLVM enabled for hurd and assume this is a temporary
> > condition?
> As long as that LLVM issue does not trigger a FTBFS, I would leave it as
> it is.
Yes, worst case is that it won't find LLVM and implicitly disable it.
> > Upgrade error from octave_3.6.4-4+b1 to octave_3.8.0-1, with
> > octave-control installed:
> > (Reading database ... 427825 files and directories currently installed.)
> > Removing octave-control (2.6.1-1) ...
> > dpkg: liboctave1:amd64: dependency problems, but removing anyway as you requested:
> > octave depends on liboctave1 (= 3.6.4-4+b1).
> > Removing liboctave1:amd64 (3.6.4-4+b1) ...
> > Processing triggers for octave (3.6.4-4+b1) ...
> > octave: error while loading shared libraries: liboctinterp.so.1: cannot open shared object file: No such file or directory
> > dpkg: error processing package octave (--remove):
> > subprocess installed post-installation script returned error exit status 127
> This is a manifestation of #671711, which is unfortunately not yet
> fixed :(
> I guess we have no other choice than removing the breaks on liboctave1
> and replacing it by a long list of package/versions that are broken with
> Octave 3.8.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the Pkg-octave-devel