Re: [OE-core] RFC: Upgrading rt-tests requires numactl

On 9/23/20 11:00 PM, Khem Raj wrote: On Wed, Sep 23, 2020 at 2:40 PM Ross Burton wrote: On Wed, 23 Sep 2020 at 18:23, Randy Witt wrote: Another issue is that ARM is removed from COMPATIBLE_HOST in http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/numactl

[OE-core] RFC: Upgrading rt-tests requires numactl

While looking into upgrading rt-tests to the latest version, on IRC, John Kacur(the maintainer of rt-tests), recommended "that they use unstable/devel/latest as the maintained stable branch". I updated the recipes in

Re: [OE-core] Linux v5.8 modules, exec format error

On 8/29/20 11:41 AM, Bruce Ashfield wrote: On Fri, Aug 28, 2020 at 10:28 PM Bruce Ashfield via lists.openembedded.org wrote: On Fri, Aug 28, 2020 at 7:15 PM Jack Mitchell wrote: Quick update, I just did an armv7 build with exactly the same codebase and everything worked fine. Do you have

Re: [OE-core] [PATCH v2] wic/bootimg-efi: IMAGE_EFI_BOOT_FILES added to separate bootimg-efi and bootimg-partition

On 8/26/20 1:13 AM, Jamaluddin, Khairul Rohaizzat wrote: From: Khairul Rohaizzat Jamaluddin Due to recent changes in bootimg-efi to include IMAGE_BOOT_FILES, when both bootimg-partition and bootimg-efi occur in a single .wks and IMAGE_BOOT_FILES are defined, files listed in IMAGE_BOOT_FILES

[OE-core] New changes to bootimg-efi.py break some wic installer image methods

Hi, The changes in https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=801f07fc00d43d107cb6ae671dbbb57ee91cc6be prevent creating an installer image using wic described here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/README#n201. This is because the IMAGE_BOOT_FILES

Re: [OE-core] [PATCH] openssh: Atomically generate host keys

On 05/23/2017 08:29 AM, Joshua Watt wrote: On Tue, May 23, 2017 at 9:37 AM, Burton, Ross wrote: On 7 May 2017 at 02:33, Joshua Watt wrote: +if [ ! -f "$NAME" ]; then +echo " generating ssh $TYPE key..." +ssh-keygen -q -f "${NAME}.tmp"

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 05/22/2017 10:29 AM, Martin Kelly wrote: (friendly ping) On 05/02/2017 12:20 PM, Martin Kelly wrote: Currently, the qemu CPUs for are specified as generic, but the built artifacts are not. For example, we build x86-64 artifacts targeting core2duo but run them in qemu with generic qemu/kvm

Re: [OE-core] [PATCH v2] libxslt: Add PACKAGECONFIG support for python

Hi Patel, On 03/22/2017 06:05 PM, Vedang Patel wrote: Add support to enable python bindings for libxslt using PACKAGECONFIG. This will include --with-python argument while compiling the package. The support is disabled by default. Signed-off-by: Vedang Patel ---

[OE-core] [PATCH v4 3/3] selftest/containerimage.py: Add container IMAGE_FSTYPES test

, and that the developer can make sure it also gets removed from a container image. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- .../container-image/container-image-testpkg.bb | 8 +++ .../container-image/container-test-image.bb| 8 +++ meta/li

[OE-core] [PATCH v3 3/3] selftest/containerimage.py: Add container IMAGE_FSTYPES test

, and that the developer can make sure it also gets removed from a container image. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- .../container-image/container-image-testpkg.bb | 8 +++ .../container-image/container-test-image.bb| 8 +++ meta/li

[OE-core] [PATCH v2 1/3] image-container.bbclass: Add the "container" IMAGE_FSTYPES

The "container" fstype does very little other than pick tar.bz2 as the actual image type and disable installation of ROOTFS_BOOTSTRAP_INSTALL. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/image-container.bbclass | 3 +++ meta/class

[OE-core] [PATCH v2 2/3] image-container.bbclass: Error if not using linux-dummy

does want to build against particular kernel headers, etc, they can override by setting IMAGE_CONTAINER_NO_DUMMY = "1". [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/image-container.bbclass | 18 ++ 1 file changed, 18 ins

[OE-core] [PATCH v2 0/3] Add initial container IMAGE_FSTYPES support

://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rewitt/contwip Randy Witt (3): image-container.bbclass: Add the "container" IMAGE_FSTYPES image-container.bbclass: Error if not using linux-dummy selftest/containerimage.py: Add container IMAGE_FSTYPES test .../container-image/conta

[OE-core] [PATCH v2 3/3] selftest/containerimage.py: Add container IMAGE_FSTYPES test

, and that the developer can make sure it also gets removed from a container image. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- .../container-image/container-image-testpkg.bb | 8 +++ .../container-image/container-test-image.bb| 8 +++ meta/li

Re: [OE-core] [PATCH 3/3] selftest/containerimage.py: Add container IMAGE_FSTYPES test

On 01/19/2017 04:01 AM, Burton, Ross wrote: On 18 January 2017 at 18:31, Randy Witt <randy.e.w...@linux.intel.com> wrote: +expected_files = [ +'./', +'./bin/', +'./bin/theapp', +

[OE-core] [PATCH] selftest/containerimage.py: Add container IMAGE_FSTYPES test

, and that the developer can make sure it also gets removed from a container image. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- .../container-image/container-image-testpkg.bb | 8 +++ .../container-image/container-test-image.bb| 8 +++ meta/li

[OE-core] [PATCH 1/3] image-container.bbclass: Add the "container" IMAGE_FSTYPES

The "container" fstype does very little other than pick tar.bz2 as the actual image type and disable installation of ROOTFS_BOOTSTRAP_INSTALL. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/image-container.bbclass | 3 +++ meta/class

[OE-core] [PATCH 0/3] Add initial container IMAGE_FSTYPES support

/poky-contrib/log/?h=rewitt/contwip Randy Witt (3): image-container.bbclass: Add the "container" IMAGE_FSTYPES image-container.bbclass: Error if not using linux-dummy selftest/containerimage.py: Add container IMAGE_FSTYPES test .../container-image/container-image-testpkg.b

[OE-core] [PATCH 3/3] selftest/containerimage.py: Add container IMAGE_FSTYPES test

, and that the developer can make sure it also gets removed from a container image. [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- .../container-image/container-image-testpkg.bb | 8 +++ .../container-image/container-test-image.bb| 8 +++ meta/li

[OE-core] [PATCH 2/3] image-container.bbclass: Error if not using linux-dummy

does want to build against particular kernel headers, etc, they can override by setting IMAGE_CONTAINER_NO_DUMMY = "1". [YOCTO #9502] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/image-container.bbclass | 18 ++ 1 file changed, 18 ins

Re: [OE-core] [PATCH 2/3] rm_work_and_downloads.bbclass: more aggressively minimize disk usage

On Mon, Jan 9, 2017 at 2:25 AM, Patrick Ohly wrote: > > > > > In principle I agree. Okay, let's separate the two. > > I hit one snag when starting to do that: the implementation of download > removal depends on do_rm_work from rm_work.bbclass for hooking into the > build

Re: [OE-core] [PATCH 2/3] rm_work_and_downloads.bbclass: more aggressively minimize disk usage

On Fri, Jan 6, 2017 at 11:22 AM, Patrick Ohly <patrick.o...@intel.com> wrote: > On Fri, 2017-01-06 at 10:31 -0800, Randy Witt wrote: > > > > > I'd rather see this be a new class independent from rm_work. People > > can always in inherit both rm_work and rm_download.

Re: [OE-core] [PATCH 2/3] rm_work_and_downloads.bbclass: more aggressively minimize disk usage

Hi Patrick, On Fri, Jan 6, 2017 at 1:55 AM, Patrick Ohly wrote: > rm_work.bbclass never deletes downloaded files, even if they are not > going to be needed again during the > build. rm_work_and_downloads.bbclass is more aggressive in minimizing > the used disk space

[OE-core] [PATCH 2/2] image_types.bbclass: IMAGE_TYPEDEP_ now adds deps for conversion types

Previously if IMAGE_TYPEDEP_* contained a conversion type of the form, "foo.bar", the dependency on CONVERSION_DEPENDS_bar would not get added to the task depends for do_rootfs. [YOCTO #10883] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/image_ty

[OE-core] [PATCH 1/2] image_typedep.py: Add a test that ensures conversion type deps get added

Add a test that ensures if IMAGE_TYPEDEP_* contains a conversion type, that the corresponding CONVERSION_DEPENDS_ for that type gets added to the dependency tree for do_rootfs. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/lib/oeqa/selftest/image_typedep.p

[OE-core] [PATCH 0/2] Fix depends for conversion types in IMAGE_TYPEDEP_*

repository at: git://git.yoctoproject.org/poky-contrib rewitt/image_typedep http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rewitt/image_typedep Randy Witt (2): image_typedep.py: Add a test that ensures conversion type deps get added image_types.bbclass: IMAGE_TYPEDEP_ now adds

Re: [OE-core] [PATCH V2 5/6] runqemu: fixes for slirp, network device and hostfwd

def setup_slirp(self): """Setup user networking""" if self.fstype == 'nfs': self.setup_nfs() self.kernel_cmdline_script += ' ip=dhcp' -self.set('NETWORK_CMD', self.get('QB_SLIRP_OPT')) +# Port mapping +hostfwd =

Re: [OE-core] [PATCH] qemu*.conf: Add slirp support for all qemu machines

"-device virtio-net-device,netdev=net0" and "-netdev user,id=net0,hostfwd=tcp::-:22" Then there is no way for user to override the second part, and we can't call the first part as a "QB_SLIRP_OPT" since it is only part of them, so I won't break them into 2, and if the user defines

[OE-core] [PATCH] qemu*.conf: Add slirp support for all qemu machines

This patch also moves the "-net user" part out of the config and into runqemu. This is done because the "-net user" portion isn't machine specific, and it contains what ports to forward. [ YOCTO #7887 ] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> ---

Re: [OE-core] [PATCH] mkefidisk.sh: add deprecation warning to the output

We should also document, the wic steps in wiki pages e.g. http://wiki.minnowboard.org/Yocto_Project It's already documented in README.hardware: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README.hardware And in Yocto manual:

Re: [OE-core] [RFC][PATCH] report-error.bbclass: Add support for autosending

On 09/08/2016 02:26 AM, Elizabeth 'pidge' Flanagan wrote: This commit pulls and extends the functionality of .oe-error-report into local.conf. It maintains the functionality of .oe-error-report. It also enables report-error to automatically send error reports to a specified error report server.

[OE-core] [PATCH v2] sstate.bbclass: Don't create symlinks, download to the correct location

. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/sstate.bbclass | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass index 22ce1ee..6bf94b0 100644 --- a/meta/classes/sstate.bbclass +++

[OE-core] [PATCH 0/1] sstate fetch symlink removal

at: git://git.yoctoproject.org/poky-contrib rewitt/sstate-symlink http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rewitt/sstate-symlink Randy Witt (1): sstate.bbclass: Don't create symlinks, download to the correct location meta/classes/sstate.bbclass | 12 +++- 1 file

[OE-core] [PATCH 1/1] sstate.bbclass: Don't create symlinks, download to the correct location

. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/sstate.bbclass | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass index 22ce1ee..6d5411f 100644 --- a/meta/classes/sstate.bbclass +++

Re: [OE-core] Make runqemu knows nothing about machine

On 04/29/2016 03:09 AM, Robert Yang wrote: On 04/29/2016 05:45 PM, Richard Purdie wrote: On Tue, 2016-04-26 at 11:42 +0800, Robert Yang wrote: Hello, The qemu-native can boot a lot of machines, but oe-core's runqemu can only boot a few of them which are hardcoded into runqemu. I'd like to

[OE-core] [PATCH 2/2] devtool: Fix build-sdk when pn doesn't match filename

If an image with the filename foo.bb could be built using the name "bar" instead, then build-sdk would fail to create the derivative sdk. This was because the code assumed that the file name matched the target, which is not necessarily the case. Signed-off-by: Randy Witt

[OE-core] [PATCH 1/2] populate_sdk_ext: Change lockedsigs task mismatch to a warning

don't need an error halting their progress. locked-sigs will still function as it should. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/populate_sdk_ext.bbcl

[OE-core] [PATCH 0/2] extensible sdk fixes

-contrib rewitt/esdk-fixes http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rewitt/esdk-fixes Randy Witt (2): populate_sdk_ext: Change lockedsigs task mismatch to a warning devtool: Fix build-sdk when pn doesn't match filename meta/classes/populate_sdk_ext.bbclass | 2 +- scripts/devtool

[OE-core] [PATCH 3/5] populate_sdk_ext.bbclass: Enable locked sigs errors

With the extensible sdk we want there to be an error if a task tries to run without signatures that match locked-sigs.inc. This patch enables that error. [YOCTO #9195] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 11 +--

[OE-core] [PATCH 4/5] sstatesig.py: Add a method to "unlock" recipes

their tasks unlocked, as well as any tasks that depend on that recipe. For example if foo->bar->baz, if you unlock baz, it will also unlock bar so that foo can be rebuilt without explicitly specifying bar as being unlocked. [YOCTO #9195] Signed-off-by: Randy Witt <randy.e.w...@linux.

[OE-core] [PATCH 5/5] devtool: Create unlocked-sigs.inc containing items in the workspace

-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 5 + scripts/devtool | 20 2 files changed, 25 insertions(+) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass

[OE-core] [PATCH 2/5] sstatesig.py: Improve the SIGGEN_LOCKEDSIGS_TASKSIG_CHECK message

to d25ba9035f7ccb308e51bbe1066e8d27 in SIGGEN_LOCKEDSIGS_t-x86-64 which will hopefully be more useful in understanding the problem. [YOCTO #9195] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/lib/oe/sstatesig.py | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-)

[OE-core] [PATCH 1/5] sstatesig.py: Split single locked sigs check into multiple checks

by SIGGEN_LOCKEDSIGS_CHECK_LEVEL. This was an issue in the extensible sdk, because we know sstate won't exist for certain items in the reverse dependencies list for tasks. However, we still want to error if task signatures don't match. [YOCTO #9195] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> ---

[OE-core] [PATCH 0/5] extensible sdk changes

: toasterconf.json: Add DL_DIR and SSTATE_DIR to poky toasterconf (2016-04-07 14:58:10 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib sigs http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sigs Randy Witt (5): sstatesig.py: Split single locked sigs check

Re: [OE-core] [PATCH] toaster: add DL_DIR and SSTATE_DIR to oe toasterconf

On 04/06/2016 10:00 AM, Michael Wood wrote: From: Ed Bartosh Shouldn't the message from the cover letter actually be the commit message here, rather than an empty message? Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood

Re: [OE-core] [PATCH] scripts:/oe-selftest: Use timestamp instead of test names in coverage data file

On 03/23/2016 05:32 PM, Humberto Ibarra wrote: This fixes the problem by changing the name to the coverage data file, using the timestamp as an identifier. Fixes what problem? The name for the coverage data file is constructed based on the tests ran; this has created a couple of issues so

[OE-core] [PATCH 2/2] mtools: Make sure mcopy works when using uninative

uninative changes the location of the IBM850 codepage used by mcopy. So make sure to set GCONV_PATH to the correct location when using uninative. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/recipes-devtools/mtools/mtools_4.0.18.bb | 8 +++- 1 file changed, 7 inse

[OE-core] [PATCH 0/2] mtools uninative fix

at: git://git.yoctoproject.org/poky-contrib b82b129692a4eb3c216901cd57d0fc51b0715a9a http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=b82b129692a4eb3c216901cd57d0fc51b0715a9a Randy Witt (2): uninative.bbclass: Set UNINATIVE_LIBDIR if uninative is enabled mtools: Make sure mcopy works

[OE-core] [PATCH 1/2] uninative.bbclass: Set UNINATIVE_LIBDIR if uninative is enabled

Set a variable so other metadata can easily tell where uninative is located. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/uninative.bbclass | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/meta/classes/uninative.bbclass b/meta/c

[OE-core] [PATCH] populate_sdk_ext: Make populate_sdk_ext nostamp

to nostamp. Unnecessary rebuilds may occur, but it's better than a user wondering why their changes didn't get added. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH] populate_sdk_ext: Only write LCONF_VERSION to bblayers if it is set

It is possible that LCONF_VERSION won't be set, such as if meta-poky is used. Without this change, bblayers.conf would have LCONF_VERSION = "None" if LCONF_VERSION wasn't set, which would cause a sanity check failure. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> -

[OE-core] [PATCH] populate_sdk_ext: Delete the buildtools tar file after installation

When installing the ext sdk, buildtools is extracted and installed as well. The tar file containing buildtools isn't used after installation so was wasted space and clutter. [YOCTO #9172] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbcla

[OE-core] [PATCH] populate_sdk_ext: Add images to SDK_INSTALL_TARGETS

sure those additional images are recognized by ext-sdk-prepare.py and don't flag an error. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/meta/classes/populate_sdk_ext

Re: [OE-core] [PATCH 2/4] classes/testsdk: Move the removal of bitbake PATH to eSDK context only

On 02/22/2016 09:05 AM, Aníbal Limón wrote: On 02/22/2016 10:48 AM, Burton, Ross wrote: On 22 February 2016 at 16:37, Aníbal Limón wrote: I agree with you to modify avoid_paths_in_environ for return the new PATH variable is better than only modify it

Re: [OE-core] [PATCH 4/4] oeqa/sdkext: Add sdk_update.SDKUpdateTest class.

On 02/22/2016 08:26 AM, Aníbal Limón wrote: On 02/22/2016 10:18 AM, Randy Witt wrote: On 02/22/2016 07:03 AM, Aníbal Limón wrote: From: Aníbal Limón <limon.ani...@gmail.com> The SDKUpdateTest class test devtool sdk-update mechanism inside eSDK. The SDKUpdateTest class search for n

Re: [OE-core] [PATCH 2/4] classes/testsdk: Move the removal of bitbake PATH to eSDK context only

On 02/22/2016 08:09 AM, Aníbal Limón wrote: On 02/22/2016 09:54 AM, Randy Witt wrote: On 02/22/2016 07:03 AM, Aníbal Limón wrote: From: Aníbal Limón <limon.ani...@gmail.com> The removal of bitbake and scripts PATH is only needed by eSDK tests so move to eSDK context only. This als

Re: [OE-core] [PATCH 4/4] oeqa/sdkext: Add sdk_update.SDKUpdateTest class.

On 02/22/2016 07:03 AM, Aníbal Limón wrote: From: Aníbal Limón The SDKUpdateTest class test devtool sdk-update mechanism inside eSDK. The SDKUpdateTest class search for new sdk if not found uses the main one then it publish the eSDK into known folder inside work and it

Re: [OE-core] [PATCH 2/4] classes/testsdk: Move the removal of bitbake PATH to eSDK context only

On 02/22/2016 07:03 AM, Aníbal Limón wrote: From: Aníbal Limón The removal of bitbake and scripts PATH is only needed by eSDK tests so move to eSDK context only. This also it's a support for eSDK update test because it needs to execute oe-publish-sdk from scripts.

[OE-core] [PATCH v2] signing-keys: Make signing keys the only publisher of keys

Previously the keys were put into the os-release package. The package indexing code was also deploying the keys rather than only using the keys. This change makes signing-keys.bb the only publisher of the keys and also uses standard tasks that already have sstate. Signed-off-by: Randy Witt

[OE-core] [PATCH v2 3/3] populate_sdk_ext.bbclass: Add SDK_RECRDEP_TASKS variable

known to be required for the image as well as for building new recipes. So the SDK_RECRDEP_TASKS variable allows a user to specify additional tasks that need to be pulled in. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 4 +++- 1 file c

Re: [OE-core] [PATCH 3/3] populate_sdk_ext.bbclass: Add SDK_RECRDEP_TASKS variable

On 02/18/2016 02:57 PM, Richard Purdie wrote: On Thu, 2016-02-18 at 09:17 -0800, Randy Witt wrote: Currently there isn't a way for the extensible sdk to know all the tasks that will need sstate for an image. This is because a layer can add it's on custom tasks that are required for an image

[OE-core] [PATCH 2/3] devtool: Don't recursively look for .devtoolbase in --basepath

-by: Randy Witt <randy.e.w...@linux.intel.com> --- scripts/devtool | 28 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/scripts/devtool b/scripts/devtool index 2d57da0b..23e9b50 100755 --- a/scripts/devtool +++ b/scripts/devtool @@ -192,13 +192,6 @@ de

[OE-core] [PATCH 1/3] populate_sdk_ext: Don't ignore SDK_TARGETS value

This fixes a problem where SDK_INSTALL_TARGETS wouldn't pick up the value in SDK_TARGETS. It also removes the inline python to make the code more readable. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 13 - 1 file chang

[OE-core] [PATCH 3/3] populate_sdk_ext.bbclass: Add SDK_RECRDEP_TASKS variable

known to be required for the image as well as for building new recipes. So the SDK_RECRDEP_TASKS variable allows a user to specify additional tasks that need to be pulled in. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 2 +- 1 file c

[OE-core] [PATCH 0/3] extsdk bug fixes

://git.yoctoproject.org/poky-contrib 941d876fe835bc1aa26039d0edec9573d482bca3 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=941d876fe835bc1aa26039d0edec9573d482bca3 Randy Witt (3): populate_sdk_ext: Don't ignore SDK_TARGETS value devtool: Don't recursively look for .devtoolbase in --basepath

[OE-core] [PATCH] signing-keys: Make signing keys the only publisher of keys

Previously the keys were put into the os-release package. The package indexing code was also deploying the keys rather than only using the keys. This change makes signing-keys.bb the only publisher of the keys and also uses standard tasks that already have sstate. Signed-off-by: Randy Witt

[OE-core] [PATCH 2/5] toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOME

orkspace" won't work. For now only set PYTHONPATH instead and continue using the python that comes from buildtools. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/toolchain-scripts.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --gi

[OE-core] [PATCH 1/5] copy_buildsystem.py: Pass the nativelsb argument to gen-lockedsig-cache

dy existed in the input_sstate_cache. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/lib/oe/copy_buildsystem.py | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/meta/lib/oe/copy_buildsystem.py b/meta/lib/oe/copy_buildsystem.py index fb51b51..0627461 100644 -

[OE-core] [PATCH 0/5] extsdk bug fixes and minimal type addition

://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=fcef7183f0ac9ab38715bb0c0a80109696d79b2d Randy Witt (5): copy_buildsystem.py: Pass the nativelsb argument to gen-lockedsig-cache toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOME populate_sdk_ext: Don't set

[OE-core] [PATCH 3/5] populate_sdk_ext: Don't set sdk_update_targets in the config

sdk_update_targets isn't used by any code, so there is no reason to set it. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/c

[OE-core] [PATCH 5/5] populate_sdk_ext: Make populate_sdk_ext depend on sdk_extra_conf

If a user changes sdk_extra_conf, it should cause populate_sdk_ext to run. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meta/classes/populate_sdk_ext.bbclass

[OE-core] [PATCH 4/5] populate_sdk_ext: Add support for a "minimal" type

If the user sets the SDK_EXT_TYPE variable to "minimal" then the sdk won't contain any sstate. The sstate can come from an sstate mirror and be installed on demand as usual. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 15 ++

[OE-core] [PATCH] populate_sdk_ext: Add SSTATE_MIRRORS to config blacklist

SSTATE_MIRRORS used by the builder may not be the same as what the installer of the sdk will use. Therefore blacklist SSTATE_MIRRORS from the builder configuration. Note: the actual SSTATE_MIRRORS for the sdk can be added using sdk_extra_conf. Signed-off-by: Randy Witt <randy.

Re: [OE-core] [PATCH] pixz: Add 1.0.6

On 01/08/2016 10:22 AM, Richard Purdie wrote: xz gives better compression results than bzip/gz but is often slower. Using parallel compression mitigates this somewhat and is particularly useful for the SDK. xz as of 5.2.0 allows for multi-threaded compression.

[OE-core] [PATCH 3/3] populate_sdk_ext: Don't put nativesdk and crosssdk items in ext sdk

of the extensible sdks that include sstate by ~300MB. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass

[OE-core] [PATCH 1/2] copy_buildsystem.py: Allow substring matches for excluded_targets

This is so that the excluded_targets passed to prune_lockedsigs can take a partial form such as nativesdk to filter based on partial matches. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/lib/oe/copy_buildsystem.py | 7 +-- 1 file changed, 5 insertions(+), 2 del

[OE-core] [PATCH 0/2] Extensible SDK size reduction

://git.yoctoproject.org/poky-contrib rewitt/extsdksize http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rewitt/extsdksize Randy Witt (2): copy_buildsystem.py: Allow substring matches for excluded_targets populate_sdk_ext: Don't put nativesdk and crosssdk items in ext sdk meta/classes

[OE-core] [PATCH 2/2] populate_sdk_ext: Don't put nativesdk and crosssdk items in ext sdk

of the extensible sdks that include sstate by ~300MB. Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/classes/populate_sdk_ext.bbclass | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass

Re: [OE-core] [jethro][master][PATCH 1/1] uninative.bbclass: Choose the correct loader based on BUILD_ARCH

On 12/10/2015 02:01 PM, Burton, Ross wrote: On 9 December 2015 at 20:50, Randy Witt <randy.e.w...@linux.intel.com> wrote: -UNINATIVE_LOADER = "${STAGING_DIR_NATIVE}/lib/ld-linux-x86-64.so.2" +UNINATIVE_LOADER ?= "${@bb.utils.contains('BUILD_ARCH', 'x86_64', '${STAGING_DIR

[OE-core] [jethro][master][PATCH 0/1] Fix for 32-bit uninative

/cgit.cgi/poky-contrib/log/?h=rewitt/uninative-32bit-fix Randy Witt (1): uninative.bbclass: Choose the correct loader based on BUILD_ARCH meta/classes/uninative.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.4.3

[OE-core] [jethro][master][PATCH 1/1] uninative.bbclass: Choose the correct loader based on BUILD_ARCH

Previously UNINATIVE_LOADER was always ld-linux-x86-64.so.2. That is incorrect when the host is 32-bit. This change also changes to using ?= so the user can override UNINATIVE_LOADER if so desired. [YOCTO #8124] Signed-off-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/c

Re: [OE-core] RFC: Reference updater filesystem

On Mon, Nov 23, 2015 at 1:41 PM, Mariano Lopez < mariano.lo...@linux.intel.com> wrote: > There has been interest in an image based software updater in Yocto > Project. The proposed solution for a image based updater is to use Stefano > Babic's software updater (http://sbabic.github.io/swupdate).

Re: [OE-core] [PATCH] scripts: analyze_patch: Analyze patch and suggest tests.

On 11/23/2015 07:55 AM, Leonardo Sandoval wrote: Hi Daniel, Some comments inline. BTW, is the script's output intended to be used as input of another one? Currently, the output is human-friendly (which is good) but at the end the purpose is to use the output and run this set of scripts/tests

Re: [OE-core] [PATCH 1/1] glibc: Allow 64 bit atomics for x86

On Thu, Oct 29, 2015 at 3:20 PM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Thu, 2015-10-29 at 13:43 -0700, Juro Bystricky wrote: > > This patch fixes [YOCTO#8140]. > > > > The fix consist of allowing 64bit atomic ops for x86. > > This should be safe for i586 and newer CPUs.

[OE-core] [PATCH 4/5] mtools_4.0.18.bb: Use create_wrapper() for mcopy

-by: Randy Witt <randy.e.w...@linux.intel.com> --- meta/recipes-devtools/mtools/mtools_4.0.18.bb | 5 + 1 file changed, 5 insertions(+) diff --git a/meta/recipes-devtools/mtools/mtools_4.0.18.bb b/meta/recipes-devtools/mtools/mtools_4.0.18.bb index 52decfd..24c9d49 100644 --- a/meta/r

[OE-core] [PATCH 5/5] wic/utils/oe/misc.py: Preserve PATH when running native tools

Previously exec_native_cmd() would remove all items from PATH except for the native sysroot. This can cause issues for the tools that are created using create_wrapper(). Now instead of wiping out the PATH, run a sanity check to check if the command is in the native sysroot. Signed-off-by: Randy

[OE-core] [PATCH 0/5] Fix live images when using the extensible sdk

/cgit.cgi/poky-contrib/log/?h=rewitt/codepage Randy Witt (3): Add 850 codepage to uninative-tarball mtools_4.0.18.bb: Use create_wrapper() for mcopy wic/utils/oe/misc.py: Preserve PATH when running native tools Richard Purdie (2): scripts/oe-pkgdata-util: Fix variable name in error handling

[OE-core] [PATCH 1/5] Add 850 codepage to uninative-tarball

--- meta/recipes-core/meta/uninative-tarball.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-core/meta/uninative-tarball.bb b/meta/recipes-core/meta/uninative-tarball.bb index 41f7927..21f3bd9 100644 --- a/meta/recipes-core/meta/uninative-tarball.bb +++

[OE-core] [PATCH 2/5] scripts/oe-pkgdata-util: Fix variable name in error handling

From: Richard Purdie Fix: logger.error('Unable to find pkgdata directory %s' % pkgdata_dir) NameError: global name 'pkgdata_dir' is not defined Signed-off-by: Richard Purdie --- scripts/oe-pkgdata-util | 2 +- 1 file

[OE-core] [PATCH 3/5] populate_sdk_base: Ensure PKGDATA_DIR exists

From: Richard Purdie Signed-off-by: Richard Purdie --- meta/classes/populate_sdk_base.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/populate_sdk_base.bbclass

[OE-core] [PATCH] runqemu-internal: Make sure two serial ports always exist

Since inittab for qemu images now always tries to start getty on a second serial device, make sure that device exists. Otherwise the following message will be spammed: INIT: Id "S1" respawning too fast: disabled for 5 minutes [YOCTO #8374] Signed-off-by: Randy Witt

Re: [OE-core] [oe] Extensible SDK install errors

On Tue, Aug 25, 2015 at 6:11 PM, Adam Lee adam.yh@gmail.com wrote: Thanks for your comments. I was not running the installer as root. I tried again and specified the install path in my home directory. This time it seems to have gone further, but still failed with this: error: Can't

[OE-core] [PATCH] runqemu: Add a tcpserial option

. This is because the hardware for the virt machine is hardcoded in the device tree blob and the addition devices must be virtio devices. So runqemu can specify virtio for qemuarm64 whereas it seems all other qemu machines work with the -serial tcp* option. Signed-off-by: Randy Witt randy.e.w

[OE-core] [PATCH V2 1/3] qemurunner.py: Move some class variables that should only be local

The bootlog and qemusock variables were set in the class as part of the create_socket() routine. However those variables are never used outside of the same function and thus serve no purpose as class variables. This initializes those variables near where they are used. Signed-off-by: Randy Witt

[OE-core] [PATCH V2 2/3] qemurunner: Make create_socket() return data and use exceptions

So that create_socket() can be called more than once to create sockets, it now returns the socket and port rather than setting class variables directly. create_socket() now only uses exceptions for errors, not the return value from the function. Signed-off-by: Randy Witt randy.e.w

[OE-core] [PATCH V2 3/3] qemurunner: Use two serial ports and log console with a thread

to use for the sole purpose of watching for the sentinel as well as being the interactive serial port. This will also prevent the possibility of lots of debug data on the console preventing the sentinel value from being seen due to interleaved text. Signed-off-by: Randy Witt randy.e.w

[OE-core] [PATCH V2 0/3] Try to fix qemu freezing due to full socket buffers

Fix copy and pasted error message that had no meaning to the actual timeout. -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 3/3] toolchain-shar-extract.sh: explain why we cannot use sudo in extensible SDK

On 08/19/2015 06:32 AM, brendan.le.f...@intel.com wrote: From: Brendan Le Foll brendan.le.f...@intel.com Signed-off-by: Brendan Le Foll brendan.le.f...@intel.com --- meta/files/toolchain-shar-extract.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 1/3] qemurunner.py: Move some class variables that should only be local

The bootlog and qemusock variables were set in the class as part of the create_socket() routine. However those variables are never used outside of the same function and thus serve no purpose as class variables. This initializes those variables near where they are used. Signed-off-by: Randy Witt

[OE-core] Try to fix qemu freezing due to full socket buffers

changes up to c0f8b3c28c4410031dc763e714bc2ad0f87171d6: qemurunner: Use two serial ports and log console with a thread (2015-08-20 14:16:29 -0700) Randy Witt (3): qemurunner.py: Move some class variables that should only

  1   2   >