[yocto] Add own dts file to arch/arm/boot/dts

Good day, How can I add my own dts file to the arch/arm/boot/dts folder? Within my yocto installation the whole path for the dts files is: tmp/work/sm2_imx6-poky-linux-gnueabi/linux-yocto-custom/4.1.15-2/git/arch/arm/boot/dts As you can see it lies within the "tmp" folder. Hence, I do not want

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Mon, Apr 24, 2017 at 12:13 PM, Burton, Ross wrote: > > On 24 April 2017 at 10:09, Burton, Ross wrote: >> >> All merged, I'll fire in a moment. > > > lttng-modules fails: > > In function 'lib_ring_buffer_align', > inlined from

Re: [yocto] [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 01:31, Bruce Ashfield wrote: > I see that it was the 4.1 kernel, which is expected to fail. I haven't > looked into backporting gcc7 fixes > that far, but if there's demand, it is something we can consider/look into. > There's demand in that the

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

"Burton, Ross" writes: > On 24 April 2017 at 10:09, Burton, Ross wrote: > >> All merged, I'll fire in a moment. >> > > lttng-modules fails: > > In function 'lib_ring_buffer_align', > inlined from 'lib_ring_buffer_try_reserve' at >

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 17:10, Khem Raj wrote: > thanks, yes I haven't been testing SDK yet, whats the gcc version on > your build host ? > It's failing across the autobuilder so I'd suggest it's not specific to a gcc version. It also breaks on my personal machine, which is

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 10:09, Burton, Ross wrote: > All merged, I'll fire in a moment. > lttng-modules fails: In function 'lib_ring_buffer_align', inlined from 'lib_ring_buffer_try_reserve' at

[yocto] Raspberry Pi 3 build issue

Hello, I am currently encountering an issue with meta-raspberry and more specifically Raspberry Pi 3 build. Since I was not sure the problem was not my fault, I cloned a fresh copy of poky and meta-raspberrypi (both checked out on morty, and meta dependencies on morty too), but the problem is

[yocto] [meta-oic][PATCH] iotivity: Sanitize URIs to support older yocto versions

Removing trailing separator solved issues observed on older version of yocto (daisy at least): Parsing recipes..ERROR: ExpansionError during parsing /recipes-core/iotivity/iotivity_1.2.0.bb: Failure expanding variable do_fetch[file-checksums], expression was

Re: [yocto] [open-amp] Build a Yocto image to be the guest (Dom1) in a system that uses Xen hypervisor and petalinux image for Dom0

HI Pello, From: open-...@googlegroups.com [mailto:open-...@googlegroups.com] On Behalf Of Pello Heriz Sent: Monday, April 24, 2017 1:44 AM To: meta-virtualizat...@yoctoproject.org; meta-xil...@yoctoproject.org; yocto@yoctoproject.org; Jiaying Liang; open-...@googlegroups.com Subject: [open-amp]

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Mon, Apr 24, 2017 at 8:54 AM, Burton, Ross wrote: > > On 24 April 2017 at 10:47, Burton, Ross wrote: >> >> The updated glibc recipe doesn't appear to be very happy: >>

Re: [yocto] bitbake core-image-base -c do_populate_sdk fails with glibc (unmet dependencies)

On 23 April 2017 at 09:40, David Bensoussan wrote: > I managed to track down how to create the SDK. Sorry for the long answer > but it might help people googling it. > Honestly no idea why this doesn't work for you: $ MACHINE=qemuarm64 bitbake core-image-base -c

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 10:47, Burton, Ross wrote: > The updated glibc recipe doesn't appear to be very happy: > https://autobuilder.yocto.io/builders/buildtools/ > builds/240/steps/BuildImages/logs/stdio > Note that every nativesdk-glibc build is failing like this, so that's

[yocto] Yocto Project Status WW17’17

Current Dev Position: YP 2.3 M4 Next Deadline: YP 2.3 M4 Cutoff is April 10, 2017 *** FEATURE FREEZE for 2.3 is now in effect. *** SWAT team rotation: Joshua -> Armin on April 21, 2017. SWAT team rotation: Armin -> Saul on April 28, 2017.

[yocto] [PATCHv2][meta-gplv2] gnutls: add older gnutls compatible with nettle

* gnutls depends on nettle-3.1* since 3.4.0: The requirement for nettle was bumped from 3.0 to 3.1 in gnutls_3_4_0 https://gitlab.com/gnutls/gnutls/commit/c84129af91b21d33ffe086e507632771b0e76498 and from 2.7 to 3.0 a bit earlier also in gnutls_3_4_0

Re: [yocto] [RFC][meta-gplv2] layer priority and worth creating branch compatible with morty?

You're right, after fixing our tooling to correctly override BBFILE_PRIORITY based on priorities in layer list I'm seeing such issue.e.g. gstreamer failing with: | autopoint: *** The AM_GNU_GETTEXT_VERSION declaration in your configure.ac file requires the infrastructure from

Re: [yocto] [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Mon, Apr 24, 2017 at 7:11 AM, Burton, Ross wrote: > > On 24 April 2017 at 11:29, Burton, Ross wrote: > >> I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to >> update the BSP with some fixes you've made? >> > > Or ideally

Re: [yocto] [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On Mon, Apr 24, 2017 at 6:29 AM, Burton, Ross wrote: > > On 24 April 2017 at 01:31, Bruce Ashfield > wrote: > >> I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto >>> should be at a high enough stable >>> release to build

Re: [yocto] [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 11:29, Burton, Ross wrote: > I'm getting that with 4.9.15 from meta-intel, should I be telling Saul to > update the BSP with some fixes you've made? > Or ideally telling myself to update meta-intel for the fixes that Saul has already merged... Ross --

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 06:45, Khem Raj wrote: > There are few other fixes that needs to be in there. glibc and gcc recipes > also needed some fixes. I have pushed the whole series to kraj/master > branch on contrib repo > grub is still failing on musl on the autobuilder: |

Re: [yocto] [oe] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 01:31, Bruce Ashfield wrote: > I wasn't able to bring up the linux-yocto one .. but the 4.10 linux Yocto >> should be at a high enough stable >> release to build with gcc7. So if there's a direct link to that error, I >> can take a closer look. >> >

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 10:09, Burton, Ross wrote: > All merged, I'll fire in a moment. > https://autobuilder.yocto.io/builders/nightly-non-gpl3/builds/237/steps/BuildImages/logs/stdio shows that the old elfutils in meta-gpl2 doesn't like gcc7 either. Ross --

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 10:09, Burton, Ross wrote: > All merged, I'll fire in a moment. > The updated glibc recipe doesn't appear to be very happy: https://autobuilder.yocto.io/builders/buildtools/builds/240/steps/BuildImages/logs/stdio Ross --

Re: [yocto] [OE-core] [RFT] gcc7 and glibc-2.26 recipes

On 24 April 2017 at 06:45, Khem Raj wrote: > There are few other fixes that needs to be in there. glibc and gcc recipes > also needed some fixes. I have pushed the whole series to kraj/master > branch on contrib repo > >

Re: [yocto] Installing shared libraries ncurses for custom application

Hi Ross, Thank you for your personalized reply. I've changed my receipe with your recommandations and clean the receipe with "bitbake -c cleanall myapp" But I still have an issue when compiling with "bitbake myapp": WARNING: myapp-0.1.1-r0 do_package_qa: QA Issue: /usr/bin/myApp contained in

[yocto] do_rootfs error when including qt5 examples "cinematicexperience" and "qt5-opengles2-test"

Good day, I included the following examples from "meta-qt5": IMAGE_INSTALL += "cinematicexperience qt5-opengles2-test" Everything works until "do_rootfs". I get the following errors: [log_check] Error opening package - qtdeclarative-dev-5.7.0+git0+d48b397cc7-r0.cortexa9hf_neon.rpm [log_check]

[yocto] Build a Yocto image to be the guest (Dom1) in a system that uses Xen hypervisor and petalinux image for Dom0

Hi all, Finally I have compiled an image using Yocto that includes the meta-virtualization layer with DISTRO_FEATURES_append = " xen" in the local.conf file. I understand that this must be used to build an image to work as a Dom0 image with Xen. If I want to have a Dom1 guest image, would be