On Wed, Jun 26, 2019 at 2:30 PM Niels Möller nisse@lysator.liu.se wrote:
Alon Bar-Lev alon.barlev@gmail.com writes:
In Gentoo and probably other downstream distributions we let package management to manage the flags
This is a bit tricky. One can already pass CFLAGS= to configure. But I think the intention is that should override configure's automatic selection of flags (I haven't tested that though). But usually, one wants the package's configure have some say, and e.g., enable warnings that are expected to be silent.
So I'd rather have something more general like APPEND_CFLAGS added after CFLAGS to make it possible to override selected flags, and with some consistency with other packages using autoconf.
I do not understand... In practice a package should not add by itself optimization or debug flags without consent (some --enable- argument), the fact that nettle is doing that is unexpected... the problem is how to tell build system to avoid adding these flags, not adding additional or keeping tack of what is added and try to suppress... up until now we patched the package to meet guidelines, can you please tell me what solution would you accept? Maybe --disable-custom-flags argument?
Thanks!