From: Petr Vorel <pvorel@suse.cz>
To: "Bird, Tim" <Tim.Bird@sony.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>,
"automated-testing@lists.yoctoproject.org"
<automated-testing@lists.yoctoproject.org>
Subject: Re: [LTP] [Automated-testing] [RFC PATCH 1/3] runltp: Deprecate, add info about kirk
Date: Mon, 10 Jun 2024 18:54:40 +0200 [thread overview]
Message-ID: <20240610165440.GA780610@pevik> (raw)
In-Reply-To: <SA3PR13MB63722C60AE789DABBCB3A311FDC62@SA3PR13MB6372.namprd13.prod.outlook.com>
Hi Tim,
> In that case, would kirk or python be required on the target?
> I presume that ltx runs on the target, and that is it a native app?
Yes.
> What are its dependencies?
IMHO no dependencies, except C toolchain. Our openSUSE spec file [1] list
nothing.
Running make on sources [2] show just:
cc -pedantic -W -Wall -Imsgpack \
msgpack/message.c msgpack/unpack.c ltx.c main.c -o ltx
I.e. just plain source code without dependencies.
Kind regards,
Petr
[1] https://build.opensuse.org/projects/benchmark:ltp:devel/packages/ltx/files/ltx.spec?expand=1
[2] https://github.com/linux-test-project/ltx/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-06-10 16:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 14:24 [LTP] [RFC PATCH 0/3] Deprecate runltp (please use kirk) Petr Vorel
2024-06-07 14:24 ` [LTP] [RFC PATCH 1/3] runltp: Deprecate, add info about kirk Petr Vorel
2024-06-07 14:50 ` [LTP] [Automated-testing] " Richard Purdie
2024-06-07 15:45 ` Cyril Hrubis
2024-06-07 16:08 ` Richard Purdie
2024-06-07 16:28 ` Bird, Tim
2024-06-07 16:48 ` Cyril Hrubis
2024-06-07 16:35 ` Cyril Hrubis
2024-06-07 17:00 ` Richard Purdie
2024-06-07 17:33 ` Cyril Hrubis
2024-06-07 21:17 ` Bird, Tim
2024-06-10 7:14 ` Andrea Cervesato via ltp
2024-06-10 15:32 ` Bird, Tim
2024-06-10 16:14 ` Petr Vorel
2024-06-11 12:28 ` Cyril Hrubis
2024-06-11 8:42 ` Cyril Hrubis
2024-06-10 9:22 ` Cyril Hrubis
2024-06-10 15:51 ` Bird, Tim
2024-06-10 16:54 ` Petr Vorel [this message]
2024-06-10 16:55 ` Petr Vorel
[not found] ` <17D79A236EC1FFC3.15678@lists.yoctoproject.org>
2024-06-12 7:53 ` Cyril Hrubis
2024-07-08 9:26 ` Petr Vorel
2024-06-08 20:32 ` Tim Orling
2024-06-10 19:54 ` Petr Vorel
2024-08-28 9:02 ` [LTP] " Cyril Hrubis
2024-08-28 12:31 ` Petr Vorel
2024-06-07 14:24 ` [LTP] [RFC PATCH 2/3] ltpmenu: Remove legacy script Petr Vorel
2024-08-28 8:52 ` Cyril Hrubis
2024-06-07 14:24 ` [LTP] [RFC PATCH 3/3] doc/old: Remove man pages Petr Vorel
2024-08-28 8:56 ` Cyril Hrubis
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=20240610165440.GA780610@pevik \
--to=pvorel@suse.cz \
--cc=Tim.Bird@sony.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=ltp@lists.linux.it \
/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