DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 54CHiSSq1048878 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 54CHiSSq1048878 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=GPA3FhEi X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 07B593858C48 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1747071867; bh=J0SUNbm5dX/WHN8+BbNh1lpuI2nAU+wGRuK2hX97SaY=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=GPA3FhEi5DXBKPxckS8yW/pipsml8cVH/qeTwhui6kW4BYzqJSnGV6zp0X5X7NCju tOQPao6H/efJ9Ea4Pu44xGUuCzQHWybcyRuTfDaPHSDPZ93oi7ck1VBXHEwjOboZhm w5BW6ejRySzzuEUUnAlhNE/F1RysIuT7MHu2hgmo= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 73EF43858D1E ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 73EF43858D1E ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1747071806; cv=none; b=KrXg57c8oTZttoxrNemoPXXIgu/vSiMpw63FBEdDhVwAN8nzNcLImh2Q11FSEGXxnyKq5EutqekSumec4Gz27oi2Rn5BBiby7MVagF5B9odsucF1yMyXQprZaIs+Mv6VDumUiFFvEcypu2TDRy6Uz0NlCdkIlO7ucn0VDRGll0M= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1747071806; c=relaxed/simple; bh=ovV0grgojNnlYIc4+MP/Q6v+Uecx2W6aSbeNUXJBfOs=; h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature; b=VE/NNqNsIOCy3hWSxSt75VjfJsIbJm1cEz7h8zYIM/yD6Mfpjn/Ek/wycVF18nqPGrHb9/FIYnhN5Z+sZAZIx0BOFHXzuuZWLSHQvq9Kv7iaz8QzJv0+j5izNiNFp/hr8gQGQ/U6nzZgENR88kCGmRA4b7QoPRAAVWgZRU6QVfM= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 73EF43858D1E Message-ID: <6ec5c987-b2ff-421d-b8f4-8b1ee7dca29c@SystematicSW.ab.ca> Date: Mon, 12 May 2025 11:43:23 -0600 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Using Cygwin installation on network share in CI fails Content-Language: en-CA To: cygwin AT cygwin DOT com References: Organization: Systematic Software In-Reply-To: X-Rspamd-Queue-Id: 44D2F80009 X-Rspamd-Server: rspamout05 X-Stat-Signature: kiwb5smxwyp8hztbcgqen1sw34abhd6n X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX1/7n7BCNUQJXJqGgwS9i0t3CwmYtCVq6Ts= X-HE-Tag: 1747071804-810548 X-HE-Meta: U2FsdGVkX19q+rDK5hqiAptsiggsqDPuxUT/TFjsI8LeLeIwlA4fzreiloof48IAkw30NPdzBhouzhGG7uLbhahfjLnKiB/sU1ozGFZlWPDgUs2Cu/mrnZ3YWpHvno0IQuRh2hRw0E0svm+Yp7igFeGsQoiliV/BugaqjWn0ZYhdIfuG0Lt17uzqb/xv+70JODIa6KOslaG/qJs1x9d551q3lDapzAZv6/FY3ovzutWBVf/qG2Qf6Z3TAvdat31unkImPHhSnc7ERpcFDkfYbXNjHDJllXR/uJy+DkH2Gx6FPiwvZQQsZtZel+t+FKrObeaSguXBPuxqwBHzUFtMpxdSIcruW3cepfYYffudmEkEt9oaNe+gMt4kgcJSbvcAfqTl3lBcIzXKiaV/VyhueXpy6ZzXraiyjCHHz/EF5JdS2vnK6IhxYw== X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Brian Inglis via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Brian Inglis Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 54CHiSSq1048878 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