public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Randy Witt" <randy.e.witt@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Randy Witt <randy.e.witt@intel.com>,
	Randy Witt <randy.e.witt@linux.intel.com>
Subject: [PATCH 2/4] numactl: Remove COMPATIBLE_HOST restrictions
Date: Mon, 19 Oct 2020 14:42:12 -0700	[thread overview]
Message-ID: <20201019214214.2528690-3-randy.e.witt@linux.intel.com> (raw)
In-Reply-To: <20201019214214.2528690-1-randy.e.witt@linux.intel.com>

From: Randy Witt <randy.e.witt@intel.com>

Since there may be recipes that depend on libnuma, even though the
hardware doesn't support numa, remove the COMPATIBLE_HOST restrictions.

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
---
 meta/recipes-support/numactl/numactl_git.bb | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/meta/recipes-support/numactl/numactl_git.bb b/meta/recipes-support/numactl/numactl_git.bb
index 20b7fed8624..e45afe9ee86 100644
--- a/meta/recipes-support/numactl/numactl_git.bb
+++ b/meta/recipes-support/numactl/numactl_git.bb
@@ -23,9 +23,6 @@ SRC_URI = "git://github.com/numactl/numactl \
 
 S = "${WORKDIR}/git"
 
-# ARM does not currently support NUMA
-COMPATIBLE_HOST = "^((?!arm).*)$"
-
 do_install() {
     oe_runmake DESTDIR=${D} prefix=${D}/usr install
     #remove the empty man2 directory
-- 
2.26.2


  parent reply	other threads:[~2020-10-19 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 21:42 [PATCH 0/4] Upgrade rt-tests to v1.8 Randy Witt
2020-10-19 21:42 ` [PATCH 1/4] numactl: Add the recipe for numactl Randy Witt
2020-10-19 21:42 ` Randy Witt [this message]
2020-10-19 21:42 ` [PATCH 3/4] numactl: Skip the ptests when numa is not supported Randy Witt
2020-10-19 21:42 ` [PATCH 4/4] rt-tests: Update recipes to use 1.8 Randy Witt

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=20201019214214.2528690-3-randy.e.witt@linux.intel.com \
    --to=randy.e.witt@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.e.witt@intel.com \
    /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