On Fri, Dec 15, 2017 at 11:24 AM, Sherif Omran
wrote:
>
> note that i am not mixing branches
Yes you are.
You have somehow setup a rocko build (path ~/yocto-rocko/...), which
is using recipes from the morty branch of meta-oe
Added a model for the PACKAGECONFIG variable, which has a one to
many relationship with the Recipe model.
Added models for static build dependencies and dynamic build
dependenices, both of which have a many to many relationship with
the Recipe model.
These objects are created in update_layer.py
In v3, fix bug that breaks search if keyword doesn't match one or both of the
dependency items.
Add a note about how dependencies may very.
Activate tooltips so we don't have to wait for them to show.
Only display PACKAGECONFIG names.
The following changes since commit
Bruce,
It turns out that unfortunately a fix found in 4.13.6 was overlooked
for addition to 4.12 because the "Fixes:" tag was newer than the
4.12 kernel. However that doesn't allow for the fact that this fix
is a fix for a fix we backported to 4.12 already. This is a corner
case I can script an
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
sherif@sherif-virtual-machine:~/yocto-rocko/poky/build$ bitbake
rpi-basic-image >a.txt
ERROR: /home/sherif/yocto/poky/meta-openembedded/meta-networking/
recipes-support/nis/ypbind-mt_1.38.bb: Error executing a python
Hello,
I use yocto x11 distro, and it works well with various application
including qt5.
On trying to use gstreamer, it seems that it does not function OK, I
first suspected that it only has to do with high resolution, but now
it seems that various distortions happens only in low resolution.
I
Hello,
I use yocto x11 distro, and it works well with various application
including qt5.
On trying to use gstreamer, it seems that it does not function OK, I
first suspected that it only has to do with high resolution, but now
it seems that various distortions happens only in low resolution.
I
On Fri, 2017-12-15 at 12:50 -0200, Daniel. wrote:
> As I told before, by pass this is a simple matter of running devshell,
> creating the folder and running running the build again,
>
> Paul ask me for more information and so I did, I'll remove that duplicated
> layer and fire `bitbake -fc
As I told before, by pass this is a simple matter of running devshell,
creating the folder and running running the build again,
Paul ask me for more information and so I did, I'll remove that duplicated
layer and fire `bitbake -fc cleanall linux-raspberry && bitbake
linux-rapsberry` again, if I
> On 15 December 2017 at 14:35 Philip Balister wrote:
>
>
> On 12/15/2017 08:36 AM, colin.helliw...@ln-systems.com wrote:
> > The current Poky I'm using (krogoth) has a recipe for dropbear, but I want
> > to upgrade to use the latest version of dropbear.
> > For source control reasons, I don't
On 12/15/2017 08:36 AM, colin.helliw...@ln-systems.com wrote:
> The current Poky I'm using (krogoth) has a recipe for dropbear, but I want
> to upgrade to use the latest version of dropbear.
> For source control reasons, I don't want to modify what's in
> meta/recipes-core/dropbear and therefore
The current Poky I'm using (krogoth) has a recipe for dropbear, but I want
to upgrade to use the latest version of dropbear.
For source control reasons, I don't want to modify what's in
meta/recipes-core/dropbear and therefore want to have my own recipe in my
own layer. Yet for cleanliness I'd
On 12/14/2017 06:38 PM, Alexander Kanavin wrote:
Got it, thanks.
I just sent the patches to yocto@ ML and published them on github -
please do try them out, and rebase your patchset on top (some of it may
no longer be relevant).
I did the rebase myself, and pushed the result here - please
On Thu, 2017-12-14 at 06:31 +0100, Zoran Stojsavljevic wrote:
> > Also is worth noting that I'm running Fedora 27 which wasn't tested...
>
> You should start from here your investigation, since you are on not tested
> YOCTO host distribution. And Fedoras are
> different from release to release,
A release candidate build for yocto-2.2.3.rc2 is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.2.3.rc2
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : c781510a5a6b45e60cc32b6614ddcce3f1452121
meta-qt4 :
Remove build host paths from target xmlsec1Conf.sh script.
Signed-off-by: Catalin Enache
Signed-off-by: Ovidiu Panait
---
recipes-security/xmlsec1/xmlsec1_1.2.24.bb | 1 +
1 file changed, 1 insertion(+)
diff --git
+ joshua.
I am no longer working on the YP, but Joshua is looking after CROPS. It is
actually a family of containers, so some parts have been updated more recently.
-brian
On 12/13/17, 10:26 AM, "Martin Kelly" wrote:
Hi,
I recently discovered the CROPS project
A release candidate build for yocto-2.5_M1.rc1 is now available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.5_M1.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 0f266744f7d542a960a78226af35403f871ba5a6
meta-qt4 :
there has been a discussion about do_sizecheck and there is already a
pending patch:
http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145376.html
Ah! Apologies, totally missed that one
--
___
yocto mailing list
On Fri, Dec 15, 2017 at 5:00 AM, Sherif Omran wrote:
> By testing the latest update of meta-raspberry pi with the Rocko or the
> morty branch, i get ERROR executing a python function in code (see
> attachment).
>
Please send error messages in plain text not as an
On Fri, Dec 15, 2017 at 9:16 AM, Jaap de Jong wrote:
> From 4d542a5a37210b4fc8c8e894554a75ba6b9be0af Mon Sep 17 00:00:00 2001
> From: Jaap de Jong
> Date: Fri, 15 Dec 2017 08:58:09 +0100
> Subject: [poky][PATCH] kernel.bbclass: Fix kernel size
From 4d542a5a37210b4fc8c8e894554a75ba6b9be0af Mon Sep 17 00:00:00 2001
From: Jaap de Jong
Date: Fri, 15 Dec 2017 08:58:09 +0100
Subject: [poky][PATCH] kernel.bbclass: Fix kernel size checking
To: yocto@yoctoproject.org
---
meta/classes/kernel.bbclass | 4 ++--
1 file
22 matches
Mail list logo