Re: tkConfig.sh vs. ./configure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tkConfig.sh vs. ./configure
Date
Msg-id 9711.1008872982@sss.pgh.pa.us
Whole thread Raw
In response to Re: tkConfig.sh vs. ./configure  (Karel Zak <zakkr@zf.jcu.cz>)
List pgsql-hackers
Karel Zak <zakkr@zf.jcu.cz> writes:
>  The other thing is that tcl*.h and tk.h files are in /usr/inlude/tcl8.3,

There's not a darn thing we can do about that, because tclConfig.sh
doesn't tell exactly where the include files are (which is Tcl's
oversight, but we're stuck with it).  We could try "$TCL_PREFIX/include",
which'd work on standard Tcl install layouts, but Debian has evidently
managed to botch that too.

>  (yes, I know --includedir= etc., but it's _standard_ latest unstable
>   Debian...)  

It may be Debian's idea of standard, but that doesn't mean it's not
broken.  How are we supposed to guess where they are hiding these files,
short of searching the entire filesystem?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Don Baccus
Date:
Subject: Recursive SQL functions ...
Next
From: Tom Lane
Date:
Subject: Re: tkConfig.sh vs. ./configure