[yocto] Cross platform compiling/build issue: "Yocto - QA Issue: Architecture did not match (20 to 62) "

Hi folks, I am trying to have cross platform build with Yocto/IOX SDK for our c-mlib lib. I am able to compile and build IPK packages and LXC container for x86 target. Using the same c-mlib.bb recipe, trying to cross compiling and build for a PPC 32-bit target on my 64-bit build

[yocto] Docs help - proper way of adding a userspace header for the kernel

Hi folks, Would someone be able to help Scott with the background for this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8596 It's not really my area of expertise and we really want this documented properly once and for all. Thanks, Paul -- Paul Eggleton Intel Open Source Technology

Re: [yocto] Clarification regarding GCC tool version supported on - Krogoth 2.1.1

Hi Vijay, On Mon, 10 Oct 2016 17:44:13 Vijayakumar Badiger wrote: > Please can some one tell me the tool chain versions supported on the latest > YPCore-Krogoth. > I know the it uses default GCC5.3, just wanted to know if older tool chain > like 4.9XX is supported or not. > > I don't see the

[yocto] Clarification regarding GCC tool version supported on - Krogoth 2.1.1

Hello All, Please can some one tell me the tool chain versions supported on the latest YPCore-Krogoth. I know the it uses default GCC5.3, just wanted to know if older tool chain like 4.9XX is supported or not. I don't see the feature list like the one listed below for Krogoth 2.1.1. which

Re: [yocto] [layerindex-web][PATCH v2 00/12] Add Distro, dependency and recommends detection, and import_project

On Tue, 11 Oct 2016 09:19:15 Paul Eggleton wrote: > On Mon, 10 Oct 2016 12:47:11 Mark Hatle wrote: > > On 10/10/16 12:37 PM, Paul Eggleton wrote: > > > On Mon, 10 Oct 2016 04:48:41 Hatle, Mark wrote: > > >>> On Oct 10, 2016, at 2:54 AM, Paul Eggleton > > >>> > > >>>

Re: [yocto] [layerindex-web][PATCH v2 00/12] Add Distro, dependency and recommends detection, and import_project

On Mon, 10 Oct 2016 12:47:11 Mark Hatle wrote: > On 10/10/16 12:37 PM, Paul Eggleton wrote: > > On Mon, 10 Oct 2016 04:48:41 Hatle, Mark wrote: > >>> On Oct 10, 2016, at 2:54 AM, Paul Eggleton > >>> > >>> > >>> wrote: > On Fri, 07 Oct 2016 13:20:50 Mark Hatle

Re: [yocto] [bitbake] Issue with SVN fetcher options

De : Mark Hatle Envoyé : lundi 10 octobre 2016 15:58 À : Karim ATIKI; yocto Objet : Re: [yocto] [bitbake] Issue with SVN fetcher options On 10/10/16 3:47 PM, Karim ATIKI wrote: > OK. > > > I found out the solution. > > > Actually, I

[yocto] [[PATCHv5][yocto-autobuilder]] buildset.controller: Add build set to test new OS distribution in autobuilder

From: Monserrat Sedeno As part of the process to set new OS distribution as supported on Yoctoc Project a new patch was created with the list of build sets that should be executed. Detailed information:

Re: [yocto] [[yocto-autobuilder][PATCHv4]] ] Build sets to test new OS distribution in autobuilder

On 10/07/2016 07:04 PM, Bill Randle wrote: > This version appears to ignore Beth's comments from yesterday where > she said buildset-config.autobuilder-qa wasn't really the appropriate > directory and suggested a different name, plus she said all buildable > configs should be present or links to

Re: [yocto] [bitbake] Issue with SVN fetcher options

On 10/10/16 3:47 PM, Karim ATIKI wrote: > OK. > > > I found out the solution. > > > Actually, I noticed in the log file "log.do_fetch()" that the SVN command > finishes with the "module" name as the output directory. > > I took a look to bitbake sourcecode and realized that the parameter I

Re: [yocto] [bitbake] Issue with SVN fetcher options

OK. I found out the solution. Actually, I noticed in the log file "log.do_fetch()" that the SVN command finishes with the "module" name as the output directory. I took a look to bitbake sourcecode and realized that the parameter I was looking for in the SRC_URI was "path_spec".

[yocto] [bitbake] Issue with SVN fetcher options

Hi all, I'm writing a recipe to build a custom project for an ARM based board (Colibri T20). I need to fetch the different sub-projects from SVN and launch the respective makefile. However, I'm experiencing a problem with the SVN fetcher of bitbake. Indeed, my URI looks like: SRC_URI =

Re: [yocto] [layerindex-web][PATCH v2 00/12] Add Distro, dependency and recommends detection, and import_project

On 10/10/16 12:37 PM, Paul Eggleton wrote: > On Mon, 10 Oct 2016 04:48:41 Hatle, Mark wrote: >>> On Oct 10, 2016, at 2:54 AM, Paul Eggleton >>> wrote: On Fri, 07 Oct 2016 13:20:50 Mark Hatle wrote: FYI, I have made sure these are re-based on top of

Re: [yocto] [layerindex-web][PATCH v2 00/12] Add Distro, dependency and recommends detection, and import_project

On Mon, 10 Oct 2016 04:48:41 Hatle, Mark wrote: > > On Oct 10, 2016, at 2:54 AM, Paul Eggleton > > wrote: > >> On Fri, 07 Oct 2016 13:20:50 Mark Hatle wrote: > >> FYI, I have made sure these are re-based on top of paule/django18 and > >> pushed to: > >> > >>

[yocto] yocto - linaro's lava integration

Hello everyone, I'm trying to integrate the testing of the resulting yocto images using Linaro's LAVA project. For now I am only using qemux86 images. Now, I am quite a newbie in both projects and maybe in general on the subject of images so I might be asking the wrong questions. So far,

[yocto] [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests

From 8f28afbfc21dc84f076b0cc620e578f9607d1465 Mon Sep 17 00:00:00 2001 From: Robert Berger Date: Mon, 10 Oct 2016 06:26:06 + Subject: [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests