[bug #68033] mkoctfile does not work using version 11.0.92 on Windows 11

Please use the bug tracker to post updates to a bug report.  The mailing list is intended as a read-only notification stream.  Info posted to this mailing list address won't appear in the tracker database where it is most useful.

Update of bug #68033 (group octave):

                  Status:          Ready For Test => In Progress

    _______________________________________________________

Follow-up Comment #13:

Apparently, redirecting output doesn't work reliably when ABI translation
layers come into the picture (be it by qemu or the Linux kernel).

We aren't actually interested in testing whether these ABI translation layers
correctly handle translations of file handles.
But imho, it is still worthwhile having these tests when no ABI translation
layers are used.

It is difficult to detect from within a running process whether it in running
on top of these ABI translation layers. (They make a good enough job to make
it appear to the process that it is running on "native" hardware.)

The attached patch uses some checks that are more or less tailored to how we
are using emulation/ABI translation in the existing CI. That would be good
enough to have the cross-building CI runners pass the test suite again.

Does anyone have a better idea how to deal with that instead?


(file #58232)

    _______________________________________________________

Additional Item Attachment:

Name: bug68033-foreign-ABI.patch     Size: 3.1KiB

<https://file.savannah.gnu.org/file/bug68033-foreign-ABI.patch?file_id=58232>


    AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://savannah.gnu.org/source/savane-9cb3993bd77cd3a7b4e316c57f63ab757e1a05d8.tar.gz


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?68033>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaYw09gAKCRCqLAuaBUf3
TpShAQDhEQOvitxx7OCQPnRVgA22+jyeGrx+o3cloey1DI8cegD/WcGtALkwg8Nh
J8nXTeKA0qW2WafaTafLd5oQgBul8wo=
=tcuN
-----END PGP SIGNATURE-----