From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v2 2/2] Default to --with-default-link=no (bug 25812)
Date: Mon, 11 Apr 2022 17:16:47 +0200 [thread overview]
Message-ID: <878rsbvee8.fsf@igel.home> (raw)
In-Reply-To: <5203390058771f6b1ee27fddce1849a7903e95d9.1649689730.git.fweimer@redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 11 Apr 2022 17:09:39 +0200")
On Apr 11 2022, Florian Weimer via Libc-alpha wrote:
> diff --git a/manual/install.texi b/manual/install.texi
> index 29c52f2927..f240d1ae4d 100644
> --- a/manual/install.texi
> +++ b/manual/install.texi
> @@ -117,6 +117,12 @@ problem and suppress these constructs, so that the library will still be
> usable, but functionality may be lost---for example, you can't build a
> shared libc with old binutils.
>
> +@item --with-default-link=@var{FLAG}
> +With @code{--with-default-link=yes}, @theglibc{} does not use a custom
> +linker scipt for linking its individual shared objects. The default for
script
> +@var{FLAG} is the opposite, @samp{no}, because the custom linker script
> +is needed for full RELRO protection.
I don't think the description is correct. It's not the library that
uses the script, it's the build process.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-04-11 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 15:09 [PATCH v2 1/2] scripts: Add glibcelf.py module Florian Weimer
2022-04-11 15:09 ` [PATCH v2 2/2] Default to --with-default-link=no (bug 25812) Florian Weimer
2022-04-11 15:16 ` Andreas Schwab [this message]
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=878rsbvee8.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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: 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).