On Fri, May 1, 2015 at 6:11 PM, Philip Nienhuis <address@hidden
<mailto:address@hidden>> wrote:
<moving private conversation to maintainers ML>
JohnD wrote:
-----Original Message-----
From: Philip Nienhuis [mailto:pr.nienhuis@
<mailto:pr.nienhuis@>******]
<snip>
I was wondering if in latest mxe-octave the OF io package is
also
(cross-) built & installed and if yes, where in the binary
installer it can be found.
Background:
I'm trying to find out why csv2cell() crashes Octave on
Windows in
--enable-windows-64 mxe builds (i.e., for Win64) (bug #44662).
Lots of cout << statements showed it crashes on simple
statements like:
while (fd.fail ())
str += line // where: std::string str , char line [MXLENGTH];
Because of the erratic crash locations I suspect it is
simply miscompiled these
days when built on the Windows side; in older 4.1.0+ 64-bit
builds it built & ran
fine.
So I figured: let's see if it works better if cross-built on
Linux and then run on
Windows.
<snip>
I believe that it is cross compiled in JWEs latest installer,
but not installed (installing still a work in progress).
Turns out that whe using the --enable-binary-packages flag as you
mentioned, csv2cell.oct is indeed built, also in case of the
"--enable-windows-64" mxe configure option, and included in the src/
subdirs of the included OF-io package. The same goes for binary
modules in other OF packages.
Well, that cross-built csv2cell.oct turns out to run fine on windows-64.
So in turn that implies that the csv2cell() issues I hit in bug
#44662 are due to mingw compiler issues; IOW the cross-built
compiler for the Windows side must be at fault.
The windows package also runs fine with cross-built 64-bit __COM__.oct.
The cross gcc is a multilib 32/64, and the gcc when installed is just
a
64 bit gcc, although I wouldnt have thought it would make a
difference
as it should be compiling programs in both cases as 64 bit.