Re: [yocto] is there a rationale for YP using sysvinit as default init manager?

On Fri, 2019-11-22 at 10:08 +1300, Paul Eggleton wrote: > On Friday, 22 November 2019 9:40:35 AM NZDT Richard Purdie wrote: > > On Thu, 2019-11-21 at 14:02 -0500, Robert P. J. Day wrote: > > > don't get me wrong, i have no problem with that, but a > > > colleague >

Re: [yocto] is there a rationale for YP using sysvinit as default init manager?

On Thu, 2019-11-21 at 14:02 -0500, Robert P. J. Day wrote: > don't get me wrong, i have no problem with that, but a colleague > asked me what the reason was for using sysvinit as the *default*. i > hemmed and hawed and suggested it was for simplicity and reliability, > and that a lot of embedded

Re: [yocto] [OE-core] Yocto Project Status WW46'19

On Thu, 2019-11-14 at 16:11 -0800, akuster808 wrote: > > Hello Stephen, > > On 11/12/19 7:47 AM, sjolley.yp...@gmail.com wrote: > > Current Dev Position: YP 3.1 M1 > > Next Deadline: YP 3.1 M1 build Dec. 2, 2019 > > > > SWAT Team Rotation: > > SWAT lead is currently: Anuj > > SWAT team

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

On Wed, 2019-11-13 at 09:02 +, Samuel Jiang (江騏先) wrote: > I got below error message: > crashdump-git-r0 do_fetch: Fetcher failure: Fetch command export > PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export > DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export >

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

On Wed, 2019-11-13 at 03:06 +, Samuel Jiang (江騏先) wrote: > I try use > SRC_URI = "git://quanta01@vs- > ssh.visualstudio.com/v3/quanta01/OpenBMC/crashdump;protocol=ssh;nobra > nch=1" > > the bitbake response below error message: > git -c core.fsyncobjectfiles=0 ls-remote >

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

On Mon, 2019-11-04 at 02:52 +, Samuel Jiang (江騏先) wrote: > Dear yocto developer, > The below disscussed about azure devops clone issue including test > result with Microsoft support team member. > We wonder know how Bitbake access repository through SSH. Does it > different between git and

Re: [yocto] [EXTERNAL] Re: Issues adding bare meta toolchain to yocto build

On Thu, 2019-10-24 at 15:37 +, Westermann, Oliver wrote: > > On Thu, 2019-10-24 at 04:01 +, Richard Purdie wrote: > > If its a native recipe, there are no packages and therefore FILES > > doesn't make sense. > > Oh, I have to admit I'm pretty new to the concept

Re: [yocto] [EXTERNAL] Re: Issues adding bare meta toolchain to yocto build

On Thu, 2019-10-24 at 10:30 -0400, William Mills wrote: > On 10/24/19 10:02 AM, richard.pur...@linuxfoundation.org wrote: > > On Thu, 2019-10-24 at 09:43 -0400, William Mills wrote: > > > Then understand that you will need to supply your own gcc > > > compiler > > > helpers and all stdc functions

Re: [yocto] [EXTERNAL] Re: Issues adding bare meta toolchain to yocto build

Hi Bill, On Thu, 2019-10-24 at 09:43 -0400, William Mills wrote: > I started looking at this thread because I had the same > questions. Is it possible to make a recipe depend on another version > of GCC and restart the whole GCC build process again with a different > config. > > Or does this

Re: [yocto] [EXTERNAL] Re: Issues adding bare meta toolchain to yocto build

On Thu, 2019-10-24 at 10:03 +, Westermann, Oliver wrote: > > On Wed, 2019-10-23 at 15:34 +, Richard Purdie wrote: > > > On Wed, 2019-10-23 at 11:23 +, Westermann, Oliver wrote: > > > Hey, > > > [...] > > > Any suggestions on what I'm doin

Re: [yocto] Issues adding bare meta toolchain to yocto build

On Wed, 2019-10-23 at 11:23 +, Westermann, Oliver wrote: > Hey, > > I'm having issues adding a build for a bare metal target to my yocto > toolchain. I've a NXP SoC with a M4 core and I would like to > integrate the M4 binary build into yocto. > My M4 binary has a CMAKE file that depends on

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

On Wed, 2019-10-23 at 08:00 +, Jain, Sangeeta wrote: > Hello all, > > This is the full report for 2.6.4 RC2: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults > > === Summary > No high milestone defects. > No new defect

Re: [yocto] Reducing the size of the image by optimizing python

On Sat, 2019-10-19 at 14:55 +, Abhi Arora wrote: > Thanks your for the suggestion. > > From where I can find out what modules and packages python3-misc > downloads and installs? I am new to yocto and Don't know where to > look for. I tried grep but didn't help me. python3-misc is a package.

Re: [yocto] Reducing the size of the image by optimizing python

On Sat, 2019-10-19 at 12:45 +, Abhi Arora wrote: > Thanks for the reply. Can you help me which file to modify to prevent > downloading certain packages and modules using BAD_RECOMMENDATION? > > And how to have only pyc files in the final image to improve speed > and reduce footprint? > >

Re: [yocto] [opkg-devel] [OE-core][opkg-utils ] Bug 13528 : adding SPDX license identifier

> opkg-list-fields > > opkg-make-index > > opkg-show-deps > > opkg-unbuild > > opkg-update-index > > > > What license do you want them to carry ? > > Looking at the commit history, opkg-graph-deps was authored by Haris > Okanovic, and the rest by

Re: [yocto] QA notification for completed autobuilder build (yocto-3.0.rc2)

On Thu, 2019-10-10 at 07:37 +, Jain, Sangeeta wrote: > Hello All, > > Intel and WR YP QA is planning for QA execution for YP build yocto- > 3.0.rc2. > We are planning to execute following tests for this cycle: > > OEQA-manual tests for following module: > 1. OE-Core > 2. BSP-hw > 3. BSP-Qemu

Re: [yocto] Task vardeps on a variable changed externally

On Wed, 2019-10-09 at 10:42 +0100, Andrei Gherzan wrote: > I struggle to figure out an issue that I lately got into. I want to > have a recipe which writes a manifest of all the layers part of the > build. > These layers are all git repositories and I want their revision to > be exposed at

Re: [yocto] global class that others will inherit

On Thu, 2019-10-03 at 11:36 +0200, Łukasz Tasz wrote: > Hi, > this is my first post here, so big hello! > > I have a problem which you might help me to solve. > I have quite complex configuration, and I would like to inject > something into build system in a right way. > > I already did some

Re: [yocto] [OE-core] Yocto Project Status WW40’19

On Tue, 2019-10-01 at 21:16 +0200, Alexander Kanavin wrote: > On Tue, 1 Oct 2019 at 16:54, Stephen K Jolley < > sjolley.yp...@gmail.com> wrote: > > A significant performance problem has been found on the autobuilder > > where some builds are scaling in time badly as the sstate cache > > grows,

Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M3.rc1)

On Mon, 2019-09-23 at 07:37 +, Jain, Sangeeta wrote: > Hi Richard, > > LSB support was expected to be removed from build 'yocto-2.8_M3.rc1' > onwards, but link on AB still points to LSB images. > The images present inside >

Re: [yocto] Pointless unlink-link in strip_execs?

On Fri, 2019-09-06 at 11:52 -0700, Kaz Kylheku wrote: > Hi, > > I'm looking at meta/lib/oe/package.py, function strip_execs, under > Yocto > 2.5. > > It has this tidbit: > > if s.st_ino in inodes: > os.unlink(file) # <--- > of

[yocto] Yocto Project Status WW36’19

Current Dev Position: YP 2.8 M4 Feature FreezeNext Deadline: YP 3.0 Final Release 25th Oct SWAT Team Rotation:SWAT lead is currently: ArminSWAT team rotation: Armin -> Paul on Sept. 6, 2019SWAT team rotation: Paul -> Ross on Sept. 13, 2019

Re: [yocto] Recipe svn-fetcher and scmdata

On Mon, 2019-08-19 at 10:18 +0300, Teemu K wrote: > Hi, > > I have some recipes that fetch sources directly from svn. I'd like to > keep the .svn to make it easier to commit changes. I checked that > those are by default removed and that there is scmdata - option if > those wanted to be kept. >

Re: [yocto] [yocto-autobuilder2][PATCH 2/3] Added remote distribution of config JSON files

On Tue, 2019-07-30 at 14:36 -0400, Thomas Goodwin wrote: > This feature/fix allows the worker to download the > autobuilder helper JSON files from the controller > rather than having to store them in the > yocto-autobuilder-helper repository. The process > installs the file into the worker's >

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.3.rc1)

On Thu, 2019-08-08 at 03:00 +, Jain, Sangeeta wrote: > Hello All, > > This is the full report for 2.6.3 RC1: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults > > === Summary > No high milestone defects. > No new defects

Re: [yocto] -staticdev packages not in sdk

On Tue, 2019-08-06 at 14:04 +, Koeller, Thomas wrote: > browsing the list archives I came across an older thread that exactly > describes the problem I am currently struggling with: > > https://lists.yoctoproject.org/pipermail/yocto/2018-February/039950.html > > In short, I have a recipe

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

On Thu, 2019-08-01 at 07:30 +, Yeoh, Ee Peng wrote: > This is the full report for 2.8 M2 RC1: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=zeus=d550d40646e1ca78a4b5d106e1b20831208b4c37 > > === Summary > No high milestone defects. > Two new

Re: [yocto] [OE-core] RFC: dropping official support for Debian 8 / Opensuse 42.3

On Thu, 2019-07-18 at 12:31 +0100, Burton, Ross wrote: > > CentOS 7 is based on Fedora 19 from 2013. > > > > This is the oldest currently supported distribution, and when to > > remove > > support for it (replacing it with the not yet existing CentOS 8) > > should > > IMHO be part of this

Re: [yocto] [ptest-runner][PATCH v2 4/4] utils: ensure child can be session leader

On Tue, 2019-06-25 at 20:51 -0500, Anibal Limon wrote: > I plan to take the Richard patches, He added in the recipe to have > real testing and looks like > there aren't problems related to, Richard can you confirm it?, We've been running the patches for a while in the recipe (since we last

Re: [yocto] [PATCH V3] update-rc.d: support enable/disable options

On Thu, 2019-06-20 at 10:07 +0800, Changqing Li wrote: > Please also help to review this patch, Thanks. This patch needs to go to OE-Core for the bbclass part. The documentation piece needs to be separated out as its a different repository. Also doesn't it depend on the change I just made to the

Re: [yocto] [ptest-runner][PATCH v2 4/4] utils: ensure child can be session leader

On Wed, 2019-06-19 at 13:49 -0400, Randy MacLeod wrote: > On 6/14/19 10:48 AM, Randy MacLeod wrote: > > When running the run-execscript bash ptest as a user rather than > > root, a warning: > >bash: cannot set terminal process group (16036): Inappropriate > > ioctl for device > >bash: no

Re: [yocto] [update-rc.d][PATCH V3] update-rc.d: support enable/disable options

On Tue, 2019-04-30 at 14:56 +0800, changqing...@windriver.com wrote: > From: Changqing Li > > Add support of enable/disable options, refer > https://manpages.debian.org/wheezy/sysv-rc/update-rc.d.8.en.html > > With support of these options, the usr can never change an existing > configuration

Re: [yocto] Download git source not the latest

On Tue, 2019-06-11 at 20:38 +1000, JH wrote: > Hi, > > I set up SRCREV = "${AUTOREV}" in the recipe of my application, but > too often it downloaded the old revision. How can I force the bitbake > to download the latest git source? What did you set PV to? You need to have SRCPV in PV for

Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

On Wed, 2019-06-12 at 00:51 +, Jain, Sangeeta wrote: > On Tue, 2019-06-11 at 03:32 +, pokybu...@debian9-ty-1.yocto.io > > wrote: > > > A build flagged for QA (yocto-2.8_M1.rc2) was completed on the > > > autobuilder and is available at: > > > > > > > > >

[yocto] Yocto Project Status WW24'19

Current Dev Position: YP 2.8 M2Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019 SWAT Team Rotation: * SWAT lead is currently: Anuj * SWAT team rotation: Anuj -> Paul on June 14, 2019 * SWAT team rotation: Paul -> Ross on June 21, 2019 *

Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

On Tue, 2019-06-11 at 03:32 +, pokybu...@debian9-ty-1.yocto.io wrote: > A build flagged for QA (yocto-2.8_M1.rc2) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2 > Some notes for QA: There was a failure in this

Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc1)

On Mon, 2019-06-10 at 21:38 +, Poky Build User wrote: > A build flagged for QA (yocto-2.8_M1.rc1) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc1 > I've triggered an rc2 since one of the autobuilder workers messed

Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

On Mon, 2019-06-10 at 00:11 +0200, Ulf Samuelsson wrote: > Den 2019-05-09 kl. 11:56, skrev Burton, Ross: > > On Thu, 9 May 2019 at 10:47, Fabian Knapp > > wrote: > > > > we have multiple MACHINEs and DISTROs and Im wondering for > > which > > combinations I have

Re: [yocto] [patchtest-oe][PATCH] test_metadata_src_uri: new unittest detecting added patch files without modifying SRC_URI

On Wed, 2019-05-29 at 10:28 +0800, Changqing Li wrote: > On 5/28/19 10:53 PM, akuster wrote: > > On 5/27/19 6:00 PM, Changqing Li wrote: > > > ping > > > > > > On 4/29/19 2:10 PM, Changqing Li wrote: > > > > ping > > > > > > Does this mean you have a working knowledge of patchtest? > > > > The

[yocto] Yocto Project Status WW23'19

Current Dev Position: YP 2.8 M1Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019 SWAT Team Rotation: * SWAT lead is currently: Armin * SWAT team rotation: Armin -> Anuj on June 7, 2019 * SWAT team rotation: Anuj -> Paul on June 14, 2019 *

Re: [yocto] [ptest-runner][PATCH] Add SPDX-License-Identifier: GPL-2.0-or-later to source files

On Mon, 2019-06-03 at 13:39 -0500, Aníbal Limón wrote: > Signed-off-by: Aníbal Limón > --- > main.c | 2 ++ > ptest_list.c | 2 ++ > ptest_list.h | 2 ++ > tests/main.c | 2 ++ > tests/ptest_list.c | 2 ++ > tests/utils.c | 2 ++ > utils.c| 2 ++ >

Re: [yocto] Yocto 2.7: SSTATEPOSTUNPACKFUNCS_remove not working

On Wed, 2019-05-29 at 22:37 +, Wolfgang Tolkien wrote: > Thanks, > > not sure I follow: 'SSTATEPOSTUNPACKFUNCS_remove' is not valid any > more and previously only worked because there was a bug? Previously the value of the expression wasn't accounted for in the hashes which represent the

Re: [yocto] Yocto 2.7: SSTATEPOSTUNPACKFUNCS_remove not working

On Wed, 2019-05-29 at 21:17 +, Wolfgang Tolkien wrote: > Hi there, > > I'm upgrading from Yocto 2.5 to 2.7. I have a recipe that (for > legacy reasons) builds a 32bit "-native" executable. I am disabling > uninative by setting > > SSTATEPOSTUNPACKFUNCS_remove = "uninative_changeinterp" > >

[yocto] Yocto Project Status WW22'19

Current Dev Position: YP 2.8 M1Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019 SWAT Team Rotation: * SWAT lead is currently: Chen * SWAT team rotation: Chen -> Armin on May. 31, 2019 * SWAT team rotation: Armin -> Anuj on June 7, 2019 *

[yocto] Yocto Project Status WW21'19

Current Dev Position: YP 2.8 M1Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019 SWAT Team Rotation: * SWAT lead is currently: Ross * SWAT team rotation: Ross -> Chen on May. 24, 2019 * SWAT team rotation: Chen -> Armin on May. 31, 2019 *

[yocto] Yocto Project Status WW20'19

Current Dev Position: YP 2.8 M1Next Deadline: YP 2.8 Milestone 1 Cutoff June 9th, 2019 SWAT Team Rotation: * SWAT lead is currently: Amanda * SWAT team rotation: Amanda -> Ross on May. 17, 2019 * SWAT team rotation: Ross -> Chen on May. 24, 2019 *

Re: [yocto] [Yocto-bsp] Error of " fs.inotify.max_user_watches " while using bitbake [ Yocto-2.6.1 + Qemux86]

On Mon, 2019-05-13 at 15:38 +0530, AshishKumar Mishra wrote: > Can team members please let me know the solution & what is causing > the below mentioned error ? > ( I am having around 128GB of disk space still left , hence don't > think that space is the issue here ) > >

Re: [Yocto-bsp] Error of " fs.inotify.max_user_watches " while using bitbake [ Yocto-2.6.1 + Qemux86]

On Mon, 2019-05-13 at 15:38 +0530, AshishKumar Mishra wrote: > Can team members please let me know the solution & what is causing > the below mentioned error ? > ( I am having around 128GB of disk space still left , hence don't > think that space is the issue here ) > >

Re: [yocto] [OE-core] Yocto Project Status WW19'19

On Tue, 2019-05-07 at 08:00 -0700, akuster wrote: > > Key Status Links for YP: > > https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status > > https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule > > https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features > > Don't we need 2.8 now ? We do,

[yocto] [OE-core] Yocto Project Status WW19'19

Current Dev Position: YP 2.8 M1 Next Deadline: YP 2.8 Milestone 1 Target May ??, 2019 SWAT Team Rotation: * SWAT lead is currently: Anuj * SWAT team rotation: Anuj -> Ross on May. 10, 2019 * SWAT team rotation: Ross -> Amanda on May. 17, 2019 *

[yocto] Newcomer bugs

Apologies for cross posting but I wanted a wider audience to see this. The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the

Re: [yocto] Could not find glib.h

On Wed, 2019-05-01 at 10:43 +1000, JH wrote: > Hi, > > I added glib-2.0 to DEPENDS but it still could find the glib.h, what > I > could be missing here? > > fatal error: glib.h: No such file or directory > > #include > > ^~~~ > > compilation terminated. You probably need to use

[yocto] [OE-core] Yocto Project Status WW18'19

Current Dev Position: YP 2.7 M4 (2.7 rc2 release being discussed) Next Deadline: YP 2.7 Release Target April 26, 2019 SWAT Team Rotation: SWAT lead is currently: PaulSWAT team rotation: Paul -> Anuj on May. 3, 2019SWAT team rotation: Anuj -> Ross on May. 10, 2019

Re: [yocto] QA cycle report for 2.7 RC2

On Fri, 2019-04-26 at 06:27 +, Jain, Sangeeta wrote: > > QA cycle report for 2.7 RC2: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, please refer to results > at public AB [1]. > ·For other test

Re: [yocto] ASSUME_PROVIDED, cmake-native and why cmake is subsequently not found?

On Thu, 2019-04-25 at 08:32 -0400, Robert P. J. Day wrote: > On Thu, 25 Apr 2019, Bach, Pascal wrote: > > > > currently trying to build a "core-image-minimal" for a zedboard > > > on my > > > wholly unsupported fedora 30 (branched) system, so i'm well aware > > > there > > > will almost

Re: [yocto] ASSUME_PROVIDED, cmake-native and why cmake is subsequently not found?

On Thu, 2019-04-25 at 08:05 -0400, Robert P. J. Day wrote: > (warning: i've been away from YP for well over a year and am now > studiously trying to catch up, so i have some work to do.) > > currently trying to build a "core-image-minimal" for a zedboard on > my wholly unsupported fedora 30

Re: [yocto] QA cycle report for 2.5.3 RC3

On Wed, 2019-04-24 at 06:28 +, Jain, Sangeeta wrote: > That looks great to me. > As a further improvement for sharing of test results, I am working to > create a wiki page for consolidated > test results. For 2.5.3, it can be viewed at: >

[yocto] [OE-core] Yocto Project Status WW17'19

Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA) Next Deadline: YP 2.7 Release Target April 26, 2019 SWAT Team Rotation: SWAT lead is currently: ArminSWAT team rotation: Armin -> Anuj on Apr. 26, 2019SWAT team rotation: Armin -> Paul on May. 3, 2019

Re: [yocto] QA cycle report for 2.5.3 RC3

On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote: > > QA cycle report for 2.5.3 RC3: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, refer to results at > public AB [1]. > ·For other test results,

Re: [yocto] QA cycle report for 2.5.3 RC3

On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote: > > QA cycle report for 2.5.3 RC3: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, refer to results at > public AB [1]. > ·For other test results,

[yocto] [OE-core] Yocto Project Status WW15'19

Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA) Next Deadline: YP 2.7 Release Target April 26, 2019 SWAT Team Rotation: SWAT lead is currently: Chen SWAT team rotation: Chen -> Armin on Apr. 19, 2019SWAT team rotation: Armin -> Anuj on Apr. 26, 2019

Re: [yocto] Dependencies on other file system types for custom file system type

On Mon, 2019-04-15 at 21:43 +0700, Eric Grunt wrote: > > Notice how the function names for squashfs are: > > > > do_image_squashfs_xz > > > > not > > > > do_image_squashfs-xz > > > > This is because shell functions/variables can't have "-" in their > > name. > > You need to change to us

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.rc2)

On Sun, 2019-04-14 at 23:48 +, pokybuild@centos7-ty-1.localdomain wrote: > A build flagged for QA (yocto-2.7.rc2) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2 > > > Build hash information: > > bitbake:

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc4)

On Mon, 2019-04-15 at 08:27 +, pokybu...@fedora29-ty-1.yocto.io wrote: > A build flagged for QA (yocto-2.6.2.rc4) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc4 > > > Build hash information: > > bitbake:

Re: [yocto] Dependencies on other file system types for custom file system type

On Fri, 2019-04-12 at 20:50 +0700, Eric Grunt wrote: > > The dependency code is only triggered if the image type is in > > IMAGE_FSTYPES. Did you add it there? > > Yes, in the distro conf file. > Guess, otherwise it wouldn't be built at all (since it isn't > dependency of another fs) Notice how

Re: [yocto] Dependencies on other file system types for custom file system type

On Fri, 2019-04-12 at 20:19 +0700, Eric Grunt wrote: > Dependencies on other file system types for custom file system type > > I'd like to add a custom fs type - a squashfs-xz on an ubi (instead > of ubifs). > For this purpose I created a new class, inherited image_types and > added > a

Re: [yocto] QA cycle report for 2.6.2 RC3

On Wed, 2019-04-10 at 02:38 +, Jain, Sangeeta wrote: > > QA cycle report for 2.6.2 RC3: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, refer to results at > public AB [1]. > ·For other test results,

Re: [yocto] QA cycle report for 2.6.2 RC3

On Wed, 2019-04-10 at 02:38 +, Jain, Sangeeta wrote: > > QA cycle report for 2.6.2 RC3: > > No high milestone defects. > Test results are available at following location: > ·For results of all automated tests, refer to results at > public AB [1]. > ·For other test results,

Re: [yocto] [OE-core] Eclipse support dropped with immediate effect

On Thu, 2019-04-11 at 08:42 +0530, akuster808 wrote: > > On 4/10/19 3:11 PM, richard.pur...@linuxfoundation.org wrote: > > On Wed, 2019-04-10 at 05:56 +0530, akuster808 wrote: > > > On 4/9/19 8:52 PM, Richard Purdie wrote: > > > > I'm sorry to have to say th

Re: [yocto] [OE-core] Eclipse support dropped with immediate effect

On Wed, 2019-04-10 at 05:56 +0530, akuster808 wrote: > > On 4/9/19 8:52 PM, Richard Purdie wrote: > > I'm sorry to have to say this but the project is terminating its > > official eclipse plugin support with immediate effect. > > Does this affect the stable branches as w

[yocto] Eclipse support dropped with immediate effect

I'm sorry to have to say this but the project is terminating its official eclipse plugin support with immediate effect. There is nobody willing to keep the builds going, fix bugs, port to new eclipse releases or release the current plugin. This has been raised in many forums, multiple times and

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

On Fri, 2019-04-05 at 06:54 +, mikko.rap...@bmw.de wrote: > On Fri, Apr 05, 2019 at 07:46:00AM +0100, > richard.pur...@linuxfoundation.org wrote: > > On Fri, 2019-04-05 at 06:16 +, mikko.rap...@bmw.de wrote: > > > On Thu, Apr 04, 2019 at 10:48:17PM +0100,

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

On Thu, 2019-04-04 at 17:58 -0700, Tim Orling wrote: > Just curious: all Perl modules in oe-core have ptest enabled, but > only libxml-parser-perl is included in these test reports. Is it > simply the only module in that image or is something else afoot? Its probably the only one in the image. I

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

On Fri, 2019-04-05 at 06:16 +, mikko.rap...@bmw.de wrote: > On Thu, Apr 04, 2019 at 10:48:17PM +0100, Richard Purdie wrote: > > On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > > > As ptest-runner communicates with child processes via pipe2(), > > >

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

On Fri, 2019-04-05 at 03:46 +0530, akuster808 wrote: > > On 4/5/19 3:25 AM, richard.pur...@linuxfoundation.org wrote: > > On Thu, 2019-04-04 at 02:19 +, Jain, Sangeeta wrote: > > > Also, I don't see any ptest results for 2.6.2.rc3 on public > > > autobuilder. Do you have any plans to run them

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

On Thu, 2019-04-04 at 02:19 +, Jain, Sangeeta wrote: > Also, I don't see any ptest results for 2.6.2.rc3 on public > autobuilder. Do you have any plans to run them and share the results > on autobuilder? These were run separately but will run as part of any new stable release builds. The

Re: [yocto] [ptest-runner] Run ptests via stdbuf configured to line-buffering

On Thu, 2019-04-04 at 18:00 +0200, Alexander Kanavin wrote: > As ptest-runner communicates with child processes via pipe2(), > the corresponding channels are not attached to a pty. In that > situation stdio facilities like printf() or fwrite() are fully > buffered. If a ptest would use them,

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

Hi, This is good information and helps a lot, thanks! I had a question below. On Wed, 2019-04-03 at 08:06 +, Jain, Sangeeta wrote: > Intel and WR YP QA is now working on QA execution for YP build 2.6.2 > RC3. We are planning to execute following tests for this cycle: > > OEQA-Manual tests

Re: [yocto] Proposed new QA process

w QA process consists below: > · Test Trigger > · Test Planning > · Test Execution > · Test Result Store > · Test Monitoring & Reporting > · Release Decision > > Test Trigger: Each QA team will subscribe to QA notification email >

Re: [yocto] QA cycle report for 2.7 M3 RC1

Hi Sangeeta/Ee Peng, On Tue, 2019-04-02 at 05:02 +, Jain, Sangeeta wrote: > QA cycle report for 2.7 M3 RC1: > > No high milestone defects. > This is completion of first QA cycle after adoption of new QA > process. Test results are available at following location: > ·For results of

Re: [yocto] [OE-core] Git commit process question.

On Mon, 2019-04-01 at 15:33 -0700, akuster808 wrote: > Hello, > > I have noticed a large number of git commits with no header > information being accepted. Can you be more specific about what "no header information" means? You mean a shortlog and no full log message? Cheers, Richard --

Re: [yocto] New: "extrapatches" bbclass.

On Thu, 2019-03-07 at 19:26 -0800, Kaz Kylheku (poky) wrote: > # > # extrapatches bbclass > # > # This bbclass allows for a recipe to apply additional patches. > # > # "Additional patches" refers to patches that are not individually > # fetched by the SRC_URI mechanism, but are already present > #

Re: [yocto] Incremental rebuild doesn't pick up FILES changes.

On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote: > Hi, > > I'm working in a Yocto 2.5 environment. > > In my own layer, I added a bbappend targeting python which does this: > >FILES_${PN}_remove = "${libdir}/python2.7/encodings" > > Now this didn't take effect as I expected. I

Re: [yocto] [opkg-devel] [opkg-utils] Question: why update-alternatives from opkg-utils chooses /usr/lib to hold database?

On Tue, 2019-03-05 at 16:05 +, Alejandro Del Castillo wrote: > > On 3/5/19 12:11 AM, ChenQi wrote: > > Hi All, > > > > Recently I'm dealing with issue from which some discussion raises. > > I'd like to ask why update-alternatives from opkg-utils chooses > > /usr/lib > > to hold its

Re: [yocto] Removing busybox

On Thu, 2019-02-28 at 09:37 -0500, Tom Rini wrote: > On Thu, Feb 28, 2019 at 02:27:37PM +0000, Richard Purdie wrote: > > On Thu, 2019-02-28 at 12:05 +, Burton, Ross wrote: > > > I thought we had some other editor in core, but can't see > > > one. Worse > > &g

Re: [yocto] Removing busybox

On Thu, 2019-02-28 at 12:05 +, Burton, Ross wrote: > On Thu, 28 Feb 2019 at 05:20, Adrian Bunk wrote: > > > That's a good start. For a oe-core packagegroup > > > > I do not think a core-only packagegroup makes sense when the goal > > is to > > completely replace busybox (and not just most

Re: [yocto] Review request 0/13: Contribute meta-tensorflow to Yocto

On Fri, 2019-02-22 at 20:49 +, Manjukumar Harthikote Matha wrote: > > > > You might be interested in the yocto layers for tensorflow, > > tensorflow-lite and > > caffe2 on github here [1]. I'm not part of the team that developed > > that work but I > > forwarded your announcement to them.

Re: [yocto] Review request 0/13: Contribute meta-tensorflow to Yocto

Hi Hongxu, On Thu, 2019-02-21 at 06:37 -0500, Hongxu Jia wrote: > Currently AI on IoT edge becomes more and more popular, but there is > no > machine learning framework in Yocto/OE. With the support of Eric > , Robert > and Randy , after two months effort, > I've > integrated TensorFlow to

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7_M2.rc2)

On Tue, 2019-02-12 at 17:57 +, pokybuild@centos7-ty-1.localdomain wrote: > A build flagged for QA (yocto-2.7_M2.rc2) was completed on the > autobuilder and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.7_M2.rc2 > > > Build hash information: > > bitbake:

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

On Fri, 2019-02-08 at 04:38 +, Jain, Sangeeta wrote: > This is the full report for 2.7 M2 RC1: > > https://wiki.yoctoproject.org/wiki/WW01_-_2019-01-28_-_Full_Test_Cycle_2.7_M2_RC1 > > === Summary > > All planned tests were executed. > Total Test Executed - 3629 > Passed

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

On Fri, 2019-01-18 at 15:16 +0100, Ulf Samuelsson wrote: > > 18 jan. 2019 kl. 12:29 skrev Richard Purdie < > > richard.pur...@linuxfoundation.org>: > > > > > On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote: > > > So if KNOWN_TASKS is

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

On Fri, 2019-01-18 at 05:30 +0100, Ulf Samuelsson wrote: > So if KNOWN_TASKS is defined in a configuration file in oe-core, it > would be OK? > It needs to be extended to check for KNOWN_TASKS == None of course. No, this is too fragile. We then have to maintain two different lists of tasks. If we

Re: [yocto] [PATCH] bb.build.addtask: add simple check for circular dependency

On Thu, 2019-01-17 at 19:15 +0100, Ulf Samuelsson wrote: > From 864e49bedbdab480c5ada9588ce8f980f23919dd Mon Sep 17 00:00:00 > 2001 > From: Ulf Samuelsson > Date: Thu, 17 Jan 2019 19:07:17 +0100 > Subject: [PATCH] bb.build.addtask: add simple check for circular > dependency We really can't

Re: [yocto] bitbake: DataSmart.expandWithRefs causing exception when handed "${@...}"

On Sun, 2019-01-13 at 22:53 +0100, Ulf Samuelsson wrote: > I am trying to add a new image class "SWU" in "sumo" for a "software > update image". > As a result: > do_sdk_depends[depends] = '${@get_ext_sdk_depends(d)} meta-extsdk- > toolchain:do_populate_sysroot' > > When data_smart.py works on

Re: [yocto] [PATCHv2][ptest-runner] ptest-runner: Add support to report duration of each ptest

On Wed, 2019-01-09 at 12:00 -0600, Anibal Limon wrote: > > > On Tue, 8 Jan 2019 at 14:00, > wrote: > > On Mon, 2019-01-07 at 15:18 -0600, Aníbal Limón wrote: > > > In stdout reported as, > > > > > > ... > > > BEGIN: ptest-dir > > > ... > > > DURATION: N > > > END: ptest-dir > > > ... > > > >

Re: [yocto] [PATCHv2][ptest-runner] ptest-runner: Add support to report duration of each ptest

On Mon, 2019-01-07 at 15:18 -0600, Aníbal Limón wrote: > In stdout reported as, > > ... > BEGIN: ptest-dir > ... > DURATION: N > END: ptest-dir > ... > > In XML reported as, > > ... > > N > > ... > > Signed-off-by: Aníbal Limón > --- > tests/data/reference.xml | 2 ++ >

Re: [yocto] [PATCH][ptest-runner] ptest-runner: Add support to report duration of each ptest

On Sun, 2019-01-06 at 11:43 -0600, Aníbal Limón wrote: > In stdout reported as, > > ... > BEGIN: ptest-dir > ... > DURATION: Ns > END: ptest-dir > ... > > In XML reported as, > > ... > > Ns > > ... Looks good, thanks! One minor detail - should this be: N ? I'm wondering if we

Re: [yocto] [PATCH][ptest-runner] ptest-runner: Add support timeout failure type to XML result file

On Sat, 2019-01-05 at 11:30 -0600, Anibal Limon wrote: > > > On Thu, 3 Jan 2019 at 15:45, > wrote: > > On Thu, 2019-01-03 at 12:02 -0600, Aníbal Limón wrote: > > > The ptest-runner support logging results to stdout and to a XML > > file > > > in stdout the ptest is mark as: > > > > > > ... > >

Re: [yocto] [PATCH][ptest-runner] ptest-runner: Add support timeout failure type to XML result file

On Thu, 2019-01-03 at 12:02 -0600, Aníbal Limón wrote: > The ptest-runner support logging results to stdout and to a XML file > in stdout the ptest is mark as: > > ... > ERROR: Exit status is 1 > TIMEOUT: ptest-directory > ... > > Add the same support in XML file for example, > > ... > > >

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

On Fri, 2018-12-28 at 22:35 +0800, Zhaolong Zhang wrote: > On 2018/12/28 19:40, richard.pur...@linuxfoundation.org wrote: > > 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

  1   2   3   4   5   >