Re: [OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

2018-08-01 Thread Andre McCurdy
On Wed, Aug 1, 2018 at 1:35 PM, Ryan Pabis (pabisr) via Openembedded-core wrote: > Alex, > > The library was precompiled by tail-f but I've also recompiled on Ubuntu > 16.04 with openssl 1.0.2n. In both cases the library crypto.so and > libconfd.so refer to libcrypto.so.1.0.0. > > Having a

Re: [OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

2018-08-01 Thread Ryan Pabis (pabisr) via Openembedded-core
Alex, The library was precompiled by tail-f but I've also recompiled on Ubuntu 16.04 with openssl 1.0.2n. In both cases the library crypto.so and libconfd.so refer to libcrypto.so.1.0.0. Having a pre-compiled library worked on krogoth and morty, but does not seem to work on rocko. Ryan On

Re: [OE-core] Why does Openssl 1.0.2n use libcrypto.so.1.0.2 and not libcrypto.so.1.0.0?

2018-08-01 Thread Alexander Kanavin
2018-08-01 20:20 GMT+02:00 Ryan Pabis (pabisr) via Openembedded-core : > I have a library that uses libcrypto.so.1.0.0 from openssl 1.0.2n, which is > the libcrypto.so version if you download the source code to ubuntu 16.04 > from openssl and compile. However, Yocto Rocko uses the same openssl