On 2025-05-12 10:34, Aurélien Couderc via Cygwin wrote:
Cygwin:
Using Cygwin install on network share in CI fails.
This seems to be a recent regression, as this was working a year before.
Now on Windows 10 with Cygwin 3.6.1 it fails with error 127.
That can mean a missing DLL function entry.
Test case, using cmd.exe:
Add some commands that show the current situation before and after each command,
and post the actual output from the script and status checking commands.
Under CMD you can display %ERRORLEVEL% and use DIR:
$ CMD /C ECHO %ERRORLEVEL%
0
$ ECHO %ERRORLEVEL%
%ERRORLEVEL%
curl --remote-name "https://www.cygwin.com/setup-x86_64.exe";
.\setup-x86_64.exe -q --no-write-registry --no-admin --root %cd%
--no-desktop --site "https://mirrors.kernel.org/sourceware/cygwin";
.\bin\bash.exe -c 'ls -l ; echo $?'
Expected result:
ls -l output, with exit code 0
Actual result:
exit code 127
I am not good in debugging Cygwin, but it looks like .\bin\cygwin1.dll
just gives up at some point.
It likely means require DLLs are not in PATH and/or ls or Cygwin could not load
them, as bash would issue a diagnostic:
$ xyzzy; echo $?
-bash: xyzzy: command not found
127
I personally think this should be diagnosed with a DLL not found from Cygwin or
Windows!
Although the call used may only be testing if the DLL is available, not actually
loading it.
Maybe add running the failing command under strace to diagnose which DLL or
entry is causing the failure.
--
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
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
