[oe] [PATCH][meta-oe] lmbench: Added 3.0-a9 version recipe files

[Tom Rini]

On Mon, Aug 22, 2011 at 12:13 PM, Paul Menzel
<paulepanter at users.sourceforge.net> wrote:
> Dear Noor,
>
>
> please try to incorporate the following comments when sending the next
> version.
>
> Am Montag, den 22.08.2011, 19:32 +0500 schrieb Noor, Ahsan:
>> From: Noor Ahsan <noor_ahsan at mentor.com>
>>
>> * Added recipe file to build 3.0-a9 version.
>
> Please do not duplicate the commit summary in the commit message body
> and please use present tense.
>
>        lmbench: Add version 3.0-a9 (initial recipe)
>
>        • imported from oe.dev (rev goes here)
>
> What build configuration do you use?
>
>> Signed-off-by: Noor Ahsan <noor_ahsan at mentor.com>
>> ---
>>  .../lmbench-3.0-a9/update-results-script.patch     |  155 ++++++++++++++++++++
>>  meta-oe/recipes-support/lmbench/lmbench_3.0-a9.bb  |   75 ++++++++++
>>  2 files changed, 230 insertions(+), 0 deletions(-)
>>
>> diff --git a/meta-oe/recipes-support/lmbench/lmbench-3.0-a9/update-results-script.patch b/meta-oe/recipes-support/lmbench/lmbench-3.0-a9/update-results-script.patch
>> new file mode 100644
>> index 0000000..3feb657
>> --- /dev/null
>> +++ b/meta-oe/recipes-support/lmbench/lmbench-3.0-a9/update-results-script.patch
>> @@ -0,0 +1,155 @@
>> +Now that we have our binaries in /usr/bin rather than the normal
>> +lmbench hierarchy we need to update the scripts as well to bave well here.
>
> s/bave/behave/
>
> Did you send that patch upstream?

This is related to the OE-specific behavior of installing into
/usr/bin, etc, rather than dumping everything into /usr/share/lmbench
or similar.  For the Upstream-Status line :)

-- 
Tom