From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: swee.aun.khor@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] openssl: Support musl-x32 build
Date: Sat, 22 Jul 2017 09:20:16 +0100 [thread overview]
Message-ID: <1500711616.22282.110.camel@linuxfoundation.org> (raw)
In-Reply-To: <82e8a77a71e50e2cc00318226a42ced7d6a0909c.1500495522.git.swee.aun.khor@intel.com>
On Wed, 2017-07-19 at 13:29 -0700, swee.aun.khor@intel.com wrote:
> From: sweeaun <swee.aun.khor@intel.com>
>
> Support musl-x32 build which to build openssl with 32 bits.
>
> Signed-off-by: sweeaun <swee.aun.khor@intel.com>
> ---
> meta/recipes-connectivity/openssl/openssl.inc | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl.inc
> b/meta/recipes-connectivity/openssl/openssl.inc
> index ce295e8..a56bd6e 100644
> --- a/meta/recipes-connectivity/openssl/openssl.inc
> +++ b/meta/recipes-connectivity/openssl/openssl.inc
> @@ -66,7 +66,8 @@ do_configure () {
> case $os in
> linux-gnueabi |\
> linux-gnuspe |\
> - linux-musl*)
> + linux-musleabi |\
> + linux-muslspe)
> os=linux
> ;;
> *)
I think there is a bug here if os=linux-musl which likely caused:
https://autobuilder.yocto.io/builders/nightly-musl/builds/364
Cheers,
Richard
next prev parent reply other threads:[~2017-07-22 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 20:29 [PATCH 0/2] Support MUSL-x32 build for openssl and libffi swee.aun.khor
2017-07-19 20:29 ` [PATCH 1/2] openssl: Support musl-x32 build swee.aun.khor
2017-07-22 8:20 ` Richard Purdie [this message]
2017-07-24 2:28 ` Khor, Swee Aun
2017-07-19 20:29 ` [PATCH 2/2] libffi: " swee.aun.khor
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=1500711616.22282.110.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=swee.aun.khor@intel.com \
/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