Thread

1. Re: [HACKERS] Configure problem, redux (was Re: TCL installation troubles)

   Bruce Momjian <maillist@candle.pha.pa.us> — 1998-10-27T23:36:31Z

   [Charset iso-8859-1 unsupported, filtering to ASCII...]
   > > We do insist on gmake.  Can't compile without it.
   > 
   > Then can we use the gmake 'include' instead of the configure *.in files?
   > 
   > > Like the term "sed monsters"?
   > 
   > Yes :)
   
   So you output all defines into a single file, and include that in every
   Makefile.  That is interesting.
   
   
   -- 
     Bruce Momjian                        |  http://www.op.net/~candle
     maillist@candle.pha.pa.us            |  (610) 853-3000
     +  If your life is a hard drive,     |  830 Blythe Avenue
     +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
   
   

2. Re: [HACKERS] Configure problem, redux (was Re: TCL installation troubles)

   Brook Milligan <brook@trillium.nmsu.edu> — 1998-10-28T00:11:44Z

      So you output all defines into a single file, and include that in every
      Makefile.  That is interesting.
   
   I guess this isn't too clear.  Here is what I am trying to advocate:
   
   configure output -> Makefile.global + config.h substituting as
   appropriate.
   
   all Makefiles include Makefile.global (which includes Makefile.custom
   if it exists? and other things like the shared library Makefile).
   
   one of the included Makefiles has a generic rule for *.sql.in -> *.sql
   that depends on Makefile.global also.
   
   If a directory has *.sql.in it will automatically be converted with
   the correct substitutions; after all, the substitution is the same in
   each case so one rule suffices (even if several variables need
   substituting); note that sed will not substitute for patterns not
   found in individual *.sql.in files even if the general rule says
   otherwise.
   
   Same mechanism for any other general substitutions, if necessary
   (probably not).
   
   Makefiles do not have any sed monsters, just one rule involving sed in
   a generally included Makefile.sed_monsters. :)  The individual
   *.sql.in files would be written in exactly the same way as if
   configure was doing the substitution.
   
   All configure information is in one place (Makefile.global and
   config.h).  All dependencies do the right thing, even if those are
   changed post-configure.
   
   Cheers,
   Brook
   
   

3. Re: [HACKERS] Configure problem, redux (was Re: TCL installation troubles)

   Marc G. Fournier <scrappy@hub.org> — 1998-10-28T02:04:28Z

   On Tue, 27 Oct 1998, Bruce Momjian wrote:
   
   > [Charset iso-8859-1 unsupported, filtering to ASCII...]
   > > > We do insist on gmake.  Can't compile without it.
   > > 
   > > Then can we use the gmake 'include' instead of the configure *.in files?
   > > 
   > > > Like the term "sed monsters"?
   > > 
   > > Yes :)
   > 
   > So you output all defines into a single file, and include that in every
   > Makefile.  That is interesting.
   
   	Technically, we are doing that now with Makefile.global ... its
   included in every Makefile in the system, and has CFLAGS and such defined
   in it.  It wouldn't be unreasonable to have a MISSING_OBJ= put into
   Makefile.global, and remove the Makefile.in in the backend/ports
   directory... *shrug*
   
   Marc G. Fournier                                
   Systems Administrator @ hub.org 
   primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 
   
   
   

4. Re: [HACKERS] Configure problem, redux (was Re: TCL installation troubles)

   Bruce Momjian <maillist@candle.pha.pa.us> — 1998-10-28T02:23:27Z

   > 	Technically, we are doing that now with Makefile.global ... its
   > included in every Makefile in the system, and has CFLAGS and such defined
   > in it.  It wouldn't be unreasonable to have a MISSING_OBJ= put into
   > Makefile.global, and remove the Makefile.in in the backend/ports
   > directory... *shrug*
   
   Yes.  I think that kind of thing would make sense, and would allow
   Makefile.custom to over-rule it, though that is more of an affect rather
   than a feature I would promote.  configure flags should do most of the
   work.
   
   
   -- 
     Bruce Momjian                        |  http://www.op.net/~candle
     maillist@candle.pha.pa.us            |  (610) 853-3000
     +  If your life is a hard drive,     |  830 Blythe Avenue
     +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026