All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 4/9] elfutils: additional ptest fixes
Date: Mon, 27 Jan 2020 15:19:03 +0100	[thread overview]
Message-ID: <20200127141908.84922-4-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20200127141908.84922-1-alex.kanavin@gmail.com>

This should address ARM64 specific failures in particular.

eu-objdump is now installed on all architectures;
ptests fail in its absence and pass when it is present, so it's
useful at least in some scenarios in non-x86 architectures and
fails gracefully otherwise.

The original decision to exclude it was here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5283

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
 meta/recipes-devtools/elfutils/elfutils_0.178.bb | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-devtools/elfutils/elfutils_0.178.bb b/meta/recipes-devtools/elfutils/elfutils_0.178.bb
index 9393628dd13..8f5deb2c62a 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.178.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.178.bb
@@ -58,11 +58,7 @@ RDEPENDS_${PN}-ptest += "libasm libelf bash make coreutils ${PN}-binutils"
 
 EXTRA_OECONF_append_class-target += "--disable-tests-rpath"
 
-do_install_append() {
-	if [ "${TARGET_ARCH}" != "x86_64" ] && [ -z `echo "${TARGET_ARCH}"|grep 'i.86'` ];then
-		rm -f ${D}${bindir}/eu-objdump
-	fi
-}
+RDEPENDS_${PN}-ptest_append_libc-glibc = " glibc-utils"
 
 do_compile_ptest() {
 	cd ${B}/tests
@@ -139,6 +135,7 @@ INHIBIT_PACKAGE_STRIP_FILES = "\
     ${PKGD}${PTEST_PATH}/tests/elfstrmerge \
     ${PKGD}${PTEST_PATH}/tests/backtrace-child \
     ${PKGD}${PTEST_PATH}/tests/backtrace-data \
+    ${PKGD}${PTEST_PATH}/tests/backtrace-dwarf \
     ${PKGD}${PTEST_PATH}/tests/deleted \
     ${PKGD}${PTEST_PATH}/src/strip \
     ${PKGD}${PTEST_PATH}/src/addr2line \
-- 
2.17.1



  parent reply	other threads:[~2020-01-27 14:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 14:19 [PATCH 1/9] core-image-sato-sdk-ptest: do not pull in ptest-pkgs Alexander Kanavin
2020-01-27 14:19 ` [PATCH 2/9] default-distrovars.inc: add vfat to DISTRO_FEATURES Alexander Kanavin
2020-01-27 14:19 ` [PATCH 3/9] mdadm: correctly set up testing location for ptests Alexander Kanavin
2020-01-27 14:19 ` Alexander Kanavin [this message]
2020-01-27 14:19 ` [PATCH 5/9] meson: update 0.52.1 -> 0.53.0 Alexander Kanavin
2020-01-27 14:19 ` [PATCH 6/9] lttng-tools: install additional scripts needed for ptests Alexander Kanavin
2020-01-27 14:19 ` [PATCH 7/9] core-image-sato-sdk-ptest: use 2G of RAM Alexander Kanavin
2020-01-27 20:54   ` Khem Raj
2020-01-27 20:55     ` Alexander Kanavin
2020-01-27 21:02       ` Khem Raj
2020-01-27 21:46         ` Alexander Kanavin
2020-01-27 22:07           ` Khem Raj
2020-01-27 14:19 ` [PATCH 8/9] valgrind: fix the remaining ptest failures Alexander Kanavin
2020-01-27 15:53   ` akuster808
2020-01-27 16:25     ` Alexander Kanavin
2020-01-27 16:26       ` Alexander Kanavin
2020-01-28  1:02   ` Khem Raj
2020-01-27 14:19 ` [PATCH 9/9] lttng-tools: disable tests that sporadically fail Alexander Kanavin
2020-01-27 16:59   ` Jonathan Rajotte-Julien

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=20200127141908.84922-4-alex.kanavin@gmail.com \
    --to=alex.kanavin@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 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.