httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: apache/linux modules
Date Wed, 04 Feb 1998 02:36:25 GMT
Yep... as I've said, all this is _possible_ with
autoconf; but most of the time it ain't. And for every
"work-around" that can be suggested for ./configure, one
can just as easily be made for ./Configure.
Dean Gaudet wrote:
> 
> cat  >>Makefile.in <<EOF
> # configure depends on configure.in
> 
> configure: configure.in
> 	autoconf
> EOF
> 
> staleness dealt with. 
> 
> Dean
> 
> On Tue, 3 Feb 1998, Jim Jagielski wrote:
> 
> > Dean Gaudet wrote:
> > > 
> > > If you remember my example it was "I want to change a Makefile".  There's
> > > no reason to do all the work again.
> > 
> > Yes... If you want to rebuild a Makefile then yep, Configure does
> > it all over again. If you compare apples to apples, I'm sure
> > Configure comes out ahead.
> > 
> > > 
> > > Yes, config.status is a cache.  Since when are caches bad?  I'm sure you
> > > enjoy the disk cache on your system, and the L2 and L1 caches on your CPU.
> > > 
> > 
> > Sure do... but all implementations that use caches have to worry
> > about their staleness. ./config.status doesn't.
> > -- 
> > ====================================================================
> >       Jim Jagielski            |       jaguNET Access Services
> >      jim@jaguNET.com           |       http://www.jaguNET.com/
> >             "Look at me! I'm wearing a cardboard belt!"
> > 
> 
> 


-- 
====================================================================
      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