INSTALL: Rephrase -with-default-link documentation

Reviewed-by: Carlos O'Donell <carlos@redhat.com>
This commit is contained in:
Florian Weimer 2022-04-26 14:22:10 +02:00
parent 1305edd42c
commit c935789bdf
2 changed files with 9 additions and 9 deletions

View File

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

View File

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