| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Search for version-numbered tclsh? |
| Date: | 2008-07-27 03:03:51 |
| Message-ID: | 488BE597.5000802@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I notice that the recent patch to enforce finding a tclsh broke a couple
> of buildfarm machines. On reflection, I remember that recent Tcl
> versions don't automatically create a 'tclsh' symlink, only a
> version-numbered program such as 'tclsh8.3'. I suggest that maybe we
> ought to allow that without forcing people to set TCLSH manually.
> Perhaps have PGAC_PATH_TCLSH do
>
> AC_PATH_PROGS(TCLSH, [tclsh tcl tclsh8.5 tclsh8.4 tclsh8.3])
>
> or some such.
>
>
>
Bleah. I guess we'll have to.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ramya Chandrasekar | 2008-07-27 03:45:30 | Re: Regd: TODO Item : Have EXPLAIN ANALYZE issue NOTICE messages ... |
| Previous Message | daveg | 2008-07-27 01:33:51 | Re: pg_dump additional options for performance |