Re: Status of Cygwin on Windows/ARM64?

I have been VERY happily pleased about how well Cygwin runs using Prism on Windows/ARM64. I can build and test my x86_64 code there using it despite the underlying CPU being an ARM. My genuine Windows/x86_64 machine is not that new these days. Using a stack Macbook-m1/UTM/Windows11-ARM64 runs t

Re: cgdb fails with cygwin 3.2.0 but is OK with 3.1.6

Thank you very much. Great service. And indeed I use the word "gcd" more often that "gdb" and so that was a typo. Arthur On Wed, 14 Apr 2021, Takashi Yano wrote: On Tue, 13 Apr 2021 15:05:56 +0100 (GMT Summer Time) Arthur Norman wrote: With the latest cygwin if I go "gcc -O0 -g hello.c -o hel

Re: cgdb fails with cygwin 3.2.0 but is OK with 3.1.6

René Berber wrote At one time it was recommended to disable a Cygwin feature, something like this: alias cgdb="env CYGWIN=disable_pcon cgdb" Not sure if this is still necesary. Thank you for the reminder about that. I had forgotten - however ion my main Windows machine I have the CYGWIN variab

Re: problem using gcc-core for compile qemu

I can't use virtualbx because what I need is to emulate the aarch64 architecture, I don't want to use binaries compiled by others, one of the reasons is that those binaries don't include sd-card emulation support... This is perhaps an off-topic response as regards compiling things on cygwin, but

symbolic links to /cygdrive/X/xxx with capital letter X

This running on Windows 10 1909 and cygwin has been updated to the latest version. The effect was also visible on a freshly installed minimal cygwin put on an almost fresh Windows 10 VM. Cygwin these days seems to have a behaviour that confuses me regarding the case of a disk name: ln -s "/