Why do we use Tcl's compiler and flags?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Why do we use Tcl's compiler and flags?
Date: 2001-05-11 23:49:56
Message-ID: Pine.LNX.4.30.0105120142201.757-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The only really interesting things that tclConfig.sh (and tkConfig.sh)
tells us are the names of various libraries. But those names can be used
portably with any compiler, so I don't see why we need to subscribe to the
whole deal. AFAICT, the rest (TCL_CC, TCL_SHLIB_SUFFIX, etc.) is merely a
help for people who don't know how to build shared libraries, but we do,
so we should use our own way.

Naah, don't tell me it breaks on HP-UX. Make it work... ;-)

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message G. Anthony Reina 2001-05-11 23:54:35 Addition to: Trouble with initdb when the #define NAMEDATALEN = 51
Previous Message G. Anthony Reina 2001-05-11 23:47:10 Trouble with initdb when the #define NAMEDATALEN = 51