From: Mike T. <mi...@br...> - 2002-08-30 07:25:43
|
Hi Earnie. The following sh script: =================================== #!/bin/sh exec "g:/gclm/lib/gcl-2.5.0/unixport/saved_gcl.exe" \ -dir "g:/gclm/lib/gcl-2.5.0/unixport/" \ -libdir "g:/gclm/lib/gcl-2.5.0/" \ -eval '(setq si::*allow-gzipped-file* t)' \ "$@" =================================== when executed from "/c/cvs/gcl" gives the following result under MSYS 1.08: =================================== $ /g/gclm/bin/gcl /g/gclm/bin/gcl: /c/cvs/gcl/g:/gclm/lib/gcl-2.5.0/unixport/saved_gcl.exe: No such file or directory /g/gclm/bin/gcl: exec: /c/cvs/gcl/g:/gclm/lib/gcl-2.5.0/unixport/saved_gcl.exe: cannot execute: No such file or directory =================================== That is, it adds the value of `pwd` onto the beginning of executable names in the shell script before running them. When the executable paths in the script are in MSYS canonical format eg "/g/gclm/lib/gcl-2.5.0/unixport/saved_gcl.exe" rather than the Mingw colon format, the script works as expected. Cheers Mike Thomas. |