On Wed, 18 Jun 2025, Jeremy Drake via Cygwin wrote:
> The "stress tests x86_64 on arm64 Windows" tests "fp" and "memcpy" seem to
> be consitently failing since 364226a. The step is allowed to continue on
> error because there is some flakiness with tests o
Hi Roumen,
On Tue, 10 Jun 2025, Roumen Petrov wrote:
> На 5.06.25 г. в 15:49 ч., Johannes Schindelin via Cygwin написа:
> [SNIP]
> > > and bisecting my problem to
> > > https://github.com/cygwin/cygwin/commit/48e7d632689313106d16b0de035fb955c54492b2,
> > > th
On Mon, 16 Jun 2025 at 22:57, Brian Inglis via Cygwin wrote:
>
> On 2025-06-16 03:17, Lionel Cons via Cygwin wrote:
> > On Fri, 13 Jun 2025 at 21:52, Brian Inglis via Cygwin
> > wrote:
> >>
> >> On 2025-06-13 06:09, Lionel Cons via Cygwin wrote:
> >&g
k if I can
get something more concrete.
[1] https://cygwin.com/pipermail/cygwin-announce/2025-May/012341.html
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info:
ling.
It seems like 3 commits were pushed at once, so there's only one job for:
Cygwin: signal: Prevent unexpected crash on frequent SIGSEGV
Cygwin: signal: Revert _cygtls::inside_kernel() change
Cygwin: signal: Enable the signal mask earlier
See for example
https://github.com/cygwin/
On Tue, Jun 17, 2025 at 5:25 PM Aurélien Couderc
wrote:
>
> Cygwin creates instead of on NTFS, but cmd.exe
> cannot find the *.exe if they are linked as .
>
> Two test cases:
> $ bash -c $'rm -f id_vers15.exe ; cp /usr/bin/id.exe id_vers15.exe ;
> ln -sf id_ve
On Tue, 17 Jun 2025 15:42:26 -0700
Mark Geisert wrote:
> Hi Takashi,
>
> On 6/17/2025 5:54 AM, Takashi Yano via Cygwin wrote:
> > Hi,
> >
> > If system() is called in parallel in threads, system()
> > fails with exit code 127.
> >
> > Just compile
Hi Cygwin,
I’ve studied Cygwin.Com for 7 days and found several technical errors
affecting your primary keywords: Cygwin Linux tools, POSIX API Windows, GNU
utilities collection ranking, impacting The Cygwin Project’s online
presence in the post-pandemic market.
Major errors found:
• No Schema
Hi Takashi,
On 6/17/2025 5:54 AM, Takashi Yano via Cygwin wrote:
Hi,
If system() is called in parallel in threads, system()
fails with exit code 127.
Just compile pthread_system.c attached and run.
I believe system() is multi-thread safe so the STC
should work.
I regret to inform that
On Tue, 17 Jun 2025, Radek Barton via Cygwin wrote:
> Hello Sebastian.
>
> AFAIK, LLVM has no *-pc-cygwin targets support and there is no-one trying to
> change that.
We're working on that. LLVM 21.x should be much better in that regard.
There has been no effort towards
On Tue, 17 Jun 2025, Sebastian Feld via Cygwin wrote:
> Now that Microsoft is porting Cygwin to Aarch64:
>
> Do you know how to run Windows Aarch64 in qemu, so people can test
> Cygwin Aarch64 changes?
>
> Sebi
Yes, but as others have said it is too slow to really be practica
Cygwin creates instead of on NTFS, but cmd.exe
cannot find the *.exe if they are linked as .
Two test cases:
$ bash -c $'rm -f id_vers15.exe ; cp /usr/bin/id.exe id_vers15.exe ;
ln -sf id_vers15.exe myid.exe ; cmd /C \'.\myid.exe\''
$ bash -c $'rm -f id_vers15
Hi,
If system() is called in parallel in threads, system()
fails with exit code 127.
Just compile pthread_system.c attached and run.
I believe system() is multi-thread safe so the STC
should work.
--
Takashi Yano
#include
#include
#include
#include
#include
void *func(void *arg)
{
prin
On Tue, Jun 17, 2025 at 12:36 PM Radek Barton via Cygwin
wrote:
> We have never considered QEMU as an option so I can't tell whether it's
> working.
IMO someone at Microsoft engineering management should look at the
issue that Windows-11 does not work on qemu.
Right now th
On Tue, Jun 17, 2025 at 9:57 AM Sebastian Feld via Cygwin
wrote:
> Now that Microsoft is porting Cygwin to Aarch64:
>
> Do you know how to run Windows Aarch64 in qemu, so people can test
> Cygwin Aarch64 changes?
I use this script for Windows 11 experiments (same as
https://nrubsi
also
that the OS stop working or it freezes without possibilities of recovering.
Don't expect to use it for something, at least in my opinion.
Sincerely,
Carlo Bramini
Il Mar 17 Giu 2025, 09:59 Sebastian Feld via Cygwin ha
scritto:
> Now that Microsoft is porting Cygwin to Aarch64:
&g
less loops.
In case of Cygwin (Cygwin is slow, we all know that), the rather low
SYMLOOP_MAX was chosen so the path handling didn't get even slower in
some circumstances I don't remember anymore. Maybe the times when this
was relevant are over, so we can try this.
However, please send a re
Hello.
We have never considered QEMU as an option so I can't tell whether it's working.
We are testing the Cygwin runtime and the GCC toolchain linked with it built
with Linux->Windows cross-compiler on self-hosted GitHub Actions runner running
on Windows Arm64 VM with WSL l
Hello Sebastian.
AFAIK, LLVM has no *-pc-cygwin targets support and there is no-one trying to
change that.
The best take you can have for now is to build your own GCC Linux to Windows
cross-compiler using
https://github.com/Windows-on-ARM-Experiments/mingw-woarm64-build scripts or
download
Does Cygwin /usr/bin/clang has Aarch64 support, to compile native
Windows Aarch64 binaries if Cygwin-x86-64 runs on Windows Aarch64?
Sebi
--
Sebastian Feld - IT security consultant
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
On Tue, Jun 17, 2025 at 10:10 AM Arthur Norman wrote:
>
> Thanka for the head up - can you provide us with a pointer to Microsoft
> work on Cygwin please?
Check the cygwin-patches mailing list, and the cygwin git log. Lots of
Aarch64 related patches.
> On a Raspberry Pi 5 "
Thanka for the head up - can you provide us with a pointer to Microsoft
work on Cygwin please?
On a Raspberry Pi 5 "botspot-VM" https://github.com/Botspot/bvm installed
a Win11 for me fairly happily and despite it not being the fastest machine
it is closer to viable than I
Now that Microsoft is porting Cygwin to Aarch64:
Do you know how to run Windows Aarch64 in qemu, so people can test
Cygwin Aarch64 changes?
Sebi
--
Sebastian Feld - IT security consultant
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq
Windows object manager.
---cut---cut---cut---
diff --git a/winsup/cygwin/include/cygwin/limits.h
b/winsup/cygwin/include/cygwin/limits.h
index 204154da9..c61466368 100644
--- a/winsup/cygwin/include/cygwin/limits.h
+++ b/winsup/cygwin/include/cygwin/limits.h
@@ -43,7 +43,13 @@ details. */
#define
On 2025-06-16 03:17, Lionel Cons via Cygwin wrote:
On Fri, 13 Jun 2025 at 21:52, Brian Inglis via Cygwin wrote:
On 2025-06-13 06:09, Lionel Cons via Cygwin wrote:
/usr/bin/setfacl is broken in 3.7.0-0.127.g2029784e05d9
my testcase:
lionel$ uname -a
CYGWIN_NT-10.0-19045 halcyonrenard17 3.7.0
Hello,
At Estimation Lab, we specialize in delivering precise estimating and takeoff
services for both general contractors and subcontractors. Whether your project
is commercial or residential, we use advanced software to ensure accuracy and
efficiency.
Send us your project plans anytime for
On 6/16/2025 5:17 AM, Lionel Cons via Cygwin wrote:
How can I install each Cygwin minor version (not just the Cygwin
*.dll, I mean EVERYTHING including dependencies)?
My understanding is that this is not a concept with cygwin. Cygwin is
not monolithic. Each package is released on its own
On Fri, 13 Jun 2025 at 21:52, Brian Inglis via Cygwin wrote:
>
> On 2025-06-13 06:09, Lionel Cons via Cygwin wrote:
> > /usr/bin/setfacl is broken in 3.7.0-0.127.g2029784e05d9
> >
> > my testcase:
> > lionel$ uname -a
> > CYGWIN_NT-10.0-19045 halcyonrenar
On Sat, 14 Jun 2025, Jeremy Drake via Cygwin wrote:
> Consider the following -std=c++20:
> #include
>
> constinit pthread_mutex_t foo = PTHREAD_MUTEX_INITIALIZER;
>
> With g++ 12.4.0, this succeeds, but with clang 20.1.6 it fails:
> pthreadtest.cpp:3:27: error: variable doe
On Sat, Jun 14, 2025 at 12:29:57PM -0600, Brian Inglis via Cygwin wrote:
> On 2025-06-13 21:39, Glenn Strauss via Cygwin wrote:
> > On Fri, Jun 13, 2025 at 02:25:17PM -0700, Jeremy Drake via Cygwin wrote:
> > > On Fri, 13 Jun 2025, Jeremy Drake wrote:
> > >
&
Consider the following -std=c++20:
#include
constinit pthread_mutex_t foo = PTHREAD_MUTEX_INITIALIZER;
With g++ 12.4.0, this succeeds, but with clang 20.1.6 it fails:
pthreadtest.cpp:3:27: error: variable does not have a constant initializer
3 | constinit pthread_mutex_t foo = PTHREAD_MUTEX_
On 2025-06-13 21:39, Glenn Strauss via Cygwin wrote:
On Fri, Jun 13, 2025 at 02:25:17PM -0700, Jeremy Drake via Cygwin wrote:
On Fri, 13 Jun 2025, Jeremy Drake wrote:
I am working on some posix_spawn tests for the new stc repository [1], and
making sure they behave the same between Cygwin and
Bruno Haible via Cygwin writes:
> When I build GCC myself from source for other platforms, the D runtime
> library is called 'libgphobos'. Without this library, both 'gdc' and 'd21'
> are useless.
If you had tried to build it for Cygwin you would have discov
On Fri, Jun 13, 2025 at 02:25:17PM -0700, Jeremy Drake via Cygwin wrote:
> On Fri, 13 Jun 2025, Jeremy Drake wrote:
>
> > I am working on some posix_spawn tests for the new stc repository [1], and
> > making sure they behave the same between Cygwin and Linux. I found one
>
On Fri, 13 Jun 2025, Jeremy Drake wrote:
> I am working on some posix_spawn tests for the new stc repository [1], and
> making sure they behave the same between Cygwin and Linux. I found one
> case (so far) which does not: passing NULL for argument "envp" to
> posix_spaw
I am working on some posix_spawn tests for the new stc repository [1], and
making sure they behave the same between Cygwin and Linux. I found one
case (so far) which does not: passing NULL for argument "envp" to
posix_spawn.
In Cygwin, this results in the child inheriting the enviro
On 2025-06-13 06:09, Lionel Cons via Cygwin wrote:
/usr/bin/setfacl is broken in 3.7.0-0.127.g2029784e05d9
my testcase:
lionel$ uname -a
CYGWIN_NT-10.0-19045 halcyonrenard17 3.7.0-0.127.g2029784e05d9.x86_64
2025-06-10 12:15 UTC x86_64 Cygwin
lionel$ mkdir nfstmp1
ionel$ setfacl -m g::rwx
On 2025-06-13 06:11, Lionel Cons via Cygwin wrote:
Is there a way to specifically install Cygwin version 3.5.1 (for
testing purposes)?
As 3.5.1 is no longer available directly via Cygwin Setup, could you use 3.5.7
which is still available in current setup.ini as the oldest stable version and
Am 13.06.2025 um 07:38 schrieb Yuyi Wang via Cygwin:
If the CWD
is /proc (so something without a Windows CWD), it seems to fall back to
referring to '/a/b' again?!?
Oh, no. That makes me nearly impossible to determine whether a path is absolute
without getting the current P
Is there a way to specifically install Cygwin version 3.5.1 (for
testing purposes)?
Lionel
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml
/usr/bin/setfacl is broken in 3.7.0-0.127.g2029784e05d9
my testcase:
lionel$ uname -a
CYGWIN_NT-10.0-19045 halcyonrenard17 3.7.0-0.127.g2029784e05d9.x86_64
2025-06-10 12:15 UTC x86_64 Cygwin
lionel$ mkdir nfstmp1
ionel$ setfacl -m g::rwx nfstmp1
setfacl: Permission denied
ionel$ setfacl -m
> If the CWD
> is /proc (so something without a Windows CWD), it seems to fall back to
> referring to '/a/b' again?!?
Oh, no. That makes me nearly impossible to determine whether a path is absolute
without getting the current PWD.
--
Yuyi Wang
--
Problem reports: https://cygwin.com/problem
On Wed, 11 Jun 2025, Jeremy Drake via Cygwin wrote:
> While making some tests for a path parser in rust
> (https://github.com/rust-lang/rust/pull/141864), an interesting corner
> case in Cygwin path handling came to light:
>
> Works:
> \\.\C:
> //.\C:
> //./C:\foo
&
On 6/12/2025 1:28 PM, Bruno Haible via Cygwin wrote:
On Cygwin 3.6.3, I have the packages
gcc-core
gcc-g++
gcc-gdc
installed, all in version 11.5.0-1.
But the D compiler is dysfunctional: The attempt to compile any D source code
fails. E.g.:
$ echo > empty.d
$ gdc -c empty.c
On Cygwin 3.6.3, I have the packages
gcc-core
gcc-g++
gcc-gdc
installed, all in version 11.5.0-1.
But the D compiler is dysfunctional: The attempt to compile any D source code
fails. E.g.:
$ echo > empty.d
$ gdc -c empty.c
d21: error: cannot find source code for runtime library f
On 2025-06-11 18:57, Jeremy Drake via Cygwin wrote:
On Thu, 12 Jun 2025, Sam Edge via Cygwin wrote:
I would think that if you're building something against Cygwin, it's probably
best to assume it's POSIX where only forward-slash is special and not try to
second-guess.
This
On 12/06/2025 01:57, Jeremy Drake wrote:
On Thu, 12 Jun 2025, Sam Edge via Cygwin wrote:
I would think that if you're building something against Cygwin, it's probably
best to assume it's POSIX where only forward-slash is special and not try to
second-guess.
This is unsafe, and
On Thu, 12 Jun 2025, Sam Edge via Cygwin wrote:
> I would think that if you're building something against Cygwin, it's probably
> best to assume it's POSIX where only forward-slash is special and not try to
> second-guess.
This is unsafe, and actually where the rust PR s
On 12/06/2025 00:01, Jeremy Drake via Cygwin wrote:
While making some tests for a path parser in rust
(https://github.com/rust-lang/rust/pull/141864), an interesting corner
case in Cygwin path handling came to light:
Works:
\\.\C:
//.\C:
//./C:\foo
Doesn't work:
//./C:
//./C:/foo
It ap
While making some tests for a path parser in rust
(https://github.com/rust-lang/rust/pull/141864), an interesting corner
case in Cygwin path handling came to light:
Works:
\\.\C:
//.\C:
//./C:\foo
Doesn't work:
//./C:
//./C:/foo
It appears to be able to use the \\.\ prefix, there must
On 2025-06-11 00:49, Cedric Blancher via Cygwin wrote:
Which character encoding is used by LookupAccountSidA() (not
LookupAccountSidW())?
Is there a way to force a specific encoding, like UTF-8 or GB18030?
Check MS:
https://learn.microsoft.com/en-us/windows/win32/intl/conventions-for-function
Good morning!
Which character encoding is used by LookupAccountSidA() (not
LookupAccountSidW())?
Is there a way to force a specific encoding, like UTF-8 or GB18030?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.
Hello,
I found a possible bug with the readline library included in
libguile3.0_1-3.0.9-3 and using it with guile3.0-3.0.9-3.
After invoking guile, I tried to load the readline library, and received
an error that guile-readline.dll is not found:
$ guile
GNU Guile 3.0.10
Copyright (C)
На 5.06.25 г. в 15:49 ч., Johannes Schindelin via Cygwin написа:
[SNIP]
and bisecting my problem to
https://github.com/cygwin/cygwin/commit/48e7d632689313106d16b0de035fb955c54492b2,
the following diff (which partially reverts that commit) fixes it for me:
Dunno what is correction in v3.6.3
On 6/10/2025 5:49 AM, Michael Wachs via Cygwin wrote:
Hello,
I'm using a PC with Win11 and since few weeks the latest cygwin64 version.
I've found that all pseudo links to binary files, which contain text aka
"!{command}" do not work at all!
Neither interactive
for ex
Hello,
I'm using a PC with Win11 and since few weeks the latest cygwin64 version.
I've found that all pseudo links to binary files, which contain text aka
"!{command}" do not work at all!
Neither interactive
for example:
/usr/bin/view
/usr/bin:[527]$ view
On Sun, 8 Jun 2025, Brian Inglis via Cygwin wrote:
> On 2025-06-07 19:50, Jeremy Drake via Cygwin wrote:
> > On Sun, 8 Jun 2025, Roland Mainz via Cygwin wrote:
> >
> >> I know... but the request is for portable applications and scripts,
> >> which either use |pat
Sorry, for the noise. I had not seen the previous messages where this was
already reported.
The bit that I can add to this discussion now is that updating to Cygwin (the
'cygwin package') 3.6.3-1 just now did resolve the issue for me and playing
with the individual app exploit securit
Hello!
It looks like a recent update of cygwin is now not letting me open any shell
anymore. I get the following error with the Window frame showing 'nologin' in
upper left corner:
Error: Could not fork child process: There are no available terminals (-1).
I have tried to appl
On 2025-06-08 15:19, Backwoods BC via Cygwin wrote:
On Sun, Jun 8, 2025 at 2:03 PM Zarquan via Cygwin wrote:
I use cygwin to run experiments on protocols on Windows using bash
scripts. I often am running multiple programs that interact with each
other, so I alt-tab between the consoles
On Sun, Jun 8, 2025 at 2:03 PM Zarquan via Cygwin wrote:
> I use cygwin to run experiments on protocols on Windows using bash
> scripts. I often am running multiple programs that interact with each
> other, so I alt-tab between the consoles. Unfortunately, when I alt-tab to
> or f
I use cygwin to run experiments on protocols on Windows using bash
scripts. I often am running multiple programs that interact with each
other, so I alt-tab between the consoles. Unfortunately, when I alt-tab to
or from a cygwin console, it adds a bunch of spaces to the outputs, which
is
On 2025-06-07 19:50, Jeremy Drake via Cygwin wrote:
On Sun, 8 Jun 2025, Roland Mainz via Cygwin wrote:
I know... but the request is for portable applications and scripts,
which either use |pathconf(...,_PC_CASE_SENSITIVE)| or /bin/getconf to
probe this information. Both APIs are not supported
On Sun, 8 Jun 2025, Roland Mainz via Cygwin wrote:
> I know... but the request is for portable applications and scripts,
> which either use |pathconf(...,_PC_CASE_SENSITIVE)| or /bin/getconf to
> probe this information. Both APIs are not supported by Cygwin yet...
Isn't it?
http
On Sat, Jun 7, 2025 at 7:06 PM Brian Inglis via Cygwin
wrote:
> On 2025-06-07 09:45, Roland Mainz via Cygwin wrote:
> > Could Cygwin /bin/getconf please add support for |pathcomf(...
> > _PC_CASE_SENSITIVE)|, either querying
> > |FILE_CASE_SENSITIVE_INFORM
On 2025-06-07 09:45, Roland Mainz via Cygwin wrote:
Could Cygwin /bin/getconf please add support for |pathcomf(...
_PC_CASE_SENSITIVE)|, either querying
|FILE_CASE_SENSITIVE_INFORMATION| (see
https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/ns-ntifs
Hi!
Could Cygwin /bin/getconf please add support for |pathcomf(...
_PC_CASE_SENSITIVE)|, either querying
|FILE_CASE_SENSITIVE_INFORMATION| (see
https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/ns-ntifs-_file_case_sensitive_information)
and check the
Dear Cygwin team,
I’ve found that rebase.exe makes certain assumptions that do not conform to the
PE specification.
1. Incorrect handling of COFF File Header position
When checking the 'Characteristics' field in the COFF File Header, rebase.exe
assumes this field is always at a fi
installer
files on NFS mounts
Ced
P.S.: Thanks go to Roland Mainz&Tigran Mkrtchyan&DESY.de for the
ms-nfs41-client work, Corinna Vinschen for adding sparse file support
in Cygwin 3.5, and many others who helped with development and testing
-- Forwarded message -
From: Rola
On Thu, Jun 05, 2025 at 11:33:18PM -0700, Jeremy Drake via Cygwin wrote:
> I noticed while looking at JIT test failures in LLVM that they don't have
> an implementation for Cygwin for flushing the instruction cache. I don't
> see any Cygwin function calling FlushInstructionC
I noticed while looking at JIT test failures in LLVM that they don't have
an implementation for Cygwin for flushing the instruction cache. I don't
see any Cygwin function calling FlushInstructionCache, is there some
POSIXy function for this? I don't really want to have to include
Hi Robert,
this patch has now been released as Cygwin v3.6.3. Would you kindly verify
that it fixes your problem?
Thanks,
Johannes
On Mon, 2 Jun 2025, Johannes Schindelin wrote:
> Hi Robert,
>
> On Wed, 28 May 2025, Robert Fensterman wrote:
>
> > getent passwd %USERNAME%
&
On Thu, Apr 10, 2025 at 8:14 PM Sebastian Feld
wrote:
>
> Could the maximum symlink depth in Cygwin please be increased for
> cygwin 3.7? We're regularly hitting that limit (seems to be 10).
>
> What is the maximum number of symlink recursion? Rumor is that this is
> 32,
On Wed, 4 Jun 2025 at 20:46, Brian Inglis via Cygwin wrote:
>
> On 2025-06-04 10:58, Cedric Blancher via Cygwin wrote:
> > Why is there no "world" group in Cygwin by default?
> > So war I've found EVERY Windows access token contains an group entry
> > for S-
On Mon, 17 Feb 2025 at 11:07, Corinna Vinschen via Cygwin
wrote:
>
> On Feb 16 16:27, Sebastian Feld via Cygwin wrote:
> > On Sat, Feb 15, 2025 at 4:15 PM Cedric Blancher via Cygwin
> > wrote:
> > >
> > > Good afternoon!
> > >
> > > Could
On 13/05/2025 18:24, ASSI via Cygwin wrote:
Hamish McIntyre-Bhatty via Cygwin writes:
I've run into a blocker when trying to build wxPython that wasn't a
problem when I last did it (which amittedly was over a year ago). Some
-werror flags are being passed to GCC, but I can't se
On 2025-06-04 10:58, Cedric Blancher via Cygwin wrote:
Why is there no "world" group in Cygwin by default?
So war I've found EVERY Windows access token contains an group entry
for S-1-1-0 (World), which makes me wonder by Cygwin doesn't generate
a GID by default.
It'
On Wed, 4 Jun 2025, Don Slutz via Cygwin wrote:
> Using 3.6.1-1 works fine. I am very sure this is based on the same issue that
> others have reported.
>
> looks like the key in that I get for "getent passwd $(id -u)":
>
> NASUNI+dslutz:*:4096:4096:U-NASUN
User@CPC-dslut-3Q3JN$
Doing more testing shows that
Unknown+User@CPC-dslut-3Q3JN$ cd /home/dslutz/cygwin-te st/
Unknown+User@CPC-dslut-3Q3JN$ touch bad
Unknown+User@CPC-dslut-3Q3JN$ ls -l
total 0
-r--r--r-- 1 Unknown+User Unknown+Group 0 Jun 4 13:47 bad
-rw-rw-r-- 1 Unknown+User Unknown+
On Fri, 23 May 2025 at 19:42, Adam Dinwoodie via Cygwin
wrote:
>
> On Fri, 23 May 2025 at 14:47, Mark Liam Brown via Cygwin wrote:
> > What is the official procedure to uninstall Cygwin properly? Just
> > deleting C:\cygwin64 from Explorer yields lots of "malformed ACL
Good evening!
Why is there no "world" group in Cygwin by default?
So war I've found EVERY Windows access token contains an group entry
for S-1-1-0 (World), which makes me wonder by Cygwin doesn't generate
a GID by default.
Ced
--
Cedric Blancher
[https://plus.google.com
On Tue, 3 Jun 2025, Jeremy Drake via Cygwin wrote:
> On Sun, 1 Jun 2025, Jon Turney wrote:
>
> > On 25/05/2025 17:53, Jeremy Drake via Cygwin wrote:
> > > On Sun, 25 May 2025, ASSI via Cygwin wrote:
> > >
> > > > Jeremy Drake via Cygwin writes:
> &
On Sun, 1 Jun 2025, Jon Turney wrote:
> On 25/05/2025 17:53, Jeremy Drake via Cygwin wrote:
> > On Sun, 25 May 2025, ASSI via Cygwin wrote:
> >
> > > Jeremy Drake via Cygwin writes:
> > > > Apparently the fix that MSYS2 made for openssl in
> > > > h
Dears,
I would like to take this opportunity, your experience in business and ask for
your advice and help. Let me briefly introduce myself – my name is Michal
Blaha, and I’m the Sales & Marketing Director at HYDRA a.s., a European
manufacturer of high-quality film capacitors for industrial a
starts with `S-1-12-1`. Together with this information:
> With cygwin 3.6.2-1, I can start bash directly from a CMD window (though it
> can't find programs, just built-ins).
> Interestingly: after that test, that and reverting back to .1, my
> .bash_history permissions seem to be
Hi,
> I see only 1 file 'virc' on my up-to-date cygwin:
> /etc/defaults/etc/virc
This was driving me nuts, I could not reproduce or test the problem.
It turns out that downgrading vim from 9.1.1054-1 to 9.0.2155-2
removes /etc/defaults/etc/virc
and upgrading again does not rest
> They won't, and Cygwin itself has no way of changing that. 64-bit
> editions of Windows cannot run anything 16-bit (technically, the V86
> mode is gone from both the CPUs and the system). That does mean DOS
> itself is not available, and therefore nothing expecting to run
I wrote:
> I want to let this rest for now
So only THEN did I notice:
https://sourceware.org/pipermail/cygwin/2025-January/257212.html
where Marco Atzeri says it will be fixed in the next cygwin release.
Perhaps I misunderstand this.
I see only 1 file 'virc' on my up-to-date c
t was caused by changes in multiple vim packages, I'd rather not
reverse-engineer how it used to work.
Anyone who runs into this problem should now be able to find a problem
description and a workaround. The problem seems to be only in the Cygwin build
of vim.
I'll probably keep my a
On 2025-06-01 10:47, Eric J Korpela via Cygwin wrote:
To be more explicit, a text mode windows program is not a DOS program. It
will do anything useful on a DOS system without windows.
If you desire 32-bit protected mode DOS programs, DJGPP may be your best
option. New builds of DJGPP are
On Sun, Jun 1, 2025 at 11:16 AM andkin773--- via Cygwin
wrote:
>
> Hi,
>
> I missed something,
> According to
> https://github.com/vim/vim/issues/17039 :
> > Looks like problem was introduced in 9.1.1054-1
>
> I downgraded vim to check:
>
Am 01.06.2025 um 18:47 schrieb Eric J Korpela via Cygwin:
To be more explicit, a text mode windows program is not a DOS program. It
will do anything useful on a DOS system without windows.
^ not
If you desire 32-bit protected mode DOS programs, DJGPP may be your best
option. New
In https://github.com/rust-lang/rust/pull/141864 I was going to say that
passing an already-posix path through cygwin_conv_path(CPP_WIN_A_TO_POSIX,
...) was unsafe because Windows ANSI file paths are either CP_ACP or
CP_OEMCP, while Cygwin POSIX path encodings are based on the C locale
encoding
sure if the current binaries run correctly under cygwin as they
are programs that run under a DOS extender. They used to work under
Windows and OS/2, but it's been a while since I tried them on a recent
version of Windows.
If you need 16-bit real mode or 16-bit protected mode DOS binaries,
Am 01.06.2025 um 10:02 schrieb Roumen Petrov via Cygwin:
Hello,
FYI: I have the same issue on the same date.
На 28.05.25 г. в 15:52 ч., Robert Fensterman via Cygwin написа:
[SNIP]
Error: Could not fork child process: There are no available terminals
The message is reported by mintty if
(I'm not sure if this reply is addressed correctly for the mailing list)
> did
> alias view >/dev/null 2>&1 || alias view=vim -R
> need quotes also ?
Yes.
To be honest, I don't understand why you ask this?
It's easier to see in interactive bash:
$ alias view=vim -R
-bash: alias: -R: not found
$
Hi,
I missed something,
According to
https://github.com/vim/vim/issues/17039 :
> Looks like problem was introduced in 9.1.1054-1
I downgraded vim to check:
$ cygcheck -c | grep vim
vim 9.0.2155-2 OK
vim-common 9.1.1054-1 Incomp
On 31/05/2025 18:50, Lee wrote:
On Sat, May 31, 2025 at 11:16 AM Jon Turney wrote:
On 31/05/2025 01:33, Takashi Yano via Cygwin wrote:
On Sat, 31 May 2025 09:00:10 +0900
Takashi Yano wrote:
On Sat, 31 May 2025 00:39:24 +0200
Dan Shelton wrote:
Hello!
Does Cygwin have a compiler which allows
On 25/05/2025 17:53, Jeremy Drake via Cygwin wrote:
On Sun, 25 May 2025, ASSI via Cygwin wrote:
Jeremy Drake via Cygwin writes:
Apparently the fix that MSYS2 made for openssl in
https://github.com/msys2/MSYS2-packages/pull/3448 is also not present in
Cygwin, so cargo continues to crash after
Hello,
FYI: I have the same issue on the same date.
На 28.05.25 г. в 15:52 ч., Robert Fensterman via Cygwin написа:
[SNIP]
Error: Could not fork child process: There are no available terminals
(-1)
[SNIP]
Also I found the same work-around i.e., revert from 3.6.2-1 to 3.6.1-1.
Robert report
1 - 100 of 5555 matches
Mail list logo
