Re: fixup_mmaps_after_fork errors building ruby 3.4.1 with high make -j

On Tue, 21 Jan 2025, Jeremy Drake via Cygwin wrote: > I did not see this happen with ruby 3.3.7, or when building with -j1. Sorry, spoke too soon, I did see this immediately with 3.3.7 as well. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/fa

fixup_mmaps_after_fork errors building ruby 3.4.1 with high make -j

I've been trying to track down why ruby 3.4.1 is failing to build for msys2. I've now confirmed that this same issue reproduces with upstream Cygwin 3.5.4 and 3.6.0-0.335.gb879cd1661ad, so I thought I'd bring it up here: when building ruby with a high -j value (I'm doing make -j21), I get errors

Handing filesystems which do not support some timestamp fields in |FILE_BASIC_INFO| and Microsoft NFSv3 driver "NfsV3Attributes" EA ...

Hi! If a Windows filesystem does not support a type of timestamp it sets the matching timestamp field in |FILE_BASIC_INFO| to |0LL| (e.g. see Windows-driver-samples/filesys/cdfs/fileinfo.c: |Buffer->LastAccessTime.QuadPart = 0| ; typically this can affect |FILE_BASIC_INFO.CreationTime| and/o

scp "lost connection" failure

Get random (but eventual) "lost connection" using scp (which uses sftp/sftp-server) when transferring huge files via 1G ethernet. No problem if use "scp -O" (don't use sftp protocol) or piping through ssh. Will also happen with a local scp via loopback (localhost) so not a network problem. Ru

Re: 7 python requests?!

On 20/01/2025 20:11, Lester Ingber wrote: I got an update OK. I just had to click on a mirror. Thanks. Lester Hi Lester nice to know that you solved the problem. Next time please REALLY reads https://cygwin.com/problems.html and send a mail with useful info for us to understand your problem,