Making kernel problem
Hi, I'm learning how to hacking the Linux kernel follow a tutorial from web, when I download the Linux kernel 5.4.8 source code and extract it to run make mrproper, the make report: Documentation/Kbuild: Is a directory. Stop. I checked Documentation directory, only have a directory name kbuild, not directory name Kbuild. How can I clean this error.
Am 06.01.20 um 12:09 schrieb c4droid:
Hi, I'm learning how to hacking the Linux kernel follow a tutorial from web, when I download the Linux kernel 5.4.8 source code and extract it to run make mrproper, the make report: Documentation/Kbuild: Is a directory. Stop. I checked Documentation directory, only have a directory name kbuild, not directory name Kbuild. How can I clean this error.
My guess would be, you are running your build on a filesystem which is case insensitive (eg. FAT) Martin -- Dipl.-Inf. Martin Christian Senior Berater Entwicklung Hardware Division Verteidigung secunet Security Networks AG Tel.: +49 201 5454-3612, Fax +49 201 5454-1323 E-Mail: martin.christian@secunet.com Ammonstraße 74, 01067 Dresden www.secunet.com __________________________________________________________________________ secunet Security Networks AG Sitz: Kurfürstenstraße 58, 45138 Essen, Deutschland Amtsgericht Essen HRB 13615 Vorstand: Axel Deininger (Vors.), Torsten Henn, Dr. Kai Martius, Thomas Pleines Aufsichtsratsvorsitzender: Ralf Wintergerst __________________________________________________________________________
My environment is MacOS Catalina, I installed docker for building kernel. The docker container using -v options to mapping local path to docker container. Martin Christian writes:
Am 06.01.20 um 12:09 schrieb c4droid:
Hi, I'm learning how to hacking the Linux kernel follow a tutorial from web, when I download the Linux kernel 5.4.8 source code and extract it to run make mrproper, the make report: Documentation/Kbuild: Is a directory. Stop. I checked Documentation directory, only have a directory name kbuild, not directory name Kbuild. How can I clean this error.
My guess would be, you are running your build on a filesystem which is case insensitive (eg. FAT)
Martin
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
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
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
participants (4)
-
c4droid -
Greg KH -
Hayward, Shaun -
Martin Christian