On Sun, Jun 07, 2026 at 08:59:11PM +0100, Gavin Smith wrote: > > Note that since it is now C only, it means that it will depend more on > > the underlying C library. It should not make much difference, except > > for translations that are done right after parsing, they won't be done > > if the libc does not handle LANGUAGE, as is the case for musl. > > When does this make a difference? As far as I understand, the SWIG > interface is for user extension code, so nothing should break with > texi2any itself, right?
Indeed, the difference I am speaking about is not for texi2any, as texi2any still uses Perl in that case, it is the difference obtained when using the SWIG interface on different platforms. > > There is now a failure in opencsw in the SWIG interface testsuite for > > solaris 10, which happen to have swig installed, for one test. > > Other than that, all the github CI pass, with swig installed when > > possible. > > The Solaris 10 failure is a problem as it shows that the SWIG code may > not be reliable if it is enabled. Will you be able to investigate the > failure? It is not so easy, but I have asked Dagobert to install swig on a cfarm host such that I can debug. Also it is too early to know if there is an issue with the SWIG code, or if it is something else, especially on this platform. -- Pat
