From: Alejandro Colomar <alx@kernel.org>
To: Fangrui Song <maskray@google.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] ld.so.8: Correct linker option name
Date: Sat, 15 Jul 2023 18:42:43 +0200 [thread overview]
Message-ID: <3879502b-90f7-c445-cc68-30f53f1c86fe@kernel.org> (raw)
In-Reply-To: <20230714070043.275611-1-maskray@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1287 bytes --]
Hi Fangrui,
On 2023-07-14 09:00, Fangrui Song wrote:
> The linker option that sets the DF_1_NODEFLIB flag is -z nodefaultlib
> instead of -z nodeflib.
Does -z nodeflib exist? Please mention that in your commit message.
Thanks,
Alex
>
> Signed-off-by: Fangrui Song <maskray@google.com>
> ---
> man8/ld.so.8 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man8/ld.so.8 b/man8/ld.so.8
> index 1c9a13f56..351913bd8 100644
> --- a/man8/ld.so.8
> +++ b/man8/ld.so.8
> @@ -83,7 +83,7 @@ From the cache file
> which contains a compiled list of candidate shared objects previously found
> in the augmented library path.
> If, however, the binary was linked with the
> -.B \-z nodeflib
> +.B \-z nodefaultlib
> linker option, shared objects in the default paths are skipped.
> Shared objects installed in hardware capability directories (see below)
> are preferred to other shared objects.
> @@ -97,7 +97,7 @@ and then
> and then
> .IR /usr/lib64 .)
> If the binary was linked with the
> -.B \-z nodeflib
> +.B \-z nodefaultlib
> linker option, this step is skipped.
> .\"
> .SS Dynamic string tokens
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-15 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 7:00 [PATCH] ld.so.8: Correct linker option name Fangrui Song
2023-07-15 16:42 ` Alejandro Colomar [this message]
2023-07-15 18:19 ` Fangrui Song
2023-07-16 0:46 ` Alejandro Colomar
2023-07-16 18:24 ` Fangrui Song
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=3879502b-90f7-c445-cc68-30f53f1c86fe@kernel.org \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=maskray@google.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