public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Chiheng Xu <chiheng.xu@gmail.com>
To: Andrey Repin <cygwin@cygwin.com>
Subject: Re: building and testing GCC, extremely slow in NTFS, fast in FAT32
Date: Wed, 08 Jun 2011 11:42:00 -0000	[thread overview]
Message-ID: <BANLkTi=EW_0Pp9AttzJuAa+bcLvQV-7VCw@mail.gmail.com> (raw)
In-Reply-To: <1864161701.20110608143639@mtu-net.ru>

On Wed, Jun 8, 2011 at 6:36 PM, Andrey Repin <anrdaemon@freemail.ru> wrote:
>
> mount
> ?

Not relevant to mount. This problem is stick to NTFS.

If I copy the just built cc1.exe/cc1plus.exe to any other place in the
file system, even overwrite the original one,  it can run efficiently.




-- 
Chiheng Xu

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-06-08 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  8:17 Chiheng Xu
2011-06-08 10:51 ` Andrey Repin
2011-06-08 11:42   ` Chiheng Xu [this message]
2011-06-09 10:21     ` Andrey Repin

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='BANLkTi=EW_0Pp9AttzJuAa+bcLvQV-7VCw@mail.gmail.com' \
    --to=chiheng.xu@gmail.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).