From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 3/5] openssl: update to 1.1.1
Date: Wed, 11 Apr 2018 13:09:49 +0300 [thread overview]
Message-ID: <0de624d1-6617-97a7-244d-5d65b8bceadf@linux.intel.com> (raw)
In-Reply-To: <CAJ86T=X4cBT=RpXzvyuoOiFVX-fj_8tXO8y6JnAa08R_CBkKeA@mail.gmail.com>
On 04/11/2018 12:20 AM, Andre McCurdy wrote:
>> -#| engines/afalg/e_afalg.c: In function 'eventfd':
>> -#| engines/afalg/e_afalg.c:110:20: error: '__NR_eventfd' undeclared (first use in this function)
>> -#| return syscall(__NR_eventfd, n);
>> -#| ^~~~~~~~~~~~
>> -EXTRA_OECONF_aarch64 += "no-afalgeng"
>> +# This prevents openssl from using getrandom() which is not available on older glibc versions
>> +# (native versions can be built with newer glibc, but then relocated onto a system with older glibc)
>> +EXTRA_OECONF_class-native += "--with-rand-seed=devrandom"
>> +EXTRA_OECONF_class-nativesdk += "--with-rand-seed=devrandom"
>
> Better to avoid += with an over-ride since it doesn't do what most new
> users etc expect. Better to use _append instead (or just the over-ride
> on it's own, if over-riding the original value is what you intended to
> do).
Thanks, I will fix this. The whole += vs. _append is a design
shortcoming in bitbake I'd say, as it's a regular source of confusion,
and can't be automatically QA'd.
Alex
next prev parent reply other threads:[~2018-04-11 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 12:07 [RFC][PATCH 1/5] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version Alexander Kanavin
2018-04-10 12:07 ` [RFC][PATCH 2/5] cryptodev-tests: port to openssl 1.1 Alexander Kanavin
2018-04-10 12:07 ` [RFC][PATCH 3/5] openssl: update to 1.1.1 Alexander Kanavin
2018-04-10 21:20 ` Andre McCurdy
2018-04-11 10:09 ` Alexander Kanavin [this message]
2018-04-11 18:56 ` Andre McCurdy
2018-04-10 12:07 ` [RFC][PATCH 4/5] libressl: add a recipe to support openssh Alexander Kanavin
2018-04-11 8:38 ` Andre McCurdy
2018-04-11 10:03 ` Alexander Kanavin
2018-04-11 19:07 ` Andre McCurdy
2018-04-10 12:07 ` [RFC][PATCH 5/5] openssh: update to 7.7p1 and depend on libressl Alexander Kanavin
2018-04-10 12:34 ` ✗ patchtest: failure for "[RFC] openssl: rename openssl ..." and 4 more Patchwork
2018-04-10 12:43 ` [RFC][PATCH 1/5] openssl: rename openssl 1.0.x to openssl10 and make openssl 1.1.x the default version Martin Jansa
2018-04-10 12:39 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0de624d1-6617-97a7-244d-5d65b8bceadf@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox