linux-kernel - Re: make headers_install: .install and ..install.cmd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 15 Dec 2008 12:31:50 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-kbuild@...r.kernel.org,
	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: make headers_install: .install and ..install.cmd

On Sun, Dec 14, 2008 at 05:31:08PM +0100, Geert Uytterhoeven wrote:
> 	Hi Sam,
> 
> When I use `make ARCH=m68k INSTALL_HDR_PATH=/tmp/headers headers_install',
> I get lots of `.install' and `..install.cmd' files in /tmp/headers and its
> subdirectories.
> 
> I'm building the kernel in a separate output directory and run my make command
> from there.
> 
> Is this intentional?

Hi Geert.

We use the files .install and ..install.cmd to check if we need to install
the headers again or need to check them again.
And there is no other place to put them than next to the relevant files.
Otherwse we would not do the right thing when exporting to
two different directories from the same repository.

The real fix would be to speed up the install step.
Today we rely on the unifdef tool and a perl scrip for the installation.
Combining the functionality in one C file would most likely
speed up the install process to such a degree that we can do it
unconditionally and then we can get rid of the .install 
and ..install.cmd files.

But noone has written a C program to do that (yet).

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/