Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi,

I have submitted a patch for review:

    https://gerrit.libreoffice.org/3327

To pull it, you can do:

    git pull ssh://gerrit.libreoffice.org:29418/core refs/changes/27/3327/1

build: warn when configure with --with-tls=openssl

When expliciting openssl as tls implementation to
use, show a warning as there are still some pieces
of code that may depend on NSS or GNUTLS.

Change-Id: I2cfaaf09b5ad83837928f2648975db956b261c19
---
M configure.ac
1 file changed, 4 insertions(+), 0 deletions(-)



diff --git a/configure.ac b/configure.ac
index 512db80..470ec8d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -8098,6 +8098,10 @@
     openssl)
         AC_DEFINE(USE_TLS_OPENSSL)
         TLS=OPENSSL
+
+        # warn that OpenSSL has been selected but not all TLS code has this option
+        AC_MSG_WARN([TLS/SSL implementation to use is OpenSSL but some code may still be depending 
on NSS or GNUTLS])
+        add_warning "TLS/SSL implementation to use is OpenSSL but some code may still be depending 
on NSS or GNUTLS"
         ;;
     nss)
         AC_DEFINE(USE_TLS_NSS)

-- 
To view, visit https://gerrit.libreoffice.org/3327
To unsubscribe, visit https://gerrit.libreoffice.org/settings

Gerrit-MessageType: newchange
Gerrit-Change-Id: I2cfaaf09b5ad83837928f2648975db956b261c19
Gerrit-PatchSet: 1
Gerrit-Project: core
Gerrit-Branch: master
Gerrit-Owner: Andres Gomez <agomez@igalia.com>


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.