summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/valgrind
AgeCommit message (Collapse)Author
2015-05-23valgrind: remove arm tests that don't compileDave Lerner
[Yocto #7453] Corrects the original commit for the patch that removed ARM ptest CFLAGS settings. Since the flags could be set by a user, the flags should be kept in place during compilation. By keeping the original up-stream CFLAGS for the tests, then additional tests successfully compile for all tested ARM tunings. However, there were still two tests listed below that did not compile for any beaglebone tuning that is valid for valgrind. With the updated patch, the set of excluded ARM ptests and their respective build failures are: intdiv - fails for all beaglebone tunings with 2 errors: {standard input}:(40 or 41): Error: selected processor does not support Thumb mode `udiv r3,r9,r10' {standard input}:(72 or 73): Error: selected processor does not support Thumb mode `sdiv r3,r9,r10' vcvt_fixed_float_VFP - fails for all beaglebone tunings in one of two ways: with neon tuning (-mfpu=neon) fails with Internal Compiler Error without neon tuning fails with 3 errors: {standard input}:33: Error: selected FPU does not support instruction -- `vcvt.f32.s32 s15,s15,#1' {standard input}:58: Error: selected FPU does not support instruction -- `vcvt.f32.s32 s15,s15,#32' {standard input}:136: Error: selected FPU does not support instruction -- `vcvt.f32.u32 s15,s15,#1' After applying this commit, the valgrind ARM ptests compile without errors for tunings: armv7[t][hf][b][-neon] cortexa8[t][hf][-neon] where the tuning [option] was successfully compiled, both with and without the 'option', and in combination with all other options. Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-04-06valgrind: add configure option to build only 32-bit or 64-bit componentsKrishnanjanappa, Jagadeesh
Building both 32-bit and 64-bit binaries in valgrind at a time would lead to following QA issue as below, (snip) ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpreload_exp-sgcheck-x86-linux.so ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/getoff-x86-linux ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpreload_core-x86-linux.so ERROR: QA Issue: Architecture did not match (62 to 3) on ${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpreload_memcheck-x86-linux.so -- CUT -- hence perform only one type of build 32-bit or 64-bit, but not both. Signed-off-by: Krishnanjanappa, Jagadeesh <jagadeesh.krishnanjanappa@caviumnetworks.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-24valgrind: enable build for MIPSAndreas Oberritter
Since 3.8.0, valgrind supports MIPS32. MIPS64 was added in 3.9.0. Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-20valgrind: enable building on 4.x kernelMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-02-17valgrind: add glibc-2.21 to glibc.patchMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-14meta: enable parallel build for several recipesRobert Yang
I used a for loop to build these packages more than 520 times, these recipes never failed. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2015-02-07valgrind: depends on boost when ptestRobert Yang
Fixed: drd/tests/boost_thread.cpp:5:38: fatal error: boost/thread/condition.hpp: No such file or directory #include <boost/thread/condition.hpp> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2014-12-11valgrind: update to 3.10.1Kai Kang
Update valgrind from 3.10.0 to 3.10.1 which is a bug fix release. It fixes various bugs reported in 3.10.0 and backports fixes for all reported missing AArch64 ARMv8 instructions and syscalls from the trunk. Add dependency perl-module-file-glob for ptest subpackage. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-12-05valgrind: Upgrade to 3.10.0Saul Wold
Rebase existing patches Add patch to fix rpath issue with ptest Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-10-10valgrind: Enforce 30 seconds limit for each testTudor Florea
Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-09-10valgrind: backport enabling for glibc 2.20Ross Burton
Now that we're running glibc 2.20 not 2.19, backport the configure.ac fixes from upstream. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-01recipes: Remove references to eglibcKhem Raj
change use of eglibc related variabled to glibc equivalents Signed-off-by: Khem Raj <raj.khem@gmail.com>
2014-08-28valgrind/oprofile/systemd: no bashism in run-ptestRobert Yang
There is no bashism in the scripts, so use /bin/sh, and add /bin/sh interpreter for systemd's run-ptest. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-25Upstream-Status CleanupsSaul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-25Globally replace 'base_contains' calls with 'bb.utils.contains'Otavio Salvador
The base_contains is kept as a compatibility method and we ought to not use it in OE-Core so we can remove it from base metadata in future. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-20valgrind: integration of regression tests to ptestDave Lerner
Modifies valgrind's regression test framework to be compatible with the yocto PTEST framework as follows: * existing recipe valgrind*bb adds new methods: do_compile_ptest and do_install_ptest. * new file run-ptest adds the wrapper interface to the valgrind regression test script vg_regtest. * existing valgrind regression test script 'vg_regtest' changes to report the status of the valgrind component tests in the format that PTEST expects, instead of the valgrind formats, but only when vg_regtest is invoked with an optional --yocto-ptest argument * four new patches disable building tests that don't compile with the yocto compiler and default options. See the patches for details. Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-02-18valgrind: Add glibc 2.19 awarenessKhem Raj
It wont compile otherwise and fail with errors e.g. Valgrind requires glibc version 2.2 - 2.17 ... Signed-off-by: Khem Raj <raj.khem@gmail.com>
2014-01-06valgrind: rrecommend libc6-dbg on all architecturesMike Crowe
It seems that valgrind requires debug symbols to be available on all architectures so there's no reason to treat arm and powerpc specially. Ensuring that libc6-dbg is installed avoids errors like this on x86: valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind: On Debian, Ubuntu: libc6-dbg valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Cannot continue -- exiting now. Sorry. Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-12-21valgrind: upgrade to 3.9.0Cristiana Voicu
Changed patches directory to "valgrind"; Removed 4 patches because they were merged upstream; Updated 2 patches because now it has configure.ac instead of .in; Changed license md5 for 2 files because of a small change for copyright year Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22valgrind: Backport patch for eglibc 2.18Saul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18valgrind: added perl dependencyFelipe F. Tonello
This is necessary since the valgrind package depends on /usr/bin/perl. This patch will fix this error while installing into rootfs: Computing transaction...error: Can't install valgrind-3.8.1-r8@armv7a_vfp_neon: no package provides /usr/bin/perl Signed-off-by: Felipe F. Tonello <eu@felipetonello.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-23valgrind: Fix out of tree buildsRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18valgrind: Fix case where ${B} != ${S}Richard Purdie
Fix out of tree builds by referring to the build object in ${B}. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-28valgrind: update to 3.8.1Radu Moisan
Changed license copyright notice 2011->2012 remove unnecessary patches built for x86, 86-64, ppc Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-01-25valgrind: explicitly disable MPI2 supportPaul Eggleton
We don't have support for this in OE-Core, so ensure we don't pick this up from the build host if e.g. openmpi development files happen to be installed there. Fixes [YOCTO #3726]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-09valgrind: update configure for eglibc 2.17Saul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-14valgrind_3.7.0.bb: fix missing leading space on _appendMatthew McClintock
Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-12valgrind: fix debug info reading error when do memcheck on ppc targetsZhenhua Luo
following is the error message: --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /lib/ld-2.13.so: --2263-- Can't make sense of .got section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /home/root/lzh: --2263-- Can't make sense of .data section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /usr/lib/valgrind/vgpreload_core-ppc32-linux.so: --2263-- Can't make sense of .data section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /usr/lib/valgrind/vgpreload_memcheck-ppc32-linux.so: --2263-- Can't make sense of .data section mapping --2263-- WARNING: Serious error when reading debug info --2263-- When reading debug info from /lib/libc-2.13.so: --2263-- Can't make sense of .data section mapping Signed-off-by: Zhenhua Luo <b19537@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-17valgrind: Fix build with eglibc 2.16Khem Raj
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-11valgrind: fix default.supp missing issueZhenhua Luo
When run valgrind, following error appears: ==2254== FATAL: can't open suppressions file "/usr/lib/valgrind/default.supp" Signed-off-by: Zhenhua Luo <b19537@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-24valgrind: Enable valgrind for armv7Samuel Stirtzel
Valgrind supports the armv7 architecture, this patch allows armv7 users to build and use Valgrind This patch was run-tested on a Gumstix Overo (armv7a cortex-a8) * The test consisted of running valgrinds memcheck (memory leakage detection), * and callgrind (profiling) on a Qt 4 application Signed-off-by: Samuel Stirtzel <s.stirtzel@googlemail.com>
2012-03-08valgrind: Support compilation without X11Mike Crowe
Only depend on X libraries if the distribution has X support. Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-02-10valgrind: Fixed Added-support-for-PPC-instructions-mfatbu-mfatbl.patch ↵Saul Wold
Upstream-Status Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-01-17valgrind: Update for eglibc 2.15Saul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-01-17add mfatbu/mfatbl instructions support in ValgrindAneesh Bansal
Upstream Status : Pending
2012-01-06valgrind: add powerpc to the compatible host and add ${TCLIBC}-dbg in ↵Zhenhua Luo
RRECOMMENDS-powerpc 1. add powerpc/powerpc64 into the compatible host list 2. valgrind requires the non-stripped libraries of ${TCLIBC}, so add ${TCLIBC}-dbg into RRECOMMENDS for powerpc Signed-off-by: Zhenhua Luo <b19537@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-04valgrind: Fix for automake updateRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-02valgrind: upgrade to 3.7.0Shane Wang
This patch is to upgrade valgrind to 3.7.0. The licenses are changed from "Copyright (C) 2000-2010 Julian Seward. All rights reserved." to "Copyright (C) 2000-2011 Julian Seward. All rights reserved." Signed-off-by: Shane Wang <shane.wang@intel.com>
2011-08-15valgrind: supporting on Linux kernel 3.xLin Tong
The old valgrind package do not support for Linux kernel 3.x, only for kernel 2.4 and 2.6. Now adding the configuration to the configure.in file to support Linux kernel 3.0. This commit fixes the problem in valgrind [YOCTO #1129] Signed-off-by: Lin Tong <tong.lin@intel.com>
2011-05-27License Field Cleanup: Non-standard field namesBeth Flanagan
I've cleaned up some odd license fields, fixed some license names and corrected some incorrect licenses. LICENSE really needs a pass through by the maintainers as some of the licensing is incorrect. Also, every license with Artistic should be gone through and noted as which version of Artistic. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
2011-04-28valgrind: upgrade to version 3.6.1Dongxiao Xu
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2010-12-09SRC_URI Checksums AdditionalsSaul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-11-18valgrind: Upgraded to version 3.6.0Dongxiao Xu
Remove valgrind_3.5.0-svn_r11264.patch.bz2 which replaces version 3.5.0 to r11264. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2010-09-02valgrind: fix perl scriptsQing He
svn version of valgrind uses #! @PERL@ for several perl scripts. However, PERL in autoconf doesn't distinguish host perl and target perl, causing STAGING_DIR_NATIVE be written in the output scripts. This causes unrunnable scripts, and fails FILERDEPENDS mechanism (thus also do_rootfs_rpm). Uses /usr/bin/perl instead to fix it. Signed-off-by: Qing He <qing.he@intel.com>
2010-08-27Major layout change to the packages directoryRichard Purdie
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>