Re: [yocto] Writing do_compile in python and importing modules

Hi, On Tue, Dec 10, 2019 at 11:15:01AM +, Ross Burton wrote: > On 09/12/2019 16:30, Patrick Doyle wrote: > > But then I started wondering if I could change do_compile to python, > > have it import assemble-tsk-blob, and get the best of both worlds -- > > the ability to test assemble-tsk-blob

Re: [yocto] Writing do_compile in python and importing modules

On 09/12/2019 16:30, Patrick Doyle wrote: But then I started wondering if I could change do_compile to python, have it import assemble-tsk-blob, and get the best of both worlds -- the ability to test assemble-tsk-blob outside of bitbake, and the efficiency of including its core operation

Re: [yocto] [meta-selinux] Dependency loop help with selinux userspace/python3/util-linux

On 12/5/19 9:46 PM, Peter Morrow via Lists.Yoctoproject.Org wrote: Hi Folks, I'm trying to upgrade the meta-selinux layer to use a newer version of the selinux userspace tools (from 2.8 to 2.9), in doing so these newer userspace tools now depend on python3 instead of python2. This

Re: [yocto] [error-report-web][PATCH V2] Add local.conf and auto.conf into error details

On 11/13/19 6:36 PM, Paul Eggleton wrote: Hi Changqing, Some comments below. On Tuesday, 12 November 2019 9:32:53 PM NZDT changqing...@windriver.com wrote: From: Changqing Li Support to display local.conf and auto.conf on error report web. Here is commit in oe-core, which add

[yocto] variable and task/function timing

Is there a document, or better yet a diagram, showing the order in which various config files, recipes, tasks, etc are parsed? Figuring out the order of the config files is easy enough (bitbake.conf), but trying to figure out when various other parts are processed is just a guess for me right

[yocto] [yocto-autobuilder-helper][PATCH] config.json: Add meta-multimedia to meta-oe job

meta-oe recipes/packagegroups needs meta-multimedia packagegroups Whitelist ffmpeg so packages depending on it can be tested Fixes ERROR: Nothing PROVIDES 'ffmpeg' (but /home/pokybuild/yocto-worker/meta-oe/build/meta-openembedded/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.12.bb

Re: [yocto][meta-rockchip][PATCH] rk3288: Append GPT image type

Applied, thanks! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#47625): https://lists.yoctoproject.org/g/yocto/message/47625 Mute This Topic: https://lists.yoctoproject.org/mt/67979336/21656 Group Owner: yocto+ow...@lists.yoctoproject.org

[yocto] [meta-security][PATCH] libseccomp: upgrade 2.4.1 -> 2.4.2

Backport a patch to fix ptest build failure on arm64. Signed-off-by: Yi Zhao --- ...SNR_xxx-instead-of-__NR_xxx-for-sysc.patch | 45 +++ ...ibseccomp_2.4.1.bb => libseccomp_2.4.2.bb} | 3 +- 2 files changed, 47 insertions(+), 1 deletion(-) create mode 100644

[yocto] Yocto Project Status WW50'19

Current Dev Position: YP 3.1 M1 Next Deadline: YP 3.1 M1 build Dec. 2, 2019 Next Team Meetings: * Bug Triage meeting Thursday Dec. 12th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Jan. 7th at 8am PDT (

[yocto][meta-rockchip][PATCH] rk3288: Append GPT image type

Appends the GPT image type to IMAGE_FSTYPES instead of overriding. This allows additional types to be preserved if they are specified in local.conf Signed-off-by: Joshua Watt --- conf/machine/include/rk3288.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [yocto] Question about shipping files to package.

If the issue were just that your FILES_* variables were set incorrectly, you’d at least end up with the .ko file somewhere in your ${WORKDIR}/image (${D}) directory. You’d almost certainly find another one in the build or source directory as well (depending on how your .bb/bbclass files define

Re: [yocto] Question about shipping files to package.

That makes a lot of sense. The version I'm on is: PV="4.1" (I just ran bitbake -e virtual/kernel | grep "^PV"). On Tue, Dec 10, 2019 at 8:54 PM McKay, Sean wrote: > If the issue were *just* that your FILES_* variables were set > incorrectly, you’d at least end up with the .ko file somewhere in

Re: [yocto] Question about shipping files to package.

I did a find for any files with a kvm and a .ko in its name throughout my entire workspace and nothing came up. But anyway, thanks for the explanation. Could packaging the files wrong (i.e. setting the FILES variable wrong) cause the kvm.ko file to never show up at all? I guess that couldn't be

[linux-yocto] [linux-yocto v5.2] Another patch series for the Marvell cn96xx support

Hi Bruce, Here is another patch series for the Marvell cn96xx SoC support. The main changes are the bug fixes for the GPIO, PCIe and Ethernet. Please help me merge these into the following branches: v5.2/standard/cn96xx v5.2/standard/preempt-rt/cn96xx The following changes since commit

Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc]][PATCH 0/3] New patches for v5.4

Hi Michal, Any comment? Thanks, Quanyang On 12/3/19 6:11 PM, quanyang.w...@windriver.com wrote: From: Quanyang Wang Hi Bruce & Michal, There are 3 patches in this pull-request. 1) The patch "0001-spi-zynq-qspi-use-wait_for_completion_timeout-instea.patch" fixes a bug which occurs in

[linux-yocto] v5.2.x - stable updates comprising v5.2.26

Bruce, Yocto kernel folks: Here is the next 5.2.x stable update "extension" primarily created for the Yocto project, as the 5th v5.2.x post-EOL release. Things are back to "normal" where this release reflects an audit of what went into 5.3.9, resulting in about 145 commits. I've put this 5.2.26