public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] INSTALL: Rephrase -with-default-link documentation
Date: Mon, 25 Apr 2022 17:58:54 -0400	[thread overview]
Message-ID: <fefad4e9-7ee9-862c-e4ac-341cc528db74@redhat.com> (raw)
In-Reply-To: <87sfq5s9aj.fsf@oldenburg.str.redhat.com>

On 4/22/22 06:27, Florian Weimer via Libc-alpha wrote:

LGTM. Double checked --with-default-link (use-default-link=yes) and 
--without-default-link (use-default-link=no)

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

> ---
>  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
> 


-- 
Cheers,
Carlos.


      reply	other threads:[~2022-04-25 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 10:27 Florian Weimer
2022-04-25 21:58 ` Carlos O'Donell [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=fefad4e9-7ee9-862c-e4ac-341cc528db74@redhat.com \
    --to=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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).