From: c4droid <c4droid@foxmail.com>
To: "Hayward\, Shaun" <haywshau@amazon.com>
Cc: c4droid <c4droid@foxmail.com>,
"kernelnewbies@kernelnewbies.org"
<kernelnewbies@kernelnewbies.org>
Subject: Re: Making kernel problem
Date: Tue, 07 Jan 2020 08:31:36 +0800 [thread overview]
Message-ID: <m2o8vgumxj.fsf@foxmail.com> (raw)
In-Reply-To: <17D43E4A-3344-4146-92FD-F21F36CEE106@amazon.com>
Even I extract source from docker container, the Documentation directory
just exist kbuild, not Kbuild.
And, in the extracted source tree, the top-level Kbuild file named
Kbuild not kbuild, only Documentation/kbuild is named
Documentation/kbuild. When I run make mrproper, make only report
_clean_Documentation target error, my linux kernel source code archive
is download from mirror.
Hayward, Shaun writes:
>> On Jan 6, 2020, at 7:24 AM, c4droid <c4droid@foxmail.com> wrote:
>>
>> My environment is MacOS Catalina, I installed docker for building
>> kernel. The docker container using -v options to mapping local path to
>> docker container.
>
> By default MacOS uses a case insensitive file system. Even in Docker, in order to compile Linux you’ll need to create a new case sensitive partition (eg SparseImage, adding a new volume to your disk’s APFS container, or some other Docker magic, etc)
>
> Shaun
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-01-07 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 11:09 Making kernel problem c4droid
2020-01-06 11:38 ` Martin Christian
2020-01-06 12:22 ` c4droid
2020-01-06 13:08 ` Hayward, Shaun
2020-01-07 0:31 ` c4droid [this message]
2020-01-07 7:11 ` Greg KH
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=m2o8vgumxj.fsf@foxmail.com \
--to=c4droid@foxmail.com \
--cc=haywshau@amazon.com \
--cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.