From: Bryan Hundven <bryanhundven@gmail.com>
To: swikar <swikarsoni@gmail.com>
Cc: Tommy Murphy <tommy_murphy@hotmail.com>,
crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: crosstool-ng build error
Date: Thu, 8 Dec 2022 01:17:11 -0800 [thread overview]
Message-ID: <CAJ+oik1x6i5XG_YGN7y2HQ4dapLmgfwcnzgeeh6vO5+sCBFxuw@mail.gmail.com> (raw)
In-Reply-To: <CAH17boiXFF6rpgxQ0XWz=t1Pqady9i+qiLZEu4ZbG6kp3gkaGw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
You're not on a case sensitive filesystem. Guessing MacOS.
Search for making a case sensitive volume.
-Bryan
On Thu, Dec 8, 2022, 1:11 AM swikar via crossgcc <crossgcc@sourceware.org>
wrote:
> Hi..
> Thanks for your reply.
> Could you please guide me how to proceed further?
> Regards,
> Swikar Soni
>
> On Thu, 8 Dec, 2022, 2:31 pm Tommy Murphy, <tommy_murphy@hotmail.com>
> wrote:
>
> > > [ERROR] Your file system in
> >
> '/mnt/d/embedded_linux_course/toolchain_understandin/crosstool-ng/.build' is
> > *not* case-sensitive!
> >
> > Isn't this your problem?
> > Your filesystem isn't case sensitive and building certain stuff (e.g.
> > Linux and maybe also a Linux toolchain) requires a case sensitive
> > filesystem because some Linux headers have the same name distinguished
> only
> > by case (e.g. Foo.h and foo.h).
> >
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
next prev parent reply other threads:[~2022-12-08 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 5:46 swikar
2022-12-08 9:01 ` Tommy Murphy
2022-12-08 9:10 ` swikar
2022-12-08 9:17 ` Bryan Hundven [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-31 15:04 crosstool-NG Build ERROR Shaahul Hameed
2010-01-31 17:43 ` Shaahul Hameed
2010-01-31 17:51 ` Yann E. MORIN
2010-01-31 18:03 ` Shaahul Hameed
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=CAJ+oik1x6i5XG_YGN7y2HQ4dapLmgfwcnzgeeh6vO5+sCBFxuw@mail.gmail.com \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=swikarsoni@gmail.com \
--cc=tommy_murphy@hotmail.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).