From: Greg KH <greg@kroah.com>
To: c4droid <c4droid@foxmail.com>
Cc: "Hayward, Shaun" <haywshau@amazon.com>,
"kernelnewbies@kernelnewbies.org"
<kernelnewbies@kernelnewbies.org>
Subject: Re: Making kernel problem
Date: Tue, 7 Jan 2020 08:11:18 +0100 [thread overview]
Message-ID: <20200107071118.GC1012134@kroah.com> (raw)
In-Reply-To: <m2o8vgumxj.fsf@foxmail.com>
On Tue, Jan 07, 2020 at 08:31:36AM +0800, c4droid wrote:
> 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.
Please use a Linux system to build the Linux kernel on for your first
attempt. Trying to get it to build on a non-Linux system is not always
a trivial exercise as you are finding out.
And again, the problem is in your filesystem type you are building on,
it is case-insensitive. Fixing that is the problem here, it is not a
Linux kernel specific thing.
good luck!
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-01-07 7:12 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
2020-01-07 7:11 ` Greg KH [this message]
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=20200107071118.GC1012134@kroah.com \
--to=greg@kroah.com \
--cc=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.