|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #43805] mxarray.in.h gets installed |
Date: | Tue, 30 Dec 2014 00:13:55 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux i686 on x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 |
Update of bug #43805 (project octave): Status: Fixed => None Open/Closed: Closed => Open _______________________________________________________ Follow-up Comment #2: Reopening this bug. As outlined here: http://octave.1599824.n4.nabble.com/MXE-quot-undefined-reference-to-mxArray-mxArray-mxClassID-long-long-long-long-mxComplexity-quot-tt4667930.html#a4667934 it seems to be the fix for this bug that makes --enable-64 (cross-)builds break with the error message in the URL above. I have no idea why such an obvious one-line change can have these consequences. As stated in the above post, mercurial needed to adapt a ridiculously large number of files going from the previous changeset by Kai (admittedly for default) to this one (for gui-release). grepping for mxarray.h in the source tree I see various references to both mxarray.h.in and mxarray.in.h ??? I've provisionally set Status back to "None" _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?43805> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |