httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Kraemer <>
Subject Re: [PATCH] lets do 1.2.5
Date Thu, 08 Jan 1998 11:13:51 GMT
On Wed, Jan 07, 1998 at 01:51:19PM -0500, Jim Jagielski wrote:
> Randy Terbush wrote:
> > 
> > I would agree with Marc's view on this. The flexibility should
> > be there.
> Nope. Not in the CC variable. Someplace else, yes, but not CC

I disagree with your view, and with Ken's statement that $(CC) must be a
possible argument to which(1). There is no prior art where $(CC) is 
`which'able or `which'ed, but (as Mark explained) there are some switches
which can be seen (together with the executable name) 
as "the atomic compiler call" for a certain situation.

If we were to impose the restriction that this be a single word, then we
force every user who happens to have such a compiler to write his own
wrapper script around cc, only to be able to use it with apache.
OTOH, the patch (as posted on the list) simply replaces "make CC=$(CC)"
by "make CC='$(CC)'" which is neither error prone nor incorrect, and is
the same mechanism as is used for AUX_CFLAGS.

The statement "this is a CFLAGS thing" is not the answer either. $(CFLAGS)
can be passed to programs other than $(CC), like "makedepend", "mkptypes"
etc. These would probably not bee too happy to receive an unexpected switch.
(I couldn't even switch between our cc and gcc if the ansi argument were
not "atomical" part of $CC: gcc doesn't understand -kansi, and our compiler
dislikes -ansi)

Just see it as a production environment improvement:
  * it breaks less often
  * it allows the possibility to easily compile apache with different
    compilation environments. Just call it like this:
      Make "CC=gcc -ansi"  # use ANSI mode with gcc
      Make "CC=cc -kansi"  # use ANSI mode with our compiler
      Make "CC=cc -Klp64"  # invoke the 64-bit compiler
      Make CC=c89          # the system's wrapper for "cc -D_XOPEN_SOURCE"
    (or env "CC=cc -Klp64" Configure to force 64-bit mode compiler)
  * it is 100% compatible (albeit not error compatible ;-) with the
    current 1.2.5 situation

You couldn't easily get the same flexibility if you insist on prohibiting
the use of more than one word for $(CC).

| S I E M E N S |  <>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

View raw message