From: Richard Levitte <levitte@openssl.org>
Date: Mon, 22 Feb 2016 09:16:50 +0000 (+0100)
Subject: Rewrite CHANGES to add some commentary about the "pic" option
X-Git-Tag: OpenSSL_1_1_0-pre4~564
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9de94148780d4b84765849896d831be62b30fc33;p=openssl

Rewrite CHANGES to add some commentary about the "pic" option

Reviewed-by: Rich Salz <rsalz@openssl.org>
---

diff --git a/CHANGES b/CHANGES
index 66e653e58d..3baef73171 100644
--- a/CHANGES
+++ b/CHANGES
@@ -5,13 +5,17 @@
  Changes between 1.0.2f and 1.1.0  [xx XXX xxxx]
 
   *) Configuration change; it's now possible to build dynamic engines
-     without having to build shared libraries and vice versa.  The
-     only requirement for building dynamic engines is the presence of
-     the DSO module, so configuring "disable-dso" will automatically
-     disable dynamic engines.  Dynamic engines are enabled by default,
-     and can be disabled with "disable-dynamic-engine".
-     This only applies to the engines in engines/, those in
-     crypto/engine/ will always be built into libcrypto (i.e. "static").
+     without having to build shared libraries and vice versa.  This
+     only applies to the engines in engines/, those in crypto/engine/
+     will always be built into libcrypto (i.e. "static").
+
+     Building dynamic engines is enabled by default; to disable, use
+     the configuration option "disable-dynamic-engine".
+
+     The only requirements for building dynamic engines is the
+     presence of the DSO module and building with position independent
+     code, so they will also automatically be disabled if configuring
+     with "disable-dso" or "disable pic".
 
      The macros OPENSSL_NO_STATIC_ENGINE and OPENSSL_NO_DYNAMIC_ENGINE
      are also taken away from openssl/opensslconf.h, as they are
@@ -24,6 +28,10 @@
      object files.  This means other libraries that use routines from
      libcrypto / libssl can be made into shared libraries regardless
      of how OpenSSL was configured.
+
+     If this isn't desirable, the configuration options "disable-pic"
+     or "no-pic" can be used to disable the use of PIC.  This will
+     also disable building shared libraries and dynamic engines.
      [Richard Levitte]
 
   *) Removed JPAKE code.  It was experimental and has no wide use.