Re: [yocto] patches to upgrade meta-jupyter layer packages

On 19.11.2019 01:15, Chandana Kalluri wrote: > Hello all, > > I have upgraded python packages from meta-jupyter layer to work with the zeus > branch. > I am planning to send out the patches to this yocto project mailing list > yocto@yoctoproject.org Please let me know if this is alright or if I

[yocto] [warrior] [meta-qt4] 3rdparty: javascriptcore: JITStubs.cpp: allow builds of JavaScriptCore with gcc v8

At least since gcc v8, source code with asm volatile won't compile anymore. The volatile qualifier anyway is a no-op since asm blocks are implicitly volatile as written in the documentation[1]. Let's get rid of this redundant qualifier so we can build with newer GCCs. The resulting error message

[yocto] [meta-qt4] [BUG] qt4-embedded broken on warrior for qemux86-64

Hi all, Just to let you know that qt4-embedded on qemux86-64 in warrior is broken with the following message during the do_compile task: | make[1]: Leaving directory '/tmp/poky/build/workspace/sources/qt4-embedded/tools' | cd translations/ && make -e -f Makefile | make[1]: Entering directory '/

[yocto] Yocto Project Status WW47'19

Current Dev Position: YP 3.1 M1 Next Deadline: YP 3.1 M1 build Dec. 2, 2019 Next Team Meetings: * Bug Triage meeting Thursday Nov. 21st at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Dec. 3rd at 8am PDT (

[yocto] [warrior] [meta-qt4] recipes-qt4: qt4-embedded: fix build on GCC v8

At least since gcc v8, source code with asm volatile won't compile anymore. The volatile qualifier anyway is a no-op since asm blocks are implicitly volatile as written in the documentation[1]. Let's get rid of this redundant qualifier so we can build with newer GCCs. The resulting error message

[yocto] Zeus Call for patches

Hello, We are planning on doing the first dot release for Zeus this coming Monday. If you would like a get your changes into this Zeus update, please have them on the list by this Friday for review. regards, Armin & Anuj -- ___ yocto mailing list yocto

[yocto] Install native recipe into filesystem

We have several executables that can run on the target (ARM64) but also on the host system (x86). I added the BBCLASSEXTEND = "native" and can build all the recipes in native mode. Once done, I would like to be able to install them on the host system, but don't see a package for them (or under

Re: [yocto] Install native recipe into filesystem

On 11/19/19 4:15 PM, Jeff Kaisner wrote: We have several executables that can run on the target (ARM64) but also on the host system (x86).  I added the BBCLASSEXTEND = "native" and can build all the recipes in native mode. What do you mean here by 'in native mode'? I'd expect that you mean:

[yocto] Device is unable to BOOT or INSTALL with generated .hddimg

All, I have device which has following configuration: - Chipset architecture - `Intel NM10 express` - Processor - `Atom D2550 Dual Core` - Display - `DVI` - Volatile Memory - `2GB DDR3` - Storage - `16GB` **Objective**: Device should run yocto embededded OS successfully What I have done, - Dow

Re: [yocto] Device is unable to BOOT or INSTALL with generated .hddimg

As the question was almost simultaneously cross-posted on stackoverflow, see answer there: https://stackoverflow.com/questions/58947276/device-is-unable-to-boot-or-install-with-generated-hddimg/58948913#58948913 Greetz On Wed, Nov 20, 2019 at 06:40:35AM +, Oriya, Raxesh wrote: > All, > > I