| From: | Daniel Kalchev <daniel(at)digsys(dot)bg> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tkConfig.sh vs. ./configure |
| Date: | 2001-12-20 17:29:35 |
| Message-ID: | 200112201729.TAA21723@dcave.digsys.bg |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>Peter Eisentraut said:
> Karel Zak writes:
>
> > [--cut--]
> > checking for tclsh... /usr/bin/tclsh
> > checking for tclConfig.sh... /usr/lib/tcl8.3/tclConfig.sh
> > checking for tkConfig.sh... no
> > configure: error: file `tkConfig.sh' is required for Tk
> >
> > ..hmm, I try:
> >
> > $ ls -la /usr/lib/tk8.3/tkConfig.sh
> > -rw-r--r-- 1 root root 3194 Oct 27 10:00
> > /usr/lib/tk8.3/tkConfig.sh
>
> The tclConfig.sh file is found by looking into the path returned by `echo
> 'puts $auto_path' | tclsh`.
>
> Then theoretically, the tkConfig.sh file should be found by looking into
> the path returned by `echo 'puts $auto_path' | wish`, which would indeed
> give the right answer, but when I execute that, wish also opens a window
> on my desktop and hangs, which is not exactly what you'd want during a
> configure run.
What about `echo 'puts $auto_path; exit' | wish'?
Daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2001-12-20 18:00:20 | Re: tkConfig.sh vs. ./configure |
| Previous Message | Peter Eisentraut | 2001-12-20 17:13:30 | Re: Thoughts on the location of configuration files |