Re: [yocto] Best practice for files copied directly into sysroot?

Thanks Bryan! On Tue, Dec 1, 2015 at 1:50 PM, Bryan Evenson wrote: > Michael, > > > -Original Message- > > From: yocto-boun...@yoctoproject.org [mailto:yocto- > > boun...@yoctoproject.org] On Behalf Of Michael Habibi > > Sent: Tuesday, December 01, 2015 10:26 AM

Re: [yocto] Best practice for files copied directly into sysroot?

Michael, > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Michael Habibi > Sent: Tuesday, December 01, 2015 10:26 AM > To: yocto@yoctoproject.org > Subject: [yocto] Best practice for files copied directly into sysroot? >

[yocto] [[AUH] 0/6] Integration error handling and enhacements

This changes can be also reviewed at, http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/log/?h=boot_images_v3 Aníbal Limón (6): recipe/git.py: Add missing import of re module. upgradehelper.py: Add support for preserve logs in workdir. upgradehelper.py: Add support for specify

Re: [yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

I'll use that so, thank you very much Paul for the tip! :) Regards, - 2015-12-01 17:59 GMT-02:00 Paul Eggleton : > Yes that's been possible for quite a long time now (possibly going back to OE- > classic). > > Cheers, > Paul > > On Tue, 01 Dec 2015 17:48:26 Daniel.

[yocto] [[AUH] 1/6] recipe/git.py: Add missing import of re module.

Signed-off-by: Aníbal Limón --- modules/recipe/git.py | 1 + 1 file changed, 1 insertion(+) diff --git a/modules/recipe/git.py b/modules/recipe/git.py index 7526a67..b1a6201 100644 --- a/modules/recipe/git.py +++ b/modules/recipe/git.py @@ -23,6 +23,7 @@ # from

[yocto] [[AUH] 6/6] upgradehelper: Remove deprecated setting drop_previous_commits.

Since recipe upgrades are done in isolate manner cleaning the repo for every recipe [1] the drop_previous_commits becomes deprecated. Also now we have Testimage integration phase that handles/reports this kind of errors. [1]

[yocto] [[AUH] 2/6] upgradehelper.py: Add support for preserve logs in workdir.

Add FileHandler log to store the log into workdir, this needs to move up the work directory creation. Signed-off-by: Aníbal Limón --- upgradehelper.py | 10 ++ 1 file changed, 10 insertions(+) diff --git a/upgradehelper.py b/upgradehelper.py index

[yocto] [[AUH] 3/6] upgradehelper.py: Add support for specify what image test.

Before this commit core-image-sato was hardcoded for image to test with this commit image name can be specified in the upgrade-helper.conf. Signed-off-by: Aníbal Limón --- README | 1 + modules/testimage.py | 10 +- upgradehelper.py | 13

Re: [yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

Yes that's been possible for quite a long time now (possibly going back to OE- classic). Cheers, Paul On Tue, 01 Dec 2015 17:48:26 Daniel. wrote: > Hmmm that seems to fit as a glove to me, is that possible on Daisy? > > Regards, > - dhs > > 2015-12-01 17:30 GMT-02:00 Paul Eggleton

[yocto] [[AUH] 5/6] testimage: Add handling of IntegrationError

A recipe can compile alone when the upgrade proccess is made but when integrate it can fail due to dependencies of another recipes. If build image fail then analyze logs to find what recipe failed if recipe is found directly on the set of recipe upgrades remove it, if not recipe found directly

[yocto] [[AUH] 4/6] testimage/ptest: Add require of ptest-pkgs in EXTRA_IMAGE_FEATURES.

Instead of add manually the ptest packages use IMAGE_FEATURE to install ptest packages this save time validating if ptest pkg exist. Signed-off-by: Aníbal Limón --- README | 3 ++- modules/testimage.py | 5 ++--- upgradehelper.py | 5 + 3

Re: [yocto] Problem using unix source in do_compile

Kherm, I did follow Paul recommendations.  The issue was not just using the source unix command. When I changed source to '.', a new error occurred.   do_compile) failed with exit code '1' What is the unexpected > operator? This error was caused by not having a gmake.  Searching to resolve the

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hmm I swear reading that, the message I get is that one should inherit the blacklist class in local.conf (if not on there already) and also set the (varflag) value of that variable for your recipe there. Perhaps the part that reads "the blacklist

[yocto] [[RRS]] rrs/recipes: Add support for persist search and filters.

Now when search something the URL is modified and you can share the URL for access to the data. [YOCTO #7809] Signed-off-by: Aníbal Limón --- rrs/views.py | 11 +++ templates/rrs/recipes.html | 35 +-- 2 files

[yocto] compiling out-of-tree modules with master

Hi All, I'm currently merging my Yocto repo up to master (from Daisy). I'm having problems compiling some of the out-of-tree modules that we have which I've tracked down to the Makefiles looking for: include/generated/autoconf.h include/generated/uapi/linux/version.h Now I originally had to

Re: [yocto] compiling out-of-tree modules with master

On 15-12-01 11:57 AM, Stuart Weaver wrote: Hi All, I’m currently merging my Yocto repo up to master (from Daisy). I’m having problems compiling some of the out-of-tree modules that we have which I’ve tracked down to the Makefiles looking for: include/generated/autoconf.h

Re: [yocto] Help with Opensips Recipe - QA run found fatal errors

Hi Caio, compile-host-path isn't about the path being different - it's about the path being something possibly bad i.e. on the host system. You really ought to fix that one rather than disable it. Cheers, Paul On Tue, 01 Dec 2015 10:21:03 Caio wrote: > Hi Paul, > > Thank you very much for

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 @Martin, I think this information about blacklisting would indeed be very useful, thanks for your input as always. @Belen, yes indeed I noticed the label also hovers even when no tooltip is present, this bugged me a little too to be honest! No

Re: [yocto] FEED_DEPLOYDIR_BASE_URI does not work

On Tue, 01 Dec 2015 08:34:15 Leonardo Sandoval wrote: > On 12/01/2015 03:49 AM, Ayoub Zaki wrote: > > |Hello, > > > > Setting FEED_DEPLOYDIR_BASE_URI > > > D_DEPLOYDIR_BASE_URI> in local.conf as specified in the yocto

[linux-yocto] [PULL REQUEST v2] Intel Axxia updates to linux-yocto-4.1

Hello! I rebased our patches upon your latest updates to linux-yocto-4.1. This series of patches brings various improvements to the Intel Axxia drivers from linux-yocto-4.1, including NCR, PCIe, Dickens, amba-pl011 and XLF device trees. Please pull the patches from

[linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-3.14

Hello! This series of patches brings various improvements to the Intel Axxia drivers from linux-yocto-3.14, including NCR and femac. Please pull the patches from https://github.com/lsigithub/axxia_yocto_linux_3.14_pull.git into git://git.yoctoproject.org/linux-yocto-3.14 Pull

[linux-yocto] [PATCH] Intel Axxia meta updates to yocto-kernel-cache yocto-3.14

Hello! This patch makes the SMP feature optional in the configuration of Axxia BSPs. Please apply it on the 'yocto-3.14' branch from git://git.yoctoproject.org/yocto-kernel-cache Thank you, Cristian Bercaru (1): bsp/axxia: make SMP feature optional bsp/axxiaarm/axxiaarm.cfg | 1 -

[linux-yocto] [PATCH] bsp/axxia: make SMP feature optional

Remove the SMP feature from the base configuration of axxiaarm and axxiapowerpc BSPs. However, it can be enabled using the config fragments from the meta-axxia yocto layer. Signed-off-by: Cristian Bercaru --- bsp/axxiaarm/axxiaarm.cfg | 1 -

[linux-yocto] [PATCH 1/2] meta: bsp/axxia: add preempt-rt support

This patch adds the headers needed to build the linux 3.4 preempt-rt configuration on Axxia arm and powerpc platforms, using config fragments. Signed-off-by: Cristian Bercaru --- .../bsp/axxiaarm/axxiaarm-preempt-rt.scc |8

[linux-yocto] [PATCH 2/2] meta: bsp/axxia: make SMP optional

Remove SMP feture from axxiaarm and axxiapowerpc BSP configurations. SMP can be enabled optionally using the config fragments from meta-axxia yocto layer. Signed-off-by: Cristian Bercaru --- meta/cfg/kernel-cache/bsp/axxiaarm/axxiaarm.cfg|4 +---

[linux-yocto] [PATCH 0/2] Intel Axxia meta updates to linux-yocto-3.4

Hello! Please apply this series of patches on the 'meta' branch from git://git.yoctoproject.org/linux-yocto-3.4.git Thank you, Cristian Bercaru (2): meta: bsp/axxia: add preempt-rt support meta: bsp/axxia: make SMP optional .../bsp/axxiaarm/axxiaarm-preempt-rt.scc |8

[linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-3.4

Hello! This series of patches brings various improvements to the Intel Axxia drivers from linux-yocto-3.4, including NCR and femac. Please pull the patches from https://github.com/lsigithub/lsi_axxia_yocto_pull.git into git://git.yoctoproject.org/linux-yocto-3.4.git Pull

[linux-yocto] [PATCH] bsp/axxia: update base configurations

Update the base configurations of axxiaarm and axxiaarm64 BSPs. Signed-off-by: Cristian Bercaru --- bsp/axxiaarm/axxiaarm.cfg | 2 +- bsp/axxiaarm/axxiaarm.scc | 4 ++-- bsp/axxiaarm64/axxiaarm64.cfg | 3 +-- 3 files changed, 4 insertions(+), 5

[linux-yocto] [PATCH] Intel Axxia meta updates to yocto-kernel-cache yocto-4.1

Hello! This patch brings minor updates to the Axxia arm and arm64 base configs. Please apply it on the 'yocto-4.1' branch from git://git.yoctoproject.org/yocto-kernel-cache Thank you, Cristian Bercaru (1): bsp/axxia: update base configurations bsp/axxiaarm/axxiaarm.cfg | 2 +-

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

On Tue, 01 Dec 2015 12:26:18 Alex Franco wrote: > @Martin, I think this information about blacklisting would indeed be > very useful, thanks for your input as always. > > @Belen, yes indeed I noticed the label also hovers even when no tooltip > is present, this bugged me a little too to be

Re: [yocto] FEED_DEPLOYDIR_BASE_URI does not work

On 12/01/2015 12:16 PM, Paul Eggleton wrote: On Tue, 01 Dec 2015 08:34:15 Leonardo Sandoval wrote: On 12/01/2015 03:49 AM, Ayoub Zaki wrote: |Hello, Setting FEED_DEPLOYDIR_BASE_URI in local.conf

Re: [yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

On Tue, 01 Dec 2015 11:27:19 Daniel. wrote: > Hi Saul, thanks for your reply > > 2015-11-30 21:29 GMT-02:00 Saul Wold : > > On Mon, 2015-11-30 at 17:25 -0200, Daniel. wrote: > >> Hi, > >> > >> I have one kernel tree where I keep all my modules in-tree. Inside > >> kernel I

Re: [yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

Hmmm that seems to fit as a glove to me, is that possible on Daisy? Regards, - dhs 2015-12-01 17:30 GMT-02:00 Paul Eggleton : > On Tue, 01 Dec 2015 11:27:19 Daniel. wrote: >> Hi Saul, thanks for your reply >> >> 2015-11-30 21:29 GMT-02:00 Saul Wold

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

On Tue, Dec 01, 2015 at 11:22:01AM +1300, Paul Eggleton wrote: > Hi Alex, > > On Mon, 30 Nov 2015 16:03:05 Alex Franco wrote: > > Display blacklisted information for recipes on Layerindex, in the > > recipe details, as well as the recipe search page, and layer page > > tables. This information is

[yocto] FEED_DEPLOYDIR_BASE_URI does not work

Hello, Setting FEED_DEPLOYDIR_BASE_URI in local.conf as specified in the yocto manual does NOT generate any /etc/opkg/base-feeds.conf in the root of the target filesystem! Is ist a known bug ? I'm

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

On 01/12/2015 09:40, "yocto-boun...@yoctoproject.org on behalf of Martin Jansa" wrote: >>Another thing that just occurred to me though - apologies for not >>raising it >>earlier - for the benefit of newer users it may be

[yocto] generating shared-state statistics from build

Hi, Is there any existing way to track usage of shared state by a build? In a multi-user environment I'm interesting in knowing how often a build is hitting in the shared state cache vs. rebuilding. Typically would have a globally visible shared state cache mirror updated by a

[yocto] Best practice for files copied directly into sysroot?

I am working on potentially migrating our distribution to Yocto (will be a long, long process). We have an area of our filesystem where any file placed will go directly into the rootfs of the target. This works well with our product, as we have certain binaries and scripts that need to be copied

[yocto] creating a ubuntu rootfs

Hi, I'm trying to create a Yocto kernel with a ubuntu-core rootfs. At the moment I'm creating a core-image-base and then splatting an ubuntu-core-12.04.5-core-armhf.tar.gz over the rootfs on the image. eg Create a core-image-base image $ bitbake core-image-base Insert a sdcard and copy the core

Re: [yocto] Help with Opensips Recipe - QA run found fatal errors

Hi Paul, Thank you very much for your help. I added INSANE_SKIP_${PN} += " libdir compile-host-path" because the instalation is different from /usr/lib. Thank you very much! Regards, Caio Pereira 2015-11-25 20:26 GMT-02:00 Paul Eggleton : > Hi Caio, > > On

Re: [yocto] [PATCHv2] [layerindex-web] recipe blacklisted information

On Tue, Dec 01, 2015 at 10:42:49AM +, Barros Pena, Belen wrote: > > > On 01/12/2015 09:40, "yocto-boun...@yoctoproject.org on behalf of Martin > Jansa" martin.ja...@gmail.com> wrote: > > >>Another thing that just occurred to me though -

Re: [yocto] Toaster GUI with No Option

On 01/12/2015 11:20, "yocto-boun...@yoctoproject.org on behalf of Albert K" wrote: >Hi, > > > I have installed yocto 2.0 on Ubuntu 15. and I can build with bitbake >but when I install the toaster I get a page that shows the

[yocto] Toaster GUI with No Option

Hi, I have installed yocto 2.0 on Ubuntu 15. and I can build with bitbake but when I install the toaster I get a page that shows the following. The is no option to create and new project. What else do I need to get this going. Thanks. [image: Inline image 1] OS is running in VM. Linux

Re: [yocto] FEED_DEPLOYDIR_BASE_URI does not work

On 12/01/2015 03:49 AM, Ayoub Zaki wrote: |Hello, Setting FEED_DEPLOYDIR_BASE_URI in local.conf as specified in the yocto manual does NOT generate any /etc/opkg/base-feeds.conf in the root of

Re: [yocto] One kernel tree, two BSP layers, two defconfigs. How to pickup the right one based on MACHINE value?

Hi Saul, thanks for your reply 2015-11-30 21:29 GMT-02:00 Saul Wold : > On Mon, 2015-11-30 at 17:25 -0200, Daniel. wrote: >> Hi, >> >> I have one kernel tree where I keep all my modules in-tree. Inside >> kernel I have two FOO_defconfig and BAR_defconfig which are >>

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, Dec. 1, 2015 8:00 AM US Pacific Time

Attendees: Stephen, Jessi, Saul, Bruce, Randy, Mark, Belen, * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) YP 2.0 was published just after our last call in Nov. YP 2.1 M1 will have feature freeze on Dec. 7th. YP 2.0.1 is planned for early Jan. ~Jan 11th.

Re: [yocto] generating shared-state statistics from build

On Tue, Dec 01, 2015 at 03:23:01PM +, Luke (Lucas) Starrett wrote: > Hi, > > Is there any existing way to track usage of shared state by a build? In a > multi-user environment I'm interesting in knowing how often a build is > hitting in the shared state cache vs. rebuilding. Typically