From: Oron Peled <oron@actcom.co.il>
To: crossgcc@sourceware.org
Subject: Re: Q: Can't build
Date: Wed, 01 Feb 2012 18:07:00 -0000 [thread overview]
Message-ID: <201202012007.23790.oron@actcom.co.il> (raw)
On Wednesday, 1 בFebruary 2012 19:17:33 Alexandr Zatevalov wrote:
> [ERROR] Your file system in '/home/áÌÅËÓÁÎÄÒ/workspace/toolchain-
build/.build' is *not* case-sensitive!
>
> Somebody know how to correct this?
Easy. Install a real OS....
(sorry, couldn't resist ;-)
--
Oron Peled Voice: +972-4-8228492
oron@actcom.co.il http://users.actcom.co.il/~oron
“If I have seen a little further it is by standing on the shoulders of
Giants."
--Isaac Newton.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2012-02-01 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 18:07 Oron Peled [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 17:17 Alexandr Zatevalov
2012-02-01 18:37 ` Oliver Schneider
2012-02-01 20:58 ` Yann E. MORIN
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=201202012007.23790.oron@actcom.co.il \
--to=oron@actcom.co.il \
--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).