Re: CFLAGS is for the user in GNU

[Ralf Corsepius]

Karl Berry wrote:
> The description of CFLAGS in the Autoconf manual omits the most
> important point about it.  To quote the coding standards
> (make-stds.texi):
>
>     If there are C compiler options that @emph{must} be used for proper
>     compilation of certain files, do not include them in @code{CFLAGS}.
>     Users expect to be able to specify @code{CFLAGS} freely themselves.
>
> I would write a patch for it, but I'm not sure if there is a variable to
> suggest for such required options for the C compiler proper these days.
> Maybe it never comes up in practice?
Ohh, the problem does come up in practice.

However, I think you trying to solve a non-issue, because such 
"hard-coded flags" are package-specific internal configuration details, 
a package's configuration implementor will treat just like any other 
package-specific configuration detail.

I.e., he will typically add some *_*FLAGS macros/AS_SUBST's and use them 
inside of his hand-crafted Makefile.in's.

Ralf