`=no` values for sanitizer configure options still enable sanitizer flags

Bug report

Bug description:

Summary

Passing no to a sanitizer option is reported as disabled, but the option's action still adds sanitizer compiler and linker flags. For AddressSanitizer, it also disables pymalloc.

Reproduction

mkdir build
cd build

../configure --with-address-sanitizer=no
grep -E '^(BASECFLAGS|LDFLAGS)=' Makefile
grep WITH_PYMALLOC pyconfig.h

Actual Behavior

Configure reports:

checking for --with-address-sanitizer... no
checking for --with-pymalloc... no

Despite that output, the AddressSanitizer action adds -fsanitize=address to BASECFLAGS and LDFLAGS, and sets with_pymalloc=no.

Expected Behavior

--with-address-sanitizer=no should not enable AddressSanitizer flags and should not change the pymalloc setting. It should have the same result as omitting the option or using the corresponding --without-... form.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Linked PRs

• gh-157355

Inizia eseguendo la riproduzione di configure fornita sul branch principale di CPython e ispeziona la gestione delle opzioni di configure del sanitizer che aggiunge BASECFLAGS e LDFLAGS e modifica with_pymalloc. Il lavoro è completato quando --with-address-sanitizer=no lascia invariati i flag del sanitizer e l'impostazione di pymalloc, come un'opzione omessa o la forma --without corrispondente.