public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Martin Wege <martin.l.wege@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Weird (path) problems with cygwin test release 3.5.0-0.384.g9939aa7d0945.x86_64 ...
Date: Mon, 14 Aug 2023 21:42:00 +0200	[thread overview]
Message-ID: <CANH4o6MvtFxqMM96ztECmX4zX+zwkoJ8ZmQPOw6cxg2zu7bDjw@mail.gmail.com> (raw)
In-Reply-To: <CAKAoaQnvSZDD6mitFsdD==aOi0n9h3JSAEiJo8QXCRAf58H_Sw@mail.gmail.com>

On Mon, Aug 14, 2023 at 7:30 PM Roland Mainz via Cygwin
<cygwin@cygwin.com> wrote:
>
> On Mon, Aug 14, 2023 at 6:25 PM Roland Mainz <roland.mainz@nrubsig.org> wrote:
> > 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:
> [snip]
> > > > 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
>
> It seems the issue can be reduced to this on  Cygwin
> 3.5.0-0.388.g1a646ad7970a.x86_64 - c++ with H:/path/.../x.cpp works,
> c++ with  /home/rmainz/path/.../x.cpp does not.
>
> This definitely *WORKED* in Cygwin 3.4.7:
>
> Example:
> ---- snip ----
> $ uname -a
> CYGWIN_NT-10.0-19045 WINGRENDEL01 3.5.0-0.388.g1a646ad7970a.x86_64
> 2023-08-11 14:14 UTC x86_64 Cygwin
>
> $ cat /etc/fstab
> # /etc/fstab
> #
> #    This file is read once by the first process in a Cygwin process tree.
> #    To pick up changes, restart all Cygwin processes.  For a description
> #    see https://cygwin.com/cygwin-ug-net/using.html#mount-table
>
> # This is default anyway:
> none /cygdrive cygdrive binary,posix=0,user 0 0
> H:      /home/rmainz    none    binary,posix=0,user     0       0
>
>
> $ mount -a
>
> $ /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/Dependencies/win/qt/qt_5_15_2/Tools/mingw810_64/bin/c++
> /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/RDE-Development/build_windows5/tmp/x.cpp
> c++.exe: error:
> /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/RDE-Development/build_windows5/tmp/x.cpp:
> No such file or directory
> c++.exe: fatal error: no input files
> compilation terminated.
>
> $ /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/Dependencies/win/qt/qt_5_15_2/Tools/mingw810_64/bin/c++
> H:/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/RDE-Development/build_windows5/tmp/x.cpp
>
> $ ./a
> Hello World!
> ---- snip ----
>
> /proc/cygwin/h/path/... does not work either...
>
> Does anyone have any idea what changed between Cygwin 3.4.7 and Cygwin
> 3.5.0-0.388.g1a646ad7970a.x86_64 in this case ?
>

Maybe MinGW compat is broken in 3.5.0-0.388.g1a646ad7970a?

Thanks,
Martin

  reply	other threads:[~2023-08-14 19:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a0f1e420-ae48-49a3-9300-c56f1948ad9b.8d485f54-9f47-42b0-bdcb-9635fbf663c3.6697971f-86bc-49dc-8072-c37095eed858@emailsignatures365.codetwo.com>
     [not found] ` <a0f1e420-ae48-49a3-9300-c56f1948ad9b.93e247b8-206a-49dd-b71c-9240681180cb.7748cdc6-d053-4197-9372-3b4751ae3949@emailsignatures365.codetwo.com>
     [not found]   ` <a0f1e420-ae48-49a3-9300-c56f1948ad9b.e52b7f5f-5a09-4346-99f8-a6591191169c.10af45d3-4cfc-48f7-a293-b6d9fa78cdd1@emailsignatures365.codetwo.com>
2023-08-11 13:36     ` Mainz, Roland
2023-08-14 10:21       ` Corinna Vinschen
2023-08-14 16:25         ` Roland Mainz
2023-08-14 17:29           ` Roland Mainz
2023-08-14 19:42             ` Martin Wege [this message]
2023-08-14 20:57               ` Corinna Vinschen
2023-08-14 20:56             ` Corinna Vinschen
2023-08-17 18:49               ` How does Cygwin detect MSFT NFSv3 file system? " Martin Wege
2023-08-18  8:44                 ` Corinna Vinschen
2023-08-18 13:09                   ` Cygwin pathconf() query filesystem kernel data? " Martin Wege
2023-08-19 17:50                     ` Brian Inglis
2023-08-21 12:03                       ` Martin Wege
2023-08-21 22:07                         ` Brian Inglis
2023-08-24 16:27                           ` Martin Wege

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANH4o6MvtFxqMM96ztECmX4zX+zwkoJ8ZmQPOw6cxg2zu7bDjw@mail.gmail.com \
    --to=martin.l.wege@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).