Politically correct way of building dhcp?

[Andrew Pollock]

On Tue, Jun 21, 2005 at 10:49:36PM +1000, Andrew Pollock wrote:
> Hi,
> 
> I notice that the DHCP software doesn't use GNU autoconf to build, and in
> fact I'm find it all a bit weird compared to other stuff I've worked with in
> the past.
> 
> What's the politically correct way of convincing it to use
> specific/additional compiler flags? Like I'd like to build it with -O2 -Wall
> for example.
> 
> If I go 'make CFLAGS="-O2 -Wall"' it seems to wipe out some -I's that would
> normally be added, which makes the build fall over.
> 
> Are there any plans to use GNU autoconf/automake etc down the track?
> 

I played with some other software that does use autoconf/automake, and it
appears that the anatomically correct way to influence the CFLAGS is at
./configure time, but as DHCP's ./configure isn't autoconf, adding a
"CFLAGS=blah" to the ./configure invocation achieves not a lot...