httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: [PATCH] lets do 1.2.5
Date Thu, 08 Jan 1998 13:07:46 GMT
Jim Jagielski wrote:
> 
> Martin Kraemer wrote:
> > 
> > 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
> > 
> > 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)
> > 
> 
> Is '-kansi' a flag?
> 
> If the answer is yes, then it belongs in a "flags" variable.
> 

In any case, I'm rescending(sp?) my -1 vote... I still think that
we should keep things clean and including flags/options under
CC just seems wrong to me (although, truth be told, sometimes
it _is_ useful). Still, I would prefer it being done right and
logically rather than "flexibly" because that opens the door
to too many crazy things :-)

AFAIK, the problem only exists in the 1.2.5/6 tree when compiling
the regex package...
-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"

Mime
View raw message