[yocto] [meta-raspberrypi][PATCH 1/2] qt5: fixed raspberrypi support

Because EGL properties were not defined properly, we always had the following error make: *** [egl] Error 1 | EGL disabled. | The EGL functionality test failed; EGL is required by some QPA plugins to manage cont | You might need to modify the include and

[yocto] Where should I append Yocto bitbake task to create work folder symlink ?

Let's say I have my package at host-64/tmp/work/x86_64-poky-linux/mypackage/1.2.3-r4/ I would like to have symlink created host-64/tmp/work/x86_64-poky-linux/mypackage/latest -> 1.2.3-r4/ each time the new version is fetched and unpacked. How can I achieve that ? Which class, task

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On śro, 2016-02-03 at 11:13 +0100, Woronicz, Bartosz ( NSN - PL/Wroclaw) wrote: > Let's say I have my package at > >  host-64/tmp/work/x86_64-poky-linux/mypackage/1.2.3-r4/ > > I would like to have symlink created > >  host-64/tmp/work/x86_64-poky-linux/mypackage/latest -> 1.2.3-r4/ >

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 3 February 2016 at 10:13, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > Let's say I have my package at > > host-64/tmp/work/x86_64-poky-linux/mypackage/1.2.3-r4/ > > I would like to have symlink created > >

[yocto] [meta-raspberrypi][PATCH 2/2] layer.conf: avoid to force users to add the qt5 layer because of qtbase bbappend

Signed-off-by: John Madieu --- conf/layer.conf | 4 1 file changed, 4 insertions(+) diff --git a/conf/layer.conf b/conf/layer.conf index bea5a65..60f1bcb 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -12,3 +12,7 @@ BBFILE_PRIORITY_raspberrypi = "9" #

Re: [yocto] Poky or oe-core instructions

On 3 February 2016 at 13:27, Nathan Sowatskey wrote: > - Which version of bitbake should one use? The one from oe-embedded, or > the one from Poky? > - Are the latest versions shown in the oe-embedded instructions correct? > They are fido for oe-embedded, and 1.26 for

[yocto] OpenEmbedded Metadata: Recipe update broken

Hi, FAQ for layerindex says recipes are updated every 3 hours but I think it does not work. E.g meta-oe geis/grail/frame are not mentioned but were committed few days ago. Andreas -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi all, I built a core-image-minimal with additions of a few packages like tools-sdk and tools-debug. With WIK tool and the kickstart file "mkgalileodisk", I created the image. Then I dd'd the image to the SD card. The Galileo booted with the image, but it's not accepting "root" as the

[yocto] Poky or oe-core instructions

Hi I can see these instructions for setting up oe-core: http://www.openembedded.org/wiki/OE-Core_Standalone_Setup Which overlap with instructions here for Poky: http://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html Specifically, the part about initialising the build

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 03.02.2016 11:28, EXT Burton, Ross wrote: On 3 February 2016 at 10:13, Woronicz, Bartosz ( NSN - PL/Wroclaw) > wrote: Let's say I have my package at host-64/tmp/work/x86_64-poky-linux/mypackage/1.2.3-r4/ I would

Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

On Wed, Feb 3, 2016 at 6:54 AM, GUEYTAT Julien wrote: > Setting properly the variable PACKAGECONFIG_GL to gles2 does NOT update > properly the variable QMAKE_LIBS_EGL. > By default QMAKE_LIBS_EGL = -lEGL > And depending on hardware... it might be something like

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 3 February 2016 at 14:16, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > But I need to the sysroot cleanup deliberately, right ? > No, that happens on startup (in master and the jethro release). Ross -- ___ yocto

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi all, I would additionally like to mention that the same problem persists when trying to boot the Galileo with core-image-sato. The steps which I followed are as follows:- Inside the poky directory, 1. source oe-init-build-env final_build/ Now ,Inside the final_build/ directory 2.

[yocto] Which Toolchain is being used to build Yocto ?

Hi, Building jethro on a Ubuntu14.04 system. I want to ensure that each person in the team is using the same tool-chain version. I notice there is a meta/recipes-devtools - I assume this pulls in from build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain comprised of these

Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

On Wed, Feb 3, 2016 at 3:46 AM, GUEYTAT Julien wrote: > Hi everyone, > > > > I understand that you are all rewriting the qtbase rule to include at least > the modification to the QMAKE_LIBS_EGL variable. > > The question is: > > Could we make somehow some work in

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi Maciek, In "final_build/conf/local.conf" , EXTRA_IMAGE_FEATURES = "debug-tweaks". So, yes "debug-tweaks" is present. Thanks, Shubham_K From: Maciek Borzecki Sent: Wednesday, February 3, 2016 8:19 PM To: Shubham Kumar

Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

I'm saying that meta-qt5 should directly GRAB the proper EGLFS settings from the virtual/libgles2 provider. If qt and gles2 then grab necessary information. If information not present then use defaults like -lEGL in this case. I guess it should be possible to get the information from a package

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On śro, 2016-02-03 at 14:00 +, shubham.kum...@wipro.com wrote: > > Hi all, > > I would additionally like to mention that the same problem persists when > trying to boot > the Galileo with core-image-sato.  > The steps which I followed are as follows:- > Inside the poky directory, > > 1.  

Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

Setting properly the variable PACKAGECONFIG_GL to gles2 does NOT update properly the variable QMAKE_LIBS_EGL. By default QMAKE_LIBS_EGL = -lEGL And depending on hardware... it might be something like QMAKE_LIBS_EGL = -lEGL -lGLESv2 for instance. And this specific line... "-lEGL -lGLESv2" is only

Re: [yocto] error: code model kernel does not support PIC mode

> On Feb 3, 2016, at 5:24 PM, Sridhar Pitchai > wrote: > > Hi, > I trying to write a simple recipe which will be building some static > libraries. the makefile has the "-fPIC" enabled. when i try to compile it > using simple yocto recipe, i am getting this error.

Re: [yocto] error: code model kernel does not support PIC mode

Sure, i will get rid of it. But i get the same error without it as well. I added it to see if this can help get the compile through. but it didn't. What am i missing here. the MACHINE is "qemux84-64" Subject: Re: [yocto] error: code model kernel does not support PIC mode From:

Re: [yocto] error: code model kernel does not support PIC mode

talk to folks whoever is providing you that SDK > On Feb 3, 2016, at 5:37 PM, Sridhar Pitchai > wrote: > > Sure, i will get rid of it. But i get the same error without it as well. I > added it to see if this can help get the compile through. but it didn't. > >

[yocto] error: code model kernel does not support PIC mode

Hi,I trying to write a simple recipe which will be building some static libraries. the makefile has the "-fPIC" enabled. when i try to compile it using simple yocto recipe, i am getting this error. "|

Re: [yocto] error: code model kernel does not support PIC mode

SDK looks fine. i was able to compile with it with direct make on my local system. make -C /path/to/sdk/systems/linux/user/x86-generic_64-3_19 this works just fine. I am trying to make my image through yocto recipe and i am facing this issue. infact doing a make @

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On Wed, Feb 3, 2016 at 10:43 PM, wrote: > Hi Maciej, > > > I did "bitbake -r core-image-sato" and redirected the output to a file. From > that I found that IMAGE_FEATURES is assigned in image.bblass. A few of the > contents in the file were as follows:- > > #

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi Khem, Thanks for your quick response. That entry is already there in "/conf/local.conf " file as follows:- # We default to enabling the debugging tweaks. EXTRA_IMAGE_FEATURES = "debug-tweaks" In addition to the above, I have also added "tools-sdk" and "tools-debug" as follows in the same

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi Maciej, I did "bitbake -r core-image-sato" and redirected the output to a file. From that I found that IMAGE_FEATURES is assigned in image.bblass. A few of the contents in the file were as follows:- # IMAGE_FEATURES may contain any available package group IMAGE_FEATURES ?= ""

Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

On Wed, Feb 3, 2016 at 6:54 AM, GUEYTAT Julien wrote: > Setting properly the variable PACKAGECONFIG_GL to gles2 does NOT update > properly the variable QMAKE_LIBS_EGL. > By default QMAKE_LIBS_EGL = -lEGL > And depending on hardware... it might be something like

Re: [yocto] [meta-raspberrypi] errors when I "bitbake" an image formyrpi2 B+ board

Hi, Karim, I have tried "sudo apt-get install curl", then do the "bitbake". But there are stiill many errors. detailed build logs are as follows: "http://www.cnblogs.com/tianya-lemon/p/5179160.html; Thank you so much for your ideas. Jack Shanghai -- Original --

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On czw, 2016-02-04 at 07:31 +, shubham.kum...@wipro.com wrote: > Hi Khem, > > Thanks for your quick response. > > That entry is already there in "/conf/local.conf " file as follows:- > > # We default to enabling the debugging tweaks. > EXTRA_IMAGE_FEATURES = "debug-tweaks" > > In addition

Re: [yocto] [meta-qt5][meta-raspberrypi]: QMAKE_LIBS_EGL not properly set

Hi everyone, I understand that you are all rewriting the qtbase rule to include at least the modification to the QMAKE_LIBS_EGL variable. The question is: Could we make somehow some work in meta-qt5 or meta-raspberrypi to not have to overwrite the qtbase rule. For instance… meta-raspberrypi is

[yocto] [PATCH][yocto-autobuilder] nightly-checkuri: use a single bitbake thread

To reduce the chance of errors due to FTP servers refusing multiple connections at the same time reduce the number of bitbake threads to 1. Signed-off-by: Ross Burton --- buildset-config.controller/nightly-checkuri.conf | 2 +- 1 file changed, 1 insertion(+), 1

[yocto] libsnmp and others

Hi I have these missing dependencies when running a test executable on my Yocto image. It is a qemux86_64 core-image-kernel-dev image, built as “bitbake core-image-kernel-dev”. 0x0001 (NEEDED) Shared library: [libsnmp.so.30] 0x0001 (NEEDED)

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

> Dnia 3 luty 2016 o 15:55 shubham.kum...@wipro.com napisał(a): > > > In "final_build/conf/local.conf" , EXTRA_IMAGE_FEATURES = "debug-tweaks". > > So, yes "debug-tweaks" is present. > Try running bitbake -e and check the value of IMAGE_FEATURES (and where it gets assigned). You may also want

Re: [yocto] Which Toolchain is being used to build Yocto ?

On 3 February 2016 at 15:07, Mark T wrote: > I notice there is a meta/recipes-devtools - I assume this pulls in from > build/downloads - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain > comprised of these recipes get built by /usr/bin/gcc before being used to >

Re: [yocto] Which Toolchain is being used to build Yocto ?

Mark, >> I notice there is a meta/recipes-devtools - I assume this pulls in from >> build/downloads >> - so gcc-5.2.0.tar.bz2 for example. Does the tool-chain comprised of these >> recipes get >> built by /usr/bin/gcc before being used to compile Yocto? You can easily check it by moving

Re: [yocto] OpenEmbedded Metadata: Recipe update broken

Hi Andreas, On Wed, 03 Feb 2016 14:41:42 Andreas Müller wrote: > FAQ for layerindex says recipes are updated every 3 hours but I think > it does not work. E.g meta-oe geis/grail/frame are not mentioned but > were committed few days ago. I do know there's a problem, but I'm honestly not sure

Re: [yocto] Problem installing ath10k firmware

Finally was able to get it work - the error seemed to be a combination of things. We went with the modular build and ended up building the following as modules: CONFIG_ATH10K=m CONFIG_ATH10K_PCI=m CONFIG_ATH_CARDS=m CONFIG_ATH_COMMON=m Then we added only "kernel-module-ath10k-pci" to

Re: [yocto] Which Toolchain is being used to build Yocto ?

On 3 February 2016 at 18:15, Mark T wrote: > Thanks. That makes sense; all the cross compile tools are built using the > Host machines native toolchain on the host then the cross-toolchain used to > cross compile yocto for the target. > Correct. Ross --

Re: [yocto] Which Toolchain is being used to build Yocto ?

Thanks. That makes sense; all the cross compile tools are built using the Host machines native toolchain on the host then the cross-toolchain used to cross compile yocto for the target. On 3 February 2016 at 17:13, Burton, Ross wrote: > > On 3 February 2016 at 15:07,

Re: [yocto] Which Toolchain is being used to build Yocto ?

> On Feb 3, 2016, at 10:15 AM, Mark T wrote: > > Thanks. That makes sense; all the cross compile tools are built using the > Host machines native toolchain on the host then the cross-toolchain used to > cross compile yocto for the target. > > > > On 3 February 2016 at

Re: [yocto] Problem installing ath10k firmware

> On Feb 3, 2016, at 10:22 AM, Todd Efflam wrote: > > Finally was able to get it work - the error seemed to be a combination > of things. > > We went with the modular build and ended up building the following as modules: > CONFIG_ATH10K=m > CONFIG_ATH10K_PCI=m >

Re: [yocto] OpenEmbedded Metadata: Recipe update broken

On Wed, Feb 3, 2016 at 8:10 PM, Paul Eggleton wrote: > Hi Andreas, > > On Wed, 03 Feb 2016 14:41:42 Andreas Müller wrote: >> FAQ for layerindex says recipes are updated every 3 hours but I think >> it does not work. E.g meta-oe geis/grail/frame are not mentioned but