On Mon, Dec 2, 2013, at 05:21 PM, Leif Walsh wrote:
look online for reports of problems with cmake and suse.
cmake is used quite reglarly with no issues, here anyway. it is, after all, used for the MariaDB build successfully, when TokuDB is disabled. re: rpath, if it's being used for the build phase to get at locally installed libs, then I should note that I cmake with, cmake ..\ ... -DCMAKE_SKIP_BUILD_RPATH=0 \ -DCMAKE_BUILD_WITH_INSTALL_RPATH=1 \ -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=1 \ ... these were (still are?) necessary to properly use & run-time link ssl libs external to the default sys paths -- e.g., ssl installed in /usr/local/ssl, so, together, cmake .. -LAH | egrep -i "crypto|ssl|rpath|suffix" -- suffixes <.a;.so> -- OPENSSL_INCLUDE_DIR = /usr/local/ssl/include -- OPENSSL_LIBRARIES = /usr/local/ssl/lib64/libssl.so -- CRYPTO_LIBRARY = /usr/local/ssl/lib64/libcrypto.so -- OPENSSL_MAJOR_VERSION = 1 -- SSL_LIBRARIES = /usr/local/ssl/lib64/libssl.so;/usr/local/ssl/lib64/libcrypto.so;dl CMAKE_SKIP_INSTALL_RPATH:BOOL=NO CMAKE_SKIP_RPATH:BOOL=NO CRYPTO_LIBRARY:FILEPATH=/usr/local/ssl/lib64/libcrypto.so OPENSSL_INCLUDE_DIR:PATH=/usr/local/ssl/include OPENSSL_LIBRARIES:FILEPATH=/usr/local/ssl/lib64/libssl.so OPENSSL_ROOT_DIR:PATH=/usr/local/ssl // path to custom SSL installation WITH_SSL_PATH:PATH=/usr/local/ssl results in mysqld --version mysqld Ver 10.0.7-MariaDB-log for Linux on x86_64 (Source distribution) ldd `which mysqld` `which mysql` | egrep "ssl|crypto|bin/" /usr/local/mariadb/bin/mysqld: libssl.so.1.0.0 => /usr/local/ssl/lib64/libssl.so.1.0.0 (0x00007fd80fea9000) libcrypto.so.1.0.0 => /usr/local/ssl/lib64/libcrypto.so.1.0.0 (0x00007fd80fabd000) /usr/local/mariadb/bin/mysql: libssl.so.1.0.0 => /usr/local/ssl/lib64/libssl.so.1.0.0 (0x00007f2d5e65d000) libcrypto.so.1.0.0 => /usr/local/ssl/lib64/libcrypto.so.1.0.0 (0x00007f2d5e271000) atm, I'm staring suspiciously at that "-DCMAKE_SKIP_BUILD_RPATH=0" ... darx