Thread

  1. Re: [HACKERS] PostgreSQL v6.4 BETA2 ...

    Billy G. Allie <bill.allie@mug.org> — 1998-10-14T02:11:15Z

    I will be posting a configure.in tonight with further clean ups to the TCL/TK 
    configuration.  TCL/TK compile information will now be obtained from the 
    tclConfig.sh and tkConfig.sh, without having to have a list of different 
    versions of TCL and TK to search for.
    
    Two item I would like to bring up for discussion is:
    
    1.  Currently TCL/TK support is disabled if TCL is present, but TK is not. This
        is not a good thing because the PL/tcl language is only dependant on TCL,
        not TK.  Also pgtclsh only requires TCL.  I propose changing configure so
        that TCL and TK support are seperate and the TCL dependant parts of the
        postgreSQL distribution will still build even if TK is not present.
    
    2.  There is currently duplicate Makefile.tcldefs.  I propose create a
        Makefile.tcldefs and Makefile.tkdefs at the same directory level as
        Makefile.global and have any Makefile that needs them include them from
        that location.  This would then become the 'standard' for compiling TCL
        and TK based packages in the postgreSQL distribution.
    
    Any comments and/or concerns?
    -- 
    ____       | Billy G. Allie    | Domain....: Bill.Allie@mug.org
    |  /|      | 7436 Hartwell     | Compuserve: 76337,2061
    |-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie@email.msn.com
    |/  |LLIE  | (313) 582-1540    | 
    
    
    
    
  2. Re: [HACKERS] PostgreSQL v6.4 BETA2 ...

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-10-14T02:43:43Z

    > I will be posting a configure.in tonight with further clean ups to the TCL/TK 
    > configuration.  TCL/TK compile information will now be obtained from the 
    > tclConfig.sh and tkConfig.sh, without having to have a list of different 
    > versions of TCL and TK to search for.
    > 
    > Two item I would like to bring up for discussion is:
    > 
    > 1.  Currently TCL/TK support is disabled if TCL is present, but TK is not. This
    >     is not a good thing because the PL/tcl language is only dependant on TCL,
    >     not TK.  Also pgtclsh only requires TCL.  I propose changing configure so
    >     that TCL and TK support are seperate and the TCL dependant parts of the
    >     postgreSQL distribution will still build even if TK is not present.
    > 
    > 2.  There is currently duplicate Makefile.tcldefs.  I propose create a
    >     Makefile.tcldefs and Makefile.tkdefs at the same directory level as
    >     Makefile.global and have any Makefile that needs them include them from
    >     that location.  This would then become the 'standard' for compiling TCL
    >     and TK based packages in the postgreSQL distribution.
    > 
    > Any comments and/or concerns?
    
    Be aware I removed the TCL_LIB, ... stuff from configure.in this
    morning.  That was the old stuff, and your new stuff made it
    unnecessary.
    
    
    -- 
      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
    
    
    
  3. Re: [HACKERS] PostgreSQL v6.4 BETA2 ...

    Marc G. Fournier <scrappy@hub.org> — 1998-10-14T03:18:32Z

    On Tue, 13 Oct 1998, Billy G. Allie wrote:
    
    > I will be posting a configure.in tonight with further clean ups to the TCL/TK 
    > configuration.  TCL/TK compile information will now be obtained from the 
    > tclConfig.sh and tkConfig.sh, without having to have a list of different 
    > versions of TCL and TK to search for.
    > 
    > Two item I would like to bring up for discussion is:
    > 
    > 1.  Currently TCL/TK support is disabled if TCL is present, but TK is not. This
    >     is not a good thing because the PL/tcl language is only dependant on TCL,
    >     not TK.  Also pgtclsh only requires TCL.  I propose changing configure so
    >     that TCL and TK support are seperate and the TCL dependant parts of the
    >     postgreSQL distribution will still build even if TK is not present.
    > 
    > 2.  There is currently duplicate Makefile.tcldefs.  I propose create a
    >     Makefile.tcldefs and Makefile.tkdefs at the same directory level as
    >     Makefile.global and have any Makefile that needs them include them from
    >     that location.  This would then become the 'standard' for compiling TCL
    >     and TK based packages in the postgreSQL distribution.
    > 
    > Any comments and/or concerns?
    > -- 
    
    	These changes sound great for post-v6.4...
    
    Marc G. Fournier                               scrappy@hub.org
    Systems Administrator @ hub.org                    
    scrappy@{postgresql|isc}.org                       ICQ#7615664
    
    
    
  4. Re: [HACKERS] PostgreSQL v6.4 BETA2 ...

    Brook Milligan <brook@trillium.nmsu.edu> — 1998-10-14T14:44:53Z

       I will be posting a configure.in tonight with further clean ups to the TCL/TK 
       configuration.  TCL/TK compile information will now be obtained from the 
       tclConfig.sh and tkConfig.sh, without having to have a list of different 
       versions of TCL and TK to search for.
    
    These ideas sound great, but I don't understand one thing.
    
    How do you locate the *Config.sh scripts without looking in a bunch of
    directories until you find them?
    
    Unless there is a general means of finding these which 1) doesn't
    involve checking directories associated with different versions of
    tcl/tk, and 2) does allow for the possibility that tcl/tk may not be
    installed in a particular filesystem (/usr/local, for example), I
    strongly recommend keeping the part of configure that searches for the
    location of tcl/tk.  Perhaps we don't need to store the location of
    include/library files based on the configure script, but I think we do
    need to use essentially the same mechanism to find the *Config.sh
    scripts.
    
    Cheers,
    Brook