Testing MXE-Octave

[Philip Nienhuis]

Hi John,

I see you've been quite busy lately with the MXE build. Thanks for that.
The last weeks I've been playing with it (in some spare hours) and found 
that while it's not perfect yet, I can do quite a bit of productivity 
tasks with it (maybe not extremely demanding ones).

Here's some feedback on the most obvious glitches I found in the 
previous version (with 3.7.1 snapshot):

- The GUI starts with a few messages:
"QObject::startTimer: timers cannot be started from another thread"
(2X)
I've encountered this error too when I could still build under MinGW (no 
more since January or so).
Israel Herraiz has fixed this error in his MSVC-based UPM build.
AFAICS this error doesn't have any negative effects (yet).

- The GUI's workspace pane isn't functional - entering something like "a 
= 10" doesn't make a show up in the workspace.

- Running ./share/octave/3.7.1/m/test/runtests.m gives an error in 
svds.m (Windows pop-up: "This application has failed to start because 
libarpack.dll was not found."
============================
  svds.m .................................................  ***** 
testif HAVE_ARPACK
 [u2,s2,v2,flag] = svds (A,k);
 s2 = diag (s2);
 assert (flag, !1);
 assert (s2, s(end:-1:end-k+1), 1e-10);

!!!!! test failed
could not find library or dependents: 
X:\Octave\octave-2013-02-09-18-21\lib\octave\3.7.1\o
ct\i686-pc-mingw32\eigs.oct
warning: test: some elements in list of return values are undefined
============================
Indeed I couldn't find arpack in the zip file.
In the meantime I see that you've fixed something with the arpack 
library (changeset 2976:a6cdc75d044b)

OTOH, a very nice -yet intruiging- outcome is that this build doesn't 
suffer from bug #34631. So apparently this bug is related to limitations 
imposed by native Windows build environments.


Trying the latest MXE (changeset 2975:839a571d0b1d) (hoping the arpack 
stuff & workspace would be OK now) the build ends with:
============================
:
[download] qhull

Wrong checksum of package qhull!
------------------------------------------------------------
Connecting to s3.amazonaws.com (s3.amazonaws.com)|207.171.163.205|:80... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2013-02-11 18:42:24 ERROR 404: Not Found.
--2013-02-11 18:42:24-- 
http://d1yihgixbnrglp.cloudfront.net/qhull-2009.1.tar.gz
Resolving d1yihgixbnrglp.cloudfront.net 
(d1yihgixbnrglp.cloudfront.net)... 54.240.166.223, 54.240.166.211, 
54.240.166.123, ...
Connecting to d1yihgixbnrglp.cloudfront.net 
(d1yihgixbnrglp.cloudfront.net)|54.240.166.223|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-02-11 18:42:24 ERROR 404: Not Found.
------------------------------------------------------------
[log]      /home/philip/devel/octdev/mxe/mxe-octave/log/qhull-download

make: *** [/home/philip/devel/octdev/mxe/mxe-octave/usr/installed/qhull] 
Error 1
address@hidden mxe-octave]$
============================

There's no mention of qhull in http://d1yihgixbnrglp.cloudfront.net

Do you prefer such issues to be reported in the maintainers list or in 
the bug tracker?

Thanks,

Philip