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/release/2.35/master] INSTALL: Rephrase -with-default-link documentation
Date: Tue, 26 Apr 2022 13:27:21 +0000 (GMT)	[thread overview]
Message-ID: <20220426132721.AE6623858C83@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e5cf8ccca655c0eb831574785a6087f3950852eb

commit e5cf8ccca655c0eb831574785a6087f3950852eb
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Apr 26 14:22:10 2022 +0200

    INSTALL: Rephrase -with-default-link documentation
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    (cherry picked from commit c935789bdf40ba22b5698da869d3a4789797e09f)

Diff:
---
 INSTALL             |  8 ++++----
 manual/install.texi | 10 +++++-----
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/INSTALL b/INSTALL
index b68884ccd6..237a2f9482 100644
--- a/INSTALL
+++ b/INSTALL
@@ -90,10 +90,10 @@ if 'CFLAGS' is specified it must enable optimization.  For example:
      library will still be usable, but functionality may be lost--for
      example, you can't build a shared libc with old binutils.
 
-'--with-default-link=FLAG'
-     With '--with-default-link=yes', the build system does not use a
-     custom linker script for linking shared objects.  The default for
-     FLAG is the opposite, 'no', because the custom linker script is
+'--with-default-link'
+     With '--with-default-link', the build system does not use a custom
+     linker script for linking shared objects.  The default is
+     '--without-default-link', because the custom linker script is
      needed for full RELRO protection.
 
 '--with-nonshared-cflags=CFLAGS'
diff --git a/manual/install.texi b/manual/install.texi
index fcfb6901e4..5feccfb6ed 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -117,11 +117,11 @@ 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}, the build system does not use a
-custom linker script for linking shared objects.  The default for
-@var{FLAG} is the opposite, @samp{no}, because the custom linker script
-is needed for full RELRO protection.
+@item --with-default-link
+With @code{--with-default-link}, the build system does not use a custom
+linker script for linking shared objects.  The default is
+@code{--without-default-link}, because the custom linker script is
+needed for full RELRO protection.
 
 @item --with-nonshared-cflags=@var{cflags}
 Use additional compiler flags @var{cflags} to build the parts of the


                 reply	other threads:[~2022-04-26 13:27 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=20220426132721.AE6623858C83@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: 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).