From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Valgrind: update to 3.11.0
Date: Fri, 8 Jan 2016 16:57:03 +0200 [thread overview]
Message-ID: <cover.1452264916.git.alexander.kanavin@linux.intel.com> (raw)
This version of the patchset fixes the ppc32 build failures, and adds
Andre McCurdy's fixes for arm.
The following changes since commit 0f3ad7c77aa0f8bb7641af1886e1420cdfa8419f:
scripts/yocto-layer: Avoids duplication of "meta-" prefix (2016-01-07 13:52:21 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib akanavin/package-version-updates
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates
Alexander Kanavin (1):
valgrind: update to 3.11.0
Andre McCurdy (2):
valgrind: don't restrict to armv7a
valgrind: include aarch64 in COMPATIBLE_HOST
...s-that-fail-to-build-on-some-PPC32-config.patch | 51 +++++
...able-rt_sigpending-syscall-on-ppc64-linux.patch | 35 ---
.../valgrind/valgrind/0002-remove-rpath.patch | 35 +++
.../valgrind/0004-Fix-out-of-tree-builds.patch | 175 +++++++++++++++
...vg_test-wrapper-to-support-PTEST-formats.patch} | 87 ++++----
.../valgrind/enable.building.on.4.x.kernel.patch | 37 ----
.../valgrind/valgrind/force-nostabs.patch | 42 ----
.../recipes-devtools/valgrind/valgrind/glibc.patch | 44 ----
.../pass-maltivec-only-if-it-supported.patch | 68 ------
.../valgrind/remove-ppc-tests-failing-build.patch | 75 -------
.../valgrind/valgrind/sepbuildfix.patch | 235 ---------------------
.../{valgrind_3.10.1.bb => valgrind_3.11.0.bb} | 41 ++--
12 files changed, 329 insertions(+), 596 deletions(-)
create mode 100644 meta/recipes-devtools/valgrind/valgrind/0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch
create mode 100644 meta/recipes-devtools/valgrind/valgrind/0002-remove-rpath.patch
create mode 100644 meta/recipes-devtools/valgrind/valgrind/0004-Fix-out-of-tree-builds.patch
rename meta/recipes-devtools/valgrind/valgrind/{add-ptest.patch => 0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch} (80%)
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/enable.building.on.4.x.kernel.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/force-nostabs.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/glibc.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/pass-maltivec-only-if-it-supported.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/remove-ppc-tests-failing-build.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind/sepbuildfix.patch
rename meta/recipes-devtools/valgrind/{valgrind_3.10.1.bb => valgrind_3.11.0.bb} (72%)
--
2.6.4
next reply other threads:[~2016-01-08 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 14:57 Alexander Kanavin [this message]
2016-01-08 14:57 ` [PATCH 1/3] valgrind: update to 3.11.0 Alexander Kanavin
2016-01-08 14:57 ` [PATCH 2/3] valgrind: don't restrict to armv7a Alexander Kanavin
2016-01-13 2:13 ` dengke.du
2016-01-13 2:18 ` dengke.du
2016-01-13 3:23 ` Andre McCurdy
2016-01-13 5:00 ` Khem Raj
2016-01-08 14:57 ` [PATCH 3/3] valgrind: include aarch64 in COMPATIBLE_HOST Alexander Kanavin
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=cover.1452264916.git.alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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 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.