octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Philip Nienhuis
Subject: Re: MXE: "undefined reference to `mxArray::mxArray(mxClassID, long long, long long, mxComplexity)"
Date: Mon, 29 Dec 2014 15:34:35 -0800 (PST)

Philip Nienhuis wrote
> 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)'
> :

After a bit of trial and error I found that it is this changeset from Rik:

1085a65e9b9b gui-release    (build: Don't install mxarray.in.h (bug #43805))

that provokes the errors with --enable-64. I'll reopen bug #43805.

FWIW, I cannot imagine what is wrong with the changeset.
But I do note that from the previous changeset 50d4fd16fb3a by Kai (which is
just a third or fourth after after a maintenance merge
stable->gui-release->default) to the 1085a65e9b9b at hand, mercurial informs
me of "946 files updated, 0 files merged, 127 files removed, 0 files
unresolved", i.e. a ridiculous number of affected files.

Philip




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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]