From: Cristiana Voicu <cristiana.voicu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Package upgrades
Date: Fri, 20 Dec 2013 11:43:48 +0200 [thread overview]
Message-ID: <cover.1387532399.git.cristiana.voicu@intel.com> (raw)
I've tested the new version of valgrind on local autobuilder on build-appliance,
nightly-arm, mips, ppc, x86, x86-64. Also, I've built on my machine a core-image-sato-sdk
for x86, and I've tested if the correct version was installed. I've done some simple tests, too.
The following changes since commit 9daa1de753e58b7f678e68cf307f6028c0c79a6a:
qemu/local.conf.sample: Add sdl PACKAGECONFIG (2013-12-16 12:13:59 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib cvoicu/work
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=cvoicu/work
Cristiana Voicu (1):
valgrind: upgrade to 3.9.0
.../configure-with-newer-glibc.patch | 41 --------------------
.../valgrind/valgrind-3.8.1/eglibc-2.18.patch | 27 -------------
.../fix_issue_caused_by_ccache.patch | 32 ---------------
.../valgrind-3.8.1/fix_unsupporting_kernel_3.patch | 26 -------------
...upport-for-PPC-instructions-mfatbu-mfatbl.patch | 0
.../fixed-perl-path.patch | 0
.../{valgrind-3.8.1 => valgrind}/sepbuildfix.patch | 26 ++++++-------
.../{valgrind_3.8.1.bb => valgrind_3.9.0.bb} | 12 ++----
8 files changed, 17 insertions(+), 147 deletions(-)
delete mode 100644 meta/recipes-devtools/valgrind/valgrind-3.8.1/configure-with-newer-glibc.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind-3.8.1/eglibc-2.18.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind-3.8.1/fix_issue_caused_by_ccache.patch
delete mode 100644 meta/recipes-devtools/valgrind/valgrind-3.8.1/fix_unsupporting_kernel_3.patch
rename meta/recipes-devtools/valgrind/{valgrind-3.8.1 => valgrind}/Added-support-for-PPC-instructions-mfatbu-mfatbl.patch (100%)
rename meta/recipes-devtools/valgrind/{valgrind-3.8.1 => valgrind}/fixed-perl-path.patch (100%)
rename meta/recipes-devtools/valgrind/{valgrind-3.8.1 => valgrind}/sepbuildfix.patch (96%)
rename meta/recipes-devtools/valgrind/{valgrind_3.8.1.bb => valgrind_3.9.0.bb} (76%)
--
1.7.9.5
next reply other threads:[~2013-12-20 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 9:43 Cristiana Voicu [this message]
2013-12-20 9:43 ` [PATCH 1/1] valgrind: upgrade to 3.9.0 Cristiana Voicu
-- strict thread matches above, loose matches on Subject: below --
2013-12-23 10:16 [PATCH 0/1] Package upgrades Cristiana Voicu
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.1387532399.git.cristiana.voicu@intel.com \
--to=cristiana.voicu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox