Re: tkConfig.sh vs. ./configure - Mailing list pgsql-hackers

From Daniel Kalchev
Subject Re: tkConfig.sh vs. ./configure
Date
Msg-id 200112201729.TAA21723@dcave.digsys.bg
Whole thread Raw
In response to Re: tkConfig.sh vs. ./configure  (Peter Eisentraut <peter_e@gmx.net>)
List 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'
isrequired 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
pathreturned by `echo 'puts $auto_path' | wish`, which would indeed> give the right answer, but when I execute that,
wishalso 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




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Thoughts on the location of configuration files
Next
From: Karel Zak
Date:
Subject: Re: tkConfig.sh vs. ./configure