From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4 v3] valgrind: update to 3.11.0 + fixes
Date: Thu, 17 Dec 2015 20:41:59 -0800 [thread overview]
Message-ID: <1450413723-22208-1-git-send-email-armccurdy@gmail.com> (raw)
Rebase Alexander's valgrind 3.11.0 update patch to current
oe-core master (remove redunant FILES_${PN}-dbg line) plus
fix additional issues.
This time based on v2 of Alexander's 3.11.0 update patch...
Alexander Kanavin (1):
valgrind: update to 3.11.0
Andre McCurdy (3):
security_flags.inc: disable -fstack-protector-XXX for valgrind
valgrind: don't restrict to armv7a
valgrind: include aarch64 in COMPATIBLE_HOST
meta/conf/distro/include/security_flags.inc | 2 +-
...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} | 42 ++--
12 files changed, 278 insertions(+), 599 deletions(-)
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%)
--
1.9.1
next reply other threads:[~2015-12-18 4:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 4:41 Andre McCurdy [this message]
2015-12-18 4:42 ` [PATCH 1/4 v3] valgrind: update to 3.11.0 Andre McCurdy
2015-12-18 4:42 ` [PATCH 2/4 v3] security_flags.inc: disable -fstack-protector-XXX for valgrind Andre McCurdy
2015-12-18 5:16 ` Khem Raj
2015-12-18 5:48 ` Andre McCurdy
2015-12-18 5:55 ` Khem Raj
2015-12-18 4:42 ` [PATCH 3/4 v3] valgrind: don't restrict to armv7a Andre McCurdy
2015-12-18 5:17 ` Khem Raj
2015-12-18 5:56 ` Andre McCurdy
2015-12-18 6:00 ` Khem Raj
2015-12-18 6:11 ` Andre McCurdy
2015-12-18 4:42 ` [PATCH 4/4 v3] valgrind: include aarch64 in COMPATIBLE_HOST Andre McCurdy
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=1450413723-22208-1-git-send-email-armccurdy@gmail.com \
--to=armccurdy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox