[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Testing MXE-Octave
From: |
John W. Eaton |
Subject: |
Re: Testing MXE-Octave |
Date: |
Mon, 11 Feb 2013 13:59:39 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 |
On 02/11/2013 01:38 PM, Philip Nienhuis wrote:
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.
Yeah, there are lots of problems with the GUI. I don't think that these
problems are specific to the MXE cross build.
- 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."
I think I fixed that problem yesterday. You probably just need to update.
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.
I have no idea why there is any difference.
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
I don't see this problem. The amazonaws.com and cloudfront.net URLs are
some sort of secondary sites that MXE uses. I didn't do that part. If
you are seeing that, then you must be having trouble connecting to the
default site for qhull downloads. Look in log/qhull for more info.
Do you prefer such issues to be reported in the maintainers list or in
the bug tracker?
Discussing issues specific to the MXE scripts on the list is OK. Bugs
in the resulting Octave binary should be reported like any other bugs.
jwe
- Testing MXE-Octave, Philip Nienhuis, 2013/02/11
- Re: Testing MXE-Octave,
John W. Eaton <=
- Re: Testing MXE-Octave, PhilipNienhuis, 2013/02/11
- Re: Testing MXE-Octave, Daniel J Sebald, 2013/02/11
- Re: Testing MXE-Octave, Torsten, 2013/02/12
- Re: Testing MXE-Octave, Philip Nienhuis, 2013/02/12
- Re: Testing MXE-Octave, Daniel J Sebald, 2013/02/12
- Re: Testing MXE-Octave, PhilipNienhuis, 2013/02/12
- using timers in the GUI (was: Re: Testing MXE-Octave), John W. Eaton, 2013/02/18
- Re: using timers in the GUI (was: Re: Testing MXE-Octave), Jacob Dawid, 2013/02/18