public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/fw/glibc-hwcaps] elf: Use the term "program interpreter" in the ld.so help message Date: Thu, 1 Oct 2020 16:54:01 +0000 (GMT) [thread overview] Message-ID: <20201001165401.43698398B89E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7f4601c6481c6bb2526fece150c2dc0948b4bd05 commit 7f4601c6481c6bb2526fece150c2dc0948b4bd05 Author: Florian Weimer <fweimer@redhat.com> Date: Mon Jun 8 17:44:52 2020 +0200 elf: Use the term "program interpreter" in the ld.so help message This is the term that the ELF standard itself uses. Diff: --- elf/dl-usage.c | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/elf/dl-usage.c b/elf/dl-usage.c index 7355b094a5..35a1c0c455 100644 --- a/elf/dl-usage.c +++ b/elf/dl-usage.c @@ -51,17 +51,17 @@ _dl_help (const char *argv0, struct dl_main_state *state) { _dl_printf ("\ Usage: %s [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]\n\ -You have invoked `ld.so', the helper program for shared library executables.\n\ -This program usually lives in the file `/lib/ld.so', and special directives\n\ -in executable files using ELF shared libraries tell the system's program\n\ -loader to load the helper program from this file. This helper program loads\n\ -the shared libraries needed by the program executable, prepares the program\n\ -to run, and runs it. You may invoke this helper program directly from the\n\ +You have invoked 'ld.so', the program interpreter for dynamically-linked\n\ +ELF programs. Usually, the program interpreter is invoked automatically\n\ +when a dynamically-linked executable is started.\n\ +\n\ +You may invoke the program interpreter program directly from the\n\ command line to load and run an ELF executable file; this is like executing\n\ -that file itself, but always uses this helper program from the file you\n\ -specified, instead of the helper program file specified in the executable\n\ -file you run. This is mostly of use for maintainers to test new versions\n\ -of this helper program; chances are you did not intend to run this program.\n\ +that file itself, but always uses the invoked program interpreter you\n\ +invoked, instead of the program interpreter specified in the executable\n\ +file you run. Invoking the program interpreter directly provides access to\n\ +additional diagnostics, and changing the dynamic linker behavior without\n\ +setting environment variables (which would be inherted by subprocesses).\n\ \n\ --list list all dependencies and how they are resolved\n\ --verify verify that given object really is a dynamically linked\n\
reply other threads:[~2020-10-01 16:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201001165401.43698398B89E@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@sourceware.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: linkBe 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).