Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Petr Vorel <pevik@seznam.cz>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ltp-testsuite: bump version to 20230127
Date: Sat, 28 Jan 2023 22:55:43 +0100	[thread overview]
Message-ID: <20230128225543.16657dc4@windsurf> (raw)
In-Reply-To: <20230127223256.132401-1-pevik@seznam.cz>

Hello Petr,

On Fri, 27 Jan 2023 23:32:56 +0100
Petr Vorel <pevik@seznam.cz> wrote:

> From: Petr Vorel <petr.vorel@gmail.com>
> 
> Remove musl related sysinfo.h patch. This Buildroot specific workaround
> is not needed any more (kernel got fixed in a85cbe6159ff ("uapi: move
> constants from <linux/kernel.h> to <linux/const.h>") in v5.11, some time
> took to rebuilt Buildroot toolchains, but even that was more than year
> ago).

Sorry, but this explanation is not entirely clear to me. Do you mean
that only toolchains with kernel headers >= 5.11 will no longer have
the problem? We definitely need to support toolchains that have kernel
headers < 5.11.

> NOTE: I'd like to add /opt/ltp/runltp-ng (tools/runltp-ng/runltp-ng in
> source, from [1]) symlink to /usr/bin (that should be trivial).
> The tool should have only Python 3.6+ (no external modules so far)
> and while we (LTP upstream developers) would recommend to not use it on
> SUT (guest), where LTP is being run, but on host, we agreed to put
> runltp-ng on both sides SUT (target package) and on host (host package).
> But whole thing might take me more time thus posting updated package
> without it.

In the context of Buildroot, I guess it makes sense to be able to start
the LTP test suite directly on the target, so indeed it would make
sense to have runltp-ng on the target. However, you could also have a
host package to install runltp-ng on the host for those who want to run
it on their machine, and control the execution of the tests on their
target.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-01-28 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 22:32 [Buildroot] [PATCH 1/1] package/ltp-testsuite: bump version to 20230127 Petr Vorel
2023-01-28 21:55 ` Thomas Petazzoni via buildroot [this message]
2023-01-28 22:26   ` Petr Vorel
2023-01-28 22:36   ` Petr Vorel

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=20230128225543.16657dc4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=pevik@seznam.cz \
    --cc=thomas.petazzoni@bootlin.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