On Wed, Jan 14, 2026 at 10:35:38AM +0100, Patrice Dumas wrote: > On Sun, Jan 11, 2026 at 10:05:23PM +0100, Bruno Haible via Bug reports for > the GNU Texinfo documentation system wrote: > > Gavin Smith wrote: > > > Could you please provide the error messages from when you tried it without > > > PERL_EXT_CC set? Did it fail due to a non-existent compiler, or for > > > another > > > reason? > > > > If PERL_EXT_CC isn't set, it apparently uses $CC instead. I get the same > > error: > > What is happening in that case is not good, and the consequence of > having added Perl flags everywhere even if XS modules cannot be built, > and not having this special case better handled. > > I'll try to come up with something saner, as it should be possible to > build part of the C code. Although the resulting libraries/binaries > would be lacking many features, be able to convert to HTML only, without > proper index sorting. Since the code produced is not really useful, it > is also possible to go back to the way it was before, if XS is disabled > do not even recurse in tta/C.
The fix I came up with in the latest commit is actually quite simple and makes sense, I simply unset the perl_conf* variables if XS is disabled. It worked for me, but my platform is not very good for testing that kind of change, because gcc is used both to compile Perl and texinfo. It would be nice if you could test on this AIX setup (or similar) if you get something that builds. If you want to test a bit more, you could also try to pass --enable-additional-checks to configure to see if the C only executable (for development only) builds, but it is not important at all. -- Pat
