On Wed, Jun 26, 2019 at 4:22 PM Niels Möller nisse@lysator.liu.se wrote:
Alon Bar-Lev alon.barlev@gmail.com writes:
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...
I'm open to discuss how to deal with CFLAGS. Currently, Nettle sets -ggdb3, various warning flags (if compiling with gcc), and it kind-of adds -fPIC, but via different autoconf and make variables.
I think GNU standard is to use something like -g -O by default.
As a developer, I find it convenient to have stricter warning flags and more debug info by default, but that could be tied to an explicit configure argument and disabled by default. When suggesting improvements, please consider recommendations in the GNU coding standards.
Also keep in mind that ./configure defaults are intended primarily to make life easy for the user that runs ./configure manually, perhaps to try out a modification of her own. If you have a packaging framework that runs configure for you, it's expected that package configuration needs to add a couple of explicit arguments to override the defaults.
Hi, I do not want to take anything from you, just for you to support disabling this behavior. I manage vast number of packages, and the well behaved ones are not manipulate flags. However, as I wrote, I do not want to take anything from your environment or default behavior, just to allow formal method (vs patching) to make this package live correctly within downstream by disabling these behaviors. Thanks!