cygwish80 problem

[Steven N. Hirsch]

I have more information on this problem.

The 1.0 CD version of cygwish80 cannot correctly "source" any file whose
patch traverses a Cygwin mount point.

For example, here is my mount scheme:

Device              Directory           Type         Flags
c:\cygwin           /                   user         textmode
f:\local            /usr/local          user         binmode
f:\X11R6            /usr/X11R6          user         binmode
c:                  /c                  user         textmode
h:                  /home/hirsch        user         binmode
e:                  /usr/src            user         binmode


If I create a file called "test.tcl" containing:

puts "Hello, world!"

and place it in "/", cygwish80 can load it by:

% source "/test.tcl"

However, if the same file is placed in /usr/local/bin, it must be sourced
by doing:

% source "f:/local/bin/test.tcl"

The cygwin path "/usr/local/bin/test.tcl" results in "..file not found".

If this behavior is not a bug, I'd be interested in the rationale for it.
The cygwish80 in B20.1 can correctly resolve cygwin paths and does not
require the above workaround.

Regards,

Steve





> All,
> 
> The version of cygwish80 shipped with the Cygwin 1.0 CD does not properly
> recognize POSIX paths for all functions.  It is unable to properly start a
> Tcl/Tk program with 
> 
> #!/bin/cygwish80 -f
> 
> as the first line.  The shell starts cygwish, which then complains that
> there is no such file as "/usr/local/bin/myscript".  In fact, the file
> does exist.
> 
> If I cd into /usr/local/bin and do
> 
> $ cygwish80 ./myscript
> 
> It will execute the script until it gets to a construct like:
> 
> if [info exists /some/file] {
> 	source /some/file
> }
> 
> The 'info exists' test comes back true, but the next line dies with the
> error that '/some/file' does not exist.
> 
> I have duplicated this misbehavior at the cygwish80 shell prompt.  Files
> that can be listed and recognized by 'info exists' cannot be loaded with
> the 'source' command.
> 
> For a reality check, I moved cygwish80.exe and its DLLs aside and copied
> the like-named files from B20.1 in their place.  No more problems.
> 
> Am I the only one seeing this?
> 
> And, yes, I tried endless experiments with setting binmode, mount options,
> etc., etc. - to no avail.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com