Re: tkConfig.sh vs. ./configure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tkConfig.sh vs. ./configure
Date: 2001-12-20 18:29:42
Message-ID: 9711.1008872982@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Karel Zak <zakkr(at)zf(dot)jcu(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bear Giles 2001-12-20 18:39:45 Wishlist: TLS, PKI
Previous Message Karel Zak 2001-12-20 18:16:26 -lperl not checked