Prev: running a script on linux
Next: ANNOUNCE: Tcl Windows API 2.2.3 released
From: Mike on 30 Dec 2009 16:14
Greetings
I am trying to install a software package (Rnaviz) that depends on
Tcl. The configure script output:
checking for Tcl configuration... found /usr/local/lib/tclConfig.sh
checking for existence of /usr/local/lib/tclConfig.sh... loading
checking for Tcl public headers... /usr/local/include
checking for building with threads... no (default)
checking how to build libraries... shared
checking for build with symbols... no
checking how to build libraries... stubs
checking for tclsh... configure: error: No tclsh found in PATH: NONE/
bin NONE/bin /usr/local/lib /usr/local/lib/../bin /sw/bin/tclsh /usr/
local/arb/bin /opt/local/bin /opt/local/sbin /sw/bin /sw/sbin /
Applications/vmatch.distribution /usr/local/mysql/bin /usr/biobin /usr/
local/wublast /usr/ebiotools/staden/macosx-bin /usr/ebiotools/staden/
macosx-bin /usr/local/bin /bin /sbin /usr/bin /usr/sbin /usr/ebiotools/
ncbi/bin /usr/ebiotools/bin /usr/ebiotools/ncbi/bin /usr/ebiotools/
bin /usr/X11R6/bin
Macintosh-8:/Applications/Rnaviz/build mmuratet$ /usr/local/bin/tclsh
% exit
It appears to find all the dependencies it needs up to tclsh where it
fails. tclsh exists in /usr/local/bin which it says it searched. I
have never seen such a problem and I am at a loss to know where to
search for the real problem. Can anyone offer any suggestions?
Thanks
Mike
From: Konstantin Khomoutov on 31 Dec 2009 05:23
On Dec 31, 12:14 am, Mike <mmura...(a)hudsonalpha.org> wrote:

[...]
> checking for tclsh... configure: error: No tclsh found in PATH:
[...]
> Macintosh-8:/Applications/Rnaviz/build mmuratet$ /usr/local/bin/tclsh
> % exit
> It appears to find all the dependencies it needs up to tclsh where it
> fails. tclsh exists in /usr/local/bin which it says it searched. I
> have never seen such a problem and I am at a loss to know where to
> search for the real problem. Can anyone offer any suggestions?

First try to read config.log file which is re-written each time ./
configure runs -- it might have clues on what actual command was run
(and failed).
If it does not give a hint on what gone wrong, resort to reading ./
configure itself as it's just a Unix shell script with no unusual
dependencies.
 | 
Pages: 1
Prev: running a script on linux
Next: ANNOUNCE: Tcl Windows API 2.2.3 released