MXE: "undefined reference to `mxArray::mxArray(mxClassID, long long, long long, mxComplexity)"

[Philip Nienhuis]

When trying to cross-build Octave (3.9.0+ & 4.1.0+) with --enable-64, the
build of Octave stops with errors a la:

:
octave-value/.libs/liboctave-value.a(octave_value_liboctave_value_la-ov-bool.o):
In function `octave_bool::as_mxArray() const':
/home/philip/devel/octdev/mxe/mxe64_20141208/tmp-octave/octave-3.9.0+/libinterp/octave-value/ov-bool.cc:234:
undefined reference to `mxArray::mxArray(mxClassID, long long, long long,
mxComplexity)'
:

In ov-bool.cc at L.234 there's indeed no function call with mxComplexity
argument, just mxReal. Admittedly I'm not very well acquainted with the C++
part of Octave code so that's where I get stuck.
It's only function calls with arg lists "(mxClassID, long long, long long,
mxComplexity)" that appear in the error messages.

I've first built up-to-date Octave (3.9.0+ and 4.1.0+) w/o --enable-64 on
64-bit Linux (where they ran fine) and then produced a dist using "make all
dist".
I've included a slight mod:
#include <stdint.h>
right above the typedefs in libinterp/corefcn/mxArray.in.h on L.89 (to be
able to compile a few OF packages with a 64-bit indexing Octave once on
Windows), as hinted by John D. 
Around Dec 9 (the last time I've cross-built Octave) that worked fine; but I
have the feeling that patch has little to do with the current issue anyway.

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/MXE-undefined-reference-to-mxArray-mxArray-mxClassID-long-long-long-long-mxComplexity-tp4667930.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.