[yocto] [[yocto-autobuilder][PATCHv2] 15/15] buildset-config: Update references from DownloadBitbakeErrorReports to DownloadErrorReports

Since DownloadBitbakeErrorReports is also downloading reports generated by RunOESelftest it don't make sense to have a hard reference of bitbake in the buildstep. Signed-off-by: Aníbal Limón --- buildset-config.controller/build-appliance.conf | 2 +-

[yocto] [[yocto-autobuilder][PATCHv2] 14/15] autobuilder/buildsteps: Rename DownloadBitbakeErrorReports to DownloadErrorReports

Since DownloadBitbakeErrorReports is also downloading reports generated by RunOESelftest it don't make sense to have a hard reference of bitbake in the buildstep. Signed-off-by: Aníbal Limón --- .../buildsteps/DownloadBitbakeErrorReports.py | 42

[yocto] [[yocto-autobuilder][PATCHv2] 12/15] buildsteps/RunOeSelftest.py: Add support for create/save error reports

Now when oe-selftest fails the error report for send to the Error report web are created and saved in the controller. Since oe-selftest is intended to do a build system testing the values for MACHINE, TARGET_SYS and DISTRO are provided so use universal value instead. Signed-off-by: Aníbal Limón

[yocto] [[yocto-autobuilder][PATCHv2] 13/15] nightly-oe-selftest.conf: Add steps for Download and Send error report.

These steps are needed for enable sending of Oe selftest error reports to the Error report WEB. Signed-off-by: Aníbal Limón --- buildset-config.controller/nightly-oe-selftest.conf | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[yocto] [[yocto-autobuilder][PATCHv2] 10/15] autobuilder/lib/{ABtools, builsteps}.py: Create save_error_report func

Create new generic function save_error_report based on _saveBitbakeErrorReport in order to use the same function on OESelftest error reports. Signed-off-by: Aníbal Limón --- .../site-packages/autobuilder/lib/ABTools.py | 13

[yocto] [[yocto-autobuilder][PATCHv2] 11/15] autobuilder/lib/ABTools.py: Add get_lsb_distro function

Try to get Linux distribution ID using lsb_release if lsb_release isn't installed use information provided by linux_distribution() method in platform returns "DISTRONAME-VERSION". Signed-off-by: Aníbal Limón --- .../site-packages/autobuilder/lib/ABTools.py |

[yocto] [[yocto-autobuilder][PATCHv2] 07/15] buiidsets: Add DownloadBitbakeErrorReport step

Add DownloadBitbakeErrorReport step to buildsets that uses bitbake, this step is responsable to download bitbake error reports (if bitbake fails) to slave in order to send it to Error report web. Signed-off-by: Aníbal Limón ---

[yocto] [[yocto-autobuilder][PATCHv2] 09/15] autobuilder/lib/buildsteps.py: BitbakeShellCommand update error report types.

The error report type values changed so update it to match the new ones. Signed-off-by: Aníbal Limón --- lib/python2.7/site-packages/autobuilder/lib/buildsteps.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[yocto] [[yocto-autobuilder][PATCHv2] 08/15] lib/buildsteps.py: BitbakeShellCommand add support for error_type

When generate bitbake error reports two type of errors could be happen a bitbake generic one or when is running bitbake-selftest. Also split the command removing environment only leave the bitbake command and it's arguments. Signed-off-by: Aníbal Limón ---

[yocto] [[yocto-autobuilder][PATCHv2] 06/15] autobuilder/buildsteps: Add DownloadBitbakeErrorReports step

Now the worker is responsible of sending error reports to ERW so in order to don't duplicate functionality add this step for download bitbake error reports generated in master AB. Signed-off-by: Aníbal Limón --- .../buildsteps/DownloadBitbakeErrorReports.py |

[yocto] [[yocto-autobuilder][PATCHv2] 05/15] buildbot: Add support for DirectoryDownload transfer step

The new DirectoryDownload transfer step provides support for download a directory from master to slave in specific location. The current implementation extends FileDownload step but it creates a tar file (may be compressed) and download it from master to slave, finally slave decompress the

[yocto] [[yocto-autobuilder][PATCHv2] 04/15] lib/ABTools: Add functions for get errordir path in controller and worker

get_error_report_controller_dir: Returns controller error report dir where bitbake exception/errors are stored. get_error_report_worker_dir: Returns controller error report dir where recipe task failures are stored. Also update the current sources to use that functions. Signed-off-by: Aníbal

[yocto] [[yocto-autobuilder][PATCHv2] 03/15] lib/buildsteps: BitbakeShellCommand add support for create error reports

When bitbake command fails and isn't a recipe task failure then create an error report and store into yocto-controller folder for be able to transfer to the worker in order to send to the Error report web. Signed-off-by: Aníbal Limón ---

[yocto] [[yocto-autobuilder][PATCHv2] 02/15] lib/buildsteps.py: Add BitbakeLogLineObserver for BitbakeShellCommands.

The BitbakeLogLineObserver look into stdio output of bitbake process and identify for exception/errors into log, Signed-off-by: Aníbal Limón --- .../site-packages/autobuilder/lib/buildsteps.py| 51 ++ 1 file changed, 51 insertions(+) diff

[yocto] [[yocto-autobuilder][PATCHv2] 01/15] lib/buildsteps.py: Add BitbakeShellCommand class

The BitbakeShellCommand is a new class for store common methods when is aim to run bitbake inside an step. Also don't call directly the ShellCommand constructur use super to be able for call the parent constructor no matter what is this enables to call BitbakeShellCommand constructor.

[yocto] [[yocto-autobuilder][PATCHv2] 00/15] Add support for generate bitbake/oe-selftest error reports

This v2 adds support for generate also oe-selftest reports this is almost the previous version with changes requested in review [1], the next patches starts from patch, autobuilder/lib/{ABtools,builsteps}.py: Create save_error_report func Also the changes could be reviewed at [2]. [1]

Re: [yocto] Sharing header files between out-of-tree KLMs

may be first one stages the header into build sysroot and otherone adds a DEPENDS on the first one and expects it in /usr/include/ wrote: > I am building two out-of-tree KLMs with separate yocto recipes. > > > > One of the KLMs depends on a data structure defined in the other one. At > > present

[linux-yocto] [PATCH 1/1] ALSA: hda - hdmi_find_pcm_slot return value bug fix

From: Libin Yang commit d10a80de04a3a8c0d7c1567cbc0a8d2e1181c10a upstream. hdmi_find_pcm_slot return -EBUSY when not no pcm slot found, not -ENODEV. So the caller should compare with -EBUSY. Fixes: a76056f2e57e ('ALSA: hda - hdmi dynamically bind PCM to pin when

[linux-yocto] [PATCH 0/1] Backport ALSA bugfix patch for standard/intel/bxt-rebase

Hi Bruce, Seems that the original ALSA backport missed this patch. See bug 9804. Please apply to linux-yocto-4.4 standard/intel/bxt-rebase branch. Thanks, Cal Sullivan Libin Yang (1): ALSA: hda - hdmi_find_pcm_slot return value bug fix sound/pci/hda/patch_hdmi.c | 2 +- 1 file changed, 1

[yocto] Issues with Jethro qemu-native package build

I have a custom image that I am trying to make the SDK for using bitbake (custom image name) -c populate_sdk. When performing this step the following error is encountered. | ERROR: User requested feature uuid |configure was not able to find it. |Install libuuid devel Can

Re: [yocto] installation of kernel modules

Take a look at deploy folder if your packages (rpm in my case) are being created. I have faced problems where files go to -dev.rpm packages and the yocto silently refuses to create empty .rpm package. Regards, 2016-06-21 5:33 GMT-03:00 : > Hej > > I have a problem when

[yocto] Release Candidate Build for yocto-2.2_M1.rc2_M1.rc2 now available.

-e A release candidate build for yocto-2.2_M1.rc2 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.2_M1.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-qt4 : 8b346c465a5efb280f8d0d23f8660f68bf9af59f meta-intel :

Re: [yocto] Yocto 2.1 perl problem

Right. In fact, there is a bug related to this problem https://bugzilla.yoctoproject.org/show_bug.cgi?id=9763 Apparently, the fix is simple: move the --exclude argument just before the FILES. Simple change but affects several recipes. Leo On 06/21/2016 09:42 AM, Anicic Damir (PSI)

Re: [yocto] Yocto 2.1 perl problem

I found something. It seems that tar 1.29 (which I recently installed) is broken. http://patchwork.openembedded.org/patch/123727/ I'll try now with tar 1.28 -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] [yocto-autobuilder][PATCHv2] nightly-world-lsb.conf: skip Publish step so artifacts don't overwrite nightly-world ones

Signed-off-by: Bill Randle --- v2: delete line, rather than commenting it out buildset-config.controller/nightly-world-lsb.conf | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/buildset-config.controller/nightly-world-lsb.conf

Re: [yocto] Yocto 2.1 perl problem

Ah, I have even deleted everything (repo, downloads, build dir) and started from scratch.: git clone -b krogoth git://git.yoctoproject.org/poky.git add my meta-gfa/* source oe-init-build-env adjust local.conf + bblayers.conf bitbake core-image-psi-gfa-cmd --continue simple everything

[yocto] meta-go

Hi,I am trying to write a recipe to compile a go program. i am using meta-go for go compiler.  getting the following error " # runtime/cgo| ../../../../../../../../../sysroots/x86_64-linux/usr/lib/x86_64-openswitch-linux/go/src/runtime/cgo/cgo.go:54:19: fatal error: errno.h: No such file or

[yocto] [license][PATCH 2/2] ref-manual: Add description for SPDX license operators

Add examples of "OR", "AND" and "WITH" operators usage. Reference: https://spdx.org/sites/spdx/files/SPDX-2.0.pdf Appendix IV: SPDX License Expression Signed-off-by: Sergei Miroshnichenko --- documentation/ref-manual/ref-variables.xml | 21 - 1 file

[yocto] [license][PATCH 1/2] license: Add support for SPDX 2.0 operators

Composite SPDX license expressions can be constructed using "OR", "AND" and "WITH" operators: map them to "|" and "&" Yocto operators accordingly. Recognize long form license identifiers: "[DocumentRef-XXX:][LicenseRef-]YYY". Tested on the following expressions: LICENSE = "Artistic-1.0" LICENSE

Re: [yocto] [[PATCH][AUH] 3/3] upgradehelper.py: Disable _order_pkgs_to_upgrade functionality

On 06/20/2016 04:27 PM, Aníbal Limón wrote: The _order_pkgs_to_upgrade function order a set of packages to be upgraded based on bitbake dependency graph, currently _order_pkgs_to_upgrade is broken so disable it while fix. Signed-off-by: Aníbal Limón ---

Re: [yocto] Yocto 2.1 perl problem

Some basic approach: Try cleaning the target (perl, in this case) and build again. $ bitbake -c cleansstate perl & bitbake perl On 06/21/2016 08:00 AM, Anicic Damir (PSI) wrote: Hi! Suddenly perl does not build any more (I did not have the problem in last two weeks). I did not change

[yocto] Yocto 2.1 perl problem

Hi! Suddenly perl does not build any more (I did not have the problem in last two weeks). I did not change anything (my humble bitbake understanding) about perl. = Build Configuration: BB_VERSION= "1.30.0" BUILD_SYS

Re: [linux-yocto] [PATCH 0/2] Backport several sensor drivers from kernel 4.6

On 2016-06-21 3:52 AM, Yong Li wrote: Dear Maintainers, This patchset backports several sensor drivers from kernel 4.6, please merge it into standard/base branch for linux-yocto-4.4 if looks okay. It looks fine to me. I've staged the changes. Bruce Thanks, Yong Li Giuseppe Barba (1):

Re: [linux-yocto] [PATCH 0/4] P-state patches for linux-yocto-4.1 (atandard/intel/base)

On 2016-06-21 1:33 AM, Yong, Jonathan wrote: These patches are for Apollo Lake Pstate support. These are not in Linus's kernel tree yet, so these should go into standard/intel/base. This series should apply AFTER the 2 P-state patches for linux-yocto-4.1 series. Indeed. I've merged the

Re: [linux-yocto] [PATCH 0/2] P-state patches for linux-yocto-4.1 part 2

On 2016-06-21 1:22 AM, Yong, Jonathan wrote: After digging through the development logs much deeper, these 2 changes were also found in the mainline kernel, originally meant for standard/intel/base, can now be moved to standard/base. Thanks for the extra effort on this .. it really does help.

Re: [linux-yocto] [PATCH 0/4] P-state patches for linux-yocto-4.1

On 2016-06-21 12:45 AM, Yong, Jonathan wrote: Backported from mainline kernel and tested on Apollo Lake. This should go into standard/base. They look good to me as well. I've merged them, and am running some test builds. Bruce Thanks. Doug Smythies (3): intel_pstate: Add tsc collection

[yocto] installation of kernel modules

Hej I have a problem when running do_rootfs() with some own kernel drivers included. My kernel recipe builds some easy GPIO drivers. # They come as one package: myKernelModules: -> a.ko -> b.ko -> c.ko # I build a recipe which creates: myKernelModules.bb ->

[linux-yocto] [PATCH 1/2] iio: accel: add Freescale MMA7455L/MMA7456L 3-axis accelerometer driver

From: Joachim Eastwood Add support for Freescale MMA7455L/MMA7456L 3-axis in 10-bit mode for I2C and SPI bus. This rather simple driver that currently doesn't support all the hardware features of MMA7455L/MMA7456L. Tested on Embedded Artist's LPC4357 Dev Kit with MMA7455L on

[linux-yocto] [PATCH 0/2] Backport several sensor drivers from kernel 4.6

Dear Maintainers, This patchset backports several sensor drivers from kernel 4.6, please merge it into standard/base branch for linux-yocto-4.4 if looks okay. Thanks, Yong Li Giuseppe Barba (1): iio: st-accel: add support for lis2dh12 Joachim Eastwood (1): iio: accel: add Freescale

Re: [yocto] [yocto-autobuilder][PATCH] nightly-world-lsb.conf: skip Publish step so artifacts don't overwrite nightly-world ones

On Mon, 2016-06-20 at 08:00 -0700, Bill Randle wrote: > Signed-off-by: Bill Randle > --- >  buildset-config.controller/nightly-world-lsb.conf | 5 +++-- >  1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git