From: "Randy Witt" <randy.e.witt@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: alex.kanavin@gmail.com
Subject: RFC: Upgrading rt-tests requires numactl
Date: Wed, 23 Sep 2020 10:22:49 -0700 [thread overview]
Message-ID: <711dd8de-1ea7-e3cd-d606-5f69faa7c8a3@linux.intel.com> (raw)
While looking into upgrading rt-tests to the latest version, on IRC, John
Kacur(the maintainer of rt-tests), recommended "that they use
unstable/devel/latest as the maintained stable branch".
I updated the recipes in
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rewitt/rt-tests-upgrade&id=551b25918d06c903fff22d76d5683b548c4f2e6f.
However, I know this won't work as is, due to the issues below.
The latest version of rt-tests requires the numa libraries for compilation via
this patch https://marc.info/?l=linux-rt-users&m=158335896221530&w=2. rt-tests
exists in oe-core, but numactl which provides libnuma/numa.h exists in
meta-openembedded.
Another issue is that ARM is removed from COMPATIBLE_HOST in
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/numactl/numactl_git.bb?h=master#n27.
This may be for legacy reasons, but libnuma can be installed on most
distributions running on an ARM host. Regardless, it would need to be changed to
allow for rt-tests on ARM.
I'm therefore trying to determine how to proceed to upgrade rt-tests. These are
the options I thought of, which are most likely not exhaustive.
1. Bring numactl into oe-core
2. move rt-tests out of oe-core
3. TMy to patch out the numa requirement and carry it forever(doesn't appear to
be a small task)
next reply other threads:[~2020-09-23 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 17:22 Randy Witt [this message]
2020-09-23 17:31 ` [OE-core] RFC: Upgrading rt-tests requires numactl Richard Purdie
2020-09-23 21:40 ` Ross Burton
2020-09-24 6:00 ` Khem Raj
2020-09-28 21:28 ` 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=711dd8de-1ea7-e3cd-d606-5f69faa7c8a3@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox