httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <>
Subject Re: Yet more patches
Date Mon, 12 Feb 1996 10:40:32 GMT
> >Re: Makefile
> >
> >> >Can you explain how this is better than the existing method?
> >> >Evertime I get a new Apache, I have to edit 2 files instead of 1.
> >> 
> >> The advantage is a reduction in the amount of files you have to read
> >> and edit. You will almost never have to edit the Makefile, and
> >> you don't have to search through a list of #defines to find your OS.
> >> 
> >> >I set LFLAGS in the Makefile, but it got ignored. I worked out how
> >> >to fix that but it's a pain in the ass..
> >> 
> >> I've fixed this in; you can set LDFLAGS (instead of
> >> LFLAGS, which is conventionally for lex) in Makefile or on the make
> >> command line;
> >> e.g. make solaris CFLAGS=-g LDFLAGS=-g
> >
> >That's a real pain in the ass. Makes it difficult to remember the flags
> >and calls needed to rerun make. The existing method is easier for the
> >likes of me since I only need to keep moving my "Configuration" file from
> >the last release into the new.
> >
> >It would appear that a compromise is called for.
> What would you prefer? Would you like to be able to put your default
> OS in the Configuration file?
> I do think that having the user have to search through all the CFLAGS
> lines is a bit cacky. Maybe all this should go into the Configure script?

Several things use a scheme where there is a line in a file somewhere for
each OS like:


which is then used by a script to set up all the relevant bits. Would this
help? The OS is usually autodetected, too, using uname, mostly.



Ben Laurie                  Phone: +44 (181) 994 6435
Freelance Consultant        Fax:   +44 (181) 994 6472
and Technical Director      Email:
A.L. Digital Ltd,           URL:
London, England.

View raw message