|
| From: | Markus Mützel |
| Subject: | [Octave-bug-tracker] [bug #49503] [mxe-octave] cross-building packages with configure script calling octave itself have issues |
| Date: | Wed, 9 Sep 2020 13:10:16 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 Edg/85.0.564.44 |
Follow-up Comment #26, bug #49503 (project octave):
The attached patch should be complete with the logic to use or not use the
build-octave package.
@Kai: If we should opt to include that change, you could configure MXE Octave
with "--disable-system-octave" and your buildbots should be able to build the
binary of-packages correctly.
All others could just configure like before and nothing would change for
them.
I don't think it is necessary to include any logic that overrides that option
in case the "hg-octave-dist" target was build. That is a separate target that
afaict is not pulled in by any other target. If someone builds that target,
they should take care to *not* configure with "--disable-system-octave".
(file #49771)
_______________________________________________________
Additional Item Attachment:
File name: bug49503_build_octave.patch Size:8 KB
<https://file.savannah.gnu.org/file/bug49503_build_octave.patch?file_id=49771>
_______________________________________________________
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] |