From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] apr/openssl10: Enable ccache for them
Date: Tue, 11 Dec 2018 17:15:48 +0800 [thread overview]
Message-ID: <38f38d90-a742-784b-c817-68eafe6c9fdd@windriver.com> (raw)
In-Reply-To: <20181210083836.GA1470@jama>
On 12/10/18 4:38 PM, Martin Jansa wrote:
> On Sun, Dec 09, 2018 at 06:24:23PM -0800, Robert Yang wrote:
>> The work well now.
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb | 3 ---
>> meta/recipes-support/apr/apr_1.6.5.bb | 1 -
>> 2 files changed, 4 deletions(-)
>>
>> diff --git a/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb b/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb
>> index 6518dac..1986cf2 100644
>> --- a/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb
>> +++ b/meta/recipes-connectivity/openssl/openssl10_1.0.2q.bb
>> @@ -76,9 +76,6 @@ EXTRA_OEMAKE = "${@bb.utils.contains('PACKAGECONFIG', 'manpages', '', 'OE_DISABL
>>
>> export OE_LDFLAGS = "${LDFLAGS}"
>>
>> -# openssl fails with ccache: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12810
>> -CCACHE = ""
>> -
>> TERMIO ?= "-DTERMIO"
>> TERMIO_libc-musl = "-DTERMIOS"
>>
>> diff --git a/meta/recipes-support/apr/apr_1.6.5.bb b/meta/recipes-support/apr/apr_1.6.5.bb
>> index c2f5900..ed93a7e 100644
>> --- a/meta/recipes-support/apr/apr_1.6.5.bb
>> +++ b/meta/recipes-support/apr/apr_1.6.5.bb
>> @@ -40,7 +40,6 @@ CACHED_CONFIGUREVARS += "ac_cv_file__dev_zero=yes"
>> # Otherwise libtool fails to compile apr-utils
>> # x86_64-linux-libtool: compile: unable to infer tagged configuration
>> # x86_64-linux-libtool: error: specify a tag with '--tag'
>> -CCACHE = ""
>
> Remove the comment as well.
Thanks, will fix it in V2.
// Robert
>
>> PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)}"
>> PACKAGECONFIG[ipv6] = "--enable-ipv6,--disable-ipv6,"
>> --
>> 2.10.2
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2018-12-11 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 2:24 [PATCH 0/4] ccache.bbclass: Refactor it to make it more reliable Robert Yang
2018-12-10 2:24 ` [PATCH 1/4] base.bbclass: Remove invalid ccache related code Robert Yang
2018-12-10 10:29 ` Richard Purdie
2018-12-11 9:24 ` Robert Yang
2018-12-11 9:44 ` richard.purdie
2018-12-11 10:12 ` Robert Yang
2018-12-11 10:42 ` richard.purdie
2018-12-11 10:59 ` Yang, Liezhi
2018-12-12 2:59 ` Robert Yang
2018-12-13 3:41 ` Robert Yang
2018-12-10 2:24 ` [PATCH 2/4] ccache.bbclass: Refactor it to make it more reliable Robert Yang
2018-12-10 8:55 ` Martin Hundebøll
2018-12-11 9:18 ` Robert Yang
2018-12-13 2:47 ` Robert Yang
2018-12-10 16:16 ` Richard Purdie
2018-12-11 9:35 ` Robert Yang
2018-12-10 2:24 ` [PATCH 3/4] apr/openssl10: Enable ccache for them Robert Yang
2018-12-10 8:38 ` Martin Jansa
2018-12-11 9:15 ` Robert Yang [this message]
2018-12-10 2:24 ` [PATCH 4/4] cmake.bbclass/goarch.bbclass: Set CCACHE_DISABLE Robert Yang
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=38f38d90-a742-784b-c817-68eafe6c9fdd@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=martin.jansa@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