|
From: | John Donoghue |
Subject: | [Octave-bug-tracker] [bug #49503] mxe-octave: packages configure script calling octave itself have issues |
Date: | Thu, 3 Nov 2016 11:59:33 +0000 (UTC) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586 |
Follow-up Comment #2, bug #49503 (project octave): There was a discussion on the maintainers list (I think) where it was decided it was resonalable to expect whoever was packaging the binary packages would have a native octave installed. Having said that, currently mxe doesn't check that a native veersion is installed, and I see from doing a build myself, that mxe silently fails on the configure script if you don't have octave and packages just the install the inst files So perhaps a check for octave and at the very least a warning given during the mxe build would be good. Theres at least one other package in mxe that would check the octave version, however I think I patched it in mxe to just not install the file make would conditionally not install. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?49503> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |