On Sun, Jan 11, 2026 at 07:51:41PM +0100, Bruno Haible wrote: > Gavin Smith wrote: > > It's completely wrong to provide these flags to gcc. > > Yes, one cannot take options meant for one compiler and apply them to another > compiler. > > > Does the build work if you only give the value of CC, not the value > > of PERL_EXT_CC? > > No, it doesn't work either. That's in fact the first thing I tried, lazy > as I am. > > Bruno
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? It would also be helpful to see the output from the configure test for whether XS modules work. If the compiler is found not to exist or to be completely broken, there would be an error message in tta/config.log like: "building Perl extension (XS) modules will be disabled" Otherwise, it should attempt to build and run under tta/perl/CheckXS. The output could look like this: configure:5910: checking Perl XS with usable getenv configure:5915: result: yes configure:6030: === configuring in perl/CheckXS (/home/g/src/texinfo/GIT/tta/perl/CheckXS) configure:6111: checking whether we can build Perl extension (XS) modules configure:6113: result: checking ./TestXS.la found ./TestXS.la ./.libs/TestXS.so loaded looking for boot_TestXS trying to call boot_TestXS... ...succeeded configure:6128: checking whether we can build Perl extension (XS) modules configure:6130: result: yes
