[OE-core] [PATCH 2/2] poky: Remove machine specific kernel overrides

les for that machine, not in the distro conf. Signed-off-by: brian avery <brian.av...@intel.com> --- meta-poky/conf/distro/poky.conf | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf index c907969.

[OE-core] [PATCH 1/2] meta-yocto-bsp: Remove superfluous kernel set

The genericx86 and genericx86-64 machine confs do not need to set the PREFERRED_PROVIDER_virtual/kernel as they will use the one set by the distribution. If there needed to be a different version for one of these machines in the future, we could add it in to the machine.conf. Signed-off-by: brian

[OE-core] [PATCH 0/2] remove qemu kernel version overrides and superfluous version settings

in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/mv_linux-yocto_into_machineconf http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/mv_linux-yocto_into_machineconf brian avery (2): meta-yocto-bsp: Remove superfluous kernel set poky: Remove machine speci

Re: [OE-core] [PATCH] gcc-7.inc: add new warning "Wnot-cross-compiler"

On Wed, Jul 19, 2017 at 6:35 PM, Khem Raj wrote: > On Wed, Jul 19, 2017 at 7:26 PM, Andre McCurdy > wrote: > > On Wed, Jul 19, 2017 at 2:57 PM, Bystricky, Juro > > wrote: > >>> precisely, the problem is that some host compiler

[OE-core] [PATCH 1/1] scripts/oe-setup-rpmrepo: leverage oe-run-native

RSS means we no longer have a large native sysroot to run binaries from. oe-run-native deals with this already, so this patch uses oe-run-native to call the createrepo_c native binary that we need to make the package feed indices. [YOCTO #11706] Signed-off-by: brian avery <brian.av...@intel.

[OE-core] [PATCH 0/1] scripts: make createrepo_c run

This uses oe-run-native to run the createrepo_c native binary. RSS means we need additional steps to run native binaries, so it is better to consolidate the logic. -brian avery The following changes since commit 98099349e358a9caaec8ec81f0d4abe588909cfe: bitbake: npm fetcher: fix unknown

Re: [OE-core] [PATCH 1/1] runqemu: drop RPC ports

looks good 2 me! ty, b an intel employee On Thu, Jun 22, 2017 at 1:30 AM, Robert Yang wrote: > The following commit has removed rpc ports from runqemu-export-rootfs, so > runqemu should also remove them, otherwise "runqemu nfs" doesn't work. And > use > abspath for

Re: [OE-core] [PATCH 1/1] tcf-agent: add -USR2 to stop/kill initscript

at 4:15 PM, Martin Kelly <mke...@xevo.com> wrote: > Looks like this is addressing the same problem as Jan's patch from earlier > today. I think the differences are: > > - kill vs start-stop-daemon > > - Jan removed the retry loop while this patch does not > > > On

[OE-core] [PATCH 1/1] tcf-agent: add -USR2 to stop/kill initscript

The current initscript was lacking a -USR2 signal in the stop section. This resulted in /etc/init.d/tcf-agent stop; taking roughly 10 seconds then failing to kill the tcf-agent process. This patch brings us in line with how upstream stops the agent. Fixes [YOCTO #10858] Signed-off-by: brian

[OE-core] [PATCH 0/1] tcf-agent: add -USR2 to stop/kill initscript

+0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/tcf-agent/10858 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/tcf-agent/10858 brian avery (1): tcf-agent: add -USR2 to stop/kill initscript meta/recipes-devtools/tcf-agent/tcf

Re: [OE-core] [PATCH 1/1] oe-find-native-sysroot: don't clear OECORE_NATIVE_SYSROOT

This worked for me. Tested on sdk and esdk and bitbake std build. Also added info to bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=11409. -brian an intel employee On Mon, Apr 24, 2017 at 8:35 PM, Robert Yang wrote: > The OECORE_NATIVE_SYSROOT may come from

[OE-core] [PATCH 1/1] testimage.bbclass: add additional dependency

to make it clearer what you need to do if you try to run testimage before you have built or downloaded the image artifacts. [YOCTO #11375] Signed-off-by: brian avery <brian.av...@intel.com> --- meta/classes/testimage.bbclass | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff

[OE-core] [PATCH 0/1] testimage: Add missing dependency

repository at: git://git.yoctoproject.org/poky-contrib bavery/testimage/11375_2 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/testimage/11375_2 brian avery (1): testimage.bbclass: add additional dependency meta/classes/testimage.bbclass | 8 ++-- 1 file changed, 6 insert

[OE-core] [PATCH 3/3] qemuboot.bbclass: save relative paths in conf file

This saves relative paths in the qemuboot.conf file instead of absolute paths. This is to allow the images and kernels to be relocated and still have the testimage and runqemu work. [YOCTO #11375] Signed-off-by: brian avery <brian.av...@intel.com> --- meta/classes/qemuboot.bbcla

[OE-core] [PATCH 1/3] meta: add search, replace strings to export2json

-by: brian avery <brian.av...@intel.com> --- meta/lib/oe/data.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/lib/oe/data.py b/meta/lib/oe/data.py index 80bba2b..b8901e6 100644 --- a/meta/lib/oe/data.py +++ b/meta/lib/oe/data.py @@ -17,7 +17,7 @@ def typed_val

[OE-core] [PATCH 2/3] rootfs-postcommands.bbclass: save relative paths

We pass the TOPDIR to do a search/replace in export2json so that we save relative paths in the testdata.json file rather than absolute paths. This is to allow the images and kernels to be relocated yet still allow testimage to work. [YOCTO #11375] Signed-off-by: brian avery <brian

[OE-core] [PATCH 0/3] meta: save relative paths to qemuboot.conf and testdata.json

) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/poky/relpath_11375 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/poky/relpath_11375 brian avery (3): meta: add search,replace strings to export2json rootfs-postcommands.bbclass: save relative

[OE-core] [PATCH 2/4] oe-find-native-sysroot: work with RSS

From: Robert Yang The generic STAGING_DIR_NATIVE is gone since RSS, so when find OECORE_NATIVE_SYSROOT, the user has to specify which recipe's STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT. * The usage is changed from ". oe-find-native-sysroot" to ".

[OE-core] [PATCH 3/4] oe-find-native-sysroot: add appopriate suggestion

right now, if it fails, the script tells the user to run bitbake foo -caddto_recipe_sysroot. This works for native recipes but not things like meta-ide. This patch checks whether the recipe is native and gives out the appopriate warning. Signed-off-by: brian avery <brian.av...@intel.

[OE-core] [PATCH 1/4] Revert "scripts: change way we find native tools (pseudo)"

s both. Therefore, reverting this patch in favor of his. Signed-off-by: brian avery <brian.av...@intel.com> --- scripts/oe-find-native-sysroot | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot index 3f4c

[OE-core] [PATCH 4/4] oe-run-native: explicitly use bash

This script sources another script (oe-find-native-sysroot) with arguments. It was using /bin/sh. Sourcing with arguments works only in bash so it was failing in dash. This commit makes it dash proof. Signed-off-by: brian avery <brian.av...@intel.com> --- scripts/oe-run-native | 2 +-

[OE-core] [PATCH 0/4] scripts: rss fixes for oe-find-sysroot and oe-run-native

pts: change way we find native tools (pseudo)" Robert Yang (1): oe-find-native-sysroot: work with RSS brian avery (2): oe-find-native-sysroot: add appopriate suggestion oe-run-native: explicitly use bash scripts/oe-find-native-sysroot | 59 -

Re: [OE-core] [PATCH 1/2] scripts: change way we find native tools (pseudo)

# add old path to allow usage of host tools > PATH=$PATH:$OLD_PATH $@ > else > - echo "Error: Unable to find '$1' in native sysroot" > +echo "Error: Unable to find '$tool' in $PATH" > exit 1 > fi > diff --git a/scripts/runqemu-export-root

[OE-core] [PATCH 1/1] devtool: point runqemu to correct native bindir

devtool/runqemu.py was relying on STAGING_BINDIR_NATIVE to find the host tools it needed like qemu-system-. In the post RSS world, this no longer exists. This patch points it to {STAGING_DIR}/{BUILD_ARCH}/{bindir_native}. [YOCTO #11223] Signed-off-by: brian avery <brian.av...@intel.

[OE-core] [PATCH 0/1] esdk: Fixes for runqemu and sysroot

bitbake: bitbake-user-manual: Fixed special character in -D output (2017-04-03 22:32:02 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/esdk_sadqemu/bug11223 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/esdk_sadqemu/bug11223 b

[OE-core] [PATCH 2/2] meta-ide-support: exclude this recipe from rm_work

The results of meta-ide-support are used by utilities like runqemu and runqemu-extract-sdk. Since the usr/bin that meta-ide-support creates is subsequently removed bu rm_work, we exclude this recipe from the rm_work list. [YOCTO #9] Signed-off-by: brian avery <brian.av...@intel.

[OE-core] [PATCH 1/2] scripts: change way we find native tools (pseudo)

-by: brian avery <brian.av...@intel.com> --- scripts/oe-find-native-sysroot | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot index 13a5c46..3f4c29d 100755 --- a/scripts/oe-find-native-sysroot +++ b/scri

[OE-core] [PATCH 0/2] runqemu-extract-sdk: Fixes for RSS

3 22:32:02 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/sadpseudo/bug9 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/sadpseudo/bug11119 brian avery (2): scripts: change way we find native tools (pseudo) meta-ide-suppor

Re: [OE-core] [PATCH 0/1] gen-lockedsig-cache: catch os.link error V2

o:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > > brian avery > > Sent: den 17 mars 2017 13:50 > > To: openembedded-core@lists.openembedded.org > > Subject: [OE-core] [PATCH 0/1] gen-lockedsig-cache: catch os.link error > V2 > > > > If your sstate-cache dir

[OE-core] [PATCH V3 1/1] gen-lockedsig-cache: catch os.link error

We do a hard link to speed up sdk creation but if your sstate-cache is across a file system boundary, this tries and fails. This patch catches that error and does a copy instead. Signed-off-by: brian avery <brian.av...@intel.com> --- scripts/gen-lockedsig-cache | 6 +- 1 file chan

[OE-core] [PATCH V3 0/1] gen-lockedsig-cache: catch os.link error

-host.bb: add cmake (2017-03-17 16:53:06 +) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/gen-sigs-linkfix http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/gen-sigs-linkfix brian avery (1): gen-lockedsig-cache: catch os.link error

[OE-core] [PATCH 2/2] bitbake.conf: remove vi from HOSTTOOLS list

Having changes the sdk test to cpio from cvs, we no longer require an editor to be present. This patch removes vi from the list of required tools. Signed-off-by: brian avery <brian.av...@intel.com> --- meta/conf/bitbake.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[OE-core] [PATCH 1/2] meta/lib/oeqa: change sdk test from cvs to cpio

switches from using cvs as a test to using cpio. cpio also uses autotools so the functionality tested is equivalent. Signed-off-by: brian avery <brian.av...@intel.com> --- meta/classes/testimage.bbclass| 6 +++--- meta/lib/oeqa/runtime/cases/{buildcvs.py => bui

[OE-core] [PATCH 0/2] testsdk: use cpio instead of cvs as test

: nativesdk-packagegroup-sdk-host.bb: add cmake (2017-03-17 16:53:06 +) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/changeCVSTestToCpioTest http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/changeCVSTestToCpioTest brian avery (2

[OE-core] [PATCH 0/2] testsdk: use cpio instead of cvs as test

: nativesdk-packagegroup-sdk-host.bb: add cmake (2017-03-17 16:53:06 +) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/changeCVSTestToCpioTest http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/changeCVSTestToCpioTest brian avery (2

[OE-core] [PATCH 1/1] gen-lockedsig-cache: catch os.link error V2

We do a hard link to speed up sdk creation but if your sstate-cache is across a file system boundary, this tries and fails. This patch catches that error and does a copy instead. Signed-off-by: brian avery <brian.av...@intel.com> --- scripts/gen-lockedsig-cache | 6 +- 1 file chan

[OE-core] [PATCH 0/1] gen-lockedsig-cache: catch os.link error V2

) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/gen-sigs-linkfix http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/gen-sigs-linkfix brian avery (1): gen-lockedsig-cache: catch os.link error scripts/gen-lockedsig-cache | 6 +- 1 file changed, 5

[OE-core] [PATCH 1/1] tivesdk-packagegroup-sdk-host.bb: add cmake

The Eclipse plugin uses cmake from the SDK and currently has issues because cmake is not installed as a host tool. This patch adds cmake as a host tool for the sdk/esdk. Signed-off-by: brian avery <brian.av...@intel.com> --- meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.

[OE-core] [PATCH 0/1] add cmake host tool to sdk and esdk

-and-esdl brian avery (1): tivesdk-packagegroup-sdk-host.bb: add cmake meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 1 + 1 file changed, 1 insertion(+) -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core

[OE-core] [PATCH 1/1] gen-lockedsig-cache: catch os.link error

We do a hard link to speed up sdk creation but if your sstate-cache is across a file system boundary, this tries and fails. This patch catches that error and does a copy instead. Signed-off-by: brian avery <brian.av...@intel.com> --- scripts/gen-lockedsig-cache | 6 ++ 1 file chan

[OE-core] [PATCH 0/1] gen-lockedsig-cache: catch os.link error

-linkfix brian avery (1): gen-lockedsig-cache: catch os.link error scripts/gen-lockedsig-cache | 6 ++ 1 file changed, 6 insertions(+) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http

Re: [OE-core] [Openembedded-architecture] RFC BuildAppliance future

ame kernel as the host. Thanks for the feedback and if I missed or shortchanged something please let me know, -Brian an intel employee On Mon, Dec 5, 2016 at 10:42 AM, Khem Raj <raj.k...@gmail.com> wrote: > On Mon, Dec 5, 2016 at 10:04 AM, Brian Avery <avery.br...@gmail.com> &

[OE-core] RFC BuildAppliance future

Please note, this is going out to 3 lists in an attempt to insure that no one who would be impacted by this change misses it. Implied spam apology included. The Yocto Project currently provides a virtual machine image called the Build Appliance (

[OE-core] [PATCH 1/1] This is a backport from master of 2 consecutive fixes.

r...@intel.com> Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org> Signed-off-by: brian avery <brian.av...@intel.com> --- meta/recipes-core/base-files/base-files/profile | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/recipes-core/base-files/base-fil

[OE-core] [PATCH 0/1] [Krogoth] base-files: fix tty resize check

This backports the 2 changes to base-files /etc/profile that addressed problems with the way the tty was being checked to decide whether to run resize or not. When the tty check has errors, it prevents Eclipse debugging from working. -brian avery The following changes since commit

Re: [OE-core] [PATCH 1/1] qemurunner: print out the runqemu command

true, you do, kind of. This commit explicitly prints out what the runqemu cmd is (for instance "runqemu snapshot -m 1024"), which is a lot easier to enter if you want to rerun qemu the way the test did. It's not a big deal, I just ended up adding it while i was trying to figure out how the tests

Re: [OE-core] [PATCH 1/2] packagegroup-core-eclipse-debug: add openssh server to support openssh-sftp-server

Hi, I spent some time today and could not replicate the issues I had with dropbear+openssh-sftp-server under Eclipse. Since I ran into these issues while tracking down the busybox/resize issue it could easily have been a red herring. So, I'm resending with the openssh-server patch removed.

Re: [OE-core] RFC: eclipse debug functionality issue

> > On 8/4/16 2:20 PM, Brian Avery wrote: > > > The core issue: > > > The busybox resize command breaks the eclipse ssh debug stream. > > > This is > > > because the resize command for busybox sends a set of cursor > > > contr

[OE-core] RFC: eclipse debug functionality issue

The core issue: The busybox resize command breaks the eclipse ssh debug stream. This is because the resize command for busybox sends a set of cursor control escape sequences to stderr. The resize cfg was added to Krogoth and is still in master. The point of resize is to set the environment and

[OE-core] [PATCH 0/1] meta/conf/toasterconf.json - remove SDKMACHINE variable

://git.yoctoproject.org/poky-contrib bavery/remove-SDKMAHINE-meta-toasterconf http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/remove-SDKMAHINE-meta-toasterconf brian avery (1): meta/conf/toasterconf.json: remove SDKMACHINE variable as it no longer used meta/conf

[OE-core] [PATCH 1/1] meta/conf/toasterconf.json: remove SDKMACHINE

Signed-off-by: brian avery <avery.br...@gmail.com> --- meta/conf/toasterconf.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/conf/toasterconf.json b/meta/conf/toasterconf.json index c8e42ef..1987793 100644 --- a/meta/conf/toasterconf.json +++ b/met

Re: [OE-core] [PATCH 1/2] systemd: test target boot time against unit timeout

On Fri, Oct 23, 2015 at 8:57 AM, Benjamin Esquivel wrote: > This reminds me I haven't been able to parse your logs to check your > data. If what you say is true, that the failure is presented when the > system (kernel + userspace) booted in less than 90 secs,

[OE-core] [PATCH 0/1] Create error recipe and error image, for testing

in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/test/error-recipe http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/test/error-recipe brian avery (1): meta-selftest: add error recipe and error-image meta-selftest/recipes-test/error/error.bb

[OE-core] [PATCH 1/1] meta-selftest: add error recipe and error-image

* The error recipe throws an error during compile * The error-image includes the error recipe * Initial target is toaster selenium testing Signed-off-by: brian avery <avery.br...@gmail.com> --- meta-selftest/recipes-test/error/error.bb| 11 +++ meta-selftest/r

[OE-core] [FIDO PATCH 1/1] toasterconf: remove master as a branch option from fido release

-by: Alexandru DAMIAN alexandru.dam...@intel.com Signed-off-by: brian avery avery.br...@gmail.com --- meta/conf/toasterconf.json | 23 --- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/meta/conf/toasterconf.json b/meta/conf/toasterconf.json index c8e42ef..ecd6a9f 100644

[OE-core] [FIDO PATCH 0/1] toasterconf: remove master as a branch option from fido release

Toaster from FIDO can't reasonably be expected to be able to build master due to unforeseeable incompatibilities. This removes master branch as an option. Alexandru DAMIAN (1): toasterconf: remove master for fido meta/conf/toasterconf.json | 23 --- 1 file changed, 4