aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/valgrind
AgeCommit message (Collapse)Author
2017-01-09valgrind: skip for linux-gnux32Christopher Larson
valgrind doesn't support x32 at this time, so skip it for that host. (From OE-Core rev: b0764fc58e2ebe0555b71392a6fd177ecfd0be66) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-16meta: remove True option to getVar callsJoshua Lock
getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-12-16valgrind: make ld-XXX.so strlen intercept optionalJackie Huang
Hack: Depending on how glibc was compiled (e.g. optimised for size or built with _FORTIFY_SOURCE enabled) the strlen symbol might not be found in ld-XXX.so. Therefore although we should still try to intercept it, don't make it mandatory to do so. (From OE-Core rev: 84ec50e587e7464b260b1b189659b93b6dab0ef6) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-11-30valgrind: Use MIPS MACHINE_OVERRIDESZubair Lutfullah Kakakhel
The mipsarch* MACHINE_OVERRIDES can be used to pass the same parameters to MIPS pre-R2 and R6 ISA variants. Use them to reduce duplication in supporting MIPS R6 ISA. (From OE-Core rev: 85280798306c0c1b1f36e5a10394ffaa7c4041f9) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-11-15valgrind: Reduce duplication in MIPS variants.Zubair Lutfullah Kakakhel
Reduce duplication in MIPS variants now that the MACHINEOVERRIDES variable is defined (From OE-Core rev: fd96266da21f84b01c1b617f3bf8462f3d9dd84c) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-11-06valgrind: update to 3.12.0Alexander Kanavin
Remove backported gcc5-port.patch Remove 11_mips-link-tool.patch as there is nothing in the target file (or the entire source tree) that resembles anything contained in the patch. (From OE-Core rev: 221093e850fbc3c154e9069f1958384b59ba3f70) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-14valgrind: MIPS: Make toolchain basename genericZubair Lutfullah Kakakhel
For the hard float case, COMPATIBLE_HOST should be set to ".*-linux" since OE can support multiple distro layers, not just poky. (From OE-Core rev: ddcb08c6a8cb2187e98aa225b86777bb52c1d21e) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05valgrind: Disable for MIPS Soft FloatZubair Lutfullah Kakakhel
Valgrind doesn't build for MIPS soft float. Disable the build until the package has support for it. (From OE-Core rev: f45a2907ba621d5e87614adcc724838fd32ad8ba) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-05-13valgrind: Fix build with gcc6Khem Raj
(From OE-Core rev: d3eb2de1b522280d6a156319d54e59d85d59452b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-04-22valgrind: turn off the file level dependencyTudor Florea
Attempting to install ptest for valgrind fails with this error: error: Can't install valgrind-ptest-3.11.0-r0.1@ppce500mc: no package provides /this/is/a/bogus/interpreter/name This is because one of the tests contains a bogus interpreter path on purpose It is not enough to skip the QA warning about the missing dependency but the dependency have to be completely removed. Since this package contains oly tests it is safe to disable per file dependencies and rely on the ones per package. (From OE-Core rev: 916650b91656fac4effde6d260006ba15f8ba23a) Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-20valgrind: fix buildpath QA issueHongxu Jia
Pass DEBUG_FLAGS to SELECTED_OPTIMIZATION which fixes build path issue in DWARF. [YOCTO #8457] (From OE-Core rev: 7b75303e6df5d685c1b50c53c53af3962d6b3722) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-11valgrind: Make dep on glibc-utils conditional on TCLIBC = glibcKhem Raj
This helps with building valgrind for non-glibc systems (From OE-Core rev: ec590f1ace7e8124dd760e5c931ba981abfd774c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-15valgrind: Fix build with muslKhem Raj
(From OE-Core rev: 0ec5ac9453e037f3999f4fa57750f87270bb78d9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-24valgrind: remove unused valgrind-remove-rpath.patchAndre McCurdy
Replaced by 0002-remove-rpath.patch during the 3.10 -> 3.11 update. (From OE-Core rev: aab27d556adf15e05351ec1a9a3c8ccc51717c75) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-24valgrind: avoid neon for targets which don't support itAndre McCurdy
The sh-mem-random.c test app tries to use neon loads and stores to test 64-bit float copies when building for ARM. Allow it to do so if possible, but fallback to C when building for ARM targets which don't support neon. (From OE-Core rev: 2194bbfe287412449d85182a4e02c8884c83170f) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-24valgrind: re-enable ARM intdiv and vcvt_fixed_float_VFP testsAndre McCurdy
The intdiv test has been partially fixed upstream and the vcvt_fixed_float_VFP test can be fixed with a similar approach, ie ensuring that it is always compiled with appropriate -march/-mcpu/-mfpu flags to support the instructions being tested. For tests requiring armv7ve instructions, ensure that we set both -march=armv7ve and -mcpu=cortex-a15 (since some TUNE_CCARGS may set -march=armv7-a and adding -mcpu=cortex-a15 alone is not enough to over-ride that). See similar cases in none/tests/arm/Makefile.am (From OE-Core rev: 3e94af90d90f6db6bab66ae87a47b31f3a0474f6) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-24valgrind: let valgrind determine its own optimisation flagsAndre McCurdy
Valgrind likes to control its own optimisation flags. It generally defaults to -O2 but uses -O0 for some specific test apps etc. Passing our own flags (via CFLAGS) means we interfere with that. Giving valgrind control of optimisation is hopefully an even better solution than the previous one of forcing -O0 for all tests. http://git.openembedded.org/openembedded-core/commit/?h=master-next&id=98c4a3ffb8dca10739be600e8d6df7fb6aa4958f (From OE-Core rev: 1c8ed8dada8d3399bd825d6f34fc440ce793ec4e) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-19valgrind: make it explicit that valgrind supports armv7a and aboveAndre McCurdy
Despite rumours to the contrary, valgrind really does require armv7a or above. (From OE-Core rev: b6135ece3249a37b67fbc00b00557cc270291e5b) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-11valgrind: include aarch64 in COMPATIBLE_HOSTAndre McCurdy
Valgrind has supported aarch64 since v3.10.0. (From OE-Core rev: 04beae24db3cbea6d5ec8f2b181d312d625d7c37) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-11valgrind: update to 3.11.0Alexander Kanavin
LICENSE checksums are changed due to a change in FSF address, or copyright years update. Added patches: 0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch replaces remove-ppc-tests-failing-build.patch and removes only those tests that are known to break the build on ppc32 configurations tested by poky autobuilders Rebased patches: sepbuildfix.patch rebased to 0004-Fix-out-of-tree-builds.patch add-ptest.patch rebased to 0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch Removed patches: force-nostabs.patch removed because it's patching lines that have been removed upstream remove-ppc-tests-failing-build.patch replaced with 0001-Remove-tests-that-fail-to-build-on-some-PPC32-config.patch enable.building.on.4.x.kernel.patch removed because the problem is fixed upstream glibc.patch removed for the same reason Removed backports: pass-maltivec-only-if-it-supported.patch 0001-valgrind-Enable-rt_sigpending-syscall-on-ppc64-linux.patch (From OE-Core rev: 9ce9c157a61442dc19fc5c6ef2737d2583fa6284) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-11valgrind: don't restrict to armv7aAndre McCurdy
Valgrind has been tested on armv5te/qemuarm, so it seems that valgrind's configure check for armv7 is over cautious. (From OE-Core rev: d68e47993277fa4fe18419b0b391bc53b1c4cdca) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-07valgrind: Define __UCLIBC__ for uclibc based systemsKhem Raj
Helps configure valgrind for uclibc targets otherwise it tries to assume funcitons that are implemented in glibc like __free_res (From OE-Core rev: 928973960d1e4d0797fe3569a07f6265368a6aff) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-12-16meta: more removals of redunant FILES_${PN}-dbgRoss Burton
In some recipes overly-split -dbg packages were merged into PN-dbg. Unless there's a very good reason, recipes should have a single -dev and -dbg package. (From OE-Core rev: a3b000643898d7402b9e57c02e8d10e677cc9722) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-12-12valgrind: import Debian link_tool patch for MIPSAndre McCurdy
Without this patch, valgrind 3.10.1 fails to run on MIPS: | root@bcm97425vms:~# valgrind /bin/ls | valgrind: mmap(0x400000, 700416) failed in UME with error 22 (Invalid argument). | valgrind: this can be caused by executables with very large text, data or bss segments. Original Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777704 (From OE-Core rev: 652c5ae2c8317dcd93ada409365eeb56ceb54d0b) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-12meta: Fix Upstream-Status statementsRoss Burton
Fix a variety of problems such as typos, bad punctuations, or incorrect Upstream-Status values. (From OE-Core rev: bd220fe6ce8c3a0805f13a14706d3130ea872604) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-03valgrind: enable rt_sigpending syscall on ppc64 linuxLi Zhou
When running one application under Valgrind on ppc64 arch, we got a missing syscall error. Get upstream patch from valgrind website to enable rt_sigpending syscall on ppc64 linux. (From OE-Core rev: 5d8f865d34aef6fb821e025da56a0a3c0656c49d) Signed-off-by: Li Zhou <li.zhou@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-19valgrind: build ptests without optimizationsDave Lerner
This commit changes the both CFLAGS and CXXFLAGS when building the valgrind ptest binaries by appending -O0, forcing no optimizations instead of the default -O2. For qemux86-64, this change results in FAIL/PASS ratio improvements from 149/394 to 58/485. It is evident that the expected result files were generated from regression tests binaries built without optimizations. [ YOCTO #8063 ] (From OE-Core rev: 98c4a3ffb8dca10739be600e8d6df7fb6aa4958f) Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-16valgrind: Fix build with glibc 2.22Khem Raj
(From OE-Core rev: addc26fb193d3fd259f10aaaae3b0de2f21c81f5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-08valgrind: build with altivec only if it supportedKai Kang
(From OE-Core rev: 9992208ad7fdf27703e9470fa6b80ab94274b3f6) Signed-off-by: Ting Liu <ting.liu@freescale.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Cherry-pick from branch dizzy. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-07valgrind: fix typo in valgrind-remove-rpath.patchAndre McCurdy
(From OE-Core rev: 603ea4e564bae7922adb185074dcc283d2d9dea3) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-05-24valgrind: 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. (From OE-Core rev: 2fb0edcb47a14e47780d545f60885b36e71fca71) Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-04-08valgrind: 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. (From OE-Core rev: 53afa26655d0b5f75ef2dd6bccef76281a14655c) Signed-off-by: Krishnanjanappa, Jagadeesh <jagadeesh.krishnanjanappa@caviumnetworks.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-25valgrind: enable build for MIPSAndreas Oberritter
Since 3.8.0, valgrind supports MIPS32. MIPS64 was added in 3.9.0. (From OE-Core rev: 13d2f0c8cd71a636de16ef33c546af7b208115bd) 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
(From OE-Core rev: e75d1d76949f944367d06bea82f519fdecda3ca3) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-17valgrind: add glibc-2.21 to glibc.patchMartin Jansa
(From OE-Core rev: 68ccb00b024efccb70efffc80a57b819f10a95e0) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-15meta: enable parallel build for several recipesRobert Yang
I used a for loop to build these packages more than 520 times, these recipes never failed. (From OE-Core rev: 7957c5bc2771a763d26e50e716733c6335cef3c2) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-08valgrind: 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> (From OE-Core rev: 5650ece64f55044a8fd7fa3fce692dfb17006f8f) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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. (From OE-Core rev: 65e15a1d4304bd3677a79d9b4c5a7a771dfd42d5) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-05valgrind: Upgrade to 3.10.0Saul Wold
Rebase existing patches Add patch to fix rpath issue with ptest (From OE-Core rev: 80b7db50d191c27c8ea78206140a4fa23adcf292) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-10valgrind: Enforce 30 seconds limit for each testTudor Florea
(From OE-Core rev: ae9a89fc1beac13f30395d191954fd70c3a9f85e) Signed-off-by: Tudor Florea <tudor.florea@enea.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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. (From OE-Core rev: 3a98dd15f19034a1837210f764310c195f9906e1) 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 (From OE-Core rev: fd15d6e0c8da75951a91d4467eda23c229b1026d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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. (From OE-Core rev: 62d455f89fb1d2c22cf987bdbb56a55e6d031ce0) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-25Upstream-Status CleanupsSaul Wold
(From OE-Core rev: ea438b58c9a90e4c3147f99d63a9afc66963c5a1) 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. (From OE-Core rev: d83b16dbf0862be387f84228710cb165c6d2b03b) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-21valgrind: 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. (From OE-Core rev: d4438e421f448cdb7e25c038d657bbebc1b6486e) Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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 ... (From OE-Core rev: cc90cbc6d36b9f15a461b877b44c7498c2061744) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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. (From OE-Core rev: 92bb949465feb39b2460ea0ddb45f259ca8baecc) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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. (From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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 (From OE-Core rev: 57794c201aa732392a135e03e04faf18929f645f) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>