From: Oskar Skog <oskar@oskog97.com>
To: cygwin@cygwin.com, cygwin-talk@cygwin.com
Subject: Cygwin on ReactOS bugs
Date: Sat, 13 Aug 2022 19:05:43 +0300 [thread overview]
Message-ID: <816bda62-6326-19a2-2566-b87e44525424@oskog97.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1168 bytes --]
This is NOT an issue with Cygwin, but I have a sneaking suspicion that
some people here may know quite a lot about Cygwin...
I have filed a couple of bugs on ReactOS that are specific to Cygwin.
My knowledge and care is about to run out, if someone happens to care
about running Cygwin 2.5.2 on ReactOS, please take over. I think it
could be helpful for the ReactOS developers to have the test cases
for these issues condensed into a small C++ program instead of running
shell commands on an actual Cygwin installation.
btrfs volumes inaccessible to Cygwin:
https://jira.reactos.org/browse/CORE-18247 (will retest this later)
Setup doesn't like btrfs volumes either:
https://jira.reactos.org/browse/CORE-18300 (specific to the local
package directory)
It also doesn't /install/ on btrfs volumes even if the local package
directory is on fat32, but it gets complicated and I hope it's just the
same bug with different symptoms.
I also had problems with git(1), it seems mmap(2) is broken. I've
scheduled investigating this until later.
To avoid clutter, I suggest replying on the cygwin-talk list rather
than the cygwin list.
/Oskar
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2485 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
reply other threads:[~2022-08-13 16:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=816bda62-6326-19a2-2566-b87e44525424@oskog97.com \
--to=oskar@oskog97.com \
--cc=cygwin-talk@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).