Re: [yocto] build fails for qemux86

On Mon, Dec 17, 2018 at 9:06 PM sanjay chopra wrote: > > Hi, > > It also happens when I build for raspberry pi, core-image-sato works fine > though. > thats ok. it just says something is not right about the tools being used during build I suspect qemu usermode since thats whats used to execute

Re: [yocto] build fails for qemux86

Hi, It also happens when I build for raspberry pi, core-image-sato works fine though. On Tue 18 Dec, 2018, 6:33 AM Khem Raj On Mon, Dec 17, 2018 at 12:09 PM sanjay chopra > wrote: > > > > Hi, > > > > Whenever I try to build core-image-minimal , it fails in rootfs step.But > I am able to build

Re: [yocto] build fails for qemux86

On Mon, Dec 17, 2018 at 12:09 PM sanjay chopra wrote: > > Hi, > > Whenever I try to build core-image-minimal , it fails in rootfs step.But I am > able to build core-image-sato. > > With thud and master branch I am getting this issue. Sumo branch was working > fine.Please help me to figure this

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

Bruce, On Mon, Dec 17, 2018 at 3:00 PM Richard Weinberger wrote: > When I set DEFAULTTUNE to i586 for a 64bit machine I'd expect > TARGET_SYS still being x86_64-poky-linux. > But it is i686-poky-linux. > > > Do you have a dump of the kernel build line that I could see ? > > Sure, let me trigger

[yocto] build fails for qemux86

Hi, Whenever I try to build core-image-minimal , it fails in rootfs step.But I am able to build core-image-sato. With thud and master branch I am getting this issue. Sumo branch was working fine.Please help me to figure this out. bitbake core-image-minimal Loading cache: 100%

[yocto] RaspberryPi 3: u-boot --- hangs on boot?

> Hi, > How do you get the u-boot built with yocto for Raspberry Pi 3? > > - I used this link > to get > the base build working for q5-image on Raspberry Pi 3. > - I have used the yocto 'thud' release. > - Now in order to get u-boot

Re: [yocto] RDEPENDS error for itstool recipe

As https://github.com/schnitzeltony/meta-qt5-extra/blob/master/recipes-support/itstool/itstool_2.0.4.bb shows, you need to fix the hashbang manually. Always check the layer index before writing a recipe. :) Ross On Mon, 17 Dec 2018 at 16:30, Q. Gouès wrote: > > Hi, > > I am trying to create

[yocto] RDEPENDS error for itstool recipe

Hi, I am trying to create the recipe for the package itstool (available https://github.com/itstool/itstool) for Yocto. Here is my recipe file (itstool_git.bb): -- SUMMARY =

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

Bruce, On Mon, Dec 17, 2018 at 2:54 PM Bruce Ashfield wrote: > > Yes, it builds with i686-poky-linux. :-( > > It's Monday, and I've only had half a coffee .. so bear with me. When > I see i686, I'd expect that without -m32 it is generating 64bit by > default .. so there's definitely a -m32

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

On 12/17/18 8:50 AM, Richard Weinberger wrote: Bruce, On Mon, Dec 17, 2018 at 2:47 PM Bruce Ashfield wrote: Yocto seems to try a different approach. When I use qemux86-64.conf with DEFAULTTUNE being "i586" it generates a 32bit toolchain by default. Build Configuration: BB_VERSION =

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

Bruce, On Mon, Dec 17, 2018 at 2:47 PM Bruce Ashfield wrote: > > Yocto seems to try a different approach. > > When I use qemux86-64.conf with DEFAULTTUNE being "i586" it generates a > > 32bit > > toolchain by default. > > > > Build Configuration: > > BB_VERSION = "1.38.0" > >

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

On 12/17/18 7:25 AM, Richard Weinberger wrote: [Resending with correct mail] Richard, On Mon, Dec 17, 2018 at 11:34 AM wrote: 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

[yocto] static build of Qt

Hello, Is it possible to make a static build of Qt using yocto ? Or does it have to be manually done as shown here: https://doc.qt.io/QtForDeviceCreation/qtee-static-linking.html Thank you, Ran -- ___ yocto mailing list yocto@yoctoproject.org

Re: [linux-yocto] [PATCH] virtio.cfg: enable CONFIG_DRM_VIRTIO_GPU

On 12/17/18 8:34 AM, Bruce Ashfield wrote: On 12/17/18 5:30 AM, Alexander Kanavin wrote: On Mon, 17 Dec 2018 at 04:31, Bruce Ashfield wrote: This adds support for a virtual graphics card provided by QEMU, which allows accelerated host-assisted GL inside QEMU guests. merged. This will be in

Re: [linux-yocto] [PATCH] virtio.cfg: enable CONFIG_DRM_VIRTIO_GPU

On 12/17/18 5:30 AM, Alexander Kanavin wrote: On Mon, 17 Dec 2018 at 04:31, Bruce Ashfield wrote: This adds support for a virtual graphics card provided by QEMU, which allows accelerated host-assisted GL inside QEMU guests. merged. This will be in my next consolidated pull request. Thanks.

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

[Resending with correct mail] Richard, On Mon, Dec 17, 2018 at 11:34 AM wrote: > > 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 > > >

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. > > > > What may work is selecting

Re: [linux-yocto] [PATCH] virtio.cfg: enable CONFIG_DRM_VIRTIO_GPU

On Mon, 17 Dec 2018 at 04:31, Bruce Ashfield wrote: > > This adds support for a virtual graphics card provided by QEMU, > > which allows accelerated host-assisted GL inside QEMU guests. > > merged. This will be in my next consolidated pull request. Thanks. I'm new to this - why is the patch in

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

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. > > What may work is selecting the i586 tune from an x64-64 target machine? > > Copying qemux86-64.conf to