You are building something that requires openssl 1.0 (most likely
openssh, which is not compatible with 1.1). You have to exclude it
from your builds first.
Alex
2018-07-16 3:19 GMT+02:00 Russell Peterson :
> Hello,
>
> I’m looking to change to openssl version 1.1. I’m using the rocko branch.
>
Hello,
I’m looking to change to openssl version 1.1. I’m using the rocko branch. I
have set PREFERRED_VERSION_openssl to 1.1%… but it doesn’t seem to work.
Anyone?
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 1.1.% of openssl not available (for item openssl10)
N
Hi all,
Since December, glib is pulling python3 for codegen, which because of
BBCLASSEXTENDS, tries to build nativesdk-python3 which in turn tries to build
nativesdk-openssl, and it looks like openssl does not support it
SDK_MACHINE=x86_64-mingw32
There is a do_configure error and I get
Hello Khem,
thanks for the answer. I'm pretty sure now that it is an ssl problem
(see below).
On 26.06.2017 16:28, Khem Raj wrote:
On Sun, Jun 25, 2017 at 11:35 PM, Jakob Hasse
wrote:
Hello,
I'm trying to run the Mircosoft Azure IoT hub mqtt example
(iothub_client_sample_amqp or simliar)
On Fri, 2014-10-24 at 11:14 +0200, Jens Rehsack wrote:
> yesterday applied OpenSSL update on daisy
> (https://github.com/rdm-dev/poky/commit/27a877becf76a1410aa96c02a25bb885bfbddf04)
> fails to bitbake, because newly added *ptest* files does not exists. Further
> patches had been removed from rec
Hi,
yesterday applied OpenSSL update on daisy
(https://github.com/rdm-dev/poky/commit/27a877becf76a1410aa96c02a25bb885bfbddf04)
fails to bitbake, because newly added *ptest* files does not exists. Further
patches had been removed from recipe without removing the files themselves ...
The first
Thanks for the nfo. I'll go there and take a look.
--MarkE
On 7/24/2014 7:51 PM, Khem Raj wrote:
On Thu, Jul 24, 2014 at 5:44 PM, Mark Evans wrote:
question on the openssl recipes and openssl versions... Point me to the
correct distro if this is the incorrect spot to ask this...
We're current
On Thu, Jul 24, 2014 at 5:44 PM, Mark Evans wrote:
> question on the openssl recipes and openssl versions... Point me to the
> correct distro if this is the incorrect spot to ask this...
>
> We're currently on Danny, 1.3.2. In there, the openssl version is 1.0.0j.
> The openssl project is currentl
question on the openssl recipes and openssl versions... Point me to the
correct distro if this is the incorrect spot to ask this...
We're currently on Danny, 1.3.2. In there, the openssl version is
1.0.0j. The openssl project is currently promoting 1.0.1h. Due to the
multiple CVEs being relea
On 04/14/2014 07:41 AM, Martin Jansa wrote:
> On Mon, Apr 14, 2014 at 02:37:52PM +, Richard Schmitt wrote:
>> Does the Yocto project plan to have some response to the heartbleed exploit
>> in openssl in the near term? Has this already been addressed?
> It was already addressed for master, dai
On Monday 14 April 2014 16:41:21 Martin Jansa wrote:
> On Mon, Apr 14, 2014 at 02:37:52PM +, Richard Schmitt wrote:
> > Does the Yocto project plan to have some response to the heartbleed
> > exploit in openssl in the near term? Has this already been addressed?
>
> It was already addressed for
On Mon, Apr 14, 2014 at 02:37:52PM +, Richard Schmitt wrote:
> Does the Yocto project plan to have some response to the heartbleed exploit
> in openssl in the near term? Has this already been addressed?
It was already addressed for master, daisy, dora and dylan.
--
Martin 'JaMa' Jansa
Does the Yocto project plan to have some response to the heartbleed exploit in
openssl in the near term? Has this already been addressed?
Thanks,
Rich
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Fri, Oct 19, 2012 at 9:03 AM, Jerrod Peach wrote:
> In this case, it seemed openssl wanted to find a config to its original
> build location, but it wasn't allowed to find it in this case, because that
> directory was owned by a different user. Grepping through the binary and
> openssl's *.so
All,
I ran into an issue yesterday when trying to run the openssl binary that
comes out of the openssl-native package. I had previously built
openssl-native in another location as another user, and that sstate entry
was copied out to an sstate mirror. I then built openssl-native in my
personal w
The OpenSSL recipe halts saying it can't find find.pl however I have
File::Find installed which brings in file.pl as a perl module (find.pm).
Could anyone shed any light on why this might not be found?
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python func
16 matches
Mail list logo
