Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] rng-tools: 5 -> 6.6
Date: Sat, 10 Nov 2018 09:14:30 +0800	[thread overview]
Message-ID: <a1a2bb6a-7ace-086c-e4f2-bd91f7b7d9b7@windriver.com> (raw)
In-Reply-To: <5c0fe7734469e010f42c6d14477928c4f6599447.camel@linuxfoundation.org>

On 2018/11/10 上午6:50, richard.purdie@linuxfoundation.org wrote:
> On Fri, 2018-11-09 at 17:12 +0800, Hongxu Jia wrote:
>> -PACKAGECONFIG = "libgcrypt"
>> +PACKAGECONFIG ??= "libgcrypt libjitterentropy"
>>   PACKAGECONFIG_libc-musl = "libargp"
>>   PACKAGECONFIG[libargp] = "--with-libargp,--without-libargp,argp-standalone,"
>>   PACKAGECONFIG[libgcrypt] = "--with-libgcrypt,--without-libgcrypt,libgcrypt,"
>> +PACKAGECONFIG[libjitterentropy] = "--enable-jitterentropy,--disable-jitterntropy,libjitterentropy"
>> +
>> +# Refer autogen.sh in rng-tools
>> +do_configure_prepend() {
>> +    cp ${S}/README.md ${S}/README
>> +}
>>   
>>   do_install_append() {
>>       # Only install the init script when 'sysvinit' is in DISTRO_FEATURES.
> This fails on musl, likely as the libc-musl override wasn't tweaked. It
> also means that the no libjitterentropy case wasn't tested as there is
> a typo likely causing this:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/11/builds/190/steps/7/logs/step1b

Sorry, I am working on it

//Hongxu

> There are also other weird hangs being observed on the autobuilder
> after these changes. I can't prove its this patchset but I am
> suspicious and its something in master-next as things were working just
> fine until we started poking around all this again :(
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/34/builds/182/steps/7/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/2/builds/188/steps/7/logs/stdio
>
>
> Cheers,
>
> Richard
>
>
>



  parent reply	other threads:[~2018-11-10  1:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09  9:12 [PATCH 0/2] Integrated the jitter entropy daemon to work around slow boot problems for Yocto Hongxu Jia
2018-11-09  9:12 ` [PATCH 1/2] rng-tools: 5 -> 6.6 Hongxu Jia
2018-11-09 22:50   ` richard.purdie
2018-11-09 23:00     ` Richard Purdie
2018-11-10  1:14     ` Hongxu Jia [this message]
2018-11-10  2:22       ` Hongxu Jia
2018-11-11 10:18         ` richard.purdie
2018-11-12  2:10           ` Hongxu Jia
2018-11-12 13:32             ` richard.purdie
2018-11-09  9:12 ` [PATCH 2/2] libjitterentropy: add 2.1.2 Hongxu Jia
2018-11-09 10:30   ` richard.purdie
2018-11-09 14:18     ` Hongxu Jia

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=a1a2bb6a-7ace-086c-e4f2-bd91f7b7d9b7@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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