From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: changqing.li@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V3] procps: support ptest when TCLIBC is glibc
Date: Wed, 28 Jan 2026 11:32:26 +0000 [thread overview]
Message-ID: <9b4c9e13e430e3cbf0a45fe15b5a361b63a2b250.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260127085808.1980602-1-changqing.li@windriver.com>
On Tue, 2026-01-27 at 16:58 +0800, Changqing Li via lists.openembedded.org wrote:
> From: Changqing Li <changqing.li@windriver.com>
>
> * support ptest for procps TCLIBC is glibc. The configure.ac only match
> LINUX as "linux-gnu", we can patch it to make test can run on musl lib
> system, but the upstream testsuite should only run on gnu libc host,
> some test cases only suitable for glibc, eg: Some of the error messages
> for free command on musl system is not the same as glibc system, which
> will make test failed. In order to avoid some other unexpected failure,
> just support ptest for glibc.
>
> * procps's testsuite use DejaGnu test framework. The testsuite is
> expected to run during build time, this implementation create the same
> folder structure as the testsuite expected to make it can work well.
>
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
> .../distro/include/ptest-packagelists.inc | 2 +
> meta/recipes-extended/procps/procps/run-ptest | 24 ++++++++
> meta/recipes-extended/procps/procps_4.0.5.bb | 57 ++++++++++++++++++-
> 3 files changed, 81 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-extended/procps/procps/run-ptest
This might trigger a ptest warning:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2990
Cheers,
Richard
next prev parent reply other threads:[~2026-01-28 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:27 [PATCH V2] procps: support ptest when TCLIBC is glibc changqing.li
2026-01-26 13:01 ` [OE-core] " Ross Burton
2026-01-27 8:57 ` Changqing Li
2026-01-27 8:58 ` [PATCH V3] " changqing.li
2026-01-28 11:32 ` Richard Purdie [this message]
2026-01-29 7:39 ` [OE-core] " Changqing Li
2026-01-29 7:48 ` [PATCH V4] " changqing.li
[not found] ` <188F2427284C7A56.4057262@lists.openembedded.org>
2026-02-09 1:58 ` [OE-core] " Changqing Li
[not found] ` <188E8AC794A362CA.3302988@lists.openembedded.org>
2026-01-27 9:06 ` [OE-core] [PATCH V3] " Changqing Li
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=9b4c9e13e430e3cbf0a45fe15b5a361b63a2b250.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=changqing.li@windriver.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