From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: Add support for Windows 8, first step
Date: Wed, 12 Oct 2011 08:27:00 -0000 [thread overview]
Message-ID: <20111012082643.GA10913@calimero.vinschen.de> (raw)
In-Reply-To: <4E949B40.20402@gmail.com>
Hi Teemu,
First of all, we need a copyright assignment from you before we can
accept non-trivial patches to Cygwin, see http://cygwin.com/contrib.html,
the "Before you get started" section.
On Oct 11 22:38, Teemu Nätkinniemi wrote:
> Hello!
>
> Here's a small patch that enables Cygwin to run on Windows 8 (tested
> on x64 build 8102, the Windows Developer Preview). Windows 8 does
> not seem to support FAST_CWD or the current implementation of
> FAST_CWD is not compatible with Windows 8 so it is disabled at the
> moment.
Windows 8 will very likely support the FAST_CWD stuff, the problem is
just to find out how to find the global pointer pointing to the current
FAST_CWD structure, and then, if the FAST_CWD structure changed.
Having this annoying message at startup was intentional, so that we
know that there's some work to do yet. However, personally I don't plan
to look into W8 so soon. Stuff like that is bound to change this early
in the release game anyway.
Therefore I don't want to disable this message. If you're interested
to get rid of it, it would be most helpful trying to track down how to
find the global FAST_CWD pointer in W8.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2011-10-12 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 19:39 Teemu Nätkinniemi
2011-10-12 8:27 ` Corinna Vinschen [this message]
2011-10-12 20:45 ` Teemu Nätkinniemi
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=20111012082643.GA10913@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).