[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTinAres6c8JaHA0Nuijany4XXyv67A@mail.gmail.com>
Date: Sun, 17 Apr 2011 12:57:05 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Francis Moreau <francis.moro@...il.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about the
last build
On Sat, Apr 16, 2011 at 10:00 PM, Francis Moreau <francis.moro@...il.com> wrote:
> On Sat, Apr 16, 2011 at 10:26 AM, Américo Wang <xiyou.wangcong@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists