From: <kai.kang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH 2/3] libhugetlbfs: 1.19 -> 1.20
Date: Wed, 9 Nov 2016 15:58:52 +0800 [thread overview]
Message-ID: <20161109075853.12636-3-kai.kang@windriver.com> (raw)
In-Reply-To: <20161109075853.12636-1-kai.kang@windriver.com>
From: Kai Kang <kai.kang@windriver.com>
Upgrade libhugetlbfs from 1.19 to 1.20.
* Remove libhugetlbfs-avoid-using-restrict-as-var-name.patch which is
fixed in upstream.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
...ugetlbfs-avoid-using-restrict-as-var-name.patch | 34 ----------------------
.../libhugetlbfs/libhugetlbfs_git.bb | 5 ++--
2 files changed, 2 insertions(+), 37 deletions(-)
delete mode 100644 meta-oe/recipes-benchmark/libhugetlbfs/files/libhugetlbfs-avoid-using-restrict-as-var-name.patch
diff --git a/meta-oe/recipes-benchmark/libhugetlbfs/files/libhugetlbfs-avoid-using-restrict-as-var-name.patch b/meta-oe/recipes-benchmark/libhugetlbfs/files/libhugetlbfs-avoid-using-restrict-as-var-name.patch
deleted file mode 100644
index b77cfe1..0000000
--- a/meta-oe/recipes-benchmark/libhugetlbfs/files/libhugetlbfs-avoid-using-restrict-as-var-name.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-Avoid using keyword restrict as variable name which causes error with gcc 5.x:
-
-| hugeutils.c: In function '__lh_hugetlbfs_setup_env':
-| hugeutils.c:304:40: error: expected identifier or '(' before 'restrict'
-| char *p, *tok, *exe, buf[MAX_EXE+1], restrict[MAX_EXE];
-| ^
-
-Upstream-Status: Pending
-
-Signed-off-by: Kai Kang <kai.kang@windriver.com>
----
-diff --git a/hugeutils.c b/hugeutils.c
-index 53a7fbd..b9d7001 100644
---- a/hugeutils.c
-+++ b/hugeutils.c
-@@ -301,14 +301,14 @@ void hugetlbfs_setup_env()
-
- env = getenv("HUGETLB_RESTRICT_EXE");
- if (env) {
-- char *p, *tok, *exe, buf[MAX_EXE+1], restrict[MAX_EXE];
-+ char *p, *tok, *exe, buf[MAX_EXE+1], restricted[MAX_EXE];
- int found = 0;
-
- exe = get_exe_name(buf, sizeof buf);
- DEBUG("Found HUGETLB_RESTRICT_EXE, this exe is \"%s\"\n", exe);
-- strncpy(restrict, env, sizeof restrict);
-- restrict[sizeof(restrict)-1] = 0;
-- for (p = restrict; (tok = strtok(p, ":")) != NULL; p = NULL) {
-+ strncpy(restricted, env, sizeof restricted);
-+ restricted[sizeof(restricted)-1] = 0;
-+ for (p = restricted; (tok = strtok(p, ":")) != NULL; p = NULL) {
- DEBUG(" ...check exe match for \"%s\"\n", tok);
- if (strcmp(tok, exe) == 0) {
- found = 1;
diff --git a/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb b/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb
index 301b550..72553cf 100644
--- a/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb
+++ b/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb
@@ -7,10 +7,10 @@ DEPENDS = "sysfsutils perl"
RDEPENDS_${PN} += "bash perl python python-io python-lang python-subprocess python-resource ${PN}-perl"
RDEPENDS_${PN}-tests += "bash"
-PV = "2.19"
+PV = "2.20"
PE = "1"
-SRCREV = "426c22d65415fcb8927f68fbc5887e075a8dc40a"
+SRCREV = "e44180072b796c0e28e53c4d01ef6279caaa2a99"
SRC_URI = " \
git://github.com/libhugetlbfs/libhugetlbfs.git;protocol=https \
file://skip-checking-LIB32-and-LIB64-if-they-point-to-the-s.patch \
@@ -18,7 +18,6 @@ SRC_URI = " \
file://tests-Makefile-install-static-4G-edge-testcases.patch \
file://0001-run_test.py-not-use-hard-coded-path-.-obj-hugeadm.patch \
file://libhugetlbfs-elf_i386-avoid-search-host-library-path.patch \
- file://libhugetlbfs-avoid-using-restrict-as-var-name.patch \
file://Force-text-segment-alignment-to-0x08000000-for-i386-.patch \
"
--
2.10.1
next prev parent reply other threads:[~2016-11-09 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 7:58 [meta-oe][PATCH 0/3] Upgrade 3 benchmark packages kai.kang
2016-11-09 7:58 ` [PATCH 1/3] iozone3: 434 -> 465 kai.kang
2016-11-09 7:58 ` kai.kang [this message]
2016-11-09 7:58 ` [PATCH 3/3] phoronix-test-suite: 6.0.1 -> 6.6.1 kai.kang
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=20161109075853.12636-3-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-devel@lists.openembedded.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