linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Francis Moreau <francis.moro@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about the last build
Date: Sat, 16 Apr 2011 11:08:45 -0400	[thread overview]
Message-ID: <62853.1302966525@localhost> (raw)
In-Reply-To: Your message of "Sat, 16 Apr 2011 16:45:33 +0200." <BANLkTimSa7=HiSKET4FSR5zqa1mXf2xGFw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

On Sat, 16 Apr 2011 16:45:33 +0200, Francis Moreau said:

> For example, user did:
>   $ make CC=distcc
> then call my script:
>   $ my-script
> which in its turn does:
>   $ make
> then the whole kernel is rebuilt..

You have two choices then:

1)  Allow them to pass stuff to your script:

$ make CC=distcc
then call my script:
$ my-script CC=distcc
which in its turn does:
$ make "$*"

2) Find out *why* they're doing a make of the kernel, and then calling your
script that *again* does a make of the kernel, instead of just calling your
script and being done with it.  This sounds like you have a poorly designed
build environment, and *that* needs fixing instead of kbuild.  There's really
an upper limit to how much kbuild is able to help a 3rd-party script writer who
has users who can't follow directions. There's just too many ways they can do
things that will cause a rebuild - they can do a make, then run a 'make
menuconfig' and change some important setting, then call your script and wham
you end up rebuilding the kernel anyhow.


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2011-04-16 15:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  7:13 Kbuild: how to cleanly retrieve information compilation about the last build Francis Moreau
2011-04-16  8:05 ` Francis Moreau
2011-04-16 13:59   ` Sam Ravnborg
2011-04-16 14:04     ` Francis Moreau
2011-04-16 14:33       ` Valdis.Kletnieks
2011-04-16 14:45         ` Francis Moreau
2011-04-16 15:08           ` Valdis.Kletnieks [this message]
2011-04-16 15:47             ` Francis Moreau
2011-04-16 15:57               ` Francis Moreau
2011-04-16 19:46                 ` Valdis.Kletnieks
2011-04-16 19:54                   ` Francis Moreau
2011-04-16 14:50       ` Sam Ravnborg
2011-04-16  8:26 ` Américo Wang
2011-04-16 14:00   ` Francis Moreau
2011-04-17  4:57     ` Américo Wang
2011-04-17 10:27       ` Francis Moreau
2011-04-19 19:24         ` Jonathan Neuschäfer

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=62853.1302966525@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=francis.moro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).