From 6413fcde4fe0272eee469aaf41c8bb1d6e6a270f Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Fri, 17 Aug 2018 11:44:39 +0200 Subject: Add --with-nonshared-cflags option to configure --- manual/install.texi | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'manual') diff --git a/manual/install.texi b/manual/install.texi index df32b39..eab4b0d 100644 --- a/manual/install.texi +++ b/manual/install.texi @@ -117,6 +117,20 @@ 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-nonshared-cflags=@var{cflags} +Use additional compiler flags @var{cflags} to build the parts of the +library which are always statically linked into applications and +libraries even with shared linking (that is, the object files contained +in @file{lib*_nonshared.a} libraries). The build process will +automatically use the appropriate flags, but this option can be used to +set additional flags required for building applications and libraries, +to match local policy. For example, if such a policy requires that all +code linked into applications must be built with source fortification, +@samp{--with-nonshared-cflags=-Wp,-D_FORTIFY_SOURCE=2} will make sure +that the objects in @file{libc_nonshared.a} are compiled with this flag +(although this will not affect the generated code in this particular +case and potentially change debugging information and metadata only). + @c disable static doesn't work currently @c @item --disable-static @c Don't build static libraries. Static libraries aren't that useful these -- cgit v1.1