Mail Archives: cygwin/2005/08/16/12:29:32
Hi, Is this issue good enough for a bug? I'm only seeing this when
running the script on a mounted drive.
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Maloney, Michael
Sent: Monday, August 15, 2005 3:21 PM
To: cygwin AT cygwin DOT com
Subject: RE: problem running tcl/expect when it lives remotely
Looks like the script cannot find its-self. It's failing at:
exec $ARTS_EXPECT -n -N "$0" "$@"
Log:
$ P:/lemon/automation/WAM/FIM/FARTS/utils/run_remote_cmds
+ TCL_LIBRARY=C:/cygwin/usr/share/tcl8.4/init.tcl
+ export TCL_LIBRARY
+ LD_LIBRARY_PATH=C:/cygwin/lib/libtcl84.a
+ export LD_LIBRARY_PATH
+ C:/cygwin/bin/expect -n -N
P:/lemon/automation/WAM/FIM/FARTS/utils/run_remote_cmds
couldn't read file
"P:/lemon/automation/WAM/FIM/FARTS/utils/run_remote_cmds": no such file
or directory
This doesn't seem right at all.
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Maloney, Michael
Sent: Monday, August 15, 2005 1:34 PM
To: cygwin AT cygwin DOT com
Subject: problem running tcl/expect when it lives remotely
Version being used: 1.5.17(0.129/4/2)
OS; Windows 2003
I am trying to get my scripts which live on a remote server running on a
test box running Windows 2003. The history is when I had all of this
running locally (all scripts on local box, instead of remote using "net
use...") it was working fine. Now when ever I execute a tcl script, I
get the following error:
HELLO WORLD!!!!!!!!!!!!!
couldn't read file
"P:/lemon/automation/WAM/FIM/FARTS/utils/run_remote_cmds": no such file
or directory
As you can see, my hello world script is being executed (it's a regular
bourne shell script). So that tells me it's just the tcl scripts that
"cannot be found". I can see the files on the filesystem:
$ ls -l P:/lemon/automation/WAM/FIM/FARTS/utils/run_remote_cmds
-rwxr-xr-x 1 rsas None 22814 Aug 15 2005
P:/lemon/automation/WAM/FIM/FARTS/utils/run_remote_cmds
Here's what I'm using as far as environment:
SET: ARTS_PERL=$ARTS_ROOT/tools/aperl/Perl/bin/perl
SET: ARTS_TCL_LIBRARY=$HOMEDRIVE/cygwin/usr/share/tcl8.4/init.tcl
SET: ARTS_TCL_LD_LIBRARY_PATH=$HOMEDRIVE/cygwin/lib/libtcl84.a
SET: ARTS_EXPECT=$HOMEDRIVE/cygwin/bin/expect
My tcl scripts just reference these variables at execution time:
# \
TCL_LIBRARY=$ARTS_TCL_LIBRARY; export TCL_LIBRARY
# \
LD_LIBRARY_PATH=$ARTS_TCL_LD_LIBRARY_PATH; export LD_LIBRARY_PATH
# \
exec $ARTS_EXPECT -n -N "$0" "$@"
# I tried using Active State TCL and had similar issues so I'm assuming
this is a cygwin issue and not tcl.
# I tried using alternate cygpaths: /cygdrive/p/.... instead of P:/...
Nothing seems to help. Any ideas to what this is?
Thanks,
Mike
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -