[yocto] Fetcher failure for mercurial repos: 'unknown revision' due to -r SRCREV in both clone and update?

I've been running into Fetcher failures for my recipes using mercurial recently. They only seem to crop up the first time a package that comes from a hg repo is fetched. I believe the issue stems from the combination of the arguments used by the hg fetcher and the fact that I specified a tag

[yocto] Disabling PREMIRRORS and upstream sources

Is there a simple way to disable the use of PREMIRRORS and MIRRORS within a recipe? (Perhaps the answer here might be worth mentioning in Section 12.23 of the Poky Reference Manual?) My use case for this is the situation where the code hasn't been released yet, so there's no point in checking

Re: [yocto] QA issue with custom recipe

I am trying to create a simple hello world recipe for a helloworld.c file. The recipe almost works except it hits a QA issue: WARNING: QA Issue: hello: Files/directories were installed but not shipped The warning leads to a failure in the do_rootfs. WARNING: QA Issue: hello:

Re: [yocto] QA issue with custom recipe

I am trying to create a simple hello world recipe for a helloworld.c file. The recipe almost works except it hits a QA issue: WARNING: QA Issue: hello: Files/directories were installed but not shipped The warning leads to a failure in the do_rootfs. WARNING: QA Issue: hello:

Re: [yocto] QA issue with custom recipe

Jon, Thanks for your help. It was a path problem with the install call. Digging into the working directory the copy from path needs to be specified. Regards, Sean Liming Owner Annabooks Tel: 714-970-7523 / Cell: 858-774-3176 Hi Sean, Good find! Sorry, I missed that install issue

Re: [yocto] packagegroup-core-boot failure for RTC-less system

I have a MACHINE_FEATURES which *does not* include rtc, as the platform I am working on doesn't have an RTC. The busybox bbappend I'm using (attached below) uses the provided defconfig, but disables the HWCLOCK features. However, my build is failing due to packagegroup-core-boot being

Re: [yocto] Disabling PREMIRRORS and upstream sources

Hi Jon, Thanks for the clarification on which manual release you were looking at. I am the technical writer for the project so hopefully someone from the team will address the technical aspect of you issue. If there is a way to disable these within a specific recipe then I can get that

Re: [yocto] Remove unwanted package from Qt

Hi, I am compiling Qt-4.8.0 with poky-denzil-7.0 for arm1136 architecture. At the time of integrating qt-embedded with rootfs, I am getting qtopia directory in usr/share path of rootfs. I tried removing qtopia directory through qt recipe but ended in compilation error. Please suggest

Re: [yocto] Remove unwanted package from Qt

Hi, I am compiling Qt-4.8.0 with poky-denzil-7.0 for arm1136 architecture. At the time of integrating qt-embedded with rootfs, I am getting qtopia directory in usr/share path of rootfs. I tried removing qtopia directory through qt recipe but ended in compilation error. Please suggest

Re: [yocto] Remove unwanted package from Qt

On Wed, Jan 16, 2013 at 1:14 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Wednesday 16 January 2013 23:26:20 Navani Srivastava wrote: On Thu, Dec 27, 2012 at 11:08 PM, Jon Szymaniak jon.szyman...@gmail.comwrote: I am compiling Qt-4.8.0 with poky-denzil-7.0 for arm1136

Re: [yocto] Remove unwanted package from Qt

On Thu, Jan 17, 2013 at 3:19 AM, Eric Bénard e...@eukrea.com wrote: Hi Jon, inherit qt4e is enough, no need to add qt4-embedded to DEPENDS. Thanks! This makes sense, as I see this dependency is established in the first few lines of qt4e.bbclass. strange, demos and examples are packaged in

Re: [yocto] Remove unwanted package from Qt

On Fri, Jan 18, 2013 at 10:59 AM, Eric Bénard e...@eukrea.com wrote: Le Fri, 18 Jan 2013 10:25:22 -0500, Jon Szymaniak jon.szyman...@gmail.com a écrit : I checked the package list on a running system (opkg list | grep -i qt). Here's all the installed Qt packages...no qt4-embedded-examples

[yocto] Finding/Generating Rootfs Package List

Hi all, I generally like to keep a little manifest file with my rootfs images, containing a list of installed packages and their associated versions. On images where I keep package data around, I usually generate this via 'opkg list'. In my current situation, I have a small read-only image

Re: [yocto] Finding/Generating Rootfs Package List

Jansa martin.ja...@gmail.comwrote: On Thu, Apr 25, 2013 at 10:10:31AM -0400, Jon Szymaniak wrote: Hi all, I generally like to keep a little manifest file with my rootfs images, containing a list of installed packages and their associated versions. On images where I keep package data

[yocto] Correctly setting a package-specific RDEPENDS

Hi all, I recently upgraded to the Dylan (9.0.0) release and am looking to clean up some QA issues associated with my RDEPENDS variables not being package-specific. I'm a bit confused by a couple lines in the manual [1]: The names of the variables you list with RDEPENDS must be the names of

Re: [yocto] Correctly setting a package-specific RDEPENDS

On Wednesday 05 June 2013 10:53:23 Jon Szymaniak wrote: I recently upgraded to the Dylan (9.0.0) release and am looking to clean up some QA issues associated with my RDEPENDS variables not being package-specific. I'm a bit confused by a couple lines in the manual [1]: The names

[yocto] do_configure() failure with my qt4-embedded_4.8.0.bbappend

Hi there, I'm working on building some embedded (arm) Qt 4.8.0 applications, and would like to strip out a lot of unused functionality. I have a set of config flags that I've used in the past when configuring Qt outside of the Yocto workflow. As you'll see below, I'm basically just looking for

Re: [yocto] do_configure() failure with my qt4-embedded_4.8.0.bbappend

QT_CONFIG_FLAGS := -release -no-rpath -reduce-relocations -shared\ -no-mmx -no-3dnow -no-sse -no-sse2 -no-sse3 -no-sse4.1 -no-sse4.2 -no-avx\ -no-glib -no-largefile -no-accessibility -no-openssl -no-gtkstyle -no-exceptions\ -no-xcursor -no-xinerama -no-phonon -no-phonon-backend -no-svg

Re: [yocto] do_configure() failure with my qt4-embedded_4.8.0.bbappend

Since you're providing your own value of QT_CONFIG_FLAGS I think you're missing -embedded $QT_ARCH and possibly -qtlibinfix ${QT_LIBINFIX} (see meta/recipes-qt/qt4/qt4-embedded.inc). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre Whoops! I most certainly did forget

Re: [yocto] do_configure() failure with my qt4-embedded_4.8.0.bbappend

Since you're providing your own value of QT_CONFIG_FLAGS I think you're missing -embedded $QT_ARCH and possibly -qtlibinfix ${QT_LIBINFIX} (see meta/recipes-qt/qt4/qt4-embedded.inc). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre Whoops! I most certainly did forget

[yocto] [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo

, and the connection eventually hangs and errors out. Signed-off-by: Jon Szymaniak jon.szyman...@gmail.com --- recipes-bsp/common/firmware.inc | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/recipes-bsp/common/firmware.inc b/recipes-bsp/common/firmware.inc index ad3176a

Re: [yocto] [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo

On Fri, Jun 26, 2015 at 10:19 AM, Burton, Ross ross.bur...@intel.com wrote: On 26 June 2015 at 15:16, Jon Szymaniak jon.szyman...@gmail.com wrote: I'm open to other suggestions as well, as this was just a first stab at it. I've been seeing that cloning this git repo containing binary

Re: [yocto] [meta-raspberrypi][PATCH] firmware.inc: Fetch a zip instead of cloning a git repo

On Fri, Jun 26, 2015 at 4:31 AM, Burton, Ross ross.bur...@intel.com wrote: On 26 June 2015 at 05:16, Jon Szymaniak jon.szyman...@gmail.com wrote: GitHub provides this ability to download repository contents at a specified changeset as a zip file. This is generally *much* quicker than

Re: [yocto] [meta-raspberrypi][PATCH] firmware.inc: fetch from SVN instead of Git

Hi all, So there is no support for depth clones until 2.5.0? I didn't really understand. Well, shallow clones are supported but only for branch tips, which is not what we need. This feature for shallow cloning a specific revision is available only in git 2.5.0+. Also, this feature

[yocto] Upstream U-Boot fetch failure (Jethro)

Hi all, When fetching from upstream U-Boot, I am encountering an initial fetch failure that "breaks" the current build. After this initial failure, successive executions of the recipe allows it to continue. The minimal recipe for me to reproduce this is a simple two liner. u-boot_2016.01.bb:

Re: [yocto] Altera Cyclone V u-boot-spl with meta-altera

> > > If you upgrade to the U-Boot 2016.01 (or maybe even earlier?), mkimage > actually supports adding the Bootrom signature to the SPL for you. The > current makefile is kind enough to concatenate the U-Boot SPL and its DTS > for you, and then run mkpimage to create an 'spl/u-boot-spl-dts.sfp'

Re: [yocto] Altera Cyclone V u-boot-spl with meta-altera

> Is there a way to produce a signed u-boot-spl image during the build, that > can be used directly on the target without using the EDS? > > If you upgrade to the U-Boot 2016.01 (or maybe even earlier?), mkimage actually supports adding the Bootrom signature to the SPL for you. The current

Re: [yocto] wic: Setting partition id value?

On Feb 10, 2016 12:24 PM, "Usman, Fahad" wrote: > > Hi, > Is there a way to create a partition with an arbitrary partition id, using wic tool. We want to create a disk image using wic for Altera Cyclone V. It require the partition id to be set to a particular hex value for

[yocto] Build failure when BUILDHISTORY_FEATURES includes "package"

Hi all, I'm encountering the following error, which I can reproduce with qemu targets, core-image-minimal, a default bblayers.conf, and the following additions to an otherwise default local.conf: INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "0" BUILDHISTORY_FEATURES = "package" ERROR:

Re: [yocto] qemu-native build fails on sumo due to missing capstone.h

On Fri, Jun 1, 2018 at 1:00 AM, Jon Szymaniak wrote: > When attempting to build core-image-minimal on sumo (@b369e61) with a > largely default local.conf, I'm experiencing qemu-native build failures due > to what appear to be an include path issue. > > Below is one of the fa

Re: [yocto] qemu-native build fails on sumo due to missing capstone.h

On Thu, Jun 14, 2018 at 14:18 Khem Raj wrote: > On Thu, Jun 14, 2018 at 9:56 AM Jon Szymaniak > wrote: > > > > On Thu, Jun 14, 2018 at 11:43 Khem Raj wrote: > > > Do you have capstone development headers/libs installed on your build > host ? > > > >

[yocto] [meta-security] buck-security not found in STAGING_BINDIR_NATIVE

te_sysroot?), and where the breakdown is happening here. If anyone else is able to reproduce this or provide some assistance in resolving or just debugging it, I'd greatly appreciate it. Thank you, Jon Szymaniak References: [1] https://git.yoctoproject.org/cgit/cgit.cgi/meta-security/ [2] https

[yocto] qemu-native build fails on sumo due to missing capstone.h

strikes me as something that would have broken the nightly builds and therefore might just be an issue on my end somehow. Thanks, Jon Szymaniak -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-security] buck-security not found in STAGING_BINDIR_NATIVE

On Fri, Jun 1, 2018 at 11:34 AM, Jon Szymaniak wrote: > From my understanding, all that should be required to run the buck-security > after an image build is adding INHERIT += "check_security" to local.conf. I > see > that check_security.bbclass [2] already takes ca

[yocto] [meta-security] buck-security not found in STAGING_BINDIR_NATIVE

ing do_populate_sysroot?), and where the breakdown is happening here. If anyone else is able to reproduce this or provide some assistance in resolving or just debugging it, I'd greatly appreciate it. Thank you, Jon Szymaniak Links: [1] https://git.yoctoproject.org/cgit/cgit.cgi/meta-security/ [2] https

Re: [yocto] Tracking changes in image

On Mon, Aug 27, 2018 at 10:13 Bryan Fishell wrote: > Hi, > I want to be able to track different parts of my image, accessible from > within userspace so I can programmatically (via an environment variable or > something) what version of my patches have been applied. Ultimately, I want > to be

Re: [yocto] Security updates question

Hi Brian, On Fri, Sep 7, 2018 at 3:36 PM Khem Raj wrote: > Hi Brian > > On Fri, Sep 7, 2018 at 1:25 PM Brian Smucker wrote: > > > > Hello all, > > > > We have a device whose image is built using an older yocto image. It is > > based on yocto Danny, if I recall correctly. > > > > How do users

Re: [yocto] Security updates question

Hi Brian, On Sat, Sep 8, 2018 at 6:20 PM Brian Smucker wrote: > Jon, > > I do appreciate your insights and I am aware of some of the update > mechanisms that are out there. At the moment we don't have a need for > that. The need at this time is a totally new image, identical to the > working

Re: [yocto] NVIDIA or AMD accelerated graphics on x86 or x86-64 machine architecture

On Fri, Oct 26, 2018 at 15:51 Matt Ervin wrote: > I’m creating a poky (sumo branch) based OS image for x86_64 PC hardware. > It’s an embedded device that is essentially a desktop PC in a box with > additional features. My device requires accelerated graphics (either NVIDIA > or AMD, not Intel)

Re: [yocto] Making a script into an executable binary in yocto

Could you provide a bit more context about your particular use-case and need to do this? i.e. Why is deployment of the existing script insufficient? I know this isn’t addressing your underlying question, but just want to see if perhaps an alternative solution may be a better one for you. On