Not in PATH syndrome?

[Brian Inglis]

On 2026-01-12 03:41, J.H. vd Water via Cygwin wrote:
> Hi,
> 
> Please, help me jog my memory ...
> 
> I have Cygwin installed in e:/Cygwin and in e:/Cygwin2; there is no
> difference between the two, except for the topdir.
> 
> 1. Using Cygwin in e:/Cygwin2: <= TWO
> 
> @@ mount -p   # my prompt = '@@ '
> Prefix Type Flags
> /drv   user binmode

[The following mount is more compatible with Unix systems:
$ mount -p
Prefix              Type         Flags
/mnt                nouser       binmode
]

> PATH=/usr/bin:...
> 
> @@ PATH=/drv/e/Cygwin/bin:$PATH which --version # fails (retval 127)
> @@ ls /drv/e/Cygwin/bin/which*
> /drv/e/Cygwin/bin/which.exe
> 
> @@ PATH=$PATH:/drv/e/Cygwin/bin which --version
> GNU which v2.29 ...
> 
> ---
> Of course, the same thing happens while using Cygwin in e:/Cygwin
> 
> @@ mount -p
> Prefix Type Flags
> /drv   user binmode
> 
> PATH=/usr/bin:...
> 
> @@ PATH=/drv/e/Cygwin2/bin:$PATH which --version # fails (retval 127)
> @@ ls /drv/e/Cygwin2/bin/which*
> /drv/e/Cygwin2/bin/which.exe
> 
> @@ PATH=$PATH:/drv/e/Cygwin2/bin which --version
> GNU which v2.29 ...
> 
> Why does the invocation of the executable fail "if referred to outside
> the current installation ..., while the necessary dll's, libraries are
> present, or so it seems to me".
> 
> I seem to remember that Cygwin looks for the necessary libs in the lib
> directory, that is "peer" to the bin directory ...
> 
> Hope someone can shed some light here ...

Would be helpful in each case to see:

	$ cygpath -m /
	$ pwd
	$ cat -A <<< "$PATH"

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry