|
From: | Philip Nienhuis |
Subject: | [Octave-task-tracker] [task #13313] MingW issues for Octave built w --enable-64 |
Date: | Sun, 07 Sep 2014 14:49:22 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 Iceape/2.22 |
Follow-up Comment #6, task #13313 (project octave): I suppose people would want 64-bit Octave with 64-bit indexing. Isn't that the point of 64-bit? Didn't you get FAILs in eig.cc-tst before you checked in that cs? (I'm referring to the last 4 input validation tests in eigs.cc-tst.) I got those consistently with --enable-64. Indeed eigs.cc tests pass fine on Octave built for Linux (Mageia-4 64 bit). I suppose a compiler bug cannot be ruled out. I got those FAILs also before gcc in MXE was upgraded to 4.9.0. But indeed - maybe those tests are too lax and simply don't trigger on Linux. I'd expect (= hope for) identical behavior on Linux and Windows. OT: What is the reason that Ghostcript isn't built for 64-bit Octave? didn't it get built properly with mingw-64? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/task/?13313> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |