[PATCH] Document that --enable-static-pie implies PIE

[H.J. Lu]

To build static PIE, all .o files are compiled with -fPIE.  Since
--enable-static-pie is designed to provide additional security hardening
benefits, it also implies that dynamic PIE is created by default for
better security hardening.

OK for master?

H.J.
---
	* manual/install.texi: Document that --enable-static-pie
	implies PIE.
	* INSTALL: Regenerated.
---
 INSTALL             | 3 ++-
 manual/install.texi | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/INSTALL b/INSTALL
index 9a1404bd3c..cae574e5e3 100644
--- a/INSTALL
+++ b/INSTALL
@@ -93,7 +93,8 @@ will be used, and CFLAGS sets optimization options for the compiler.
      programs as well as static tests are built as static PIE, except
      for those marked with no-pie.  The resulting glibc can be used with
      the GCC option, -static-pie, which is available with GCC 8 or
-     above, to create static PIE.
+     above, to create static PIE. This option also implies that dynamic
+     position independent executable (PIE) is created by default.
 
 '--disable-profile'
      Don't build libraries with profiling information.  You may want to
diff --git a/manual/install.texi b/manual/install.texi
index fb956b5d6a..95eea19459 100644
--- a/manual/install.texi
+++ b/manual/install.texi
@@ -123,7 +123,8 @@ address without help from a dynamic linker.  All static programs as
 well as static tests are built as static PIE, except for those marked
 with no-pie.  The resulting glibc can be used with the GCC option,
 -static-pie, which is available with GCC 8 or above, to create static
-PIE.
+PIE.  This option also implies that dynamic position independent
+executable (PIE) is created by default.
 
 @item --disable-profile
 Don't build libraries with profiling information.  You may want to use
-- 
2.14.3