matthias sweertvaegher <[email protected]> writes: > On Mon, Apr 4, 2011 at 3:16 PM, Raphael Kubo da Costa <[email protected]> > wrote: >> By taking a quick look at the diff output between KDE's >> FindOpenSSL.cmake and CMake's FindOpenSSL.cmake, the only relevant >> difference I can see is that CMake's FindOpenSSL.cmake also looks for >> libcrypto besides libssl. > > that's indeed what I found out but I'm puzzled how you can build my > plasmoid without having the libcrypto linked in.. actually i make > cmake output the openssl libraries like this: > ssl libs = /usr/lib64/libssl.so;/usr/lib64/libcrypto.so > > Can you check if it outputs both libraries in your build environment? > When I use the KDE FindOpenSSL module I only get the libssl and not > libcrypto. That explains why it does not build on my (suse) system > unless I remove the KDE version.
I get "ssl libs = /usr/lib/libssl.so", with no mention to libcrypto.so in it. ldd does show that libssl.so depends on libcrypto.so here, and readelf tells me functions such as BIO_read are defined in libcrypto and referenced in libssl. >From your build log, it looks like OBS uses a lot of linking flags which are not used here, perhaps that's where the issue lies. In any case, I think it might make sense to sync KDE's FindOpenSSL.cmake with CMake's, or at least fetch this part of it from CMake. I'd like neundorf to have a final say on this, though, as he's the buildsystem demigod. > Or maybe the kde file does not take precedence over the system (cmake) > file in your case? I think it does, as only libssl.so was found. _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
