From: Francis Moreau <francis.moro@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about the last build
Date: Sat, 16 Apr 2011 10:05:43 +0200 [thread overview]
Message-ID: <BANLkTi=2aRu6x3uZtpMvPd2BSpYpkT5yfQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=GXro_xEiRyzZY86kWM9duJ3KAUQ@mail.gmail.com>
Hello Sam,
Maybe could suggest something, it would be great.
Thanks
On Thu, Apr 14, 2011 at 9:13 AM, Francis Moreau <francis.moro@gmail.com> wrote:
> Hello,
>
> I'm writing a script to automatise some parts of my kernel compilation process.
>
> From those scripts I'd like to be able to call the top makefile the
> same way it had been called during its last invocation.
>
> For example, if Ido:
>
> $ make CC=my-gcc CFLAGS="-g -fwhatever"
>
> I would like to retrieve the "CC=my-gcc CFLAGS="-g -fwhatever" part of
> the last invocation so my script can call make with the same
> arguments.
>
> Is this possible ?
>
> Thanks for any ideas
> --
> Francis
>
--
Francis
next prev parent reply other threads:[~2011-04-16 8:05 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 [this message]
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
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='BANLkTi=2aRu6x3uZtpMvPd2BSpYpkT5yfQ@mail.gmail.com' \
--to=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).