I've been building a kernel with an initramfs, by using INITRAMFS_IMAGE to specify a recipe that generates an image as a .cpio.gz archive. I've been having issues creating /dev/console (or any other

Hello, Here is the Full Pass test report for 1.7_M4.rc4 build. As issue summary, the previous ADT-installer fails are fixed, also for Build Appliance. No new Medium+/High bugs are found during this

Signed-off-by: Laurentiu Palcu <lpalcu@...> --- ...bappend => gstreamer1.0-plugins-bad_%.bbappend} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename

I have started to integrate clang into oe Which probably is quitquite similar to this effortwise. Its very prelimpreliminary. Check my github repo. I should add it to layer index

Am 18.10.2014 um 23:33 schrieb Tyler Hall: Tested and this works, when added to my pyotherside recipe. It is indeed not very intuitive, but writing recipes is anyway something mysterical (e.g. I need

A release candidate build for yocto-1.7.rc5 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc5 Please begin QA on this build as soon as possible. Build hash

** Resent to [yocto] as apparently I wasn't subscribed ** That patch changed python3-config to use distutils.sysconfig to get paths. That was already patched by OE to use environment variables

That patch changed python3-config to use distutils.sysconfig to get paths. That was already patched by OE to use environment variables to substitute the correct path, but it seems there's nothing

+ Tyler Hall My guess is that your app is receiving the include path with sysroot prefix now from sysconfig and then adds another sysroot prefix so it points to non-existent directory, check the

There is very different version of qtmultimedia and gst-1.0 support recipes-qt/qt5/qtmultimedia-git/0001-Initial-porting-effort-to-GStreamer-1.0.patch | 2369

Am 18.10.2014 um 11:10 schrieb Martin Jansa: THANKS A LOT!!! This is it. This patch broke the recipe. I reverted it and it runs through now without error. THANKS A LOT!!! What shall we do now? Is

Am 18.10.2014 um 11:10 schrieb Martin Jansa: Hmm, master. Didn't know there was a daisy branch. Did a diff between the two branches now and do not see any difference though which could solve the above

Are you using meta-qt5/daisy or meta-qt5/master? Please report it to meta-fsl-arm maintainer, I'm not using that layer, but I think they should either provide separate .bbappends for _5.*.bb

Am 18.10.2014 um 10:44 schrieb Martin Jansa: Thanks, they look very promising. Currently I have completely set up my yocto environment from scratch again. It's curently compiling. There was another

Have you tried to revert these 2

I don't see any chance to get this running. The whole environment seems to be missing, such as BUILD_SYS, HOST_SYS, STAGING_LIB_DIR and other. I will now completely resetup yocto from scratch, hoping

Thanks - I was wondering if layers had something to do with it. I can work with that - the layer is being used to up-rev various recipes for bug fixes (e.g. bash) and to add later versions of things

That's by (IMHO wrong) design:https://bugzilla.yoctoproject.org/show_bug.cgi?id=2964 Instead of setting P_V 2.40 only for that single project which needs that newer libsoup, you need to set P_V to

I've got a layer that includes a recipe for libsoup at version 2.40.3 which sets DEFAULT_PREFERENCE = "-1". However, this version gets used when I build rather than the 2.38.? version in poky/meta

Ah - I meant to say "with a syntax error" ! Thanks, I'll have a look at that. In the mean time I've added CFLAGS+=" -std=c++x0" to get me going. -- Chris