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 10:33:54 -0400 [thread overview]
Message-ID: <61322.1302964434@localhost> (raw)
In-Reply-To: Your message of "Sat, 16 Apr 2011 16:04:57 +0200." <BANLkTi=wdDsrV+ikoxLhnTpLhQTuVKW0mA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Sat, 16 Apr 2011 16:04:57 +0200, Francis Moreau said:
> For example a user can do:
>
> $ make ARCH=arm CROSS_COMPILE=arm-linux-
>
> Then call my script and expect it to pass the same flags to make.
Odd, don't ARCH and CROSS_COMPILE get saved in the .config?
What *are* you trying to pass to kbuild that isn't either saved in the .config
or deduced at build time (the cross-compile gets saved, stuff like "where is
python?" is deduced). Is there a *real* problem you're hitting here, or is
it merely theoretical?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-04-16 14:34 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 [this message]
2011-04-16 14:45 ` Francis Moreau
2011-04-16 15:08 ` Valdis.Kletnieks
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=61322.1302964434@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 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.