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

On Sun, Apr 23, 2017 at 3:04 PM, Burton, Ross wrote: > > On 16 April 2017 at 16:50, Khem Raj wrote: >> >> I have put together recipes for upcoming gcc-7 major release as well >> as glibc 2.26 release, which we would target for next release ( 2.4 ) > > >

[yocto] [Recipe reporting system] Upgradable recipe name list

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version

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

On Sun, Apr 23, 2017 at 5:31 PM, Bruce Ashfield wrote: > > > On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield > wrote: >> >> >> >> On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross >> wrote: >>> >>> On 16 April 2017 at 16:50,

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

On Sun, Apr 23, 2017 at 8:30 PM, Bruce Ashfield wrote: > > > On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross > wrote: > >> On 16 April 2017 at 16:50, Khem Raj wrote: >> >> > I have put together recipes for upcoming gcc-7 major

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

On Sun, Apr 23, 2017 at 6:04 PM, Burton, Ross wrote: > On 16 April 2017 at 16:50, Khem Raj wrote: > > > I have put together recipes for upcoming gcc-7 major release as well > > as glibc 2.26 release, which we would target for next release ( 2.4 ) > > >

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

On 16 April 2017 at 16:50, Khem Raj wrote: > I have put together recipes for upcoming gcc-7 major release as well > as glibc 2.26 release, which we would target for next release ( 2.4 ) > I threw these at the autobuilder and the errors are starting to appear:

[yocto] [meta-raspberrypi][morty][PATCH 2/2] xserver-xorg: add xf86-input-libinput to XSERVER_RRECOMMENDS

oe-core's commit is not merged in morty branch. | xorg-xserver recommends xf86-input-libinput since oe-core's commit | | | commit 2d005faff6341a81a2afae28860101ba9db51ae8 | | Author: Jussi Kukkonen | | Date: Wed Oct 26 11:37:38 2016 +0300 | | | |conf:

[yocto] [meta-raspberrypi][morty][PATCH 1/2] xserver-xf86-config: remove evdev configuration

From: Andreas Müller xorg-xserver recommends xf86-input-libinput since oe-core's commit | commit 2d005faff6341a81a2afae28860101ba9db51ae8 | Author: Jussi Kukkonen | Date: Wed Oct 26 11:37:38 2016 +0300 | |conf: Use

Re: [yocto] Problem with mesa and nvidia

On Sun, Apr 23, 2017 at 7:35 AM, Alvaro Garcia wrote: > mesa-driver-i915 if you are building for x86 based machines and including conf/machine/include/x86-base.inc in your machine config then you are getting it. You need to define XSERVER variable that fits your machine. you

[yocto] Problem with mesa and nvidia

Hi, my goal is build the core-image-x11 using the nvidia drivers instead of mesa. My recipe provides the following: PROVIDES = "virtual/libgl virtual/libgles1 virtual/libgles2 virtual/egl" and in my local.conf: PREFERRED_PROVIDER_virtual/libgl = "nvidia-proprietary"

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

I forgot to precise, compiling, doesn't work on the host system, it cannot compile a simple .c file, not finding "stdio.h". On Sun, 23 Apr 2017 at 10:40 David Bensoussan wrote: > I managed to track down how to create the SDK. Sorry for the long answer > but it might

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

I managed to track down how to create the SDK. Sorry for the long answer but it might help people googling it. DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC} ${POKY_DEFAULT_DISTRO_FEATURES}" in *meta-poky/conf/distro/poky.conf* DISTRO_FEATURES_LIBC is defined as