From: Changqing Li <changqing.li@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/2] procps: support ptest when TCLIBC is glibc
Date: Fri, 27 Feb 2026 14:17:02 +0800 [thread overview]
Message-ID: <1f902e9e-e85b-43f1-91e7-8ed1d31f0846@windriver.com> (raw)
In-Reply-To: <7C785637-73B8-4927-8A7E-C689573CB8BD@arm.com>
On 2/26/26 21:13, Ross Burton wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Hi,
>
> On 24 Feb 2026, at 01:47, Changqing Li via lists.openembedded.org <changqing.li=windriver.com@lists.openembedded.org> wrote:
>> * 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.
> I filed a bug for musl support just now, https://gitlab.com/procps-ng/procps/-/issues/420. Please link to this in your changes.
OK. I will update the commit message in V2.
>
> I think we should build the tests for everything, and skip the few tests which break. In my testing in an alpine container there are five failing tests, but it seems that two of them are busybox related so we can resolve that with dependencies to pull in the proper tools.
Maybe we can add musl support later after upstream add musl support.
//Changqing
> Ross
next prev parent reply other threads:[~2026-02-27 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 1:47 [PATCH 1/2] procps: upgrade from 4.0.5 to 4.0.6 Changqing Li
2026-02-24 1:47 ` [PATCH 2/2] procps: support ptest when TCLIBC is glibc Changqing Li
2026-02-26 13:13 ` [OE-core] " Ross Burton
2026-02-27 6:17 ` Changqing Li [this message]
2026-02-27 6:49 ` [PATCH V2] " Changqing Li
2026-03-05 15:16 ` [OE-core] " Ross Burton
2026-03-06 4:05 ` [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=1f902e9e-e85b-43f1-91e7-8ed1d31f0846@windriver.com \
--to=changqing.li@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=mathieu.dubois-briand@bootlin.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