[yocto] [meta-security][PATCH] keynote: add new recipe

From: Jackie Huang KeyNote is a simple and flexible trust-management system designed to work well for a variety of large- and small- scale Internet-based applications Signed-off-by: Jackie Huang --- .../configure-remove-hardcode-path.patch | 37 ++ .../keynote/key

[yocto] cogl-1.0-dev

Hi, I build myself an image (x86_64) for my NUC. Because i´m including all dev packages i encountered the following problem while switching from pyro to the recent poky master do_rootfs crashes with an error message because cogl-1.0-dev wants to install package cogl-1.0. Cogl-1.0 is empty and

Re: [yocto] cogl-1.0-dev

the problem could also be resolved in the way it was done here: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8e15e9b6e478f6368034519b2a8fd3c7ea71d23b On Wed, 26 Jul 2017 17:48:31 +0200 Markus Volk wrote: > Hi, > > I build myself an image (x86_64) for my NUC. Because i´m includin

[yocto] automount pyro, /run/media/sda1 empty, not under morty

I am new to this area. I have been using morty to build my image and moved over to pyro now my automount is resulting in a /run/media/sda1 which is empty where , under the morty build, I see my files on the usb stick drive in /run/media/sda1 Note: login as root, not a privilege issue using same

Re: [yocto] do_compile errors.

On 2017-07-19 09:13 AM, Joseph Ngigi wrote: Here's my console output: ngigijoe@ngigijoe-HP-2000-Notebook-PC:~/src/git/pyro/poky/cubieboard2$ bitbake core-image-sato Loading cache: 100% |

Re: [yocto] Mpich and yocto ?

On 2017-07-26 02:09 AM, Riko Ho wrote: How can we do that ? bitbake in which node ? I don't understand ? On 26/07/17 13:57, Josef Holzmayr wrote: Hi On 26.07.2017 05:12, Riko Ho wrote: Does anyone know on how to run poky on mpich cluster ? That's a rather ambiguous question. What OS/Dist

[yocto] [PATCH] dev-manual, ref-manual: Update for vmdk/vdi/qcow2/u-boot image changes

Recently a number of changes have happened on the implementation side of some image formats, and a few have been renamed. The u-boot image signing code is now always available and no longer in a stand-alone file. The vmdk/vdi/qcow2 images have been removed and are now just a conversion type that

Re: [yocto] Mpich and yocto ?

Dear Yocto Team Member, The cluster is using Ubuntu. I haven't checked all the packages on the other computer. I will. My goal is getting more hardrive space and compiling speed. How can I relate bitbake with mpicc or other compilers needed by yocto (arm-linux-gcc, gcc, etc)? I have tested a sm

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel

Delete jasperforest, sugarbay, and nuc buildsets. These are deprecated. We no longer release/support these. Signed-off-by: Graydon, Tracy --- buildset-config.meta-intel/jasperforest-lsb.conf | 58 buildset-config.meta-intel/jasperforest.conf | 51

[yocto] [meta-cgl][PATCH] monit: update to 5.20.0

From: Jackie Huang Changes: - Fix the license to AGPLv3 - Add summary, description and homepage - Add systemd support - Don't change the files in ${S}, change them after installing. - Add PACKAGECONFIG for pam and enable it when it's in DISTRO_FEATURES Signed-off-by: Jackie Huang --- .../m

Re: [yocto] [layerindex-web][PATCH] layerindex-web : adding asynchronous task execution

Great! Thanks for testing it out and identifying that issue. I've put together a PR on GitHub that includes some changes that appear to fix the issue you're describing. It also updates the readme to document how to configure the connection to the

Re: [yocto] Mpich and yocto ?

On 2017-07-26 08:08 PM, Riko Ho wrote: Dear Yocto Team Member, The cluster is using Ubuntu. I haven't checked all the packages on the other computer. I will. My goal is getting more hardrive space and compiling speed. How can I relate bitbake with mpicc or other compilers needed by yocto (arm

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/nightly-meta-intel.conf

Update nightl-meta-intel.conf to reflect what is currently being used in production. - Drop deprecated crownbay, jasperforest, sugarbay, and nuc -related stuff. - Change various SRCREVs to use blank as default instead of linux-yocto or AUTOREV. Signed-off-by: Graydon, Tracy --- buildset-config.

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/yoctoAB.conf

Remove the deprecated configs for jasperforest, crownbay, sugarbay, and nuc. Signed-off-by: Graydon, Tracy --- buildset-config.meta-intel/yoctoAB.conf | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/buildset-config.meta-intel/yoctoAB.conf b/buildset-config.meta-intel/yocto

[yocto] [yocto-autobuilder][PATCH] /buildset-config.meta-intel/*.conf

Update meta-intel buildsets to reflect current production versions: - Change various SRCREVs to default to blank instead of linux-yocto or AUTOREV. Signed-off-by: Graydon, Tracy --- .../intel-core2-32-lsb-rt.conf | 12 +- buildset-config.meta-intel/intel-core2-32-lsb

Re: [yocto] Mpich and yocto ?

Dear Yocto Team Member, Thanks for the reply, So : "YP+distcc/icecream" is equal to MpichCluster ? or that one is inside MpichCluster, I have tested : https://help.ubuntu.com/community/MpichCluster I don't have a fancy systems as you said below, but I have a spare motherboards, memories a