mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kbuild@vger.kernel.org,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: make headers_install: .install and ..install.cmd
Date: Mon, 15 Dec 2008 12:31:50 +0100	[thread overview]
Message-ID: <20081215113150.GA10911@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812141728370.5714@anakin>

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

      reply	other threads:[~2008-12-15 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 16:31 Geert Uytterhoeven
2008-12-15 11:31 ` Sam Ravnborg [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=20081215113150.GA10911@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®