Re: [Autoconf] Re: HTML format documentation

2000-09-16 Thread Richard Stallman
I'm not sure I know what was being meant here for sure either but my interpretation is that configuration items such as the CC and CFLAGS Make variables (which are as I say unfortunately sometimes taken from the environment) have the nature of being variables This is starting to m

Re: [Autoconf] Re: HTML format documentation

2000-09-15 Thread Greg A. Woods
[ On Friday, September 15, 2000 at 16:29:04 (-0600), Richard Stallman wrote: ] > Subject: [Autoconf] Re: HTML format documentation > > The GNU coding standards explicitly specifies the possible configure > options. Whatever names we choose for new options, they will have to >

[Autoconf] Re: HTML format documentation

2000-09-15 Thread Richard Stallman
The GNU coding standards explicitly specifies the possible configure options. Whatever names we choose for new options, they will have to be given in the coding standards. They will not be exceptions, they will be defined options. I agree, and this is why I proposed to move the foodir into

[Autoconf] Re: HTML format documentation

2000-09-15 Thread Greg A. Woods
[ On Tuesday, September 12, 2000 at 14:12:42 (-0600), Richard Stallman wrote: ] > Subject: Re: HTML format documentation > > It is an incompatible change in the spec, and that is very bad. There are ways to fix what might be called ``design flaws'' without causing permanent headaches for everyone

Re: [Autoconf] Re: HTML format documentation

2000-09-14 Thread Akim Demaille
> "Richard" == Richard Stallman <[EMAIL PROTECTED]> writes: > XEmacs already uses --with-cc and --with-cflags, although I'd tend > to go for the shorter --cc=sun-cc and --cflags=-O2. You'd also need > --cxx and --cxx-flags; I'm not sure what other environment variables > are similarly specia

[Autoconf] Re: HTML format documentation

2000-09-14 Thread Akim Demaille
| So maybe something like | --set-CFLAGS=-ggdb? | | That is a uniform scheme but not very convenient. Since all of these | options would be designated by us, and we would make an explicit list | of them, we don't have to limit ourselves to a simple uniform naming | scheme. Please, do

[Autoconf] Re: HTML format documentation

2000-09-14 Thread Richard Stallman
Hence, we need an open scheme, so I think --VAR=VAL is wrong, there is way too much risks to confuse actual options with variables, or to forbid any extension in the future. I think you are right--if we use options, the option name should not have to be the same as the variable name.

[Autoconf] Re: HTML format documentation

2000-09-14 Thread Richard Stallman
XEmacs already uses --with-cc and --with-cflags, although I'd tend to go for the shorter --cc=sun-cc and --cflags=-O2. You'd also need --cxx and --cxx-flags; I'm not sure what other environment variables are similarly special. If we go in that direction, should we say that ALL th