[MDEV-16014] Mariadb10.3 compile the WITH_SSL in cmake conflict between ssl.cmake and libmariadb. Created: 2018-04-25  Updated: 2018-04-25  Resolved: 2018-04-25

Status: Closed
Project: MariaDB Server
Component/s: Compiling, SSL
Affects Version/s: 10.2, 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Ze Yang Assignee: Sergei Golubchik
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

Mariadb10.3

ssl.cmake WITH_SSL=[yes|bundled|system|<path/to/custom/installation>]
libmariadb WITH_SSL=[ON|OPENSSAL|GNUTLS]

when build with DWITH_SSL=bundled,

CMake Error at /usr/share/cmake28/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
Could NOT find GnuTLS: Found unsuitable version "2.8.5", but required is at

when build with DWITH_SSL=OPENSSL

CMake Error at cmake/ssl.cmake:167 (MESSAGE):
Wrong option for WITH_SSL. Valid values are: bundled (use yassl), yes
(prefer os library if present, otherwise use bundled), system (use os
library), </path/to/custom/installation>

 Comments   
Comment by Sergei Golubchik [ 2018-04-25 ]

There is no conflict. If you compile MariaDB server (with libmariadb as a subdirectory), you use

 WITH_SSL=[yes|bundled|system|<path/to/custom/installation>]

values for the server, they'll be adjusted automatically for libmariadb. If you compile libmariady only (running cmake in libmariadb directory) then you use libmariadb WITH_SSL values.

The rule is, if the server is compiled with openssl, libmariadb will be compiled with openssl. If you don't want openssl, you get yassl in the server and gnutls in the libmariadb.

Generated at Thu Feb 08 08:25:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.