From: Oliver Schneider <oliver@f-prot.com>
To: crossgcc@sourceware.org
Subject: Re: Q: Can't build
Date: Wed, 01 Feb 2012 18:37:00 -0000 [thread overview]
Message-ID: <4F298641.1020408@f-prot.com> (raw)
In-Reply-To: <D4C14D03-0C88-40A6-9FD2-2402F5E39613@narod.ru>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On 2012-02-01 17:17, Alexandr Zatevalov wrote:
> [ERROR] Your file system in '/home/áÌÅËÓÁÎÄÒ/workspace/toolchain-build/.build' is *not* case-sensitive!
>
> Somebody know how to correct this?
You might try to download the (now free of charge) "Windows Services for
UNIX" (SFU) as they provide the subsystem for it. NTFS is
case-sensitive, the Win32 subsystem is not. Unfortunately still cause
for a lot of bashing and misunderstandings.
Either way, the SFU don't provide the best performance, to put it
mildly. I would second the suggestion to install a VMM and then install
a proper Linux inside of that.
// Oliver
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2012-02-01 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 17:17 Alexandr Zatevalov
2012-02-01 18:10 ` ANDY KENNEDY
2012-02-01 18:37 ` Oliver Schneider [this message]
2012-02-01 20:58 ` Q: " Yann E. MORIN
2012-02-01 18:07 Oron Peled
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=4F298641.1020408@f-prot.com \
--to=oliver@f-prot.com \
--cc=crossgcc@sourceware.org \
/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).