From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] pgaccess 0.98 |
Date: | 1999-11-04 15:43:51 |
Message-ID: | 3821A9B7.1FBB1797@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The tricky part is that pgaccess must know the 'wish' path that is
> determined by configure, and the POSTGRESDIR path which comes from
> Makefile.global, so I had to create a Makefile.in, and a pgaccess.sh.
> Makefile.in is set a configure time, and pgaccess.sh is set at compile
> time. The final script pgaccess has hardcoded in it the path to wish,
> and the pgaccess directory inside the install directory.
Hmm. There is a common trick to finding wish (and presumably other
"shells") for a shell script; it involves an "exec" as the first
executable line of the script. Did this just recently. I'll look it up
when I get to work.
Your path must of course be set properly; is that not acceptable?
Can't we tolerate minor changes in wish version without
rebuilding/reinstalling from Postgres sources??
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-11-04 15:50:14 | Re: [HACKERS] sort on huge table |
Previous Message | Thomas Lockhart | 1999-11-04 15:35:17 | Re: Performance glitch in GetCurrentAbsoluteTime() |