Re: [yocto] devtool finish & patch order

2018-06-15 2:11 GMT+03:00 Peter Kjellerstedt : > * `devtool modify -w ` > * Modify some file, e.g., add some comment to the Makefile. > * Commit it with subject "Change 1" > * Repeat the two steps above two more times, increasing the number in > the subject each time. > * `devtool finish ` > * E

Re: [yocto] devtool finish & patch order

> -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Alexander Kanavin > Sent: den 14 juni 2018 09:07 > To: Tim Hammer > Cc: Yocto discussion list > Subject: Re: [yocto] devtool finish & patch order > > 2018-06-14 7:02 GMT+03

[yocto] [ANNOUNCEMENT] Yocto Project 2.4.3 (rocko-18.0.3) Released

Hello, The latest release of the Yocto Project 2.4.3 (rocko-18.0.3) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.3/poky-rocko-18.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.3/poky-rocko-18.0.3.tar.bz2 A gpg signed version of these

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

On Thu, Jun 14, 2018 at 1:08 PM Jon Szymaniak wrote: > 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

Re: [yocto] How handle files needing updates in read-only filesystem

I looked at the populate-volatile.sh, and this seemed to almost do the job, if I solve the problem using symlinks. What it needs is a copy file function. As a temporary solution, I created a derivative: populate-settings.sh which will check /etc/default/settings in the same way populate-volatile.s

Re: [yocto] Issue when integrating different bsp-layers on a single bblayers.conf

Just thought I should mention that since Krogoth, BBMASK is actually a list of regular expressions, so your example below is better written as: BBMASK += "${@bb.utils.contains('MACHINE', '', '', '/meta-rockchip/recipes-.*', d)}" (including changing base_conditional() to bb.utils.contains(), and

Re: [yocto] Issue yocto strip the kernel module signature during packaging

On 6/13/18 12:10 PM, Mathieu Alexandre-Tétreault wrote: > Hello, > > I am working to activate the kernel module signature for in-tree and > out-of-tree packages. > While I was debugging the cause of the kernel complaining about unsigned > modules. > I noticed that yocto was stripping the signatu

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 ? > > > > > > > No, and I understand that's an easy thi

Re: [yocto] Build failure when BUILDHISTORY_FEATURES includes "package"

On Thu, Jun 14, 2018 at 10:58 AM Jon Szymaniak wrote: > > 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" > BUIL

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

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 ? > > > > No, and I understand that's an easy thing to address on the build host. > > However, I don't think this s

[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: core-i

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

On Thu, Jun 14, 2018 at 11:43 Khem Raj wrote: > Do you have capstone development headers/libs installed on your build host ? > No, and I understand that's an easy thing to address on the build host. However, I don't think this should be necessary build host dependency. QEMU includes the capstone

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

On 6/14/18 8:49 AM, Jon Szymaniak wrote: > 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. >>

Re: [yocto] /boot/ content into root filesystem?

On Thu, Jun 14, 2018 at 2:40 AM, Josef Holzmayr < holzm...@rsi-elektrotechnik.de> wrote: > Hi Tim, > > On Wed, Jun 13, 2018 at 11:57:10PM -0400, Tim Hammer wrote: > > I would like to include the kernel Image and DTB files in the /boot/ > > directory of the root filesystem that will be installed in

[yocto] License information for Mono recipe?

Hi all, I've been doing some updating of meta-mono mono support and the license file has changed. IANAL and I'd like to get this right so is anybody in a position to advise me on what the recipe should contain to correctly reflect the various licenses for mono? ref: https://github.com/mono

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 failures -- those not lis

Re: [yocto] sysroot not being populated

On Thu, Jun 14, 2018 at 5:45 AM Patrick Vacek wrote: > > On 12.06.2018 00:48, Andre McCurdy wrote: > > On Fri, Jun 8, 2018 at 2:42 AM, Patrick Vacek > > wrote: > >> On 08.06.2018 10:26, Khem Raj wrote: > >>> On 6/8/18 12:27 AM, Patrick Vacek wrote: > On 07.06.2018 19:06, Khem Raj wrote: > >

Re: [yocto] bbappend extra SRC_URI ignored

See ./recipes-bsp/tegra-binaries/tegra-shared-binaries.inc It's disabling standard do_fetch, do_unpack, do_patch and replacing them with tegra-binaries:do_unpack tegra-binaries:do_preconfigure which populates S directory in work-shared S = "${TMPDIR}/work-shared/L4T-${SOC_FAMILY}-${PV}-${PR}/Linux

Re: [yocto] bbappend extra SRC_URI ignored

On 14.06.2018 14:16, Damien LEFEVRE wrote: HI, I'm working on meta-tegra layer and I'd like to append a recipe. The original recipe looks like this: https://github.com/madisongh/meta-tegra/blob/rocko-l4t-r28.2/recipes-bsp/tegra-binaries/tegra-tools_28.2.0.bb

Re: [yocto] bbappend extra SRC_URI ignored

Thanks Here are some interesting parts of bitbake -e. It seems my syntax is correct # $FILESEXTRAPATHS [3 operations] # set? /home/damien/procbox-pyro/sources/poky/meta/conf/bitbake.conf:325 # "__default:" # set /home/damien/procbox-pyro/sources/poky/meta/conf/documentation.conf:173 #

Re: [yocto] bbappend extra SRC_URI ignored

On Thu, 14 Jun 2018, Damien LEFEVRE wrote: > HI, > I'm working on meta-tegra layer and I'd like to append a recipe. The original > recipe looks like > this: > https://github.com/madisongh/meta-tegra/blob/rocko-l4t-r28.2/recipes-bsp/tegra-binaries/tegra-t > ools_28.2.0.bb  > > I've made a tegra-to

Re: [yocto] bbappend extra SRC_URI ignored

On Thu, Jun 14, 2018 at 03:16:00PM +0300, Damien LEFEVRE wrote: > HI, > > I'm working on meta-tegra layer and I'd like to append a recipe. The > original recipe looks like this: > https://github.com/madisongh/meta-tegra/blob/rocko-l4t-r28.2/recipes-bsp/tegra-binaries/tegra-tools_28.2.0.bb >

Re: [yocto] bbappend extra SRC_URI ignored

Typo sorry. I've tried all possible combination - SRC_URI += "file://nvpmodel.conf" - SRC_URI_append = " file://nvpmodel.conf" - SRC_URI_prepend = "file://nvpmodel.conf " - SRC_URI_append_tegra186 = " file://nvpmodel.conf" - SRC_URI_prepend_tegra186 = "file://nvpmodel.conf " -Dam

[yocto] bbappend extra SRC_URI ignored

HI, I'm working on meta-tegra layer and I'd like to append a recipe. The original recipe looks like this: https://github.com/madisongh/meta-tegra/blob/rocko-l4t-r28.2/recipes-bsp/tegra-binaries/tegra-tools_28.2.0.bb

Re: [yocto] devtool finish & patch order

2018-06-14 7:02 GMT+03:00 Tim Hammer : > > My changes for U-Boot are not working as expected. I am wondering- did I use > devtool incorrectly? > > I used 'devtool modify' to create a working copy of the vendor's u-boot and > copied & modified files to add support for my custom board. I did my work