Re: gpg2 / gpg-agent passphrase prompt

2025-01-22 Thread Dimitry Andric via Cygwin
On 22 Jan 2025, at 09:00, ASSI via Cygwin wrote: > > I've got a new machine with Win11 at work, copied over all my > configuration from the old Win10 one, but I can't seem to get gpg2 to > show the passphrase prompt through the W32 GUI of GPG agent. In fact > the agent doesn't seem to even start

Re: Testing for 32bit or 64bit Cygwin in Makefile?

2024-11-09 Thread Dimitry Andric via Cygwin
On 9 Nov 2024, at 11:42, Sebastian Feld via Cygwin wrote: > > On Wed, Nov 6, 2024 at 4:30 PM Dimitry Andric > wrote: >> >> On 6 Nov 2024, at 16:11, Sebastian Feld via Cygwin wrote: >>> >>> How can I test in a /usr/bin/make Makefile whether I am running on a >>> 32bit or 64bit Cygwin (not Wind

Re: cygpath command no longer accepts -s (--short-name) switch

2024-11-08 Thread Dimitry Andric via Cygwin
On 8 Nov 2024, at 16:20, Soren via Cygwin wrote: > > > Hello users. I have a reasonably recently installed Cygwin that I've kept > updated with setup. I am just now seeing that the provided `cygpath` > command no longer works the way it ought to. Could someone(s) confirm or > deny this? And fix

Re: Testing for 32bit or 64bit Cygwin in Makefile?

2024-11-06 Thread Dimitry Andric via Cygwin
On 6 Nov 2024, at 16:11, Sebastian Feld via Cygwin wrote: > > How can I test in a /usr/bin/make Makefile whether I am running on a > 32bit or 64bit Cygwin (not Windows kernel)? Usually in a shell you use "uname -m", or with bash specifically, the $HOSTTYPE variable. However in GNU make you sho

Re: g++ 12 -std=gnu++20

2024-10-31 Thread Dimitry Andric via Cygwin
On 31 Oct 2024, at 06:40, Brian Inglis via Cygwin wrote: > > On 2024-10-30 10:30, Dimitry Andric via Cygwin wrote: >> On 30 Oct 2024, at 17:14, Csaba Ráduly via Cygwin wrote: >>> On 30/10/2024 17:00, Dimitry Andric via Cygwin wrote: >>>> #include >>&g

Re: g++ 12 -std=gnu++20

2024-10-30 Thread Dimitry Andric via Cygwin
On 30 Oct 2024, at 17:14, Csaba Ráduly via Cygwin wrote: > > On 30/10/2024 17:00, Dimitry Andric via Cygwin wrote: >> #include >> #include >> >> constexpr bool foo() >> { >> std::string str2{"abcwe"}; >> return str2.si

Re: g++ 12 -std=gnu++20

2024-10-30 Thread Dimitry Andric via Cygwin
On 30 Oct 2024, at 16:06, Brian Inglis via Cygwin wrote: > Trying to update a package using c++ (requires gcc 12.4+ for adequate c++ > 2020 support) and getting confusing error messages. > > It appears that noexcept in the header files may here redefined by the > compiler or headers as __GLIBC_

Re: Installer freezes in windows-2022 GitHub Action

2024-10-22 Thread Dimitry Andric via Cygwin
Yeah, this is even happening over http/2: Host cygwin.com:443 was resolved. * IPv6: (none) * IPv4: 8.43.85.97 * Trying 8.43.85.97:443... * Connected to cygwin.com (8.43.85.97) port 443 > GET /setup-x86_64.exe HTTP/2 > Host: cygwin.com > User-Agent: curl/8.7.1 > Accept: */* > * Request completely

Re: no sshd in package for openssh

2024-07-31 Thread Dimitry Andric via Cygwin
On 31 Jul 2024, at 21:16, Jim McNamara via Cygwin wrote: > I am running into a little difficulty with openssh can you please assist ? > > thanks jim > > ./cygrunsrv --install sshd -d "Cygwin SSHD" -p /usr/bin/sshd -a "-D" > ./cygrunsrv: Given path doesn't point to a valid executable The sshd bi

Re: Technical reason why 32bit Cygwin cannot be installed on 64bit Windows?

2024-05-17 Thread Dimitry Andric via Cygwin
On 17 May 2024, at 09:48, Cedric Blancher via Cygwin wrote: > > Is there a technical reason why 32bit Cygwin cannot be installed on > 64bit Windows? We like to create a CI build pipeline, and want to > create binaries for 32bit and 64bit Cygwin on the same machine, but > setup.exe for 32bir Cygwi

Re: Bogus exit code 127 from a child process

2024-03-17 Thread Dimitry Andric via Cygwin
On 17 Mar 2024, at 13:50, Dimitry Andric wrote: > > On 17 Mar 2024, at 13:35, Takashi Yano via Cygwin wrote: > ... >> >> I also test your test case: >> while bash -c 'true & true & wait -n || { echo 1: $?; exit 1; } && wait -n >> || { echo 2: $?; exit 1; }'; do echo $((i++)); done >> in Linux

Re: Bogus exit code 127 from a child process

2024-03-17 Thread Dimitry Andric via Cygwin
On 17 Mar 2024, at 13:35, Takashi Yano via Cygwin wrote: ... > > I also test your test case: > while bash -c 'true & true & wait -n || { echo 1: $?; exit 1; } && wait -n || > { echo 2: $?; exit 1; }'; do echo $((i++)); done > in Linux (Debian 12.5), and the issue reproduced! Yeah, same here wit

Re: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel

2024-03-04 Thread Dimitry Andric via Cygwin
t; > Same here building gcc with the msnfs41client NFSv4.1 filesystem > driver (https://sourceforge.net/p/ms-nfs41-client/mailman/message/58741244/), > make -j8 and make -j128 builds now succeed again. > > Is a Cygwin 3.5.x backport required? > > Ced > > On Mon, 4 Ma

Re: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel

2024-03-04 Thread Dimitry Andric via Cygwin
Same here, did a bunch of make -j8 builds, and with 3.6.0-0.71.gb160b690b6ac they now complete without any hangs. Thanks for the quick fix! -Dimitry > On 4 Mar 2024, at 16:58, Kate Deplaix via Cygwin wrote: > > After testing that version without interruption for the past 3 hours on test > ca

Re: Regression: Cygwin 3.5.1 freezes when launching several mingw processes in parallel

2024-03-04 Thread Dimitry Andric via Cygwin
I think I've been experiencing something similar with 3.5.1, where date.exe randomly hangs with a full core pegged. Loading it in gdb shows: Thread 1 received signal SIGTRAP, Trace/breakpoint trap. 0x7ffe23b0b503 in KERNELBASE!DebugBreak () from /cygdrive/c/Windows/System32/KERNELBASE.dll (g

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

2024-02-26 Thread Dimitry Andric via Cygwin
On 26 Feb 2024, at 20:03, Corinna Vinschen wrote: > > On Feb 26 17:34, Dimitry Andric via Cygwin wrote: >> Hi, >> >> After a recent upgrade of a Cygwin installation, including cygwin1.dll >> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

2024-02-26 Thread Dimitry Andric via Cygwin
On 26 Feb 2024, at 18:30, Marco Atzeri via Cygwin wrote: > > On 26/02/2024 18:16, Dimitry Andric via Cygwin wrote: >> On 26 Feb 2024, at 18:00, Marco Atzeri via Cygwin wrote: >>> >>> On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote: >>>> H

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

2024-02-26 Thread Dimitry Andric via Cygwin
On 26 Feb 2024, at 18:00, Marco Atzeri via Cygwin wrote: > > On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote: >> Hi, >> After a recent upgrade of a Cygwin installation, including cygwin1.dll >> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html)

cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

2024-02-26 Thread Dimitry Andric via Cygwin
Hi, After a recent upgrade of a Cygwin installation, including cygwin1.dll (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of) GNU make 4.4.1-2, when it starts external processes and those external processe