Hi Mark, On 2025-10-29 05:13, Mark Brown wrote: > On Wed, Oct 29, 2025 at 05:48:07PM +0100, Emanuele Rocca wrote: > > In the general case, packages honoring CFLAGS, LDFLAGS, and other > > similar environment variables get the default build flags for free > > without the need for any work on the maintainer side. In the case of > > clc-intercal, the flags are either ignored or overridden. > > This package is written in an interpreted language, none of these will > do anything.
In the build logs I see commands such as: aarch64-linux-gnu-gcc -c \ -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -Wall \ -DPERL_EXTMALLOC_DEF -Dmalloc=Perl_malloc -Dfree=Perl_mfree -Drealloc=Perl_realloc -Dcalloc=Perl_calloc -DVERSION=\"1.406498505\" \ -DXS_VERSION=\"1.406498505\" -fPIC "-I/usr/lib/aarch64-linux-gnu/perl/5.40/CORE" blib/xs/Numbers.c -o blib/xs/Numbers.o Suggesting that at least some parts of the software are written in C?
