Khem Raj | 19 Apr 11:59 2014

[master/daisy][PATCH] libav: Add libsdl to DEPENDS only when x11 is enabled

When we have opengl in distro features but not x11 and try to
build libav then it calls out to build libsdl which inturn has depependency on libglu
and libglu fails to build

ld: error: cannot find -lGL
| collect2: error: ld returned 1 exit status
| make: *** [] Error 1
| ERROR: oe_runmake failed

since libglu wants glx enabled in mesa and glx in mesa is (righly) enabled only when x11
is in distro features.

This breaks the dependency chain leading to this problem

Signed-off-by: Khem Raj <raj.khem@...>
 meta/recipes-multimedia/libav/ |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-multimedia/libav/ b/meta/recipes-multimedia/libav/
index 5e675be..2152936 100644
--- a/meta/recipes-multimedia/libav/
+++ b/meta/recipes-multimedia/libav/
 <at>  <at>  -9,7 +9,7  <at>  <at>  PROVIDES = "ffmpeg"


-DEPENDS = "virtual/libsdl zlib libogg libvorbis libtheora yasm-native"
+DEPENDS = "zlib libogg libvorbis libtheora yasm-native"

(Continue reading)

Mike Looijmans | 19 Apr 11:08 2014

How to migrate from PRINC to PR_SERVER?

Attempting to move to the current OE-head now yields about a hundred 
messages like this:

WARNING: Use of PRINC 7 was detected in the recipe ...

The page tells what the PR 
server is.

However, it does not tell what to do with the recipes. Just removing 
PRINC from the recipes will break the upgrade path.

What are we supposed to do now?

Mike Looijmans

Joe Slater | 19 Apr 00:38 2014

[PATCH 1/1] apr: do not try to use sctp.h

If we let configure look for sctp.h it might find it
on the host, so suppress the search with two cached
config variables.

Signed-off-by: Joe Slater <jslater@...>
 meta/recipes-support/apr/ |    4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-support/apr/ b/meta/recipes-support/apr/
index d834170..c14f64b 100644
--- a/meta/recipes-support/apr/
+++ b/meta/recipes-support/apr/
 <at>  <at>  -24,6 +24,10  <at>  <at>  OE_BINCONFIG_EXTRA_MANGLE = " -e 's:location=source:location=installed:'"
 # Added to fix some issues with cmake. Refer to
 CACHED_CONFIGUREVARS += "apr_cv_mutex_recursive=yes"

+# Also suppress trying to use sctp.
+CACHED_CONFIGUREVARS += "ac_cv_header_netinet_sctp_h=no ac_cv_header_netinet_sctp_uio_h=no"
 do_configure_prepend() {
 	cd ${S}


Martin Jansa | 18 Apr 23:27 2014

[PATCH] gsettings-desktop-schemas: add missing dependency on intltool-native

* do_configure fails with:
  | NOTE: Executing intltoolize --copy --force --automake
/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/gsettings-desktop-schemas/3.10.1-r1/temp/run.do_configure.1111: 180:
   intltoolize: not found
  | WARNING: exit code 127 from a shell command.
  | ERROR: Function failed: do_configure (log file is located at
  NOTE: recipe gsettings-desktop-schemas-3.10.1-r1: task do_configure:

* introduced in:
  commit 1138976f7bdcd24ef57451a2c2ceffa43666610f
  Author: Alexandru Palalau <alexandrux.palalau@...>
  Date:   Tue Mar 11 13:27:46 2014 +0000

    gsettings-desktop-schemas: removed unneeded class inheritance

Signed-off-by: Martin Jansa <Martin.Jansa@...>
 meta/recipes-gnome/gnome/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-gnome/gnome/ b/meta/recipes-gnome/gnome/
index 7217c66..eb09d2f 100644
--- a/meta/recipes-gnome/gnome/
+++ b/meta/recipes-gnome/gnome/
 <at>  <at>  -6,7 +6,7  <at>  <at>  LICENSE = "LGPLv2.1"
 LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c"
 PR = "r1"
(Continue reading)

gary.robertson | 18 Apr 22:12 2014

[PATCH] rt-tests: bump version 0.87 => 0.89

From: "Gary S. Robertson" <gary.robertson@...>

cyclictest was updated to correct some problems with CPU affinity selection
and display of help and/or execution details.
These patches were accepted by the maintainer of the cyclictest utility.
The changes were reflected in an updated release of rt-tests - v0.89
The cyclictest changes were successfully tested on both an ARM v7 and x86_64
host environments.
The OE recipe was updated locally to incorporate the updated rt-tests release
and the resulting builds were verified for the same ARM v7 target
and for qemux86.
This patch set was then generated from the local commit for the recipe update
and is now submitted for your review and hopefully your approval.

Anders Roxell (1):
  rt-tests: bump version 0.87 => 0.89

 meta/recipes-rt/rt-tests/              |    7 ++-----
 .../{ =>}         |    0
 2 files changed, 2 insertions(+), 5 deletions(-)
 rename meta/recipes-rt/rt-tests/{ =>} (100%)



Martin Jansa | 18 Apr 22:01 2014

[PATCH] libnotify: add dbus-glib dependency

* | No package 'dbus-glib-1' found
  | configure:11865: error: Package requirements (gtk+-2.0 >= 2.18, glib-2.0 >= 2.6,
    dbus-1 >= 0.76, dbus-glib-1 >= 0.76 gmodule-2.0) were not met:

* introduced in:
  commit 5c1eeb5d16566521e45947b07fdcd9f552fec45b
  Author: Alexandru Palalau <alexandrux.palalau@...>
  Date:   Thu Feb 27 12:05:41 2014 +0200

      libnotify: don't use gnome.bbclass

  because gnome.bbclass was adding gconf->dbus-glib dependency

* it was also causing other recipes to fail when they were depending
  on libnotify which has dbus-glib in pkg-config and dbus-glib was
  missing, e.g. firefox:
  | checking for libnotify >= 0.4... Package dbus-glib-1 was not found
  in the pkg-config search path. Perhaps you should add the directory
  containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment
  variable Package 'dbus-glib-1', required by 'libnotify', not found
  | configure: error: Library requirements (libnotify >= 0.4) not met;
  consider adjusting the PKG_CONFIG_PATH environment variable if your
  libraries are in a nonstandard prefix so pkg-config can find them.

Signed-off-by: Martin Jansa <Martin.Jansa@...>
 meta/recipes-gnome/libnotify/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-gnome/libnotify/ b/meta/recipes-gnome/libnotify/
(Continue reading)

Martin Jansa | 18 Apr 20:36 2014

State of bitbake world, test-dependencies 2014-04-18

On Thu, Apr 03, 2014 at 03:06:09PM +0200, Martin Jansa wrote:
> I've just started this long test-dependencies build so jenkins will be busy
> for next 14 days or so, but I'll send complete qa.log in advance as soon as
> it finishes building world from scratch.

The build finally finished today, here are results:

Complete logs:

Interesting parts, (mostly) missing dependencies:

I'll take care of failing meta-efl, meta-shr recipes and 
| checking for libnotify >= 0.4... Package dbus-glib-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-glib-1.pc' to the PKG_CONFIG_PATH environment
variable Package 'dbus-glib-1', required by 'libnotify', not found
| configure: error: Library requirements (libnotify >= 0.4) not met; consider adjusting the
PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can
find them.

And more importantly floating dependencies, reply here
when you start working on some of these.

Found differences: 
ccid/ccid/latest lost dependency on  flex
console-tools/console-tools/latest lost dependency on  flex
consolekit/consolekit/latest lost dependency on  polkit
daq/daq/latest lost dependency on  libdnet libmnl libnetfilter-queue libnfnetlink
(Continue reading)

JAVA build problem with latest poky + meta-fsl-ppc + meta-java

Hi all, 

When I try to use latest poky + meta-fsl-ppc + meta-java to build java-test-image for e6500 target, the
compilesteptwo step of openjdk-6-jre failed as following:
| GENERATING /home/jenkins/poky/build_b4860qds_release/tmp/work/ppce6500-fsl-linux/openjdk-6-jre/6b27-1.12.5-r22.2/icedtea6-1.12.5/build/
| Unable to find CPU definition

According to the investigation, the compilesteptwo step of openjdk-6-jre launches qemu for e6500
target, seems like the qemu source provided by poky doesn't support e6500 emulation, so above "Unable to
find CPU definition" error appears. Java can be built correctly before below two commits are merged.

IMHO, following are three possible ways to solve the issue 
1. Reverse above two commits until qemu supports ppce6500 targets 
2. Use the cpu parameter to something that QEMU supports and is similar to e6500 (e,g, e500mc) until
ppce6500 is supported by qemu 
3. Use FSL qemu source for qemu-native build when machine is ppce6500 targets, we are verifying this way. 

Any comment on the problem, and any better solution for this issue?

Best Regards,


Cristiana Voicu | 18 Apr 08:40 2014

[PATCH 0/7] PUs

The packages has been succesfully compiled for all major architectures.
Tested locally on a core-image-sato image.

The following changes since commit 863cc7483f5ee43189537940de8ee5c0964d24cc:

  poky.conf: Post release version bump (2014-04-10 18:03:07 +0100)

are available in the git repository at:

  git:// cvoicu/work

Cristiana Voicu (7):
  pango: upgrade to 1.36.3
  curl: upgrade to 7.36.0
  atk: upgrade to 2.12.0
  at-spi2-atk: upgrade to 2.12.0
  at-spi2-core: upgrade to 2.12.0
  mtd-utils: upgrade to 1.5.1+gitAUTOINC+12158de
  kmod: upgrade to v17 via git

 meta/recipes-devtools/mtd/         |    4 ++--
 .../pango/{ =>}     |    4 ++--
 meta/recipes-kernel/kmod/                  |    4 ++--
 ...alling-bswap_-instead-of-htobe-and-be-toh.patch |    4 ++-- =>} |    4 ++-- =>} |    4 ++--
 .../atk/{ =>}           |    4 ++--
 .../curl/{ =>}        |    4 ++--
 8 files changed, 16 insertions(+), 16 deletions(-)
(Continue reading)

Denys Dmytriyenko | 17 Apr 21:05 2014

[PATCH] u-boot: fix beaglebone boot issue with large kernel images

From: Denys Dmytriyenko <denys@...>

Fix beaglebone boot issue with large kernel images overwriting Device Tree.
See very detailed comments inside the patch.

The original patch is being reviewed upstream and is targeting mainline U-boot
version 2014.07. This is the adaptation of the patch for 2013.07 version we use

Signed-off-by: Denys Dmytriyenko <denys@...>
 ...h-Add-use-DEFAULT_LINUX_BOOT_ENV-environm.patch | 74 ++++++++++++++++++++++
 meta/recipes-bsp/u-boot/          |  4 +-
 2 files changed, 77 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-bsp/u-boot/files/0001-am335x_evm.h-Add-use-DEFAULT_LINUX_BOOT_ENV-environm.patch

diff --git
a/meta/recipes-bsp/u-boot/files/0001-am335x_evm.h-Add-use-DEFAULT_LINUX_BOOT_ENV-environm.patch b/meta/recipes-bsp/u-boot/files/0001-am335x_evm.h-Add-use-DEFAULT_LINUX_BOOT_ENV-environm.patch
new file mode 100644
index 0000000..77e35bb
--- /dev/null
+++ b/meta/recipes-bsp/u-boot/files/0001-am335x_evm.h-Add-use-DEFAULT_LINUX_BOOT_ENV-environm.patch
 <at>  <at>  -0,0 +1,74  <at>  <at> 
+From 5701384cea4a829b772bf7a96a74825b58c22385 Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko <denys@...>
+Date: Thu, 17 Apr 2014 12:25:40 -0400
+Subject: [PATCH] am335x_evm.h: Add, use DEFAULT_LINUX_BOOT_ENV environment
+ string
+Modified version of the patch currently being reviewed for mainline:
(Continue reading)

Gabriel Barbu | 17 Apr 13:27 2014

How to add a distro feature from an image recipe?



Is there a specific mechanism to add a distro feature from an image recipe?

DISTRO_FEATURES_append does not seem to work from an image-*.bb or from a packagegroup-*.bb.


Or, if not, what would be the best way to achieve this?

The need is that I have a number of images and only want to add a certain distro feature (ptest) to just one or two of them (some test images).







Openembedded-core mailing list