From: Philippe Gerum <rpm@xenomai.org>
To: liyinjie <liyinjie@sinsegye.com.cn>
Cc: xenomai@lists.linux.dev
Subject: Re: [PATCH] commands/evl: improve argument of help
Date: Sat, 07 Oct 2023 16:03:50 +0200 [thread overview]
Message-ID: <87ttr2edbk.fsf@xenomai.org> (raw)
In-Reply-To: <20231007112300.1352970-1-liyinjie@sinsegye.com.cn>
liyinjie <liyinjie@sinsegye.com.cn> writes:
> Hi all.
>
> Enter the command `evl --help`, output
>
> usage: evl [options] [<command> [<args>]]
> -P --prefix=<path> set command path prefix
> -v -V --version print library and required ABI versions
> -h --help this help
> evl: no 'help' command. Try 'evl --help'.
>
> This patch will fix incorrect output "evl: no 'help' command. Try 'evl --help'.".
>
This output means a problem with the installation, it looks like the
evl-help sub-command file is not there on your system. On a typical
installation with evl rooted at /usr, the following file should be
present:
root@blade-qemu-x86_64:~# ls -l /usr/libexec/evl/evl-help
-r-xr-x--- 1 root root 394 Mar 9 2018 /usr/libexec/evl/evl-help
With this file present, the output would be:
root@blade-qemu-x86_64:~# evl --help
usage: evl [options] [<command> [<args>]]
-P --prefix=<path> set command path prefix
-v -V --version print library and required ABI versions
-h --help this help
available commands:
check check kernel configuration
gdb debug EVL command plugin with GDB
ps report a snapshot of the current EVL threads
start start the EVL core
stop stop the EVL core
test run the EVL tests
trace ftrace control front-end for EVL
--
Philippe.
next prev parent reply other threads:[~2023-10-07 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 11:23 [PATCH] commands/evl: improve argument of help liyinjie
2023-10-07 14:03 ` Philippe Gerum [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-07 11:19 liyinjie
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=87ttr2edbk.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=liyinjie@sinsegye.com.cn \
--cc=xenomai@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).