|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #49503] [mxe-octave] cross-building packages with configure script calling octave itself have issues |
Date: | Fri, 2 Oct 2020 15:45:54 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36 Edg/85.0.564.63 |
Follow-up Comment #49, bug #49503 (project octave): The changes to the buildbot builder were needed to be able to do this last change. If you'd revert that change, all cross-building builders would build an additional native Octave (the "build-octave" package). The ones that create tarballs (all but the release builders) already build and install a native Octave of the correct version with the "hg-octave-dist" target. So they don't need to build it again as a build tool (with a different and maybe conflicting configuration). The change you pushed to the buildbot configuration explicitly disables building the "build-octave" package for these builders. So changing the default in the MXE Octave configuration doesn't have an effect on them. John Donoghue proposed to make that change in comment #38. I agree that this is a good change since many developers (incl. me) probably ignore the warning about a missing native Octave on their build systems (see bug #59081) or don't update their installation regularly. _______________________________________________________ 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] |