Re: [yocto] Accelerate kernel module built in eSDK?

On Fri, 2018-12-28 at 18:19 +0800, Zhaolong Zhang wrote: > Hi Experts, > > Building out-of-tree kernel modules in eSDK will trigger a new > rebuilding of kernel, which consumes lots of time. > Is it possible to cache the do_shared_workdir() task in sstate-cache > and ship it within eSDK? And how?

Re: [yocto] x86_64 kernel with i586 userland plus SDK?

On Mon, 2018-12-17 at 11:26 +0100, Richard Weinberger wrote: > On Wed, Nov 28, 2018 at 9:42 AM Richard Purdie > wrote: > > The system can definitely do it, its just not something we tend to > > do > > very often so its not entirely clear the best way to do it. > >

[yocto] [PATCH][auh] upgradehelper: Replace do_checkpkg usage with oe.recipeutils function call

and clarifing the code. This change uses a lib/oe/recipeutils function call to remove the need to use checkpkg at all. Signed-off-by: Richard Purdie --- upgradehelper.py | 105 ++- 1 file changed, 39 insertions(+), 66 deletions(-) diff --git

[yocto] [PATCH][auh] upgradehelper: Replace do_checkpkg usage with direct tinfoil calls

are not skipped here (images, pieces of gcc, nativesdk only recipes). Signed-off-by: Richard Purdie --- upgradehelper.py | 148 ++- 1 file changed, 82 insertions(+), 66 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 8fb27d3..7ad4917 100755

Re: [yocto] [PATCH] meta-yocto-bsp: beaglebone-yocto.conf: support 8250 serial driver

On Mon, 2018-12-10 at 12:01 +0100, Heiko Schocher wrote: > Hello all, > > Am 13.11.2018 um 08:06 schrieb Heiko Schocher: > > it is possible to use the beagleboneblack with the 8250 serial > > driver or with the deprecated omap serial driver. > > > > Unfortunately serial console get different

Re: [yocto] x86_64 kernel with i586 userland plus SDK?

On Mon, 2018-12-03 at 09:52 +0100, Richard Weinberger wrote: > On Wed, Nov 28, 2018 at 9:26 PM Richard Weinberger > wrote: > > Richard, > > > > On Wed, Nov 28, 2018 at 9:42 AM Richard Purdie > > wrote: > > > > But it seems that building an

Re: [yocto] QA cycle report for 2.4.4 RC1

On Wed, 2018-11-28 at 07:07 +, Jain, Sangeeta wrote: > The test cases run for 2.4.4 RC1 are same as run for 2.4 release. Ok, but I'm not sure they're correct. Are the test cases we're talking about also run for the 2.5 release? I'll explain more below. > > Thanks for running the QA for

Re: [yocto] x86_64 kernel with i586 userland plus SDK?

Hi, On Tue, 2018-11-27 at 22:46 +0100, Richard Weinberger wrote: > I have a hard time understanding how to build a distro with x86_64 > kernel, i586 userland > and an SDK for that. > In the beginning I assumed and have been told on IRC that multilib is > the way to go. > > But it seems that

Re: [yocto] Autobuilder changes

On Sat, 2018-11-24 at 07:40 -0700, akuster wrote: > On 11/23/18 10:02 AM, Richard Purdie wrote: > > We now run "a-quick" on master at 1am every day which will make > > What Time zone for 1am? I'm not 100% sure but I think its UTC. > > Building older releases

Re: [yocto] [OE-core] Autobuilder changes

On Fri, 2018-11-23 at 17:02 +, Richard Purdie wrote: > I've take this quiet period as an opportunity to make some > significant autobuilder changes: I knew I was missing something: Successful builds are now deleted when they complete using the background deletion (clobberdir). This

[yocto] Autobuilder changes

I've take this quiet period as an opportunity to make some significant autobuilder changes: The targets have all been renamed and split up. "nightly-arm" became "qemuarm" and "beaglebone". The "nightly-" prefixes were dropped. The nightly target was dropped and replaced by "a-quick" and

Re: [yocto] QA cycle report for 2.4.4 RC1

On Fri, 2018-11-23 at 03:23 +, Jain, Sangeeta wrote: > > Hello All, > > This is the full report for 2.4.4 RC1: > https://wiki.yoctoproject.org/wiki/WW46_-_2018-11-14_-_Full_Test_Cycle_2.4.4_RC1 > > > Summary > > All planned tests were executed. > > Total Test Executed – 3330 >

Re: [yocto] Yocto layers missing thud branches

On Tue, 2018-11-20 at 16:21 -0700, akuster808 wrote: > > On 11/20/18 4:05 PM, Richard Purdie wrote: > > On Mon, 2018-11-19 at 09:47 +1300, Paul Eggleton wrote: > > > On Monday, 19 November 2018 12:11:35 AM NZDT Max Krummenacher wrote: > > > > Am Samstag, de

Re: [yocto] Yocto layers missing thud branches

On Mon, 2018-11-19 at 09:47 +1300, Paul Eggleton wrote: > On Monday, 19 November 2018 12:11:35 AM NZDT Max Krummenacher wrote: > > Am Samstag, den 17.11.2018, 15:50 -0800 schrieb akuster808: > > > Can the maintainers of meta-qt3, meta-qt4, meta-selinux, and > > > meta-cgl > > > please add a "Thud"

Re: [yocto] [OE-core] Yocto Project Status WW46’18

On Tue, 2018-11-13 at 19:59 +, Peter Kjellerstedt wrote: > From the updates below: > > Patches for the thud point release are queuing on the branch. > > On what branch? The thud-next branch is behind the thud branch, and > the master-next branch contains a lot of recipe updates that do

Re: [yocto] QA cycle report for 2.6 M4 RC1

On Sun, 2018-11-11 at 13:18 -0800, akuster808 wrote: > On 11/11/18 2:21 AM, richard.pur...@linuxfoundation.org wrote: > > On Sat, 2018-11-10 at 10:02 -0800, akuster808 wrote: > > > On 11/10/18 8:25 AM, richard.pur...@linuxfoundation.org wrote: > > > > On Fri, 2018-11-09 at 09:24 +, Jain,

Re: [yocto] QA cycle report for 2.6 M4 RC1

On Sat, 2018-11-10 at 10:02 -0800, akuster808 wrote: > > On 11/10/18 8:25 AM, richard.pur...@linuxfoundation.org wrote: > > On Fri, 2018-11-09 at 09:24 +, Jain, Sangeeta wrote: > > > This is the full report for 2.6 M4 RC1: > > >

Re: [yocto] QA cycle report for 2.6 M4 RC1

On Fri, 2018-11-09 at 09:24 +, Jain, Sangeeta wrote: > > This is the full report for 2.6 M4 RC1: > https://wiki.yoctoproject.org/wiki/WW44_-_2018-10-30_-_Full_Test_Cycle_2.6_M4_RC1 Thanks Sangeeta and team! Now we have the QA report for YP 2.6 M4 rc1 (Final 2.6) we need to make a release

Re: [yocto] [yocto-autobuilder-helper][PATCH] config.json: Enable dedicated sstate during build and remove after

On Sat, 2018-11-10 at 04:25 -0800, Michael Halstead wrote: > Without any sstate available oe-selftest cannot run in parallel. Set > sstate to a > location used only by these builds and remove it as the last step. > > Signed-off-by: Michael Halstead > --- > config.json | 5 - > 1 file

Re: [yocto] [RFC] Yocto Autobuilder and LAVA Integration

Hi Anibal, On Wed, 2018-11-07 at 16:25 -0600, Anibal Limon wrote: > We know the need to execute OE testimage over real HW not only QEMU, > > I'm aware that currently there is an implementation on the Yocto > Autobuilder Helper > , this initial implementation looks pretty well separating parts

Re: [yocto] [yocto-autobuilder-helper][PATCH] config.json: Add steps to test new workers before adding to the main pool

On Wed, 2018-11-07 at 11:15 -0800, akuster wrote: > On 11/7/18 10:33 AM, Michael Halstead wrote: > > We add workers to the nightly-bringup pool to test them in a > > production like > > enviroment. Include one completely emulated target and one to test > > virtualization extentions. > > > Would

Re: [yocto] [patchtest-oe][PATCH] test_patch_cve.py: fix cve tag checking logic

On Fri, 2018-11-02 at 14:03 +0800, Chen Qi wrote: > The current logic for checking cve tag is not correct. It errors > out if and only if the patch contains a line which begins with > CVE-- and contains nothing else. > > It will not error out if the patch contains no CVE information, nor

Re: [yocto] [patchtest-oe][PATCH] test_patch_cve.py: fix cve tag checking logic

On Fri, 2018-11-02 at 14:03 +0800, Chen Qi wrote: > The current logic for checking cve tag is not correct. It errors > out if and only if the patch contains a line which begins with > CVE-- and contains nothing else. > > It will not error out if the patch contains no CVE information, nor

[yocto] Yocto Project Source Mirroring - Now working correctly

Hi, At ELC-E/OEDEM there were reports of problems with the project's source mirroring. We've also had reports of problems with people using http only connections without access to git (e.g. being behind http only proxies). Michael and I have looked into it and there were some problems caused by

[yocto] QA notification for completed autobuilder build (yocto-2.6.rc1)

A build flagged for QA (yocto-2.6.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6.rc1 Build hash information: bitbake: 0cfc71d1a342b82781b0ba547421e41f6340902a eclipse-poky-neon: 303e46a6848f1937d12541a7fd58e61aa1361225

Re: [yocto] [opkg-utils PATCH] opkg-make-index: use ctime instead of mtime

stead of > mtime to prevent failures like this. > > Suggested-by: Khem Raj > Signed-off-by: Stefan Agner Acked-by: Richard Purdie (I've been following this problem and this makes sense to me) > --- > This addresses the issue discussed here: > http://lists.openembedded

Re: [yocto] [pseudo] Pseudo 1.8+ xattr sqlite corruption

On Wed, 2018-08-22 at 14:54 +, jack.f...@dell.com wrote: > So failure mode is the target filesystem is devoid of SELinux file > contexts, all files are unlabeled_t, which pretty much breaks > everything in enforcing mode. So whatever the corruption > cause/effect in the Psuedo database, the

Re: [yocto] [yocto-docs][PATCH] ref-manual: Removed misleading paragraph in siteinfo section

On Tue, 2018-08-14 at 10:30 -0700, Scott Rifenbark wrote: > Yevgeny and Richard, > > See the siteinfo.bbclass section here - https://yoctoproject.org/docs > /2.6/ref-manual/ref-manual.html#ref-classes-siteinfo. > > Paragraph removed. Looks good thanks. Cheers, Richard --

Re: [yocto] Yocto userbase in numbers?

On Thu, 2018-08-09 at 17:19 +, Frazer, Will wrote: > I was asked recently what a ballpark figure for the number of systems > running distributions built with yocto might be and I could not find > anything. > > I realise it’s almost impossible to tell since technically everyone > builds a

Re: [yocto] QA cycle report for 2.6 M2 RC1

On Thu, 2018-08-09 at 05:57 +, Yeoh, Ee Peng wrote: > === Summary > > All planned tests were executed except a few SDK automated tests were > skipped in Autobuilder (testrun# 9830-9836, 9796-9797). Team found > that these SDK automated tests were running successfully in core- >

Re: [yocto] Ordering of anonymous Python functions and task signature calculations

On Thu, 2018-07-26 at 09:22 -0500, Matt Hoosier wrote: > On Wed, Jul 25, 2018 at 4:58 PM Richard Purdie > wrote: > Your advice about BB_DONT_CACHE does cause reparsing to get > triggered. I can see that in logs. > > > and that the > > task dependency exists. Yo

Re: [yocto] Ordering of anonymous Python functions and task signature calculations

On Wed, 2018-07-25 at 08:47 -0500, Matt Hoosier wrote: > Quite a while ago I wrote the following message: > On Tue, Jan 24, 2017 at 11:55 AM Matt Hoosier > wrote: > > In order to support a use-case that embeds information about the > > Git revision of Yocto itself that was used to make a build, I

Re: [yocto] QA cycle report for 2.2.4 RC1

On Thu, 2018-07-19 at 09:55 +, Yeoh, Ee Peng wrote: > This is the full report for 2.2.4.rc1: > https://wiki.yoctoproject.org/wiki/WW28_-_2018-07-13_-_Full_Test_Cycl > e_2.2.4_rc1 > > === Summary > > All planned tests were executed. There were zero high milestone > defect.

Re: [yocto] Why can diffsigs take sometimes really looooong?

On Mon, 2018-07-16 at 11:26 +0300, Uwe Geuder wrote: > On Sun, Jul 15, 2018 at 1:38 PM, Richard Purdie wrote: > > On Fri, 2018-07-13 at 19:18 +0300, Uwe Geuder wrote: > > > At times I find the diffsigs command useful/educational to > > > understand > &g

Re: [yocto] Why can diffsigs take sometimes really looooong?

On Fri, 2018-07-13 at 19:18 +0300, Uwe Geuder wrote: > At times I find the diffsigs command useful/educational to understand > what is going on in my build. > > $ bitbake-diffsigs -t myimage do_image > > Often the result is shown in no time. However, recently I got some > cases were it takes 150

Re: [yocto] QA cycle report for 2.3.4 RC1

On Tue, 2018-07-10 at 06:11 +, Yeoh, Ee Peng wrote: > This is the full report for 2.3.4.rc1: > https://wiki.yoctoproject.org/wiki/WW25_-_2018-06-22-_Full_Test_Cycle > _-_2.3.4_rc1 > > === Summary > > All planned tests were executed. There were zero high milestone > defect.

Re: [yocto] [PATCH] [yocto-autobuilder] init: Fix the import module yoctoabb & yocto_console_view

On Wed, 2018-07-11 at 02:23 +, Chan, Aaron Chun Yew wrote: > It appears that your using virtualenv (switch to python3) to startup > your buildbot processes and not using the default python from host > distribution. > I am aware that you can switch interpreter to python2/3 in > virtualenv.

Re: [yocto] [PATCH] [yocto-autobuilder] init: Fix the import module yoctoabb & yocto_console_view

On Tue, 2018-07-10 at 10:47 +, Chan, Aaron Chun Yew wrote: > [Richard] I think this means you're using python2 and we really > should be using > python3 as I don't want to support both... > > [Reply] This error/bug was found during buildbot startup meaning this > is out of my

Re: [yocto] [PATCH] [yocto-autobuilder] master.cfg: Defaults autobuilder URL based on FQDN

On Tue, 2018-07-10 at 11:18 +0800, Aaron Chan wrote: > This patch is to enable auto-assignments buildbot URL based on Hosts FQDN. > The socket module allows the retrieval on FQDN and constructs the entire > URL by default, this default settings can be overwritten in c['buildbotURL'] > based on

Re: [yocto] [PATCH] [yocto-autobuilder] init: Fix the import module yoctoabb & yocto_console_view

On Tue, 2018-07-10 at 11:24 +0800, Aaron Chan wrote: > This patch is to fix the inconsistency in loading custom module > yoctoabb & yocto_console_view during Buildbot Master startup. > > Signed-off-by: Aaron Chan > --- > __init__.py| 0 > yocto_console_view/__init__.py | 0 >

Re: [yocto] [PATCH] [yocto-ab-helper] scripts/run-jinja-parser: Add Jinja2 parser extension in autobuilder

On Fri, 2018-07-06 at 17:15 +0800, Aaron Chan wrote: > This patch is introduced as a feature in 2.6 M2 to support the > extension of autobuilder to LAVA (Linaro Automated Validation > Architecture). > run-jinja2-parser loads lava config module and generates LAVA job > config in a YAML format

Re: [yocto] [PATCH] [yocto-ab-helper] clobberdir: Fix Unicode data expansion with utils API

On Thu, 2018-07-05 at 13:34 +0800, Aaron Chan wrote: > This fix is to move clobberdir from python2 to python3 to resolve > unicode data > in python2 and change the data extraction expansion from > ourconfig["TRASH_DIR"] > to utils.getconfig("TRASH_DIR", ourconfig) on "Clobber build dir" >

Re: [yocto] [PATCH] [yocto-ab-helper] utils.py: Resolved unicode data expansion

Hi Aaron, On Wed, 2018-07-04 at 06:42 +, Chan, Aaron Chun Yew wrote: > This morning I had the new autobuilder setup from scratch with the > latest patch you just check out, thanks for that and rollout the fix > below manually. Everything else is clean and I did what you asked me > to. >

Re: [yocto] [PATCH] [yocto-ab-helper] Extend LAVA buildset JSON to ABHELPER

On Tue, 2018-07-03 at 16:40 +0800, Aaron Chan wrote: > This patch is an extension to default config.json with ABHELPER_JSON > env set. > This extension is to support buildset config for target MACHINE > intel-corei7-64 > with meta-intel layer included. > > Signed-off-by: Aaron Chan > --- >

Re: [yocto] [PATCH] [yocto-ab-helper] utils.py: Resolved unicode data expansion

On Tue, 2018-07-03 at 09:44 +0800, Aaron Chan wrote: > Updated patch to trigger handlestr() when unicode string is found > during iteration json.loads(config.json). Unicode and list with data > expansion were not handled hence adding this patch to handle > conversion. > Added a debug message to

Re: [yocto] Fwd: Basehash value changed issue

On Mon, 2018-07-02 at 17:37 +0530, techi eth wrote: > I have not got success of building my first image so it happen's to > me always. I also tried deleting tmp,cache folder & re-build again > but problem persist. > Is it something to do with timestamps ? > > I do see below patch & applied

Re: [yocto] QA cycle report for 2.6 M1 RC1

Thanks Ee Peng and team, this release seemed to have a number of issues and proved challenging to QA. I appreciate the work that goes into these (particularly given the other releases also queued), this is a useful QA report and has found some real issues. On Tue, 2018-07-03 at 07:09 +, Yeoh,

Re: [yocto] [PATCH 2/2] [yocto-ab-helper] utils.py: Resolved unicode data expansion

On Mon, 2018-07-02 at 18:30 +0800, Aaron Chan wrote: > A patch to fix the data expansion config.json > > Signed-off-by: Aaron Chan > --- > scripts/utils.py | 16 > 1 file changed, 16 insertions(+) > > diff --git a/scripts/utils.py b/scripts/utils.py > index 7c6535c..d26cd0c

Re: [yocto] [PATCH] [yocto-ab-helper] Add qemux86, qemux86-64 WIC testimage buildset-config

On Tue, 2018-06-26 at 16:51 +0800, Aaron Chan wrote: > Signed-off-by: Aaron Chan > --- > config.json | 32 +++- > 1 file changed, 31 insertions(+), 1 deletion(-) This patch looks like it might be correct. I say "might" as your commit message tells me what you did

Re: [yocto] [PATCH] [yocto-ab-helper] Add config support intel-corei7-64

On Tue, 2018-06-26 at 09:51 +0800, Aaron Chan wrote: > Signed-off-by: Aaron Chan > --- > scripts/config-intel-lava.json | 129 > + > scripts/utils.py | 2 +- > 2 files changed, 130 insertions(+), 1 deletion(-) > create mode 100644

Re: [yocto] [PATCH] [yocto-ab-helper] Fix syntax load config.json clobber buildStep

On Tue, 2018-06-26 at 15:05 +0800, Aaron Chan wrote: > Signed-off-by: Aaron Chan > --- > config.json| 5 ++--- > janitor/clobberdir | 3 +-- > 2 files changed, 3 insertions(+), 5 deletions(-) > > diff --git a/config.json b/config.json > index ecfca51..c9dc21e 100644 > --- a/config.json

Re: [yocto] [PATCH] [yocto-autobuilder2] Add nightly-x86-64-bsp job to enable BSP HW Testcase

On Wed, 2018-06-20 at 23:29 +0100, Richard Purdie wrote: > Right now the simplistic logic in loadconfig() won't allow the simple > addition/replacement of an entry within a dict/list but that is > something which should be easily fixed. FWIW I just pushed something to fix this. Cheers,

Re: [yocto] [PATCH] [yocto-autobuilder2] Add nightly-x86-64-bsp job to enable BSP HW Testcase

Hi Aaron, Thanks for this. I think this made it clear we needed an extensions mechanism for yocto-autobuilder-helper (note this patch is against yocto-autobuilder-helper, not yocto-autobuilder2). I've just pushed a change to yocto-autobuilder2 which should allow it to load extra json files

[yocto] Release Candidate Build for yocto-2.6_M1.rc1 now available.

A release candidate build for yocto-2.6_M1.rc1 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6_M1.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : fec5d45ec3978d4b7c9649bee45fe58f914bcee4 meta-qt4 :

Re: [yocto] [autobuilder][PATCH 1/2] yocto-autobuilder2: add missing __init__.py to top level

On Sun, 2018-06-03 at 17:22 -0700, Armin Kuster wrote: > This fixes the import of modules when starting buildbot > as master.cfg has: > from yoctoabb import builders, config, schedulers, workers, services, > www > > Signed-off-by: Armin Kuster > --- > __init__.py | 0 > 1 file changed, 0

Re: [yocto] Gratitude

On Wed, 2018-06-06 at 06:42 +, Osier-mixon, Jeffrey wrote: > I have been the Yocto Project community manager for over 7 years now, > and have had the pleasure of knowing or conversing individually with > several hundred of you. It is with mixed feelings that I must > announce that I am

Re: [yocto] HELP: Release Candidate Build for yocto-2.4.3.rc2 now available.

Hi David, On Tue, 2018-05-29 at 03:36 +, Reyna, David wrote: > I apologize for sending this patch for Toaster for Roco 2.4.3 very > late. I have been focused on Sumo and I thought I had more time. > > The Toaster for Rocko is broken on HEAD. There are two patches that > made it into master

[yocto] Release Candidate Build for yocto-2.2.4.rc1 now available.

A release candidate build for yocto-2.2.4.rc1 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.2.4.rc1 Please begin QA on this build as soon as possible. Build hash information:  meta-intel : c781510a5a6b45e60cc32b6614ddcce3f1452121  meta-qt4 :

[yocto] Release Candidate Build for yocto-2.4.3.rc2 now available.

A release candidate build for yocto-2.4.3.rc2 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.4.3.rc2 Please begin QA on this build as soon as possible. Build hash information:  meta-intel : f66ce51d059d291a441d896854be8db70de5a554  meta-qt4 :

[yocto] Release Candidate Build for yocto-2.3.4.rc1 now available.

A release candidate build for yocto-2.3.4.rc1 is now available at:          https://autobuilder.yocto.io/pub/releases/yocto-2.3.4.rc1     Please begin QA on this build as soon as possible.      Build hash information:   meta-intel : 9b37952d6af36358b6397cedf3dd53ec8962b6bf   meta-qt4 :

[yocto] 2.6 planning proposals and meeting

[Widely cross posted but please reply to openembedded-core only for want of picking somewhere to discuss this] The next big question facing us is what would we like to do in 2.6? What can we do with the resources we have? I'm proposing to hijack the next monthly Yocto Project technical call[1]

Re: [yocto] [OE-core] Yocto Project Status WW12’18

On Tue, 2018-03-20 at 20:00 +0200, Alexander Kanavin wrote: > On 03/20/2018 05:59 PM, Richard Purdie wrote: > > > > > > > > > > > > > How long does a single run take, and why not run it every > > > > month? > > > Just a bit

[yocto] Release candidate build for Yocto Project 2.5 M3 rc1

Hi, We have a build ready for QA for the Yocto Project release 2.5 M3 rc1. This build is slightly different in that it has been run on the new autobuilder codebase. We don't have automated release emails yet so I'm writing this manually. The release is available at:

Re: [yocto] [OE-core] Yocto Project Status WW12’18

On Tue, 2018-03-20 at 13:26 +0200, Alexander Kanavin wrote: > On 03/20/2018 12:52 PM, Burton, Ross wrote: > > > > Which brings me to a question: what is a good schedule and > > cadence > > for AUH runs? Currently it's run on the 15th of every odd- > > numbered > > month (so January,

Re: [yocto] extending HOSTTOOLS

On Fri, 2018-03-09 at 11:12 -0700, Oleg K Dzhimiev wrote: > Poky 2.4. > I would like to add ping and scp to HOSTTOOLS from a class inherited > by a recipe. HOSTTOOLS is updated but the links will not appear in > the build/tmp/hosttools/ > Is there any way to do this? HOSTTOOLS is a global

Re: [yocto] [PATCH][meta-mingw] gcc-crosssdk: use oe.utils.str_filter_out

On Tue, 2018-01-30 at 11:25 +, Ross Burton wrote: > oe_filter_out has been removed from oe-core so use the replacement > function. > > Signed-off-by: Ross Burton > --- >  recipes-devtools/gcc/gcc-crosssdk_%.bbappend | 2 +- >  1 file changed, 1 insertion(+), 1

Re: [yocto] QA cycle report for 2.4.1 RC1

Hi, On Fri, 2017-12-22 at 01:40 -0800, Yeoh, Ee Peng wrote: > Enjoy viewing the full Report for 2.4.1 > RC1:  https://wiki.yoctoproject.org/wiki/WW51_-_2017-12-21- > _Full_Test_Cycle_-_2.4.1_rc1 > > === Summary > > The QA cycle for release 2.4.1 RC1 is complete.  There are 5 new

Re: [yocto] QA cycle report for 2.3.3 RC1

On Wed, 2017-12-20 at 20:25 -0800, Cruz, Libertad wrote: > Hello All, > Enjoy viewing the full Report for 2.3.3 RC1:  https://wiki.yoctoproje > ct.org/wiki/WW51_-_2017-12-20-_Full_Test_Cycle_-_2.3.3_rc1 > > === Summary > > The QA cycle for release 2.3.3 RC1 is complete.  There are 4

Re: [yocto] [yocto-docs][PATCH] kernel-dev: fix typo

Hi, >...I'm sorry to insist, but I can't figure out why this trivial typo > fix has been ignored for long. I mentioned this to Scott who hadn't seen it for some reason. He's merged it now, thanks. Cheers, Richard -- ___ yocto mailing list

Re: [yocto] [yocto-infrastructure] [infra] git domain name updates

On Mon, 2017-09-25 at 17:17 -0700, Michael Halstead wrote: > This is all ready to go right now. Please update your remotes. > > We will have to make these changes required before we can start to > get performance benefits from them. I suggest November 1st 2017 but I > need more feedback before we

Re: [yocto] Path to current bb-file or layer

On Fri, 2017-09-22 at 13:04 +0200, Svein Seldal wrote: > On 22. sep. 2017 10:30, Richard Purdie wrote: > > Its all about when your code is executed. Try putting: > >  > > SP_BASEVERSION := "${@read_spbaseversion(d)}" > >  > > in the bbclass file. I

Re: [yocto] Path to current bb-file or layer

On Fri, 2017-09-22 at 10:17 +0200, Svein Seldal wrote: > On 21. sep. 2017 23:36, Richard Purdie wrote: >  > You mean like ${FILE} ? >  > >  > $ bitbake bash -e | grep ^FILE= >  > FILE="/media/build1/poky/meta/recipes-extended/bash/bash_4.4.bb" > >

Re: [yocto] Path to current bb-file or layer

On Thu, 2017-09-21 at 22:00 +0200, Svein Seldal wrote: > To determine a image version, I'd like to read a VERSION file which > is  > located in the root of the layer. (Per our development procedure.) > I'd  > like to read it from a bbclass file. However I seem to be unable to > find  > any methods

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

On Fri, 2017-06-30 at 09:48 +, Michael Ho wrote: > Hi, at BMW Car IT we are working on an experimental feature to > improve sstate cache hits and we are looking for comments on the > approach who might have some insights to the problem and seeing if > anyone is interested in the feature for

Re: [yocto] QA cycle report for 2.2.2 rc2

This is a tricky one to evaluate. Going through the bugs in the QA report: Bug 12075 - think this is ok to fix on the branch and release note Bug 12080 - we think minimal eSDK never worked in morty therefore this              is a QA testing error? Bug 12073 - we continue to see various gpg

Re: [yocto] Pyro's uninative and libstdc++ symbols

On Fri, 2017-09-01 at 12:14 -0700, akuster wrote: > > On 08/29/2017 01:03 AM, Richard Purdie wrote: > > > > On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote: > > > > > > I've recently updated my host system to Fedora 26, which has GCC > >

Re: [yocto] Pyro's uninative and libstdc++ symbols

On Fri, 2017-08-25 at 14:50 +0200, Raphael Kubo da Costa wrote: > I've recently updated my host system to Fedora 26, which has GCC 7. > > This seems to be causing some issues on Pyro, where I have a -native > recipe that is built with my system's g++ and ends up generating a > binary with the

Re: [yocto] Release Candidate Build for yocto-2.3.1. now available.

On Mon, 2017-08-21 at 12:03 -0700, Perez Carranza, Jose wrote: > This mail is kind of strange, artifacts are not published, there are > not rc specified and afaiu we worked on QA for pyro 2.3.1 last > month.  > > Can anyone clarify this?  The eSDK artefacts in 2.3.1 were broken and its had to be

Re: [yocto] QA cycle report for 2.4 M2 rc2

On Wed, 2017-08-02 at 17:55 -0700, Cruz, Libertad wrote: > QA does not approve that  the workarounds provided  for 2.4 m2 rc2 >  were on different commits. Testing was not limited to 2.4 m2 rc2 > commit “8e15e9b6e478f6368034519b2a8fd3c7ea71d23b” it was performed by > following each commit on the

Re: [yocto] localhost toaster faild after commit 4602408c6

On Fri, 2017-07-28 at 14:48 +0800, Jacob Chen wrote: > Hi, > > I have use a localhost toaster server as the CI server, and recently > it failed to runbuild. > > I try to fix it by editing > "bitbake/lib/toaster/bldcontrol/localhostbecontroller.py", but then I > give up, i'm not familiar with

Re: [yocto] [PATCH] yocto-bsp: update reference BSPs to 4.1 latest

On Fri, 2017-06-09 at 09:30 +0800, Kevin Hao wrote: > On Thu, Jun 08, 2017 at 02:45:14PM -0400, Bruce Ashfield wrote: > > > > The reference BSPs are lagging on their 4.1 SRCREVs, which means > > -stable updates, and gcc-7 build fixes are missing. > I have made a patch to update the SRCREVs for

Re: [yocto] [OE-core] [PATCH 1/2] logrotate: Bump to 3.11.0

On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote: > This commit updates the recipe to the last upstream tag. Then, as the > tarball no longer contains the pre-generated Makefile, inherit from > autotools > > [...] > -PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl > selinux',

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Wed, 2017-03-01 at 16:51 +0100, Patrick Ohly wrote: > On Wed, 2017-03-01 at 15:12 +0000, Richard Purdie wrote: > > > > On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote: > > > > > > Is the "build single distro for different machines" scenario tha

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Wed, 2017-03-01 at 08:10 +0100, Patrick Ohly wrote: > On Wed, 2017-03-01 at 04:00 +0000, Richard Purdie wrote: > > > > On Tue, 2017-02-28 at 21:09 +0100, Patrick Ohly wrote: > > > > > > On Mon, 2017-02-20 at 15:12 -0600, Aníbal Limón wrote: > > >

Re: [yocto] [OE-core] [PATCHv2] yocto-compat-layer.py: Add script to YP Compatible Layer validation

On Tue, 2017-02-28 at 21:09 +0100, Patrick Ohly wrote: > On Mon, 2017-02-20 at 15:12 -0600, Aníbal Limón wrote: > > > > common.test_signatures: Test executed in BSP and DISTRO layers to > > review > > doesn't comes with recipes that changes the signatures. > I have a question about the goal

Re: [yocto] task is executed even when sstate-cache md5 matches

On Tue, 2017-02-21 at 06:30 +, Pepe Perez wrote: > I have following siginfo packages: > > Generated in my build sstate-cache > build/sstate-cache/be/sstate:proc- > fifo::1.0.3:r1::3:be9c419f0caa05042d43c03d576d2e15_fetch.tgz.siginfo > > Previously existing in my build SSTATE_MIRRORS: >

Re: [yocto] [OE-core] Yocto Project Status WW01

On Tue, 2017-01-03 at 15:51 +, Jolley, Stephen K wrote: > Current Dev Position: YP 2.3 M2 -> M3 > Next Deadline: YP 2.3 M2 by Jan 23, 2017 >   > SWAT team rotation: Maxin -> Joshua > https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team >   > Key Status/Updates: > ·    M1 is

Re: [yocto] build a toolchain compiler with ARM hard-float support

On Thu, 2016-09-29 at 09:10 +, Karim ATIKI wrote: > Hi, > > I'm using Poky Jethro to build on Toradex Colibri-T20 (armv7). > > I want to build my own SDK Installer to have  a toolchain and a > sysroot. > > Currently, I realied that the toolchain installer files do not > provide an

Re: [yocto] [meta-mingw][PATCH 0/7] Updates for krogoth/master

On Wed, 2016-09-28 at 17:06 +0300, Ioan-Adrian Ratiu wrote: > On Sat, 20 Aug 2016, Juro Bystricky wrote: > > > > Krogoth recipes fail to cross-compile for Windows using meta-mingw > > layer. > > In particular, the following should/used to work (jethro with meta- > >

Re: [yocto] Failing build following Quick Start

On Tue, 2016-09-06 at 13:13 +, Adolfo Sanchez wrote: > I am new to Yocto and trying to learn the basics of the system > > I am following the Yocto Quick Start guide:  > http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-q > s.html > > Details: > 1) I am using Lubuntu 16.04

Re: [yocto] libSegFault.so crashing on Daisy

On Fri, 2016-09-02 at 16:36 -0300, Daniel. wrote: > Hi everybody, > > I was trying to use libSegFault.so to capture stacktraces but the > libSegFault it self is crashing? Can someone try to reproduce this? > > 1) Install libc6-dbg. This will give you access to libSegFault.so at >

Re: [yocto] [OE-core] [RFT] gcc 6.2 RC1 update

On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote: > Hi All > > I have put together recipe upgrade for upcoming gcc 6.2 release now > that it entered RC phase. With gcc 6.2 the recipes are using tarballs > instead of git fetcher as promised :) > Please help testing it out in your setups and

Re: [yocto] [OE-core] [RFT] binutils 2.27

On Tue, 2016-08-09 at 07:42 -0700, Khem Raj wrote: > I could also see it on ppc. backtrace, shows the segfault is in exit > path and happens in libc > at this point, I think the problem is how libc is compiled with > binutils 2.27, connman itself > is ok. Its the issue here:

Re: [yocto] [OE-core] [RFT] binutils 2.27

On Mon, 2016-08-08 at 08:21 -0700, Khem Raj wrote: > They are different issues. for OE ppc also shows same errors with lib > unwind. FWIW, I think the connmand segfault on mips and powerpc is hinted at with this bug: https://bugs.launchpad.net/ubuntu/+source/lua5.3/+bug/1570055 connmand is a

Re: [yocto] [OE-core] [RFT] binutils 2.27

On Mon, 2016-08-08 at 00:24 -0700, Khem Raj wrote: > > On Aug 7, 2016, at 11:28 PM, Richard Purdie < > > richard.pur...@linuxfoundation.org> wrote: > > > > On Sun, 2016-08-07 at 01:39 -0700, Khem Raj wrote: > > > I have put together upgrade for binuti

Re: [yocto] [OE-core] [RFT] binutils 2.27

On Sun, 2016-08-07 at 01:39 -0700, Khem Raj wrote: > I have put together upgrade for binutils 2.27 here ( kraj/master > branch ) > > https://github.com/kraj/openembedded-core/commit/b98f5761d2285ffd773e > c6ecb901b799302ebd6b > > I have started bunch of test builds. but I would appreciate any

Re: [yocto] do_rootfs OSError: [Errno 13] Permission denied

On Tue, 2016-07-19 at 07:17 +, Maier, Chris wrote: > Hello together, > > I ran into an “Permission denied” error while trying to setup a > nightly build on our Jenkins server and I can’t figure out where the > problem comes from. > It seems that the problem is coming from creating and

[yocto] Yocto Project Status WW27

Current Dev Position: YP 2.2 M2 Next Deadline: YP 2.2 M2 cut off would be: 7/18/16 SWAT team rotation: Armin -> Bill (https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team) Key Status/Updates: * QA test report for 2.2 M1 is looking reasonable. There are some issues in toaster,

Re: [yocto] prelink support

On Mon, 2016-06-20 at 08:24 -0400, Kyle Russell wrote: > It looks like the image-prelink support is still disabled in master > because of an issue with IFUNC symbol relocation. > > https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta-poky/conf >

Re: [yocto] [OE-core] Yocto Project Status WW25

On Fri, 2016-06-17 at 14:42 -0700, Christopher Larson wrote: > On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K < > stephen.k.jol...@intel.com> wrote: > > ·There is a multilib issue related to the layout of the > > host libraries leaking into python’s build process which we’re > >

<    1   2   3   4   5   >