Jürgen, That all looks fine, and the latest trunk (SVN: 3892", "2026-11-02 22:17:43 CET") builds/tests without issue on sparc64. Including the four testcases you mentioned (Quad_CR, ZZ17_Regression, AP100 and AP210) which all pass.
In my latest debian packaging I enabled build-time testing using some debian/tests/ scripts, but some of the "upstream" tests failed so I only run the ones that ran okay. This is how the sparc64 (bigendian) issues were picked up. I'll let you know if the multiple-arch builds pick up anything else. I do have a pretty heavily patched 2.0, with 14 patches (https://tracker.debian.org/pkg/gnu-apl has a link "debian patches" that shows them, if you don't want to deal with git.) All the important ones are already deal with in the SVN trunk, what's left is reconstructed-texi-files (you have apl-library.info without the corresponding .texi source); spelling is merged but there's a stray new "GNU Public License" that should read "GNU General Public License"; and the doc-info-html stuff with info_TEXINFOS. Would you like me to modify the doc-info-html patch to hot-wire things so if makeinfo isn't available the build falls back to using prebuilt documentation files? Anyway, release 2.0 is pretty old at this point. Should I just wait for a new release? Or should I package a snapshot of the SVN trunk at some point? Cheers, --Barak.
