Re: tkConfig.sh vs. ./configure

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:48:16
Message-ID: 20011220194816.D25755@zf.jcu.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 20, 2001 at 01:29:42PM -0500, Tom Lane wrote:
> 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

I agree, but change of this is probably out of our possibility...

> broken. How are we supposed to guess where they are hiding these files,
> short of searching the entire filesystem?

I see debian/rule (build system) of tkdvi package and here is

./configure --with-tcl=/usr/lib/tcl8.3 \
--with-tk=/usr/lib/tk8.3 \
--with-tclinclude=/usr/include/tcl8.3 \
--with-tkinclude=/usr/include/tcl8.3

Karel

--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/

C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-12-20 21:21:25 Re: SunOS patch for memcmp()
Previous Message Bear Giles 2001-12-20 18:39:45 Wishlist: TLS, PKI