From: Matt Caswell <matt@openssl.org>
Date: Fri, 25 Aug 2017 13:14:27 +0000 (+0100)
Subject: Clarify the meaning of no-stdio in INSTALL
X-Git-Tag: OpenSSL_1_1_0g~86
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=5a4bb0de9e8cc4562f3ef34676b81f66843304fc;hp=b9377bd080108beba7231eeb5ea21bb50a20f651;p=oweals%2Fopenssl.git

Clarify the meaning of no-stdio in INSTALL

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/4259)

(cherry picked from commit 219b4643e40ada993730c55ae2c09815f89b4a2d)
---

diff --git a/INSTALL b/INSTALL
index b03643fffd..27271de433 100644
--- a/INSTALL
+++ b/INSTALL
@@ -408,8 +408,9 @@
                    has an impact when not built "shared".
 
   no-stdio
-                   Don't use any C "stdio" features. Only libcrypto and libssl
-                   can be built in this way. Using this option will suppress
+                   Don't use anything from the C header file "stdio.h" that
+                   makes use of the "FILE" type. Only libcrypto and libssl can
+                   be built in this way. Using this option will suppress
                    building the command line applications. Additionally since
                    the OpenSSL tests also use the command line applications the
                    tests will also be skipped.