Johannes Schindelin
Johannes Schindelin
> Please rebase the branch and force-push. @maryis please do...
> 0xC000000D That looks like [`STATUS_INVALID_PARAMETER`](https://github.com/git-for-windows/git-sdk-64/blob/dab0f3c7888b8165c69a6e5da8ddaa87d26abfa7/mingw32/include/ntstatus.h#L258). > I assume that FILE_DISPOSITION_POSIX_SEMANTICS is not supported on mounted volumes. @YO4 you mean to imply that [this part of the code](https://github.com/msys2/msys2-runtime/blob/9acb704afe9d9d8a090f2391e2bb88add63997c6/winsup/cygwin/syscalls.cc#L722-L726) fails? If...
> tested on my local environment > > ``` > ../../.././winsup/cygwin/syscalls.cc:696: has posix unlink semantics: 1, is remote: 0, is ntfs: 1 > ../../.././winsup/cygwin/syscalls.cc:728: NtSetInformationFile returned status 0xC000000D > ../../.././winsup/cygwin/syscalls.cc:732:...
Please note that @kanaka is not a maintainer of LibVNCServer I just added an official GitHub repository for the project: https://github.com/LibVNC/libvncserver. Please consider opening the pull request there.
There is no native MSYS2 runtime that supports ARM64. What you are running is an x86_64 MSYS2 runtime, running in emulation mode. Therefore the `uname -m` is actually correct: the...
Lying about the CPU architecture the MSYS2 runtime is running on might help _some_ use cases, but totally break others. That's worse than undesirable, that would be willful. The proper...
> I'm glad we all agree that an arm64 native build of msys2-runtime would resolve this issue. So. Are you working on this? Maybe you did not hear me when...