Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...

[Roland Mainz <roland.mainz@nrubsig.org>]

On Mon, Aug 14, 2023 at 12:21 PM Corinna Vinschen via Cygwin
<cygwin@cygwin.com> wrote:
>
> On Aug 11 13:36, Mainz, Roland via Cygwin wrote:
> > Hi!
> >
> > ----
> >
> > Cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 has some weird
> > path problems with network filesystems on Windows 10. Previous stable
> > version of Cygwin (4.7.x ?) worked fine.
>
> 3.4.7

Autsch. My mistake... ;-/

> > In our case we have a project with both custom binaries and sources
> > both hosted on the filesystem as /home/rmainz/ (i.e. filesystem
> > mounted on H:, and then bind mount to /home/rmainz).
> >
> > After updating Cygwin to 3.5.0-0.384.g9939aa7d0945.x86_64 the build
> > now fails *IF* I access the binaries with their full absolute path AND
> > the sources with their absolute path:
> > ---- snip ----
> > $ cd /home/rmainz/tmp/try10_rde_new_rds/RDE-Development/build_windows4/tmp
> > $ ls -l x.cpp
> > -rw-r--r-- 1 rmainz rovdevel 110 Aug 11 15:32 x.cpp
> > $ /home/rmainz/tmp/try10_rde_new_rds/Dependencies/win/qt/qt_5_15_2/Tools/mingw810_64/bin/c++ $PWD/x.cpp
> > c++.exe: error: /home/rmainz/tmp/try10_rde_new_rds/RDE-Development/build_windows4/tmp/x.cpp: No such file or directory
> > c++.exe: fatal error: no input files
> > compilation terminated.
> > ---- snip ----
>
> I can't reproduce this:
>
> $ net use H: <blah>

Is <blah> Samba, CIFS or NFS ?

> $ mount -o exec H: /home/rmainz
> $ cd /home/rmainz/tmp
> $ cp /bin/cat.exe .
> $ mkdir baz
> $ echo foo > baz/bar
> $ /home/rmainz/tmp/cat $PWD/baz/bar
> foo

Grumpf... ;-(

... I'm still seeing this problem.
The sources we are building are proprietary (sorry), but I can
reproduce this with both CITI's NFSv4.1 and Windows 10 builtin NFSv3
clients.

Setup for Windows's NFSv3 client on Cygwin is simple:
1. Install Windows 10 builtin NFSv3 client via "Programs&Features" (I
think there is a way to do that in a scripted way, but I still didn't
had time to figure that out)

2. Export NFSv3 directory 10.49.20.131:/export/home/rmainz (rmainz has
uid=1616, gid=1616) on a Linux NFS-Server (RHEL, Debian etc.)

3. Mount NFSv3 filesystem in Windows 10 in a Cygwin terminal, with
default user uid=1616, gid=1616 like this:
---- snip ----
$ regtool -i -s set
'/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/ClientForNFS/CurrentVersion/Default/AnonymousUID'
1616
$ regtool -i -s set
'/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/ClientForNFS/CurrentVersion/Default/AnonymousGID'
1616
$ /cygdrive/c/Windows/system32/mount -o anon
'\\10.49.20.131\export\home\rmainz' H:
---- snip ----

4. After that I started building our sources with Cygwin 3.4.7
(works), then closed all Cygwin windows etc., and installed Cygwin
3.5.0-0.388.g1a646ad7970a.x86_64 (reboot or not reboot - doesn't
matter). After that the build fails.

- See https://rovema.kpaste.net/e5774d8077 build log on Cygwin 3.4.7,
which works without problems
- See https://rovema.kpaste.net/1a3b98e0b for the build failure on
Cygwin 3.5.0-0.388.g1a646ad7970a.x86_64
- The horrifying abdomination ("buildrdecygwin.bash") used to build
the mess can be found at https://rovema.kpaste.net/e98be

----

Bye,
Roland
-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz@nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)