From: Markus Mayer <mmayer@broadcom.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/2] lmbench patches
Date: Thu, 13 Jun 2019 12:50:45 -0700 [thread overview]
Message-ID: <20190613195047.24870-1-mmayer@broadcom.com> (raw)
We recently stumbled upon two lmbench issues, one being discovered
while investigating the other.
- lmbench's scripts/build script is declared as /bin/sh script, but
uses bash only syntax which can lead to errors
- lmbench's install routine doesn't install the lmbench script itself
Here are two patches to address both issues.
Changes since v2:
- used GIT to generate the lmbench patch files, so they contain a
description and a signed-off-by line
- no changes to the actual code
Markus Mayer (2):
lmbench: mark scripts/build as bash script
lmbench: install the lmbench script on the target
...-scripts-build-use-bin-bash-as-shell.patch | 28 ++++++++++++++++++
...e-add-lmbench-to-list-of-executables.patch | 29 +++++++++++++++++++
2 files changed, 57 insertions(+)
create mode 100644 package/lmbench/0001-scripts-build-use-bin-bash-as-shell.patch
create mode 100644 package/lmbench/0002-src-Makefile-add-lmbench-to-list-of-executables.patch
--
2.17.1
next reply other threads:[~2019-06-13 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 19:50 Markus Mayer [this message]
2019-06-13 19:50 ` [Buildroot] [PATCH v2 1/2] lmbench: mark scripts/build as bash script Markus Mayer
2019-06-24 19:53 ` Peter Korsgaard
2019-06-13 19:50 ` [Buildroot] [PATCH v2 2/2] lmbench: install the lmbench script on the target Markus Mayer
2019-06-24 19:53 ` Peter Korsgaard
2019-06-22 8:15 ` [Buildroot] [PATCH v2 0/2] lmbench patches Thomas Petazzoni
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=20190613195047.24870-1-mmayer@broadcom.com \
--to=mmayer@broadcom.com \
--cc=buildroot@busybox.net \
/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