On 2016-09-19 17:49, Alexey Brodkin wrote: > So with help of our IT guys I was able to get both libssl and libcrypto of > the same version in /usr/local/lib > but now another problem hits me. CMake determines openssl version reading > opensslv.h file where ever it is found. > > In my case there're no headers in "/usr/local" tree instead there's one in > "/usr/include/openssl" which is a part > of openssl 1.0.1x installation that exist in "/usr/lib64" folder. > > So in absence of libssl.pc in "staging_dir/host/lib/pkgconfig/" it is a real > nightmare to get > cmake configured and built with multiple openssl versions installed on the > host. > > In that light I'm wondering why don't we build openssl for host? > What's even more interesting why OpenSSL building for host was once > introduced in > https://git.lede-project.org/?p=source.git;a=commit;h=c8ad508d37297400364ee276733de90d29e94778 > and almost immediately after was reverted by > https://git.lede-project.org/?p=source.git;a=commit;h=82c182f828b3741c494d9014cedb9d0edd9af94e > ? I guess it did not work properly back then. We do have tools/libressl now, but it is only used on Darwin at the moment. Maybe we should enable it unconditionally and add proper dependencies instead of introducing more search path hacks.
- Felix _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
