All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about the last build
Date: Sun, 17 Apr 2011 12:57:05 +0800	[thread overview]
Message-ID: <BANLkTinAres6c8JaHA0Nuijany4XXyv67A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinMh7bofvSNW0gEoqaKvs27-xDGpQ@mail.gmail.com>

On Sat, Apr 16, 2011 at 10:00 PM, Francis Moreau <francis.moro@gmail.com> wrote:
> On Sat, Apr 16, 2011 at 10:26 AM, Américo Wang <xiyou.wangcong@gmail.com> wrote:
>> So why not just put that line into your script?
>>
>
> Because this line was an _example_ of how the makefile could had been invoked.
>
> But the script has currently no idea how the previous invocation was
> made, hence my question.

You use a bad design, why not just pass these parameters to your script?
Something like,

$ ./your_script CC=my-gcc CFLAGS="-g -fwhatever"

or whatever you want.

Also, if you really have to read the previous command (I doubt),
you can use the `history` command.

  reply	other threads:[~2011-04-17  4:57 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
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 [this message]
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=BANLkTinAres6c8JaHA0Nuijany4XXyv67A@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=francis.moro@gmail.com \
    --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 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.