|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #49503] [mxe-octave] cross-building packages with configure script calling octave itself have issues |
Date: | Tue, 8 Sep 2020 12:34:51 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 |
Follow-up Comment #15, bug #49503 (project octave): The octave detection mechanism by the OF-packages is broken for the mxe-crossbuilds. It was pure luck, that the maintainers building the mxe-crossbuilds had the "correct" Octave naively installed. If the maintainer had Octave 4.2 or older installed, all mxe-crossbuilds were flawed. In bug #59081 John reported, that only two packages are affected. I agree to jwe (comment #11) to solve this on per package basis, than making mxe-octave even more complicated. Maybe one can work with octave-config -p VERSION which is available during the mxe-octave package build. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?49503> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |