[yocto] [meta-gplv2][PATCH] gnutls: update 3.3.27 -> 3.3.28

[Andre McCurdy]

* Version 3.3.28 (released 2017-07-04)

** libgnutls: Fixed issue when rehandshaking without a client certificate in
   a session which initially used one. Reported by Frantisek Sumsal.

** libgnutls: fix issue in RSA-PSK client callback which resulted in no username
   being sent to the peer. Patch by Nicolas Dufresne.

** libgnutls: no longer parse the ResponseID field of the status response
   TLS extension. The field is not used by GnuTLS nor is made available to
   calling applications. That addresses a null pointer dereference on server
   side caused by packets containing the ResponseID field. Reported
   by Hubert Kario. [GNUTLS-SA-2017-4]

** libgnutls: Handle specially HSMs which request explicit authentication.
   There are HSMs which return CKR_USER_NOT_LOGGED_IN on the first private key
   operation. Detect that state and try to login.

** libgnutls: the GNUTLS_PKCS11_OBJ_FLAG_LOGIN will force a login on HSMs.
   That is, even in tokens which do not have a CKF_LOGIN_REQUIRED flag
   a login will be forced. This improves operation on certain Safenet HSMs.

** libgnutls: do not set leading zeros when copying integers on HSMs.
   PKCS#11 defines integers as unsigned having most significant byte
   first, e.g., 32768 = 0x80 0x00. This is interpreted literraly by
   some HSMs which do not accept an integer with a leading zero. This
   improves operation with certain Atos HSMs.

** libgnutls: Backported PKCS#11 key generation functionality for DSA keys.

** libgnutls: Improve check for /dev/urandom uniqueness. Ensure that when
   gnutls_global_init() is called for a second time that /dev/urandom is
   re-opened when the inode or device ID has changed.

** API and ABI modifications:
No changes since last version.

Signed-off-by: Andre McCurdy 
---
 recipes-support/gnutls/gnutls.inc   |  9 -
 recipes-support/gnutls/gnutls_3.3.27.bb | 17 -
 recipes-support/gnutls/gnutls_3.3.28.bb |  8 
 3 files changed, 12 insertions(+), 22 deletions(-)
 delete mode 100644 recipes-support/gnutls/gnutls_3.3.27.bb
 create mode 100644 recipes-support/gnutls/gnutls_3.3.28.bb

diff --git a/recipes-support/gnutls/gnutls.inc 
b/recipes-support/gnutls/gnutls.inc
index 4a5c3df..4cf375f 100644
--- a/recipes-support/gnutls/gnutls.inc
+++ b/recipes-support/gnutls/gnutls.inc
@@ -8,9 +8,8 @@ LICENSE_${PN}-xx = "LGPLv2.1+"
 LICENSE_${PN}-bin = "GPLv3+"
 LICENSE_${PN}-openssl = "GPLv3+"
 
-LIC_FILES_CHKSUM = "file://LICENSE;md5=71391c8e0c1cfe68077e7fce3b586283 \
-file://doc/COPYING;md5=d32239bcb673463ab874e80d47fae504 \
-
file://doc/COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
+file://COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
 
 DEPENDS = "nettle gmp virtual/libiconv"
 DEPENDS_append_libc-musl = " argp-standalone"
@@ -21,9 +20,8 @@ SRC_URI = 
"ftp://ftp.gnutls.org/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar.xz;
 
 inherit autotools texinfo binconfig pkgconfig gettext lib_package gtk-doc
 
-PACKAGECONFIG ??= "libidn zlib"
+PACKAGECONFIG ??= "zlib"
 
-PACKAGECONFIG[libidn] = "--with-idn,--without-idn,libidn"
 PACKAGECONFIG[libtasn1] = 
"--with-included-libtasn1=no,--with-included-libtasn1,libtasn1"
 PACKAGECONFIG[p11-kit] = "--with-p11-kit,--without-p11-kit,p11-kit"
 PACKAGECONFIG[tpm] = "--with-tpm,--without-tpm,trousers"
@@ -31,6 +29,7 @@ PACKAGECONFIG[zlib] = "--with-zlib,--without-zlib,zlib"
 
 EXTRA_OECONF = " \
 --enable-doc \
+--disable-crywrap \
 --disable-libdane \
 --disable-guile \
 --disable-rpath \
diff --git a/recipes-support/gnutls/gnutls_3.3.27.bb 
b/recipes-support/gnutls/gnutls_3.3.27.bb
deleted file mode 100644
index a1dcdb5..000
--- a/recipes-support/gnutls/gnutls_3.3.27.bb
+++ /dev/null
@@ -1,17 +0,0 @@
-require gnutls.inc
-
-LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
-file://COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
-
-SRC_URI += " \
-file://configure.ac-fix-sed-command.patch \
-file://use-pkg-config-to-locate-zlib.patch \
-"
-SRC_URI[md5sum] = "8ee8cebd7f7575b11f232766a21c31d3"
-SRC_URI[sha256sum] = 
"8dfda16c158ef5c134010d51d1a91d02aa5d43b8cb711b1572650a7ffb56b17f"
-
-# This version doesn't support this option added in newer gnutls
-# ERROR: gnutls-3.3.27-r0 do_configure: QA Issue: gnutls: configure was passed 
unrecognised options: --with-idn [unknown-configure-option]
-PACKAGECONFIG[libidn] = ""
-# but it still has the libidn dependency, without this option
-EXTRA_OECONF += "--disable-crywrap"
diff --git a/recipes-support/gnutls/gnutls_3.3.28.bb 
b/recipes-support/gnutls/gnutls_3.3.28.bb
new file mode 100644
index 000..1b23369
--- /dev/null
+++ b/recipes-support/gnutls/gnutls_3.3.28.bb
@@ -0,0 +1,8 @@
+require gnutls.inc
+
+SRC_URI += " \
+file://configure.ac-fix-sed-command.patch \
+

Re: [yocto] use native (cross) toolchain instead of a populated nativesdk (cross-canadian) toolchain

[ChenQi]

If I understand it correctly, you are talking about using native 
components directly for SDK.
If you are using all the same machine with the same OS, you could use 
native components directly, maybe with a little modification.
But in fact, the host where SDK is installed might be different from the 
host where SDK is built.

Check the SDKMACHINE variable.

Best Regards,
Chen Qi

On 11/07/2017 11:09 PM, Zhen LiWei wrote:


Hi, I am working on a yocto 2.0 based distro and we usually 
populate_sdk and use the toolchain included in SDK.


But we also like to check the SDK into a SVN repo, and checkout it 
anywhere, and use it away right where it is checked out. And since the 
nativesdk binaries are based on a different glibc than native, and 
have the “dynamic loader” path hardcoded in them, I have to patch the 
toolchain binaries’ .interp secion to point to a common place, and 
update the loader into that common place automatically in some way. 
Other than this, things work very good for us.


Then I was thinking: is it a good practice, to use the native/cross 
toolchain directly from the tmp/sysroots/x86_64-native folder. I tried 
and succeeded, by just moving the sysroot to where the checked-out 
nativesdk toolchain was.


An extra bonus about this is that we got a more populated sysroot for 
native platform too, for example a openssl dev package at the same 
version as that on target, that we can actually use to make the native 
platform a closer-to-target dev env for some “workbench” build.


However I’m still wondering: is there any thing negative about this 
style? One thing known is that the SDK-using host need to be similar 
to the SDK-building host, but that is not an issue for us. But 
anything else, guys?






-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] dpkg --print-architecture returns wrong result

[John Rama]

Hi, Yocto specialists

I've built the whole system with deb package,
and trying to use package feed feature of yocto.

When try trying to install some package from target, I faced following error.

# apt-get install fontconfig-utils

package architecture (armhf) does not match system (armel)


When checking the install package of the target system, everything is armhf 
architecture. 
# dpkg -l 
...
||/ Name   Version 
Architecture Description
+++-==-===--===
ii  alsa-conf:armhf1.1.0-r0
armhfALSA sound library
ii  alsa-conf-base:armhf   1.1.0-r0
armhfALSA sound library
ii  alsa-lib:armhf 1.1.0-r0
armhfALSA sound library
...

However, when checking with following commands, it tells armel.
# dpkg --print-architecture
armel

I think "dpkg --print-architecture" returns wrong result. 

I'm using toolchain "arm-poky-linux-gnueabi-gcc" and result of dumpmachine 
option is as followings.
$ arm-poky-linux-gnueabi-gcc -dumpmachine 
arm-poky-linux-gnueabi

I have no idea how to tell yocto to configure the target system correctly.
Any feedback is highly appreciated.

Kind Regards,
Jonh Rama
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][patch v3 1/1] recipes.html: Require keyword for recipe search

[Mark Hatle]

On 11/8/17 1:08 PM, Paul Eggleton wrote:
> On Thursday, 9 November 2017 4:42:50 AM NZDT Mark Hatle wrote:
>> On 11/7/17 8:43 PM, Paul Eggleton wrote:
>>> On Wednesday, 8 November 2017 11:47:49 AM NZDT Mark Hatle wrote:
 On 11/7/17 4:31 PM, Amanda Brindle wrote:
> Use JavaScript to check if the search box for recipe search is
> empty before querying the database. This will prevent the "502
> Bad Gateway" error that occurs when the query takes too long due
> to the large list of recipes. Since there are so many recipes
> spread across the layers in the OE index, there's no point in
> allowing a user to search without a keyword in order to browse
> the list; it simply isn't digestible as a whole.
>
> Add a browse button for the Machines, Classes, and Distros pages.

 There are reasons to view all of the recipes, machines, classes, distros,
 etc. (Not necessarily good reasons, but I know people do it.)

 If the query is too long, it would be better to figure out a way to get a
 partial response and formulate the first page based on partial
 responses... having a multipage response that the user can look at.
>>>
>>> I'm willing to be proven wrong, but unfortunately it looks to me like this 
>>> will require major re-engineering to sort out for a fairly weak use case.
>>> If you consider this important, would you be able to look into making it
>>> work?
>>
>> I suspect much of the display engine probably needs a rework as the contents
>> of the layer index have grown.  I can't promise anything, but I'll see if I
>> can find anyone who can work on it.
> 
> Could be yes, thanks.
> 
>> For recipes, the use-case is very weak.  I have talked with people though
>> who have just wanted a list of what is available (one big list).  Primarily
>> so they can compare what is available to some magic spec sheet they are
>> looking at.
> 
> If that's the use case though we should provide a proper export capability, 
> because comparing big lists manually 50 items at a time isn't how you'd best 
> support that. Theoretically the API could be used there but an explicit 
> export 
> function would be more accessible.

For my own uses, I export this using the restapi.  So it can certainly be
exported easily enough and processed externally.  (Of course, few people know
about the restapi or how to use it.)

>> For the Machines, Distros pages..  people do want a full list here, as they
>> simply won't know what is available or what something is called.  The scope
>> of the machines and distros of course is nowhere near the scope for the full
>> recipe list.
> 
> Right, and this patch doesn't remove the ability to browse those - in fact it 
> makes it easier to do so by adding an explicit browse button, so I think 
> we're 
> OK there.

I misunderstood that.  I though the machine/distro would be restricted like 
recipes.

> Cheers,
> Paul
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] apt-get

[Burton, Ross]

Set PACKAGE_CLASSES to package_deb, and then ensure IMAGE_FEATURES includes
package-management.

Ross

On 8 November 2017 at 19:16, Ran Shalit  wrote:

> Hello,
>
> Is there a way to add "apt-get" command (and package manager) in yocto ?
>
> Thank you,
> Ran
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] apt-get

[Ran Shalit]

Hello,

Is there a way to add "apt-get" command (and package manager) in yocto ?

Thank you,
Ran
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto problem for Ryzen-7 cpu

[Ayoub Zaki]

On 08.11.2017 20:07, Jerry Lian wrote:

(weird, yocto mails to me blocked by my gmail, treated as spam?)

Anyway, just change to Ubuntu-17, run first build, succeed with no 
failures, good sign!

Will run more and see.

Glad to read that you solved your problem :-)

You are Welcome!







On Wed, Nov 8, 2017 at 12:06 PM, Jerry Lian > wrote:


(my Gmail does not accept new message for same subject? so I open
a new thread)

So bad: I do use Ryzen-7.
will Ubuntu-17 or latest Debian fix the problem?








--
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg

Tel. : +4971415074546
Mobile   : +4917662901545
Email: ayoub.z...@embexus.com
Homepage : https://embexus.com
VAT No.  : DE313902634

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][patch v3 1/1] recipes.html: Require keyword for recipe search

[Paul Eggleton]

On Thursday, 9 November 2017 4:42:50 AM NZDT Mark Hatle wrote:
> On 11/7/17 8:43 PM, Paul Eggleton wrote:
> > On Wednesday, 8 November 2017 11:47:49 AM NZDT Mark Hatle wrote:
> >> On 11/7/17 4:31 PM, Amanda Brindle wrote:
> >>> Use JavaScript to check if the search box for recipe search is
> >>> empty before querying the database. This will prevent the "502
> >>> Bad Gateway" error that occurs when the query takes too long due
> >>> to the large list of recipes. Since there are so many recipes
> >>> spread across the layers in the OE index, there's no point in
> >>> allowing a user to search without a keyword in order to browse
> >>> the list; it simply isn't digestible as a whole.
> >>>
> >>> Add a browse button for the Machines, Classes, and Distros pages.
> >>
> >> There are reasons to view all of the recipes, machines, classes, distros,
> >> etc. (Not necessarily good reasons, but I know people do it.)
> >>
> >> If the query is too long, it would be better to figure out a way to get a
> >> partial response and formulate the first page based on partial
> >> responses... having a multipage response that the user can look at.
> > 
> > I'm willing to be proven wrong, but unfortunately it looks to me like this 
> > will require major re-engineering to sort out for a fairly weak use case.
> > If you consider this important, would you be able to look into making it
> > work?
> 
> I suspect much of the display engine probably needs a rework as the contents
> of the layer index have grown.  I can't promise anything, but I'll see if I
> can find anyone who can work on it.

Could be yes, thanks.

> For recipes, the use-case is very weak.  I have talked with people though
> who have just wanted a list of what is available (one big list).  Primarily
> so they can compare what is available to some magic spec sheet they are
> looking at.

If that's the use case though we should provide a proper export capability, 
because comparing big lists manually 50 items at a time isn't how you'd best 
support that. Theoretically the API could be used there but an explicit export 
function would be more accessible.

> For the Machines, Distros pages..  people do want a full list here, as they
> simply won't know what is available or what something is called.  The scope
> of the machines and distros of course is nowhere near the scope for the full
> recipe list.

Right, and this patch doesn't remove the ability to browse those - in fact it 
makes it easier to do so by adding an explicit browse button, so I think we're 
OK there.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto problem for Ryzen-7 cpu

[Jerry Lian]

(weird, yocto mails to me blocked by my gmail, treated as spam?)

Anyway, just change to Ubuntu-17, run first build, succeed with no
failures, good sign!
Will run more and see.





On Wed, Nov 8, 2017 at 12:06 PM, Jerry Lian  wrote:

> (my Gmail does not accept new message for same subject? so I open a new
> thread)
>
> So bad: I do use Ryzen-7.
> will Ubuntu-17 or latest Debian fix the problem?
>
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto problem for Ryzen-7 cpu

[Ayoub Zaki]

On 08.11.2017 18:06, Jerry Lian wrote:
(my Gmail does not accept new message for same subject? so I open a 
new thread)


So bad: I do use Ryzen-7.
will Ubuntu-17 or latest Debian fix the problem?


try it out and give us feedback ;-)








--
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg

Tel. : +4971415074546
Mobile   : +4917662901545
Email: ayoub.z...@embexus.com
Homepage : https://embexus.com
VAT No.  : DE313902634

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 32-bit sdk (/opt/poky) in 64 bit machine

[Khem Raj]

On Wed, Nov 8, 2017 at 6:23 AM, Ran Shalit  wrote:
> Hello,
>
> Is it possible to use 32-bit sdk (/opt/poky) in 64 bit machine ?
>

I dont think it will be straight forward, you might be able to get by
adding all multilib to your sdkhost and see if it works.

> Regards,
> Ran
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto problem for Ryzen-7 cpu

[Jerry Lian]

(my Gmail does not accept new message for same subject? so I open a new
thread)

So bad: I do use Ryzen-7.
will Ubuntu-17 or latest Debian fix the problem?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

So bad: I do use Ryzen-7!
I will try new kernel, how about Ubuntu-17? or should be latest Debian?

On Wed, Nov 8, 2017 at 11:47 AM, Jerry Lian  wrote:

> Really, only me got this problem?
>
>
>
>
> On Wed, Nov 8, 2017 at 11:40 AM, Burton, Ross 
> wrote:
>
>> The failure doesn't happen for anyone else.  You're literally saying "it
>> breaks" but not even saying what "it" is, or how "it" is breaking.
>>
>> Ross
>>
>> On 8 November 2017 at 16:38, Jerry Lian  wrote:
>>
>>> Isn't my problem clear: the failure pop-up randomly!
>>> Do you mean the random failure also help you for debugging?
>>>
>>>
>>>
>>>
>>> On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross 
>>> wrote:
>>>
 Well next time it happens feel free to reply to this thread. Otherwise
 you're asking us "fix my problem" without saying what the problem is.

 Ross

 On 8 November 2017 at 16:31, Jerry Lian  wrote:

> So that is further tricky part:
> * it may fail when finishing 20%, 40% 60%, 80%
> * And the failure last time may not appear next time.
> * So it just pop-up randomly
>
> (By the way, I just build brand new PC with 16 threads CPU, 32G
> memory, and install Ubuntu 16.4.3 with ESXI-6.5)
> (so really confused)
>
>
>
> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
> wrote:
>
>> The autobuilder does about 50 builds a night using pure poky and we
>> don't see this, so again: what recipe and what errors?
>>
>> Ross
>>
>> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>>
>>> I am not talking about my own layer or recipe.
>>> It happens even when I run the demo QEMU/beaglebone builds.
>>> (I just download poky, and make NO modifications)
>>>
>>>
>>>
>>>
>>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz <
>>> e...@sw-optimization.com> wrote:
>>>
 Most likely a dependency problem of the package which fails w/ exit
 code 1.
 Check the dependencies in the recipe and w/ Yocto's bitbake it self.

 Cheers
 Eric


 Am 08.11.2017 16:49, schrieb Jerry Lian:

 I am not sure whether it is a bug or an error: * Quite often,
> bitbake will fail before finishing, with message like: ... task 
> failed with
> exit code 1... * But if you rerun bitbake, it will continue to build. 
> * So
> sometimes I have to rerun many times for finish one build  
> annoying!
> (by the way, my CPU can run 16 threads)
>
> Any idea to clear this annoying bug? thanks.
>

>>>
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>
>

>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Ayoub Zaki]

On 08.11.2017 17:47, Jerry Lian wrote:

Really, only me got this problem?

Probably it's just you did forgot to update your system to fix known SMT 
Problems ...






On Wed, Nov 8, 2017 at 11:40 AM, Burton, Ross > wrote:


The failure doesn't happen for anyone else. You're literally
saying "it breaks" but not even saying what "it" is, or how "it"
is breaking.

Ross

On 8 November 2017 at 16:38, Jerry Lian > wrote:

Isn't my problem clear: the failure pop-up randomly!
Do you mean the random failure also help you for debugging?




On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross
> wrote:

Well next time it happens feel free to reply to this
thread. Otherwise you're asking us "fix my problem"
without saying what the problem is.

Ross

On 8 November 2017 at 16:31, Jerry Lian
> wrote:

So that is further tricky part:
* it may fail when finishing 20%, 40% 60%, 80%
* And the failure last time may not appear next time.
* So it just pop-up randomly

(By the way, I just build brand new PC with 16 threads
CPU, 32G memory, and install Ubuntu 16.4.3 with ESXI-6.5)
(so really confused)



On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross
>
wrote:

The autobuilder does about 50 builds a night using
pure poky and we don't see this, so again: what
recipe and what errors?

Ross

On 8 November 2017 at 16:22, Jerry Lian
> wrote:

I am not talking about my own layer or recipe.
It happens even when I run the demo
QEMU/beaglebone builds.
(I just download poky, and make NO modifications)




On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz
> wrote:

Most likely a dependency problem of the
package which fails w/ exit code 1.
Check the dependencies in the recipe and
w/ Yocto's bitbake it self.

Cheers
Eric


Am 08.11.2017 16:49, schrieb Jerry Lian:

I am not sure whether it is a bug or
an error: * Quite often, bitbake will
fail before finishing, with message
like: ... task failed with exit code
1... * But if you rerun bitbake, it
will continue to build. * So sometimes
I have to rerun many times for finish
one build  annoying! (by the way,
my CPU can run 16 threads)

Any idea to clear this annoying bug?
thanks.



--
___
yocto mailing list
yocto@yoctoproject.org

https://lists.yoctoproject.org/listinfo/yocto












--
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg

Tel. : +4971415074546
Mobile   : +4917662901545
Email: ayoub.z...@embexus.com
Homepage : https://embexus.com
VAT No.  : DE313902634

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Ayoub Zaki]

On 08.11.2017 17:47, Burton, Ross wrote:
On 8 November 2017 at 16:41, Ayoub Zaki > wrote:


    (By the way, I just build brand new PC with 16 threads CPU, 32G

    memory, and install Ubuntu 16.4.3 with ESXI-6.5)


Do you have a Ryzen 7 based CPU ?!

In this case Ubuntu 16.4 with Linux kernel 4.4.x is know to be broken
You should upgrade your System with a recent kernel !!!


Following up, it's possible that this brand new PC has a cooling 
problem and is overheating during the build, or the memory isn't 
installed correctly.  This will cause random failures.


[1] 
https://www.pcworld.com/article/3176323/linux/kernel-410-gives-linux-support-for-zen-multithreading.html


Ross


--
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg

Tel. : +4971415074546
Mobile   : +4917662901545
Email: ayoub.z...@embexus.com
Homepage : https://embexus.com
VAT No.  : DE313902634

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto documentation: no content, no PDF?

[Burton, Ross]

On 8 November 2017 at 16:45, Jerry Lian  wrote:

> The mega-manual should have content like: at least one line for each
> chapter, so that we can have a big picture.
>
> By the way, where is the "real docs"?
>
>
https://www.yoctoproject.org/documentation

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

Really, only me got this problem?




On Wed, Nov 8, 2017 at 11:40 AM, Burton, Ross  wrote:

> The failure doesn't happen for anyone else.  You're literally saying "it
> breaks" but not even saying what "it" is, or how "it" is breaking.
>
> Ross
>
> On 8 November 2017 at 16:38, Jerry Lian  wrote:
>
>> Isn't my problem clear: the failure pop-up randomly!
>> Do you mean the random failure also help you for debugging?
>>
>>
>>
>>
>> On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross 
>> wrote:
>>
>>> Well next time it happens feel free to reply to this thread. Otherwise
>>> you're asking us "fix my problem" without saying what the problem is.
>>>
>>> Ross
>>>
>>> On 8 November 2017 at 16:31, Jerry Lian  wrote:
>>>
 So that is further tricky part:
 * it may fail when finishing 20%, 40% 60%, 80%
 * And the failure last time may not appear next time.
 * So it just pop-up randomly

 (By the way, I just build brand new PC with 16 threads CPU, 32G memory,
 and install Ubuntu 16.4.3 with ESXI-6.5)
 (so really confused)



 On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
 wrote:

> The autobuilder does about 50 builds a night using pure poky and we
> don't see this, so again: what recipe and what errors?
>
> Ross
>
> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>
>> I am not talking about my own layer or recipe.
>> It happens even when I run the demo QEMU/beaglebone builds.
>> (I just download poky, and make NO modifications)
>>
>>
>>
>>
>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz <
>> e...@sw-optimization.com> wrote:
>>
>>> Most likely a dependency problem of the package which fails w/ exit
>>> code 1.
>>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>>
>>> Cheers
>>> Eric
>>>
>>>
>>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>>
>>> I am not sure whether it is a bug or an error: * Quite often,
 bitbake will fail before finishing, with message like: ... task failed 
 with
 exit code 1... * But if you rerun bitbake, it will continue to build. 
 * So
 sometimes I have to rerun many times for finish one build  
 annoying!
 (by the way, my CPU can run 16 threads)

 Any idea to clear this annoying bug? thanks.

>>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>

>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Burton, Ross]

On 8 November 2017 at 16:41, Ayoub Zaki  wrote:

> (By the way, I just build brand new PC with 16 threads CPU, 32G
>
>> memory, and install Ubuntu 16.4.3 with ESXI-6.5)
>>
>>
> Do you have a Ryzen 7 based CPU ?!
>
> In this case Ubuntu 16.4 with Linux kernel 4.4.x is know to be broken
> You should upgrade your System with a recent kernel !!!
>

Following up, it's possible that this brand new PC has a cooling problem
and is overheating during the build, or the memory isn't installed
correctly.  This will cause random failures.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto documentation: no content, no PDF?

[Jerry Lian]

The mega-manual should have content like: at least one line for each
chapter, so that we can have a big picture.

By the way, where is the "real docs"?




On Wed, Nov 8, 2017 at 11:30 AM, Burton, Ross  wrote:

> On 8 November 2017 at 15:41, Jerry Lian  wrote:
>
>> Just wondering:
>> * As an active project, why yocto documentation does not provide a
>> content (better be clickable)?
>>
>
> The megamanual (Complete Documentation) doesn't have a top-level table of
> contents as that basically exists to search globally.  The real docs (such
> as Tasks Manual) have a top level table of contents.
>
> * Or PDF format for easy printing.
>>
>
> That would be massive.  The source is in git as docbook so it's fairly
> simple to generate a PDF.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Ayoub Zaki]

Hi,

On 08.11.2017 17:33, Burton, Ross wrote:
Well next time it happens feel free to reply to this thread. Otherwise 
you're asking us "fix my problem" without saying what the problem is.


Ross

On 8 November 2017 at 16:31, Jerry Lian > wrote:


So that is further tricky part:
* it may fail when finishing 20%, 40% 60%, 80%
* And the failure last time may not appear next time.
* So it just pop-up randomly

(By the way, I just build brand new PC with 16 threads CPU, 32G
memory, and install Ubuntu 16.4.3 with ESXI-6.5)



Do you have a Ryzen 7 based CPU ?!

In this case Ubuntu 16.4 with Linux kernel 4.4.x is know to be broken
You should upgrade your System with a recent kernel !!!



(so really confused)



On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross
> wrote:

The autobuilder does about 50 builds a night using pure poky
and we don't see this, so again: what recipe and what errors?

Ross

On 8 November 2017 at 16:22, Jerry Lian > wrote:

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)




On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz
>
wrote:

Most likely a dependency problem of the package which
fails w/ exit code 1.
Check the dependencies in the recipe and w/ Yocto's
bitbake it self.

Cheers
Eric


Am 08.11.2017 16:49, schrieb Jerry Lian:

I am not sure whether it is a bug or an error: *
Quite often, bitbake will fail before finishing,
with message like: ... task failed with exit code
1... * But if you rerun bitbake, it will continue
to build. * So sometimes I have to rerun many
times for finish one build  annoying! (by the
way, my CPU can run 16 threads)

Any idea to clear this annoying bug? thanks.



--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto









--
Ayoub Zaki
Embedded Systems Consultant

Vaihinger Straße 2/1
D-71634 Ludwigsburg

Tel. : +4971415074546
Mobile   : +4917662901545
Email: ayoub.z...@embexus.com
Homepage : https://embexus.com
VAT No.  : DE313902634

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Burton, Ross]

The failure doesn't happen for anyone else.  You're literally saying "it
breaks" but not even saying what "it" is, or how "it" is breaking.

Ross

On 8 November 2017 at 16:38, Jerry Lian  wrote:

> Isn't my problem clear: the failure pop-up randomly!
> Do you mean the random failure also help you for debugging?
>
>
>
>
> On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross 
> wrote:
>
>> Well next time it happens feel free to reply to this thread. Otherwise
>> you're asking us "fix my problem" without saying what the problem is.
>>
>> Ross
>>
>> On 8 November 2017 at 16:31, Jerry Lian  wrote:
>>
>>> So that is further tricky part:
>>> * it may fail when finishing 20%, 40% 60%, 80%
>>> * And the failure last time may not appear next time.
>>> * So it just pop-up randomly
>>>
>>> (By the way, I just build brand new PC with 16 threads CPU, 32G memory,
>>> and install Ubuntu 16.4.3 with ESXI-6.5)
>>> (so really confused)
>>>
>>>
>>>
>>> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
>>> wrote:
>>>
 The autobuilder does about 50 builds a night using pure poky and we
 don't see this, so again: what recipe and what errors?

 Ross

 On 8 November 2017 at 16:22, Jerry Lian  wrote:

> I am not talking about my own layer or recipe.
> It happens even when I run the demo QEMU/beaglebone builds.
> (I just download poky, and make NO modifications)
>
>
>
>
> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz  > wrote:
>
>> Most likely a dependency problem of the package which fails w/ exit
>> code 1.
>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>
>> Cheers
>> Eric
>>
>>
>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>
>> I am not sure whether it is a bug or an error: * Quite often, bitbake
>>> will fail before finishing, with message like: ... task failed with exit
>>> code 1... * But if you rerun bitbake, it will continue to build. * So
>>> sometimes I have to rerun many times for finish one build  annoying!
>>> (by the way, my CPU can run 16 threads)
>>>
>>> Any idea to clear this annoying bug? thanks.
>>>
>>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

Isn't my problem clear: the failure pop-up randomly!
Do you mean the random failure also help you for debugging?




On Wed, Nov 8, 2017 at 11:33 AM, Burton, Ross  wrote:

> Well next time it happens feel free to reply to this thread. Otherwise
> you're asking us "fix my problem" without saying what the problem is.
>
> Ross
>
> On 8 November 2017 at 16:31, Jerry Lian  wrote:
>
>> So that is further tricky part:
>> * it may fail when finishing 20%, 40% 60%, 80%
>> * And the failure last time may not appear next time.
>> * So it just pop-up randomly
>>
>> (By the way, I just build brand new PC with 16 threads CPU, 32G memory,
>> and install Ubuntu 16.4.3 with ESXI-6.5)
>> (so really confused)
>>
>>
>>
>> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
>> wrote:
>>
>>> The autobuilder does about 50 builds a night using pure poky and we
>>> don't see this, so again: what recipe and what errors?
>>>
>>> Ross
>>>
>>> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>>>
 I am not talking about my own layer or recipe.
 It happens even when I run the demo QEMU/beaglebone builds.
 (I just download poky, and make NO modifications)




 On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
 wrote:

> Most likely a dependency problem of the package which fails w/ exit
> code 1.
> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>
> Cheers
> Eric
>
>
> Am 08.11.2017 16:49, schrieb Jerry Lian:
>
> I am not sure whether it is a bug or an error: * Quite often, bitbake
>> will fail before finishing, with message like: ... task failed with exit
>> code 1... * But if you rerun bitbake, it will continue to build. * So
>> sometimes I have to rerun many times for finish one build  annoying!
>> (by the way, my CPU can run 16 threads)
>>
>> Any idea to clear this annoying bug? thanks.
>>
>

 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto


>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Burton, Ross]

Well next time it happens feel free to reply to this thread. Otherwise
you're asking us "fix my problem" without saying what the problem is.

Ross

On 8 November 2017 at 16:31, Jerry Lian  wrote:

> So that is further tricky part:
> * it may fail when finishing 20%, 40% 60%, 80%
> * And the failure last time may not appear next time.
> * So it just pop-up randomly
>
> (By the way, I just build brand new PC with 16 threads CPU, 32G memory,
> and install Ubuntu 16.4.3 with ESXI-6.5)
> (so really confused)
>
>
>
> On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross 
> wrote:
>
>> The autobuilder does about 50 builds a night using pure poky and we don't
>> see this, so again: what recipe and what errors?
>>
>> Ross
>>
>> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>>
>>> I am not talking about my own layer or recipe.
>>> It happens even when I run the demo QEMU/beaglebone builds.
>>> (I just download poky, and make NO modifications)
>>>
>>>
>>>
>>>
>>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
>>> wrote:
>>>
 Most likely a dependency problem of the package which fails w/ exit
 code 1.
 Check the dependencies in the recipe and w/ Yocto's bitbake it self.

 Cheers
 Eric


 Am 08.11.2017 16:49, schrieb Jerry Lian:

 I am not sure whether it is a bug or an error: * Quite often, bitbake
> will fail before finishing, with message like: ... task failed with exit
> code 1... * But if you rerun bitbake, it will continue to build. * So
> sometimes I have to rerun many times for finish one build  annoying!
> (by the way, my CPU can run 16 threads)
>
> Any idea to clear this annoying bug? thanks.
>

>>>
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

So that is further tricky part:
* it may fail when finishing 20%, 40% 60%, 80%
* And the failure last time may not appear next time.
* So it just pop-up randomly

(By the way, I just build brand new PC with 16 threads CPU, 32G memory, and
install Ubuntu 16.4.3 with ESXI-6.5)
(so really confused)



On Wed, Nov 8, 2017 at 11:24 AM, Burton, Ross  wrote:

> The autobuilder does about 50 builds a night using pure poky and we don't
> see this, so again: what recipe and what errors?
>
> Ross
>
> On 8 November 2017 at 16:22, Jerry Lian  wrote:
>
>> I am not talking about my own layer or recipe.
>> It happens even when I run the demo QEMU/beaglebone builds.
>> (I just download poky, and make NO modifications)
>>
>>
>>
>>
>> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
>> wrote:
>>
>>> Most likely a dependency problem of the package which fails w/ exit code
>>> 1.
>>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>>
>>> Cheers
>>> Eric
>>>
>>>
>>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>>
>>> I am not sure whether it is a bug or an error: * Quite often, bitbake
 will fail before finishing, with message like: ... task failed with exit
 code 1... * But if you rerun bitbake, it will continue to build. * So
 sometimes I have to rerun many times for finish one build  annoying!
 (by the way, my CPU can run 16 threads)

 Any idea to clear this annoying bug? thanks.

>>>
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto documentation: no content, no PDF?

[Burton, Ross]

On 8 November 2017 at 15:41, Jerry Lian  wrote:

> Just wondering:
> * As an active project, why yocto documentation does not provide a content
> (better be clickable)?
>

The megamanual (Complete Documentation) doesn't have a top-level table of
contents as that basically exists to search globally.  The real docs (such
as Tasks Manual) have a top level table of contents.

* Or PDF format for easy printing.
>

That would be massive.  The source is in git as docbook so it's fairly
simple to generate a PDF.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Burton, Ross]

The autobuilder does about 50 builds a night using pure poky and we don't
see this, so again: what recipe and what errors?

Ross

On 8 November 2017 at 16:22, Jerry Lian  wrote:

> I am not talking about my own layer or recipe.
> It happens even when I run the demo QEMU/beaglebone builds.
> (I just download poky, and make NO modifications)
>
>
>
>
> On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
> wrote:
>
>> Most likely a dependency problem of the package which fails w/ exit code
>> 1.
>> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>>
>> Cheers
>> Eric
>>
>>
>> Am 08.11.2017 16:49, schrieb Jerry Lian:
>>
>> I am not sure whether it is a bug or an error: * Quite often, bitbake
>>> will fail before finishing, with message like: ... task failed with exit
>>> code 1... * But if you rerun bitbake, it will continue to build. * So
>>> sometimes I have to rerun many times for finish one build  annoying!
>>> (by the way, my CPU can run 16 threads)
>>>
>>> Any idea to clear this annoying bug? thanks.
>>>
>>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)




On Wed, Nov 8, 2017 at 11:21 AM, Burton, Ross  wrote:

> On 8 November 2017 at 15:49, Jerry Lian  wrote:
>
>> I am not sure whether it is a bug or an error:
>> * Quite often, bitbake will fail before finishing, with message like: ...
>> task failed with exit code 1...
>> * But if you rerun bitbake, it will continue to build.
>> * So sometimes I have to rerun many times for finish one build 
>> annoying!
>> (by the way, my CPU can run 16 threads)
>>
>
> If you tell us what recipe is failing, and what the actual error is, then
> we may be able to help.  Generally this is a bug in the makefiles that the
> recipe is building and not a problem with Yocto itself.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)




On Wed, Nov 8, 2017 at 10:56 AM, Eric Schwarz 
wrote:

> Most likely a dependency problem of the package which fails w/ exit code 1.
> Check the dependencies in the recipe and w/ Yocto's bitbake it self.
>
> Cheers
> Eric
>
>
> Am 08.11.2017 16:49, schrieb Jerry Lian:
>
> I am not sure whether it is a bug or an error: * Quite often, bitbake will
>> fail before finishing, with message like: ... task failed with exit code
>> 1... * But if you rerun bitbake, it will continue to build. * So sometimes
>> I have to rerun many times for finish one build  annoying! (by the way,
>> my CPU can run 16 threads)
>>
>> Any idea to clear this annoying bug? thanks.
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Burton, Ross]

On 8 November 2017 at 15:49, Jerry Lian  wrote:

> I am not sure whether it is a bug or an error:
> * Quite often, bitbake will fail before finishing, with message like: ...
> task failed with exit code 1...
> * But if you rerun bitbake, it will continue to build.
> * So sometimes I have to rerun many times for finish one build 
> annoying!
> (by the way, my CPU can run 16 threads)
>

If you tell us what recipe is failing, and what the actual error is, then
we may be able to help.  Generally this is a bug in the makefiles that the
recipe is building and not a problem with Yocto itself.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not talking about my own layer or recipe.
It happens even when I run the demo QEMU/beaglebone builds.
(I just download poky, and make NO modifications)

On Wed, Nov 8, 2017 at 11:15 AM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:

> On Wed, Nov 8, 2017 at 5:13 PM, Jerry Lian  wrote:
> > So according to what you said: the build will fail no matter what.
> > But that is not my observation: my build succeed eventually (but you just
> > need to rerun many times)!!!
>
> ah. sorry, i missed that part. So then it's probably a bug in the
> recipe, missing dependency or something along these lines. It would be
> legit to report this bug then.
>
>
> >
> > On Wed, Nov 8, 2017 at 10:53 AM, Nicolas Dechesne
> >  wrote:
> >>
> >> On Wed, Nov 8, 2017 at 4:49 PM, Jerry Lian 
> wrote:
> >> > I am not sure whether it is a bug or an error:
> >> > * Quite often, bitbake will fail before finishing, with message like:
> >> > ...
> >> > task failed with exit code 1...
> >> > * But if you rerun bitbake, it will continue to build.
> >> > * So sometimes I have to rerun many times for finish one build 
> >> > annoying!
> >> > (by the way, my CPU can run 16 threads)
> >> >
> >> > Any idea to clear this annoying bug?
> >>
> >> it's not a bug. bitbake is using parallel tasks a lot. At any time it
> >> is running N tasks. When one task fails, it will wait for N-1 ongoing
> >> tasks to finish, and then stops.
> >>
> >> If you restart again, it will likely try N new tasks again, and the
> >> same task that failed,  will fail again, it will wait for N-1 tasks to
> >> complete.
> >>
> >> if you do that several times, you will  end up in a situation where
> >> the only task that can run is the 'failing' one, so it will try 1 task
> >> and fail immediately.
> >>
> >> > thanks.
> >> >
> >> > --
> >> > ___
> >> > yocto mailing list
> >> > yocto@yoctoproject.org
> >> > https://lists.yoctoproject.org/listinfo/yocto
> >> >
> >
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Nicolas Dechesne]

On Wed, Nov 8, 2017 at 5:13 PM, Jerry Lian  wrote:
> So according to what you said: the build will fail no matter what.
> But that is not my observation: my build succeed eventually (but you just
> need to rerun many times)!!!

ah. sorry, i missed that part. So then it's probably a bug in the
recipe, missing dependency or something along these lines. It would be
legit to report this bug then.


>
> On Wed, Nov 8, 2017 at 10:53 AM, Nicolas Dechesne
>  wrote:
>>
>> On Wed, Nov 8, 2017 at 4:49 PM, Jerry Lian  wrote:
>> > I am not sure whether it is a bug or an error:
>> > * Quite often, bitbake will fail before finishing, with message like:
>> > ...
>> > task failed with exit code 1...
>> > * But if you rerun bitbake, it will continue to build.
>> > * So sometimes I have to rerun many times for finish one build 
>> > annoying!
>> > (by the way, my CPU can run 16 threads)
>> >
>> > Any idea to clear this annoying bug?
>>
>> it's not a bug. bitbake is using parallel tasks a lot. At any time it
>> is running N tasks. When one task fails, it will wait for N-1 ongoing
>> tasks to finish, and then stops.
>>
>> If you restart again, it will likely try N new tasks again, and the
>> same task that failed,  will fail again, it will wait for N-1 tasks to
>> complete.
>>
>> if you do that several times, you will  end up in a situation where
>> the only task that can run is the 'failing' one, so it will try 1 task
>> and fail immediately.
>>
>> > thanks.
>> >
>> > --
>> > ___
>> > yocto mailing list
>> > yocto@yoctoproject.org
>> > https://lists.yoctoproject.org/listinfo/yocto
>> >
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Eric Schwarz]

Most likely a dependency problem of the package which fails w/ exit code 
1.

Check the dependencies in the recipe and w/ Yocto's bitbake it self.

Cheers
Eric

Am 08.11.2017 16:49, schrieb Jerry Lian:

I am not sure whether it is a bug or an error: * Quite often, bitbake 
will fail before finishing, with message like: ... task failed with 
exit code 1... * But if you rerun bitbake, it will continue to build. * 
So sometimes I have to rerun many times for finish one build  
annoying! (by the way, my CPU can run 16 threads)


Any idea to clear this annoying bug? thanks.

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Nicolas Dechesne]

On Wed, Nov 8, 2017 at 4:49 PM, Jerry Lian  wrote:
> I am not sure whether it is a bug or an error:
> * Quite often, bitbake will fail before finishing, with message like: ...
> task failed with exit code 1...
> * But if you rerun bitbake, it will continue to build.
> * So sometimes I have to rerun many times for finish one build 
> annoying!
> (by the way, my CPU can run 16 threads)
>
> Any idea to clear this annoying bug?

it's not a bug. bitbake is using parallel tasks a lot. At any time it
is running N tasks. When one task fails, it will wait for N-1 ongoing
tasks to finish, and then stops.

If you restart again, it will likely try N new tasks again, and the
same task that failed,  will fail again, it will wait for N-1 tasks to
complete.

if you do that several times, you will  end up in a situation where
the only task that can run is the 'failing' one, so it will try 1 task
and fail immediately.

> thanks.
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Annoying "rerun to fix" bug for bitbake: task failed, but rerun can fix it.

[Jerry Lian]

I am not sure whether it is a bug or an error:
* Quite often, bitbake will fail before finishing, with message like: ...
task failed with exit code 1...
* But if you rerun bitbake, it will continue to build.
* So sometimes I have to rerun many times for finish one build 
annoying!
(by the way, my CPU can run 16 threads)

Any idea to clear this annoying bug?
thanks.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][patch v3 1/1] recipes.html: Require keyword for recipe search

[Mark Hatle]

On 11/7/17 8:43 PM, Paul Eggleton wrote:
> On Wednesday, 8 November 2017 11:47:49 AM NZDT Mark Hatle wrote:
>> On 11/7/17 4:31 PM, Amanda Brindle wrote:
>>> Use JavaScript to check if the search box for recipe search is
>>> empty before querying the database. This will prevent the "502
>>> Bad Gateway" error that occurs when the query takes too long due
>>> to the large list of recipes. Since there are so many recipes
>>> spread across the layers in the OE index, there's no point in
>>> allowing a user to search without a keyword in order to browse
>>> the list; it simply isn't digestible as a whole.
>>>
>>> Add a browse button for the Machines, Classes, and Distros pages.
>>
>> There are reasons to view all of the recipes, machines, classes, distros,
>> etc. (Not necessarily good reasons, but I know people do it.)
>>
>> If the query is too long, it would be better to figure out a way to get a
>> partial response and formulate the first page based on partial responses...
>> having a multipage response that the user can look at.
> 
> I'm willing to be proven wrong, but unfortunately it looks to me like this 
> will require major re-engineering to sort out for a fairly weak use case. If 
> you consider this important, would you be able to look into making it work?

I suspect much of the display engine probably needs a rework as the contents of
the layer index have grown.  I can't promise anything, but I'll see if I can
find anyone who can work on it.

For recipes, the use-case is very weak.  I have talked with people though who
have just wanted a list of what is available (one big list).  Primarily so they
can compare what is available to some magic spec sheet they are looking at.

For the Machines, Distros pages..  people do want a full list here, as they
simply won't know what is available or what something is called.  The scope of
the machines and distros of course is nowhere near the scope for the full recipe
list.

--Mark

> Cheers,
> Paul
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] yocto documentation: no content, no PDF?

[Jerry Lian]

Just wondering:
* As an active project, why yocto documentation does not provide a content
(better be clickable)?
* Or PDF format for easy printing.

Isn't good documentation the basic requirement for a good project?
 (By the way, the yocto homepage is also ugly!)

Thanks,
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-oracle-java][PATCH v2] Don't preserve ownership when copying files

[Martin Nordqvist]

Don't preserve ownership when copying files. Instead let root be
owner of all files.
---
 recipes-devtools/oracle-java/oracle-jse.inc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/recipes-devtools/oracle-java/oracle-jse.inc 
b/recipes-devtools/oracle-java/oracle-jse.inc
index 4346f23..5e5f406 100644
--- a/recipes-devtools/oracle-java/oracle-jse.inc
+++ b/recipes-devtools/oracle-java/oracle-jse.inc
@@ -19,7 +19,8 @@ JDK_HOME = "${libdir_jvm}/${JDK_DIR}"
 
 do_install () {
install -d -m 0755  ${D}${libdir_jvm}
-   cp -a ${S}/${JDK_JRE}${PV}_${PV_UPDATE} ${D}${JDK_HOME}
+   cp -a --no-preserve=ownership \
+   ${S}/${JDK_JRE}${PV}_${PV_UPDATE}   ${D}${JDK_HOME}
 }
 
 # All the files are provided in a binaray package, and keeping all the
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] 32-bit sdk (/opt/poky) in 64 bit machine

[Ran Shalit]

Hello,

Is it possible to use 32-bit sdk (/opt/poky) in 64 bit machine ?

Regards,
Ran
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] u-boot recipe: Missing dependencies

[Eric Schwarz]

Am 09.10.2017 12:30, schrieb Burton, Ross:


On 8 October 2017 at 18:04, Eric Schwarz  
wrote:


Don't _append when you can just extend the assignment above. I just 
did it that way for the moment since I wanted to circumvent merge

conflicts when I upgrade the underlying recipes from openembedded.


Well it's ugly, so if you want a patch in oe-core then don't introduce 
ugly for your convenience.


Well, I have only done this, so the patch does apply the next time. 
Since in case someone changes something in the mainline it is always a 
hassle otherwise. For the final version it will be fixed.


Depending on python-native does nothing as the binary isn't in $PATH 
still.
I thought any Yocto native binaries built are in the PATH 
automatically. - How

to fix this/do it correctly?


You need to inherit python3native, as python (and some others) are 
opt-in.


Well, okay, but WTH I do not need to inherit from something for 
"bc-native" and "dtc-native"?


Eric
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Fwd: kernel menuconfig with screen is not populating clearly

[Vineeth Karumanchi]

Hi ALL,

When my oe_term is set to screen/tmux, the menuconfig for kernel,u-boot,.. is
having some empty spaces. This is making distorted view.
Please see the attachment. It is looking good with gnome and other
terminals with ssh -x.

Anything i need to do to get clear menuconfig without ssh -X ?

Thanks
VIneeth



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-oracle-java][PATCH] Don't preserve ownership when copying files

[Vincent Prince]

Hi Martin,

Any reason to give root rights to JDK?

Best Regards,
Vincent

2017-11-06 15:33 GMT+01:00 Martin Nordqvist :

> Don't preserve ownership when copying files. Instead let root be
> owner of all files.
> ---
>  recipes-devtools/oracle-java/oracle-jse-jdk.inc | 3 ++-
>  recipes-devtools/oracle-java/oracle-jse.inc | 3 ++-
>  2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> index a7210d9..ca6af22 100644
> --- a/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> +++ b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> @@ -13,7 +13,8 @@ require oracle-jse.inc
>
>  do_install_class-native() {
> install -d  ${D}${libdir_jvm}
> -   cp -a ${S}/${JDK_JRE}${PV}_${PV_UPDATE} ${D}${JDK_HOME}
> +   cp -a --no-preserve=ownership \
> +   ${S}/${JDK_JRE}${PV}_${PV_UPDATE}   ${D}${JDK_HOME}
>
> install -d  ${D}${bindir}
> ln -sf ${JDK_HOME}/bin/java ${D}${bindir}
> diff --git a/recipes-devtools/oracle-java/oracle-jse.inc
> b/recipes-devtools/oracle-java/oracle-jse.inc
> index 4346f23..5e5f406 100644
> --- a/recipes-devtools/oracle-java/oracle-jse.inc
> +++ b/recipes-devtools/oracle-java/oracle-jse.inc
> @@ -19,7 +19,8 @@ JDK_HOME = "${libdir_jvm}/${JDK_DIR}"
>
>  do_install () {
> install -d -m 0755  ${D}${libdir_jvm}
> -   cp -a ${S}/${JDK_JRE}${PV}_${PV_UPDATE} ${D}${JDK_HOME}
> +   cp -a --no-preserve=ownership \
> +   ${S}/${JDK_JRE}${PV}_${PV_UPDATE}   ${D}${JDK_HOME}
>  }
>
>  # All the files are provided in a binaray package, and keeping all the
> --
> 1.9.1
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto