>>>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'?
pgsql-hackers by date
|Next:||From: Karel Zak||Date: 2001-12-20 18:00:20|
|Subject: Re: tkConfig.sh vs. ./configure|
|Previous:||From: Peter Eisentraut||Date: 2001-12-20 17:13:30|
|Subject: Re: Thoughts on the location of configuration files |