[CONC-115] Revision 166 of mariadbclient is not compatible with Openssl-1.0.1h Created: 2014-11-14  Updated: 2014-11-18  Resolved: 2014-11-18

Status: Closed
Project: MariaDB Connector/C
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1

Type: Bug Priority: Major
Reporter: Abhishek Assignee: Georg Richter
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Windows 8, Visual studio 2010, Cmake version-2.8.11.2, Openssl version-1.0.1h

Attachments: Text File testingerrors.txt    

 Description   

Latest revision 166, on compiling from source with openssl gives linker error for many SSL related symbols. Most of the symbols used in ma_secure.obj are not compatible with Openssl version-1.0.1h.



 Comments   
Comment by Georg Richter [ 2014-11-14 ]

Please attach the output of cmake and build run.

Comment by Abhishek [ 2014-11-18 ]

Attached file shows Errors when using this library.

Comment by Abhishek [ 2014-11-18 ]

output of cmake-
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
E:\MOnyog\Documents\maraiadb_fix_new_32>cmake . -G "Visual Studio 10" -DWITH_OPE
NSSL=yes -DOPENSSL_ROOT_DIR=E:\MOnyog\Documents\maraiadb_fix_new_32\openssl -DOP
ENSSL_LIBRARIES=E:\MOnyog\Documents\maraiadb_fix_new_32\openssl -DOPENSSL_INCLUD
E_DIR=E:\MOnyog\Documents\maraiadb_fix_new_32\include\openssl
– CMAKE_C_FLAGS_DEBUG= /D_DEBUG /MTd /Zi /Ob0 /Od /RTC1
– CMAKE_C_FLAGS_RELEASE= /MT /O2 /Ob2 /D NDEBUG
– CMAKE_C_FLAGS_RELWITHDEBINFO= /MT /Zi /O2 /Ob1 /D NDEBUG
– MariaDB Connector/c configuration:
– CPack generation: ZIP
– SSL support: yes
– Experimental Sqlite support: OFF
– Zlib support: yes (using bundled zlib)
– Installation layout: DEFAULT
– Include files will be installed in /include/mariadb
– Libraries will be installed in /lib/mariadb
– Binaries will be installed in /bin
– Configuring done
– Generating done
– Build files have been written to: E:/MOnyog/Documents/maraiadb_fix_new_32

Comment by Georg Richter [ 2014-11-18 ]

Hi,

libmariadb doesn't link OpenSSL statically, so the location of the .dll files have to be in your PATH variable (likely your application also needs to link against openssl libs).

This is different to liibmysql, which uses by default the builtin yassl library. Since Yassl is GPL licensed, libmariadb can't use it.

For the 3.0 version (late spring 2015) we plan to add SChannel support ,so the libary will be able to use Windows native SSL stuff by default.

Generated at Thu Feb 08 03:02:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.