Re: [OE-core] meta-toolchain-sdk LDFLAGS fails for ARMv7 (beagleboard)

2014-04-07 Thread Ulf Samuelsson
Clearing LDFLAGS allows U-Boot to build.

Now trying to build a busybox with static linking, but the SDK only provides 
the lib.so 
and not the lib.a static libraries. 

Any easy way to make it include both?

Best Regards
Ulf Samuelsson

7 apr 2014 kl. 22:17 skrev Denys Dmytriyenko :

> On Mon, Apr 07, 2014 at 10:02:40PM +0200, Ulf Samuelsson wrote:
>> Trying to build an SDK for the Beaglebone
>> 
>> $ git clone git://git.yoctoproject.org/poky
>> $ cd poky
>> $ git checkout -b dora origin/dora
>> 
>> $ . oe-init-build-env
>> 
>> MACHINE is set to "beagleboard" in local.conf
> 
> It's not critical to your case, but in general beagleboard != beaglebone...
> 
> And cutting to the chase - U-boot recipe in OE clears CFLAGS, LDFLAGS and 
> CPPFLAGS before building it...
> 
> 
>> $ ./environment-angstrom-v2013.06
>> 
>> $ bitbake meta-toolchain-sdk
>> 
>> SDK is generated, and installed in /opt/poky/1.5.1 (default)
>> 
>> The toolchain environment file is "sourced"
>> 
>> Then I try to build U-Boot-13.10 (with a minor patch)
>> 
>> 
>> $ make am335x_boneblack_config
>> 
>> $ make
>> 
>> After compiling a number of file, the linking of a library fails:
>> 
>> arm-poky-linux-gnueabi-ld.bfd -Wl,-O1 -Wl,--hash-style=gnu
>> -Wl,--as-needed   -r -o libcommon.o  cmd_bdinfo.o cmd_boot.o
>> cmd_bootm.o cmd_console.o cmd_dfu.o cmd_disk.o cmd_echo.o
>> cmd_eeprom.o cmd_exit.o cmd_ext2.o cmd_ext4.o cmd_fat.o cmd_fdt.o
>> cmd_fs.o cmd_gpio.o cmd_help.o cmd_i2c.o cmd_itest.o cmd_load.o
>> cmd_mem.o cmd_misc.o cmd_mmc.o cmd_net.o cmd_nvedit.o cmd_pcmcia.o
>> cmd_sf.o cmd_source.o cmd_spi.o cmd_spl.o cmd_test.o cmd_usb.o
>> cmd_version.o cmd_ximg.o command.o console.o dlmalloc.o env_attr.o
>> env_callback.o env_common.o env_flags.o env_mmc.o exports.o
>> fdt_support.o flash.o hash.o hush.o image-fdt.o image.o main.o
>> memsize.o miiphyutil.o s_record.o splash.o stdio.o usb.o usb_hub.o
>> usb_storage.o xyzModem.o
>> arm-poky-linux-gnueabi-ld.bfd: unrecognized option '-Wl,-O1'
>> arm-poky-linux-gnueabi-ld.bfd: use the --help option for usage information
>> make[1]: *** [libcommon.o] Fel 1
>> make[1]: Lämnar katalogen
>> "/home/ulf/felabs/sysdev/bootloader/u-boot-2013.10/common"
>> make: *** [common/libcommon.o] Fel 2
>> 
>> ---
>> The environment looks like:
>> ---
>> export 
>> PATH=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi:$PATH
>> export 
>> PKG_CONFIG_SYSROOT_DIR=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi
>> export 
>> PKG_CONFIG_PATH=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/lib/pkgconfig
>> export 
>> CONFIG_SITE=/opt/poky/1.5.1/site-config-armv7a-vfp-neon-poky-linux-gnueabi
>> export CC="arm-poky-linux-gnueabi-gcc  -march=armv7-a
>> -mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
>> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
>> export CXX="arm-poky-linux-gnueabi-g++  -march=armv7-a
>> -mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
>> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
>> export CPP="arm-poky-linux-gnueabi-gcc -E  -march=armv7-a
>> -mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
>> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
>> export AS="arm-poky-linux-gnueabi-as "
>> export LD="arm-poky-linux-gnueabi-ld 
>> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
>> export GDB=arm-poky-linux-gnueabi-gdb
>> export STRIP=arm-poky-linux-gnueabi-strip
>> export RANLIB=arm-poky-linux-gnueabi-ranlib
>> export OBJCOPY=arm-poky-linux-gnueabi-objcopy
>> export OBJDUMP=arm-poky-linux-gnueabi-objdump
>> export AR=arm-poky-linux-gnueabi-ar
>> export NM=arm-poky-linux-gnueabi-nm
>> export M4=m4
>> export TARGET_PREFIX=arm-poky-linux-gnueabi-
>> export CONFIGURE_FLAGS="--target=arm-poky-linux-gnueabi
>> --host=arm-poky-linux-gnueabi --build=x86_64-linux 
>> --with-libtool-sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
>> export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types"
>> export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types -fpermissive"
>> export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
>> export CPPFLAGS=""
>> export OECORE_NATIVE_SYSROOT="/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux"
>> export 
>> OECORE_TARGET_SYSROOT="/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
>> export OECORE_ACLOCAL_OPTS="-I
>> /opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/share/aclocal"
>> export OECORE_DISTRO_VERSION="1.5.1"
>> export OECORE_SDK_VERSION="1.5.1"
>> export PYTHONHOME=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr
>> export ARCH=arm
>> export CROSS_COMPILE=arm-poky-linux-gnueabi-
>> ---

[OE-core] [PATCH 1/1] libx11: fix invalid preprocessing directive errors

2014-04-07 Thread Chong Lu
Backport the patch to fix invalid preprocessing directive errors.

nls: always use XCOMM instead of # for comments in Compose.pre files

[YOCTO #6116]

Signed-off-by: Chong Lu 
---
 ...use-XCOMM-instead-of-for-comments-in-Comp.patch | 101 +
 meta/recipes-graphics/xorg-lib/libx11_1.6.2.bb |   1 +
 2 files changed, 102 insertions(+)
 create mode 100644 
meta/recipes-graphics/xorg-lib/libx11/nls-always-use-XCOMM-instead-of-for-comments-in-Comp.patch

diff --git 
a/meta/recipes-graphics/xorg-lib/libx11/nls-always-use-XCOMM-instead-of-for-comments-in-Comp.patch
 
b/meta/recipes-graphics/xorg-lib/libx11/nls-always-use-XCOMM-instead-of-for-comments-in-Comp.patch
new file mode 100644
index 000..b7f5356
--- /dev/null
+++ 
b/meta/recipes-graphics/xorg-lib/libx11/nls-always-use-XCOMM-instead-of-for-comments-in-Comp.patch
@@ -0,0 +1,101 @@
+Upstream-Status: Backport
+
+Signed-off-by: Chong Lu 
+
+From b64bee2ddb7b96f00713a8b8435f11ad9ac1c9e0 Mon Sep 17 00:00:00 2001
+From: Ran Benita 
+Date: Sun, 16 Feb 2014 15:24:58 +0200
+Subject: [PATCH] nls: always use XCOMM instead of # for comments in
+ Compose.pre files
+
+Lines starting with # are considered as preprocessor directives in the
+.pre files.
+
+Fixes warnings like:
+:3:0: error: invalid preprocessing directive #Khmer
+
+Signed-off-by: Ran Benita 
+Signed-off-by: James Cloos 
+---
+ nls/km_KH.UTF-8/Compose.pre |2 +-
+ nls/sr_CS.UTF-8/Compose.pre |   32 
+ 2 files changed, 17 insertions(+), 17 deletions(-)
+
+diff --git a/nls/km_KH.UTF-8/Compose.pre b/nls/km_KH.UTF-8/Compose.pre
+index 77651d0..dc89119 100644
+--- a/nls/km_KH.UTF-8/Compose.pre
 b/nls/km_KH.UTF-8/Compose.pre
+@@ -1,6 +1,6 @@
+ include "X11_LOCALEDATADIR/en_US.UTF-8/Compose"
+ 
+-# Khmer digraphs
++XCOMM Khmer digraphs
+:   "ាំ"
+:   "ោះ"
+:   "េះ"
+diff --git a/nls/sr_CS.UTF-8/Compose.pre b/nls/sr_CS.UTF-8/Compose.pre
+index 119e23e..b2397f7 100644
+--- a/nls/sr_CS.UTF-8/Compose.pre
 b/nls/sr_CS.UTF-8/Compose.pre
+@@ -1,17 +1,17 @@
+ include "X11_LOCALEDATADIR/en_US.UTF-8/Compose"
+ 
+-# Serbian accented Cyrillic
+-# а А - U+0430, U+0410 Cyrillic_a, Cyrillic_A
+-# е Е - U+0435, U+0415 Cyrillic_e, Cyrillic_E
+-# о О - U+043E, U+041E Cyrillic_o, Cyrillic_O
+-# у У - U+0443, U+0423 Cyrillic_u, Cyrillic_U
+-# и И - U+0438, U+0418 Cyrillic_i, Cyrillic_I
+-#
+-# ̀ - U+0300 , ,  
+-# ́ - U+0301   ,  ,  , 

+-# ̂ - U+0302 ,  
+-# ̏ - U+030F  , 
+-# ̀ - kratkouzlazni, U+0300 , ,  

++XCOMM Serbian accented Cyrillic
++XCOMM а А - U+0430, U+0410 Cyrillic_a, Cyrillic_A
++XCOMM е Е - U+0435, U+0415 Cyrillic_e, Cyrillic_E
++XCOMM о О - U+043E, U+041E Cyrillic_o, Cyrillic_O
++XCOMM у У - U+0443, U+0423 Cyrillic_u, Cyrillic_U
++XCOMM и И - U+0438, U+0418 Cyrillic_i, Cyrillic_I
++XCOMM
++XCOMM ̀ - U+0300 , ,  
++XCOMM ́ - U+0301   ,  ,  
, 
++XCOMM ̂ - U+0302 ,  
++XCOMM ̏ - U+030F  , 
++XCOMM ̀ - kratkouzlazni, U+0300 , ,  

+   : "а̀"
+  : "а̀"
+ : "а̀"
+@@ -42,7 +42,7 @@ include "X11_LOCALEDATADIR/en_US.UTF-8/Compose"
+   : "У̀"
+  : "У̀"
+ : "У̀"
+-# ́ - dugouzlazni, U+0301   ,  ,  
, 
++XCOMM ́ - dugouzlazni, U+0301   ,  , 
 , 
+: "а́"
+   : "а́"
+  : "а́"
+@@ -83,7 +83,7 @@ include "X11_LOCALEDATADIR/en_US.UTF-8/Compose"
+   : "У́"
+  : "У́"
+ : "У́"
+-# ̂ - dugosilazni, U+0302 ,  
++XCOMM ̂ - dugosilazni, U+0302 ,  
+: "а̂"
+ : "а̂"
+: "А̂"
+@@ -104,8 +104,8 @@ include "X11_LOCALEDATADIR/en_US.UTF-8/Compose"
+ : "у̂"
+: "У̂"
+ : "У̂"
+-# ̏ - kratkosilazni, U+030F  , 
+-# there's no appropriate dead_doublegrave, so we use these two dead keys
++XCOMM ̏ - kratkosilazni, U+030F  , 
++XCOMM there's no appropriate dead_doublegrave, so we use these two dead keys
+  : "а̏"
+: "а̏"
+  : "А̏"
+-- 
+1.7.9.5
+
diff --git a/meta/recipes-graphics/xorg-lib/libx11_1.6.2.bb 
b/meta/recipes-graphics/xorg-lib/libx11_1.6.2.bb
index 2377d61..700bc36 100644
--- a/meta/recipes-graphics/xorg-lib/libx11_1.6.2.bb
+++ b/meta/recipes-graphics/xorg-lib/libx11_1.6.2.bb
@@ -4,6 +4,7 @@ inherit gettext
 BBCLASSEXTEND = "native nativesdk"
 
 SRC_URI += "file://disable_tests.patch \
+file://nls-always-use-XCOMM-instead-of-for-comments-in-Comp.patch \
"
 
 SRC_URI[md5sum] = "c35d6ad95b06635a524579e88622fdb5"
-- 
1.8.1.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 0/1] libx11: fix invalid preprocessing directive errors

2014-04-07 Thread Chong Lu
The following changes since commit bb66113bde5361b869dce2bdaece5b938f077ea8:

  bitbake: fetch2: Fix bug in file checksum generation (2014-04-06 11:31:26 
+0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib chonglu/libx11
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/libx11

Chong Lu (1):
  libx11: fix invalid preprocessing directive errors

 ...use-XCOMM-instead-of-for-comments-in-Comp.patch | 101 +
 meta/recipes-graphics/xorg-lib/libx11_1.6.2.bb |   1 +
 2 files changed, 102 insertions(+)
 create mode 100644 
meta/recipes-graphics/xorg-lib/libx11/nls-always-use-XCOMM-instead-of-for-comments-in-Comp.patch

-- 
1.8.1.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH V4 1/1] dbus: fix a hard dependency about dbus-ptest

2014-04-07 Thread Chong Lu
If image contains dbus and ptest is in DISTRO_FEATURES, dbus-ptest package
is installed, regardless of whether ptest-pkgs is in IMAGE_FEATURES. This
issue will increase size for most small images.
This patch fixes this problem.

[YOCTO #5702]

Signed-off-by: Chong Lu 
---
 meta/recipes-core/dbus/{dbus-ptest_1.6.18.bb => dbus-test_1.6.18.bb} | 0
 meta/recipes-core/dbus/dbus.inc  | 4 +++-
 2 files changed, 3 insertions(+), 1 deletion(-)
 rename meta/recipes-core/dbus/{dbus-ptest_1.6.18.bb => dbus-test_1.6.18.bb} 
(100%)

diff --git a/meta/recipes-core/dbus/dbus-ptest_1.6.18.bb 
b/meta/recipes-core/dbus/dbus-test_1.6.18.bb
similarity index 100%
rename from meta/recipes-core/dbus/dbus-ptest_1.6.18.bb
rename to meta/recipes-core/dbus/dbus-test_1.6.18.bb
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index 5727ae7..9a9a00a 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++ b/meta/recipes-core/dbus/dbus.inc
@@ -6,9 +6,11 @@ LICENSE = "AFL-2 | GPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
 
file://dbus/dbus.h;beginline=6;endline=20;md5=7755c9d7abccd5dbd25a6a974538bb3c"
 DEPENDS = "expat virtual/libintl"
-RDEPENDS_dbus = "${@base_contains('DISTRO_FEATURES', 'ptest', 
'dbus-ptest-ptest', '', d)}"
 RDEPENDS_dbus_class-native = ""
 RDEPENDS_dbus_class-nativesdk = ""
+PACKAGES += "${@base_contains('DISTRO_FEATURES', 'ptest', 'dbus-ptest', '', 
d)}"
+ALLOW_EMPTY_dbus-ptest = "1"
+RDEPENDS_dbus-ptest_class-target = "dbus-test-ptest"
 
 SRC_URI = "http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
file://tmpdir.patch \
-- 
1.8.1.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH V4 0/1] dbus: fix a hard dependency about dbus-ptest

2014-04-07 Thread Chong Lu
Changes since V3:

Add class-target suffix to RDEPENDS_dbus-ptest.

The following changes since commit bb66113bde5361b869dce2bdaece5b938f077ea8:

  bitbake: fetch2: Fix bug in file checksum generation (2014-04-06 11:31:26 
+0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib chonglu/dbus
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/dbus

Chong Lu (1):
  dbus: fix a hard dependency about dbus-ptest

 meta/recipes-core/dbus/{dbus-ptest_1.6.18.bb => dbus-test_1.6.18.bb} | 0
 meta/recipes-core/dbus/dbus.inc  | 4 +++-
 2 files changed, 3 insertions(+), 1 deletion(-)
 rename meta/recipes-core/dbus/{dbus-ptest_1.6.18.bb => dbus-test_1.6.18.bb} 
(100%)

-- 
1.8.1.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 3/3] binconfig.bbclass: fix multilib file conflicts

2014-04-07 Thread Ming Liu

On 04/07/2014 07:36 PM, Richard Purdie wrote:

On Mon, 2014-04-07 at 19:27 +0800, Ming Liu wrote:

In most cases binconfig files conflict among multilib packages, to avoid
that, use update-alternatives link *-config from real path with a
PACKAGE_ARCH suffix.

Signed-off-by: Ming Liu 
---
  meta/classes/binconfig.bbclass | 65 --
  1 file changed, 56 insertions(+), 9 deletions(-)

This isn't going in, its complex and supports a minority use case.
binconfig should be dying out, not being extended and shored up like
this.

I'd also add this patch is buggy, its pure luck that update-alternatives
is available at rootfs generation time since its not in a visible
dependency.

So going forward I'd like to see patches which simply delete binconfig
scripts. Where there isn't a .pc alternative we should be adding them
and pushing them upstream.
Did you mean we'd better remove all *-config scripts, insteaded by 
providing .pc files, and send the changes to all upstreams providing and 
using *-config? That seems a huge work and we need co-operate with a lot 
of projects.


//Ming Liu


Cheers,

Richard







--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 1/3] e2fsprogs: fix multilib header conflict - ext2_types.h

2014-04-07 Thread Ming Liu

On 04/08/2014 03:50 AM, Khem Raj wrote:



On Apr 7, 2014 1:28 AM, "Ming Liu" > wrote:

>
> ext2_types.h conflicts between 32-bit and 64-bit versions.
>

can you explain the conflicts
may be they can be addressed

Yes, of course, see the following diff output of 64bits and 32bits 
ext2_types.h :

diff -urpN /tmp/64bits/ext2_types.h /tmp/32bits/ext2_types.h
--- /tmp/64bits/ext2_types.h
+++ /tmp/32bits/ext2_types.h
@@ -63,7 +63,7 @@ typedef __U32_TYPEDEF __u32;
 #if (4 == 4)
 typedefunsigned int__u32;
 #else
-#if (8 == 4)
+#if (4 == 4)
 typedefunsigned long__u32;
 #else
 #if (2 == 4)
@@ -81,7 +81,7 @@ typedef __S32_TYPEDEF __s32;
 #if (4 == 4)
 typedefint__s32;
 #else
-#if (8 == 4)
+#if (4 == 4)
 typedeflong__s32;
 #else
 #if (2 == 4)
@@ -102,7 +102,7 @@ typedef unsigned int__u64;
 #if (8 == 8)
 typedef unsigned long long__u64;
 #else
-#if (8 == 8)
+#if (4 == 8)
 typedef unsigned long__u64;
 #endif /* SIZEOF_LONG_LONG == 8 */
 #endif /* SIZEOF_LONG == 8 */
@@ -122,7 +122,7 @@ typedef __signed__ long long__s64;
 typedef signed long long__s64;
 #endif /* __GNUC__ */
 #else
-#if (8 == 8)
+#if (4 == 8)
 typedef long__s64;
 #endif /* SIZEOF_LONG_LONG == 8 */
 #endif /* SIZEOF_LONG == 8 */

ext2_types.h conflicts between 32-bit and 64-bit versions.

//Ming Liu


> Signed-off-by: Ming Liu >

> ---
>  meta/recipes-devtools/e2fsprogs/e2fsprogs.inc   | 3 +--
>  meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb 
 | 2 ++

>  2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc

> index a34df37..99447c1 100644
> --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
> @@ -22,5 +22,4 @@ DEPENDS = "util-linux"
>  SRC_URI = "${SOURCEFORGE_MIRROR}/e2fsprogs/e2fsprogs-${PV}.tar.gz \
> file://mkdir.patch"
>
> -inherit autotools gettext pkgconfig
> -
> +inherit autotools gettext pkgconfig multilib_header
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb 
 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb 


> index 3a5d6ee..2bdd724 100644
> --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb 

> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb 


> @@ -52,6 +52,8 @@ do_install () {
> mv ${D}${base_libdir}/e2initrd_helper ${D}${libdir}
> mv ${D}${base_libdir}/pkgconfig ${D}${libdir}
> fi
> +
> +   oe_multilib_header ext2fs/ext2_types.h
>  }
>
>  RDEPENDS_e2fsprogs = "e2fsprogs-badblocks"
> --
> 1.8.4.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org 


> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 1/1] kernelshark/trace-cmd: fix syntax error of shell

2014-04-07 Thread Chong Lu


On 04/04/2014 06:41 PM, Richard Purdie wrote:

On Fri, 2014-04-04 at 16:33 +0800, Chong Lu wrote:

Delete "<<<" syntax of bash in Makefile, else we would get following error:

 Syntax error: redirection unexpected

[YOCTO #6112]

Signed-off-by: Chong Lu 
---
  meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb   |  3 ++-
  .../kernelshark-fix-syntax-error-of-shell.patch| 30 ++
  .../trace-cmd-fix-syntax-error-of-shell.patch  | 30 ++
  meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb |  1 +
  4 files changed, 63 insertions(+), 1 deletion(-)
  create mode 100644 
meta/recipes-kernel/trace-cmd/trace-cmd/kernelshark-fix-syntax-error-of-shell.patch
  create mode 100644 
meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-fix-syntax-error-of-shell.patch

diff --git a/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb 
b/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
index 9268a50..d61097d 100644
--- a/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
+++ b/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
@@ -15,7 +15,8 @@ inherit pkgconfig pythonnative
  SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git \
 file://addldflags.patch \
 file://make-docs-optional.patch \
-   file://blktrace-api-compatibility.patch"
+   file://blktrace-api-compatibility.patch \
+   file://kernelshark-fix-syntax-error-of-shell.patch"
  S = "${WORKDIR}/git"
  
  EXTRA_OEMAKE = "'CC=${CC}' 'AR=${AR}' 'prefix=${prefix}' gui"

diff --git 
a/meta/recipes-kernel/trace-cmd/trace-cmd/kernelshark-fix-syntax-error-of-shell.patch
 
b/meta/recipes-kernel/trace-cmd/trace-cmd/kernelshark-fix-syntax-error-of-shell.patch
new file mode 100644
index 000..994a9fa
--- /dev/null
+++ 
b/meta/recipes-kernel/trace-cmd/trace-cmd/kernelshark-fix-syntax-error-of-shell.patch
@@ -0,0 +1,30 @@
+kernelshark: fix syntax error of shell
+
+Delete "<<<" syntax of bash in Makefile, else we would get following error:
+
+   Syntax error: redirection unexpected
+
+Upstream-Status: Inappropriate [embedded specific]

How is this embedded specific?

Cheers,

Richard

This issue only produced in yocto.
It is not problem for kernelshark and trace-cmd itself.
So I think this is embedded specific.

Best Regards
Chong

+Signed-off-by: Chong Lu 
+---
+ Makefile |3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index c1fa906..be84415 100644
+--- a/Makefile
 b/Makefile
+@@ -89,8 +89,7 @@ endif
+
+ # $(call test-build, snippet, ret) -> ret if snippet compiles
+ #  -> empty otherwise
+-test-build = $(if $(shell $(CC) -o /dev/null -c -x c - > /dev/null 2>&1 \
+-<<<'$1' && echo y), $2)
++test-build = $(if $(shell echo '$1' |$(CC) -o /dev/null -c -x c - > /dev/null 2>&1 
&& echo y), $2)
+
+ # have udis86 disassembler library?
+ udis86-flags := $(call test-build,\#include ,-DHAVE_UDIS86 -ludis86)
+--
+1.7.9.5
+
diff --git 
a/meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-fix-syntax-error-of-shell.patch
 
b/meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-fix-syntax-error-of-shell.patch
new file mode 100644
index 000..79abad5
--- /dev/null
+++ 
b/meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-fix-syntax-error-of-shell.patch
@@ -0,0 +1,30 @@
+trace-cmd: fix syntax error of shell
+
+Delete "<<<" syntax of bash in Makefile, else we would get following error:
+
+   Syntax error: redirection unexpected
+
+Upstream-Status: Inappropriate [embedded specific]
+
+Signed-off-by: Chong Lu 
+---
+ Makefile |3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index c1fa906..7973c53 100644
+--- a/Makefile
 b/Makefile
+@@ -89,8 +89,7 @@ endif
+
+ # $(call test-build, snippet, ret) -> ret if snippet compiles
+ #  -> empty otherwise
+-test-build = $(if $(shell $(CC) -o /dev/null -c -x c - > /dev/null 2>&1 \
+-<<<'$1' && echo y), $2)
++test-build = $(if $(shell echo '$1' |$(CC) -o /dev/null -c -x c - > /dev/null 2>&1 
&& echo y), $2)
+
+ # have udis86 disassembler library?
+ udis86-flags := $(call test-build,\#include ,-DHAVE_UDIS86 -ludis86)
+--
+1.7.9.5
+
diff --git a/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb 
b/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb
index 74eafbb..a0c823b 100644
--- a/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb
+++ b/meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb
@@ -18,6 +18,7 @@ SRC_URI = 
"git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git \
 file://trace-cmd-Add-checks-for-invalid-pointers-to-fix-seg.patch \
 file://trace-cmd-Do-not-call-stop_threads-if-doing-latency-.patch \
 file://trace-cmd-Setting-plugin-to-nop-clears-data-before-i.patch \
+   file://trace-cmd-fix-syntax-error-of-shell.patch \
  "
  S = "${WORKDIR}/git"
  
--

1.8.1.2







--
__

Re: [OE-core] [PATCH 3/4] cryptodev-module: recipe for out-of-tree cryptodev device driver

2014-04-07 Thread Denys Dmytriyenko
On Mon, Apr 07, 2014 at 03:13:14PM -0700, Saul Wold wrote:
> On 04/06/2014 07:29 PM, Denys Dmytriyenko wrote:
> >From: Denys Dmytriyenko 
> >
> >Depends on cryptodev-linux for providing a header file
> >
> 
> I am seeing failure on the Autobuilder with multilib enabled
> (lib32), I am not sure if this is a multilib issue, but it shows up
> here

Ah, only tested it on 3.12 and 3.13+ requires this patch:
http://patchwork.ozlabs.org/patch/312943/

Will re-submit shortly...


> >NOTE: Running task 14174 of 19826 (ID: 13044, 
> >virtual:multilib:lib32:/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/meta/recipes-core/libcgroup/libcgroup_0.41.bb,
> > do_configure)
> >ERROR: Function failed: do_compile (log file is located at 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/log.do_compile.19322)
> >ERROR: Logfile of failure stored in: 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/log.do_compile.19322
> >Log data follows:
> >| DEBUG: Executing shell function do_compile
> >| NOTE: make -j 16 
> >KERNEL_DIR=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
> > 
> >PREFIX=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/image
> > 
> >KERNEL_PATH=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
> > 
> >KERNEL_SRC=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
> > KERNEL_VERSION=3.14.0-yocto-standard CC=i586-poky-linux-gcc  
> >LD=i586-poky-linux-ld.bfd  AR=i586-poky-linux-ar
> >| make -C 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
> > SUBDIRS=`pwd` modules
> >| make[1]: Entering directory 
> >`/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel'
> >| make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent 
> >make rule.
> >|   CC [M]  
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/ioctl.o
> >| 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/ioctl.c:710:21:
> > warning: 'is_known_accelerated' defined but not used [-Wunused-function]
> >|  static unsigned int is_known_accelerated(struct crypto_tfm *tfm)
> >|  ^
> >|   CC [M]  
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/main.o
> >|   CC [M]  
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.o
> >| 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.c:
> > In function 'cryptodev_cipher_encrypt':
> >| 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.c:223:2:
> > error: implicit declaration of function 'INIT_COMPLETION' 
> >[-Werror=implicit-function-declaration]
> >|   INIT_COMPLETION(cdata->async.result->completion);
> >|   ^
> >| cc1: some warnings being treated as errors
> >| make[2]: *** 
> >[/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.o]
> > Error 1
> >| make[1]: *** 
> >[_module_/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6]
> > Error 2
> >| make[1]: Leaving directory 
> >`/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel'
> >| make: *** [build] Error 2
> >| ERROR: oe_runmake failed
> >| WARNING: 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/run.do_compile.19322:1
> > exit 1 from
> >|   exit 1
> >| ERROR: Function failed: do_compile (log file is located at 
> >/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/log.do_compile.19322)
> >NOTE: recipe cryptodev-module-1.6-r0: task do_compile: Failed
> >ERROR: Task 13808 
> >(/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/meta/recipes-kernel/cryptodev/cryptodev-module_1.6.bb,
> > do_compile) failed with exit code '1'
> >NOTE: Running task 14175 of 19826 (ID: 13002, 
> >virtual:mul

Re: [OE-core] [PATCH 3/4] cryptodev-module: recipe for out-of-tree cryptodev device driver

2014-04-07 Thread Saul Wold

On 04/06/2014 07:29 PM, Denys Dmytriyenko wrote:

From: Denys Dmytriyenko 

Depends on cryptodev-linux for providing a header file



I am seeing failure on the Autobuilder with multilib enabled (lib32), I 
am not sure if this is a multilib issue, but it shows up here




NOTE: Running task 14174 of 19826 (ID: 13044, 
virtual:multilib:lib32:/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/meta/recipes-core/libcgroup/libcgroup_0.41.bb,
 do_configure)
ERROR: Function failed: do_compile (log file is located at 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/log.do_compile.19322)
ERROR: Logfile of failure stored in: 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/log.do_compile.19322
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 16 
KERNEL_DIR=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
 
PREFIX=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/image
 
KERNEL_PATH=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
 
KERNEL_SRC=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
 KERNEL_VERSION=3.14.0-yocto-standard CC=i586-poky-linux-gcc  
LD=i586-poky-linux-ld.bfd  AR=i586-poky-linux-ar
| make -C 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel
 SUBDIRS=`pwd` modules
| make[1]: Entering directory 
`/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel'
| make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent make 
rule.
|   CC [M]  
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/ioctl.o
| 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/ioctl.c:710:21:
 warning: 'is_known_accelerated' defined but not used [-Wunused-function]
|  static unsigned int is_known_accelerated(struct crypto_tfm *tfm)
|  ^
|   CC [M]  
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/main.o
|   CC [M]  
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.o
| 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.c:
 In function 'cryptodev_cipher_encrypt':
| 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.c:223:2:
 error: implicit declaration of function 'INIT_COMPLETION' 
[-Werror=implicit-function-declaration]
|   INIT_COMPLETION(cdata->async.result->completion);
|   ^
| cc1: some warnings being treated as errors
| make[2]: *** 
[/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6/cryptlib.o]
 Error 1
| make[1]: *** 
[_module_/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/cryptodev-linux-1.6]
 Error 2
| make[1]: Leaving directory 
`/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/sysroots/qemux86/usr/src/kernel'
| make: *** [build] Error 2
| ERROR: oe_runmake failed
| WARNING: 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/run.do_compile.19322:1
 exit 1 from
|   exit 1
| ERROR: Function failed: do_compile (log file is located at 
/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/build/tmp/work/qemux86-poky-linux/cryptodev-module/1.6-r0/temp/log.do_compile.19322)
NOTE: recipe cryptodev-module-1.6-r0: task do_compile: Failed
ERROR: Task 13808 
(/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/meta/recipes-kernel/cryptodev/cryptodev-module_1.6.bb,
 do_compile) failed with exit code '1'
NOTE: Running task 14175 of 19826 (ID: 13002, 
virtual:multilib:lib32:/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-world/build/meta/recipes-devtools/python/python-mako_0.9.1.bb,
 do_configure)
NOTE: recipe liburcu-0.8.1-r0: task do_package_write_deb: Succeeded





Signed-off-by: Denys Dmytriyenko 
---
  .../cryptodev/cryptodev-module_1.6.bb  | 15 
  ...talling-header-file-provided-by-another-p.patch | 28 ++
  2

[OE-core] libxslt populate_sysroot dependencies

2014-04-07 Thread Slater, Joseph
I have attached a patch that makes sure libxml2-native is available when both 
it and libxslt-native
are taken from sstate.

The patch parallels one from a few weeks ago for pixbufcache, but the 
underlying problem might
have been fixed since then.  I looked for likely commits, and didn't see 
anything, so this patch
might still be needed.

Joe



0001-libxslt-native-add-populate_sysroot-dependencies.patch
Description: 0001-libxslt-native-add-populate_sysroot-dependencies.patch
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] OEDAM updates

2014-04-07 Thread Denys Dmytriyenko
On Mon, Apr 07, 2014 at 04:01:57PM -0700, Philip Balister wrote:
> Once again, please add yourself (or email Jefro or myself) if you plan
> to attend OEDAM. We have room for about 5-10 more people.
> 
> http://www.openembedded.org/wiki/OEDAM
> 
> We should also get serious about creating an agenda. Even if you are not
> able to attend please take a look at the agenda and add topics you think
> should be discussed. We'll likely have to review the agenda when we
> start, but now is a good time to air your grievances.

I'm not sure how many will be staying all day Saturday, but can we try to 
group agenda topics so most pressing matters fall on Friday and maybe Saturday 
morning?

-- 
Denys
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 1/1] vala: add dependencies on native packages

2014-04-07 Thread Joe Slater
We do not want to run the host xsltproc one time, and ours
another, so we add a dependency on libxslt-native.  We also
need to add a dependency on pkgconfig-native because the host
pkg-config will not see native packages we have built.

Signed-off-by: Joe Slater 
---
 meta/recipes-devtools/vala/vala.inc |   11 +--
 1 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/vala/vala.inc 
b/meta/recipes-devtools/vala/vala.inc
index a8927d7..9d273aa 100644
--- a/meta/recipes-devtools/vala/vala.inc
+++ b/meta/recipes-devtools/vala/vala.inc
@@ -3,7 +3,13 @@ Vala compiles to plain C and has no runtime environment nor 
penalities whatsoeve
 SECTION = "devel"
 DEPENDS = "glib-2.0 dbus gtk+"
 BBCLASSEXTEND = "native"
-DEPENDS_virtclass-native = "bison-native glib-2.0-native dbus-native"
+
+# libxslt provides xsltproc, which is probably on the host, but we want to use 
ours.
+# We need our pkg-config, too.  (Inheriting pkgconfig supplies that 
dependency, but
+# we clobber it here).
+#
+DEPENDS_virtclass-native = "bison-native glib-2.0-native dbus-native 
libxslt-native pkgconfig-native"
+
 HOMEPAGE = "http://vala-project.org";
 LICENSE = "LGPLv2.1"
 LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
@@ -12,7 +18,8 @@ INC_PR = "r1"
 SHRT_VER = 
"${@d.getVar('PV',1).split('.')[0]}.${@d.getVar('PV',1).split('.')[1]}"
 
 SRC_URI = 
"http://ftp.gnome.org/pub/GNOME/sources/${BPN}/${SHRT_VER}/${BP}.tar.xz";
-inherit autotools
+
+inherit autotools pkgconfig
 
 EXTRA_OECONF = "--disable-vapigen"
 
-- 
1.7.3.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] OEDAM updates

2014-04-07 Thread Philip Balister
Once again, please add yourself (or email Jefro or myself) if you plan
to attend OEDAM. We have room for about 5-10 more people.

http://www.openembedded.org/wiki/OEDAM

We should also get serious about creating an agenda. Even if you are not
able to attend please take a look at the agenda and add topics you think
should be discussed. We'll likely have to review the agenda when we
start, but now is a good time to air your grievances.

Philip
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] openssl: Address CVE-2014-0160

2014-04-07 Thread Mark Hatle

On 4/7/14, 5:05 PM, Saul Wold wrote:

This was the suggested fix for those unable to update to the new 1.0.1g version.
Since we are so close to our release, we should hold of on the update until 1.7

Signed-off-by: Saul Wold 
---
  meta/recipes-connectivity/openssl/openssl_1.0.1e.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb 
b/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb
index 618ba68..874aa21 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb
@@ -4,7 +4,7 @@ require openssl.inc
  # if they are available.
  DEPENDS += "cryptodev-linux"

-CFLAG += "-DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS"
+CFLAG += "-DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS -DOPENSSL_NO_HEARTBEATS"

  PR = "${INC_PR}.0"




Between 1.0.1e and f there are 3 CVEs.  'g' adds two more.

This is a very low risk change, as the API and other components are stable.

--Mark
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2] udev-extraconf: update mount.sh to use /run/media instead of /media

2014-04-07 Thread Richard Purdie
On Mon, 2014-04-07 at 17:05 -0400, Denys Dmytriyenko wrote:
> I understand the timing concern and am fine waiting another week for when 1.7 
> window opens.
> 
> But I'm slightly confused as to since when OE-Core is concerned about 
> breaking 
> bbappends in other layers? I guess some layers are not created equal, eh? :)

The question is more one of timing. I don't think its reasonable that we
break things like that between -rc2 and -rc3 of 1.6 without a better
reason...

I'm even nervous changing the sstate checksums but I think the CONFFILES
change does warrant that for example.

Cheers,

Richard



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] openssl: Address CVE-2014-0160

2014-04-07 Thread Saul Wold
This was the suggested fix for those unable to update to the new 1.0.1g version.
Since we are so close to our release, we should hold of on the update until 1.7

Signed-off-by: Saul Wold 
---
 meta/recipes-connectivity/openssl/openssl_1.0.1e.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb 
b/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb
index 618ba68..874aa21 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.0.1e.bb
@@ -4,7 +4,7 @@ require openssl.inc
 # if they are available.
 DEPENDS += "cryptodev-linux"
 
-CFLAG += "-DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS"
+CFLAG += "-DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS -DOPENSSL_NO_HEARTBEATS"
 
 PR = "${INC_PR}.0"
 
-- 
1.8.3.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] mesa: Avoid picking up the "local" wayland-scanner.

2014-04-07 Thread Søren Holm
The generated headers turn out wrong and breaks compilation if
the local version is different from the target version.

Signed-off-by: Søren Holm 
---
 meta/recipes-graphics/mesa/mesa.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-graphics/mesa/mesa.inc 
b/meta/recipes-graphics/mesa/mesa.inc
index afc795c..822b236 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -65,6 +65,7 @@ MESA_LLVM_RELEASE ?= "3.3"
 PACKAGECONFIG[gallium-llvm] = "--enable-gallium-llvm --with-llvm-shared-libs, 
--disable-gallium-llvm, llvm${MESA_LLVM_RELEASE} \
${@'elfutils' if 
${GALLIUMDRIVERS_LLVM33_ENABLED} else ''}"
 export WANT_LLVM_RELEASE = "${MESA_LLVM_RELEASE}"
+export WAYLAND_SCANNER = "${STAGING_DIR_NATIVE}/usr/bin/wayland-scanner"
 
 # llvmpipe is slow if compiled with -fomit-frame-pointer (e.g. -O2)
 FULL_OPTIMIZATION_append = " -fno-omit-frame-pointer"
-- 
1.9.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2] udev-extraconf: update mount.sh to use /run/media instead of /media

2014-04-07 Thread Denys Dmytriyenko
On Mon, Apr 07, 2014 at 08:49:44AM -0700, Saul Wold wrote:
> On 04/06/2014 03:46 PM, Denys Dmytriyenko wrote:
> >ping
> >
> 
> This change is a little late for 1.6 as we are prepping for the
> final RC this week.  It's kind of an API change since it moves the
> mount location /media, should we be linking /media to /run/media?
> 
> There is also an issue with the Freescale PPC BSP, which has a
> bbappend for 1.0, so some coordination with them will be needed.
> 
> I can revisit this for 1.7 in a week or so.
> 
> Sau!

I understand the timing concern and am fine waiting another week for when 1.7 
window opens.

But I'm slightly confused as to since when OE-Core is concerned about breaking 
bbappends in other layers? I guess some layers are not created equal, eh? :)

-- 
Denys


> >On Mon, Mar 31, 2014 at 11:54:11PM -0400, Denys Dmytriyenko wrote:
> >>From: Denys Dmytriyenko 
> >>
> >>This is done to work around the issue of auto-mounting block devices
> >>(i.e. SD cards) when root filesystem is still in read-only mode and
> >>creating /media/ mount-points by udev is not possible. That
> >>is due to udev (/etc/rcS.d/S03udev) getting started earlier than
> >>checkroot (/etc/rcS.d/S10checkroot.sh) gets a chance to re-mount the
> >>rootfs as read-write.
> >>
> >>Although, canonical FHS specifies /media/ as a mount point
> >>for removable media devices, the latest 2.3 version was released in
> >>2004 and since then FreeDesktop/udisks and other tools adopted the
> >>new /run/media// location. That was done to overcome
> >>read-only rootfs limitation, since /run is usually a tmpfs mounted
> >>partition, plus avoid name-clash between users.
> >>
> >>For our embedded systems environment we assume single-user operation
> >>and hence simplify mount point to just /run/media/. But for
> >>proper per-user mounting to /run/media//, some sort of
> >>session management is required along with the tool like udisks, that
> >>is out of scope of this simple udev-based auto-mounting.
> >>
> >>Signed-off-by: Denys Dmytriyenko 
> >>---
> >>v2 - drop PR, bump PV, elaborate on session/user mounting option
> >>
> >>  meta/recipes-core/udev/udev-extraconf/mount.sh | 14 
> >> +++---
> >>  .../udev/{udev-extraconf_1.0.bb => udev-extraconf_1.1.bb}  |  2 --
> >>  2 files changed, 7 insertions(+), 9 deletions(-)
> >>  rename meta/recipes-core/udev/{udev-extraconf_1.0.bb => 
> >> udev-extraconf_1.1.bb} (99%)
> >>
> >>diff --git a/meta/recipes-core/udev/udev-extraconf/mount.sh 
> >>b/meta/recipes-core/udev/udev-extraconf/mount.sh
> >>index cb57e47..3e4f21f 100644
> >>--- a/meta/recipes-core/udev/udev-extraconf/mount.sh
> >>+++ b/meta/recipes-core/udev/udev-extraconf/mount.sh
> >>@@ -20,7 +20,7 @@ done
> >>  automount() { 
> >>name="`basename "$DEVNAME"`"
> >>
> >>-   ! test -d "/media/$name" && mkdir -p "/media/$name"
> >>+   ! test -d "/run/media/$name" && mkdir -p "/run/media/$name"
> >># Silent util-linux's version of mounting auto
> >>if [ "x`readlink $MOUNT`" = "x/bin/mount.util-linux" ] ;
> >>then
> >>@@ -38,12 +38,12 @@ automount() {
> >>;;
> >>esac
> >>
> >>-   if ! $MOUNT -t auto $DEVNAME "/media/$name"
> >>+   if ! $MOUNT -t auto $DEVNAME "/run/media/$name"
> >>then
> >>-   #logger "mount.sh/automount" "$MOUNT -t auto $DEVNAME 
> >>\"/media/$name\" failed!"
> >>-   rm_dir "/media/$name"
> >>+   #logger "mount.sh/automount" "$MOUNT -t auto $DEVNAME 
> >>\"/run/media/$name\" failed!"
> >>+   rm_dir "/run/media/$name"
> >>else
> >>-   logger "mount.sh/automount" "Auto-mount of [/media/$name] 
> >>successful"
> >>+   logger "mount.sh/automount" "Auto-mount of [/run/media/$name] 
> >>successful"
> >>touch "/tmp/.automount-$name"
> >>fi
> >>  }
> >>@@ -60,7 +60,7 @@ rm_dir() {
> >>
> >>  # No ID_FS_TYPE for cdrom device, yet it should be mounted
> >>  name="`basename "$DEVNAME"`"
> >>-[ -e /sys/block/$name/device/media ] && media_type=`cat 
> >>/sys/block/$name/device/media`
> >>+[ -e /sys/block/$name/device/run/media ] && media_type=`cat 
> >>/sys/block/$name/device/run/media`
> >>
> >>  if [ "$ACTION" = "add" ] && [ -n "$DEVNAME" ] && [ -n "$ID_FS_TYPE" -o 
> >> "$media_type" = "cdrom" ]; then
> >>if [ -x "$PMOUNT" ]; then
> >>@@ -87,5 +87,5 @@ if [ "$ACTION" = "remove" ] && [ -x "$UMOUNT" ] && [ -n 
> >>"$DEVNAME" ]; then
> >>
> >># Remove empty directories from auto-mounter
> >>name="`basename "$DEVNAME"`"
> >>-   test -e "/tmp/.automount-$name" && rm_dir "/media/$name"
> >>+   test -e "/tmp/.automount-$name" && rm_dir "/run/media/$name"
> >>  fi
> >>diff --git a/meta/recipes-core/udev/udev-extraconf_1.0.bb 
> >>b/meta/recipes-core/udev/udev-extraconf_1.1.bb
> >>similarity index 99%
> >>rename from meta/recipes-core/udev/udev-extraconf_1.0.bb
> >>rename to meta/recipes-core/udev/udev-extraconf_1.1.bb
> >>index 3810b28..d69056d 100644
> >>--- a/meta/recipes-core/udev/udev-extraconf_1.0.bb
> >>++

Re: [OE-core] meta-toolchain-sdk LDFLAGS fails for ARMv7 (beagleboard)

2014-04-07 Thread Denys Dmytriyenko
On Mon, Apr 07, 2014 at 10:02:40PM +0200, Ulf Samuelsson wrote:
> Trying to build an SDK for the Beaglebone
> 
> $ git clone git://git.yoctoproject.org/poky
> $ cd poky
> $ git checkout -b dora origin/dora
> 
> $ . oe-init-build-env
> 
> MACHINE is set to "beagleboard" in local.conf

It's not critical to your case, but in general beagleboard != beaglebone...

And cutting to the chase - U-boot recipe in OE clears CFLAGS, LDFLAGS and 
CPPFLAGS before building it...


> $ ./environment-angstrom-v2013.06
> 
> $ bitbake meta-toolchain-sdk
> 
> SDK is generated, and installed in /opt/poky/1.5.1 (default)
> 
> The toolchain environment file is "sourced"
> 
> Then I try to build U-Boot-13.10 (with a minor patch)
> 
> 
> $ make am335x_boneblack_config
> 
> $ make
> 
> After compiling a number of file, the linking of a library fails:
> 
> arm-poky-linux-gnueabi-ld.bfd -Wl,-O1 -Wl,--hash-style=gnu
> -Wl,--as-needed   -r -o libcommon.o  cmd_bdinfo.o cmd_boot.o
> cmd_bootm.o cmd_console.o cmd_dfu.o cmd_disk.o cmd_echo.o
> cmd_eeprom.o cmd_exit.o cmd_ext2.o cmd_ext4.o cmd_fat.o cmd_fdt.o
> cmd_fs.o cmd_gpio.o cmd_help.o cmd_i2c.o cmd_itest.o cmd_load.o
> cmd_mem.o cmd_misc.o cmd_mmc.o cmd_net.o cmd_nvedit.o cmd_pcmcia.o
> cmd_sf.o cmd_source.o cmd_spi.o cmd_spl.o cmd_test.o cmd_usb.o
> cmd_version.o cmd_ximg.o command.o console.o dlmalloc.o env_attr.o
> env_callback.o env_common.o env_flags.o env_mmc.o exports.o
> fdt_support.o flash.o hash.o hush.o image-fdt.o image.o main.o
> memsize.o miiphyutil.o s_record.o splash.o stdio.o usb.o usb_hub.o
> usb_storage.o xyzModem.o
> arm-poky-linux-gnueabi-ld.bfd: unrecognized option '-Wl,-O1'
> arm-poky-linux-gnueabi-ld.bfd: use the --help option for usage information
> make[1]: *** [libcommon.o] Fel 1
> make[1]: Lämnar katalogen
> "/home/ulf/felabs/sysdev/bootloader/u-boot-2013.10/common"
> make: *** [common/libcommon.o] Fel 2
> 
> ---
> The environment looks like:
> ---
> export 
> PATH=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi:$PATH
> export 
> PKG_CONFIG_SYSROOT_DIR=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi
> export 
> PKG_CONFIG_PATH=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/lib/pkgconfig
> export 
> CONFIG_SITE=/opt/poky/1.5.1/site-config-armv7a-vfp-neon-poky-linux-gnueabi
> export CC="arm-poky-linux-gnueabi-gcc  -march=armv7-a
> -mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export CXX="arm-poky-linux-gnueabi-g++  -march=armv7-a
> -mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export CPP="arm-poky-linux-gnueabi-gcc -E  -march=armv7-a
> -mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export AS="arm-poky-linux-gnueabi-as "
> export LD="arm-poky-linux-gnueabi-ld 
> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export GDB=arm-poky-linux-gnueabi-gdb
> export STRIP=arm-poky-linux-gnueabi-strip
> export RANLIB=arm-poky-linux-gnueabi-ranlib
> export OBJCOPY=arm-poky-linux-gnueabi-objcopy
> export OBJDUMP=arm-poky-linux-gnueabi-objdump
> export AR=arm-poky-linux-gnueabi-ar
> export NM=arm-poky-linux-gnueabi-nm
> export M4=m4
> export TARGET_PREFIX=arm-poky-linux-gnueabi-
> export CONFIGURE_FLAGS="--target=arm-poky-linux-gnueabi
> --host=arm-poky-linux-gnueabi --build=x86_64-linux 
> --with-libtool-sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types"
> export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types -fpermissive"
> export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
> export CPPFLAGS=""
> export OECORE_NATIVE_SYSROOT="/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux"
> export 
> OECORE_TARGET_SYSROOT="/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export OECORE_ACLOCAL_OPTS="-I
> /opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/share/aclocal"
> export OECORE_DISTRO_VERSION="1.5.1"
> export OECORE_SDK_VERSION="1.5.1"
> export PYTHONHOME=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr
> export ARCH=arm
> export CROSS_COMPILE=arm-poky-linux-gnueabi-
> -
> 
> Notable is:
> export LD="arm-poky-linux-gnueabi-ld 
> --sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
> export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
> 
> From the error message I see:
> "arm-poky-linux-gnueabi-ld.bfd -Wl,-O1 ..."
> 
> Note that 

Re: [OE-core] State of bitbake world, Failed tasks 2014-04-03

2014-04-07 Thread Trevor Woerner
Is anyone seeing any build failures with proj-4.8.0? Or does anyone have
any local fixes? This one has been failing for me for a while, and yet
doesn't show up on the SOBBW lists.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] meta-toolchain-sdk LDFLAGS fails for ARMv7 (beagleboard)

2014-04-07 Thread Ulf Samuelsson

Trying to build an SDK for the Beaglebone

$ git clone git://git.yoctoproject.org/poky
$ cd poky
$ git checkout -b dora origin/dora

$ . oe-init-build-env

MACHINE is set to "beagleboard" in local.conf

$ ./environment-angstrom-v2013.06

$ bitbake meta-toolchain-sdk

SDK is generated, and installed in /opt/poky/1.5.1 (default)

The toolchain environment file is "sourced"

Then I try to build U-Boot-13.10 (with a minor patch)


$ make am335x_boneblack_config

$ make

After compiling a number of file, the linking of a library fails:

arm-poky-linux-gnueabi-ld.bfd -Wl,-O1 -Wl,--hash-style=gnu 
-Wl,--as-needed   -r -o libcommon.o  cmd_bdinfo.o cmd_boot.o cmd_bootm.o 
cmd_console.o cmd_dfu.o cmd_disk.o cmd_echo.o cmd_eeprom.o cmd_exit.o 
cmd_ext2.o cmd_ext4.o cmd_fat.o cmd_fdt.o cmd_fs.o cmd_gpio.o cmd_help.o 
cmd_i2c.o cmd_itest.o cmd_load.o cmd_mem.o cmd_misc.o cmd_mmc.o 
cmd_net.o cmd_nvedit.o cmd_pcmcia.o cmd_sf.o cmd_source.o cmd_spi.o 
cmd_spl.o cmd_test.o cmd_usb.o cmd_version.o cmd_ximg.o command.o 
console.o dlmalloc.o env_attr.o env_callback.o env_common.o env_flags.o 
env_mmc.o exports.o fdt_support.o flash.o hash.o hush.o image-fdt.o 
image.o main.o memsize.o miiphyutil.o s_record.o splash.o stdio.o usb.o 
usb_hub.o usb_storage.o xyzModem.o

arm-poky-linux-gnueabi-ld.bfd: unrecognized option '-Wl,-O1'
arm-poky-linux-gnueabi-ld.bfd: use the --help option for usage information
make[1]: *** [libcommon.o] Fel 1
make[1]: Lämnar katalogen 
"/home/ulf/felabs/sysdev/bootloader/u-boot-2013.10/common"

make: *** [common/libcommon.o] Fel 2

---
The environment looks like:
---
export 
PATH=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi:$PATH
export 
PKG_CONFIG_SYSROOT_DIR=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi
export 
PKG_CONFIG_PATH=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi/usr/lib/pkgconfig
export 
CONFIG_SITE=/opt/poky/1.5.1/site-config-armv7a-vfp-neon-poky-linux-gnueabi
export CC="arm-poky-linux-gnueabi-gcc  -march=armv7-a -mthumb-interwork 
-mfloat-abi=softfp -mfpu=neon 
--sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
export CXX="arm-poky-linux-gnueabi-g++  -march=armv7-a -mthumb-interwork 
-mfloat-abi=softfp -mfpu=neon 
--sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
export CPP="arm-poky-linux-gnueabi-gcc -E  -march=armv7-a 
-mthumb-interwork -mfloat-abi=softfp -mfpu=neon 
--sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"

export AS="arm-poky-linux-gnueabi-as "
export LD="arm-poky-linux-gnueabi-ld 
--sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"

export GDB=arm-poky-linux-gnueabi-gdb
export STRIP=arm-poky-linux-gnueabi-strip
export RANLIB=arm-poky-linux-gnueabi-ranlib
export OBJCOPY=arm-poky-linux-gnueabi-objcopy
export OBJDUMP=arm-poky-linux-gnueabi-objdump
export AR=arm-poky-linux-gnueabi-ar
export NM=arm-poky-linux-gnueabi-nm
export M4=m4
export TARGET_PREFIX=arm-poky-linux-gnueabi-
export CONFIGURE_FLAGS="--target=arm-poky-linux-gnueabi 
--host=arm-poky-linux-gnueabi --build=x86_64-linux 
--with-libtool-sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"

export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types"
export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types -fpermissive"
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
export CPPFLAGS=""
export OECORE_NATIVE_SYSROOT="/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux"
export 
OECORE_TARGET_SYSROOT="/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"
export OECORE_ACLOCAL_OPTS="-I 
/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr/share/aclocal"

export OECORE_DISTRO_VERSION="1.5.1"
export OECORE_SDK_VERSION="1.5.1"
export PYTHONHOME=/opt/poky/1.5.1/sysroots/x86_64-pokysdk-linux/usr
export ARCH=arm
export CROSS_COMPILE=arm-poky-linux-gnueabi-
-

Notable is:
export LD="arm-poky-linux-gnueabi-ld 
--sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"

export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"

From the error message I see:
"arm-poky-linux-gnueabi-ld.bfd -Wl,-O1 ..."

Note that $(CROSS_COMPILE)-ld.bfd is used, not $(CROSS_COMPILE)-ld

so the linker is linking with $(LDFLAGS) which contains switches to be 
passed to the compiler, and bombs


Changing LD to:
export LD="arm-poky-linux-gnueabi-gcc 
--sysroot=/opt/poky/1.5.1/sysroots/armv7a-vfp-neon-poky-linux-gnueabi"


Does not help, still you get the same error message with
$(CROSS_COMPILE)-ld.bfd called with "-Wl,..." arguments.

Only when I am setting LDF

Re: [OE-core] [PATCH 1/3] e2fsprogs: fix multilib header conflict - ext2_types.h

2014-04-07 Thread Khem Raj
On Apr 7, 2014 1:28 AM, "Ming Liu"  wrote:
>
> ext2_types.h conflicts between 32-bit and 64-bit versions.
>

can you explain the conflicts
may be they can be addressed

> Signed-off-by: Ming Liu 
> ---
>  meta/recipes-devtools/e2fsprogs/e2fsprogs.inc   | 3 +--
>  meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb | 2 ++
>  2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
> index a34df37..99447c1 100644
> --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
> @@ -22,5 +22,4 @@ DEPENDS = "util-linux"
>  SRC_URI = "${SOURCEFORGE_MIRROR}/e2fsprogs/e2fsprogs-${PV}.tar.gz \
> file://mkdir.patch"
>
> -inherit autotools gettext pkgconfig
> -
> +inherit autotools gettext pkgconfig multilib_header
> diff --git 
> a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bbb/meta/recipes-devtools/e2fsprogs/
e2fsprogs_1.42.9.bb
> index 3a5d6ee..2bdd724 100644
> --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb
> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb
> @@ -52,6 +52,8 @@ do_install () {
> mv ${D}${base_libdir}/e2initrd_helper ${D}${libdir}
> mv ${D}${base_libdir}/pkgconfig ${D}${libdir}
> fi
> +
> +   oe_multilib_header ext2fs/ext2_types.h
>  }
>
>  RDEPENDS_e2fsprogs = "e2fsprogs-badblocks"
> --
> 1.8.4.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] export TARGET_LDFLAGS and native sstate

2014-04-07 Thread Khem Raj
-Khem
On Apr 7, 2014 5:53 AM, "Mike Crowe"  wrote:
>
> We're building for both ARM and MIPS-based MACHINEs in a single source
> tree. This seems to result in us compiling (or luckily most of the time
> resurrecting from sstate-cache) two different versions of all -native
> packages due to different base hashes.
>
> It seems that this difference in base hashes is due to the exported
> variable TARGET_LDFLAGS being different between the two CPUs:
>
> < export TARGET_LDFLAGS="-Wl,-O1  -Wl,--as-needed"
> ---
> > export TARGET_LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
>
> which in turn is because TARGET_LINK_HASH_STYLE is explicitly set to
"sysv"
> on MIPS but allowed to be "gnu" on everything else.
>
> Every time I switch back and forth between building ARM-based and
> MIPS-based machines the do_populate_sysroot_setscene tasks run for each
> required -native recipe.
>
> If I modify native.bbclass to do:
>
>  TARGET_LDFLAGS = "${BUILD_LDFLAGS}"

this is reasonable to do
>
> then the hashes match and this unnecessary sysroot population is avoided.
>
> Is this a sensible thing to be doing? It does mean that TARGET_LDFLAGS
> contains a lot of (presumably unnecessary) rpath shenanigans but perhaps
> that doesn't matter. :(
>
> Thanks.
>
> Mike.
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] OE Changelog since 2014-03-30 until 2014-04-06

2014-04-07 Thread cliff . brake
Changelog since 2014-03-30 until 2014-04-06.  Projects included in this report:

bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom: git://github.com/Angstrom-distribution/meta-angstrom.git
meta-arago: git://arago-project.org/git/meta-arago.git
meta-beagleboard: git://github.com/beagleboard/meta-beagleboard.git
meta-browser: git://github.com/OSSystems/meta-browser.git
meta-bug: git://github.com/buglabs/meta-bug.git
meta-chicken: git://github.com/OSSystems/meta-chicken
meta-efikamx: git://github.com/kraj/meta-efikamx.git
meta-ettus: http://github.com/koenkooi/meta-ettus.git
meta-fsl-arm: git://git.yoctoproject.org/meta-fsl-arm
meta-fsl-arm-extra: git://github.com/Freescale/meta-fsl-arm-extra.git
meta-fsl-ppc: git://git.yoctoproject.org/meta-fsl-ppc
meta-guacamayo: git://github.com/Guacamayo/meta-guacamayo.git
meta-gumstix: git://github.com/gumstix/meta-gumstix.git
meta-gumstix-community: 
git://gitorious.org/schnitzeltony-oe-meta/meta-gumstix-community.git
meta-handheld: git://git.openembedded.org/meta-handheld
meta-igep: http://github.com/ebutera/meta-igep.git
meta-intel: git://git.yoctoproject.org/meta-intel
meta-ivi: git://git.yoctoproject.org/meta-ivi
meta-java: git://github.com/woglinde/meta-java
meta-kde: git://gitorious.org/openembedded-core-layers/meta-kde.git
meta-micro: git://git.openembedded.org/meta-micro
meta-mono: git://git.yoctoproject.org/meta-mono.git
meta-netbookpro: git://github.com/tworaz/meta-netbookpro
meta-nslu2: git://github.com/kraj/meta-nslu2
meta-opie: git://git.openembedded.org/meta-opie
meta-qt3: git://git.yoctoproject.org/meta-qt3
meta-qt5: git://github.com/meta-qt5/meta-qt5.git
meta-slugos: git://github.com/kraj/meta-slugos
meta-systemd: git://git.yoctoproject.org/meta-systemd
meta-raspberrypi: git://github.com/djwillis/meta-raspberrypi.git
meta-smartphone: http://git.shr-project.org/repo/meta-smartphone.git
meta-ti: git://git.yoctoproject.org/meta-ti
meta-webos: git://github.com/openwebos/meta-webos.git
meta-xilinx: git://git.yoctoproject.org/meta-xilinx
meta-yocto: git://git.yoctoproject.org/meta-yocto
openembedded: git://git.openembedded.org/openembedded


Changelog for bitbake:

Alexandru DAMIAN (5):
  toaster: update saving sstate task data
  toaster: fix timezone detection
  bitbake: cooker: mark setFeatures command as read-only
  toasterui: avoid variable name conflict
  toasterui: save warnings from non-build context

Belen Barros Pena (14):
  toaster: Show "No builds found" in the builds table
  toaster: Remove trailing spaces from 'name'
  toaster: Small tweaks to the packages included interface
  toaster: Fix the fade out animation
  toaster: Increase animation duration
  toaster: Match search results form to no results form
  toaster: Update help text in format_vpackage_namehelp tag
  toaster: Update API
  toaster: Remove html validation errors in tasks.html
  toaster: Changes to help text
  toaster: Fix "Recent builds" links
  toaster: Fix the empty packages alert
  toaster: Make tables happy in Chrome
  toaster: Fixes to the build dashboard

Cristiana Voicu (2):
  toaster: use deploy_dir var to obtain the license.manifest path
  hob: adding INHERIT += " testimage " affects image recipes list

Dave Lerner (1):
  toaster: unbuilt package dependency formats

David Reyna (4):
  toaster: disable configvar sorts for value and files
  toaster: secondary sort key as table's default order
  toaster: link task order to right tasks page
  toaster: catch IndexError error in dictionary lookups

Farrell Wymore (2):
  toaster: correct package count
  toaster: added covered task list

Marius Avram (2):
  hob: fix customization of empty image recipe
  cooker: Overwrite IMAGE_BASENAME to default in custom image

Paul Eggleton (2):
  toaster: fix help texts not showing for most tasks
  toaster: fix mis-detection of targets as images

Ravi Chintakunta (1):
  toaster: Display task description

Richard Purdie (3):
  runqueue: Fix sstate task dependency problems
  runqueue: Address issues with incomplete sstate sets
  fetch2: Fix bug in file checksum generation

Scott Rifenbark (1):
  user-manual-metadata.xml: Added new section on mapping functions.


Changelog for openembedded-core:

Alexandru DAMIAN (1):
  sstate.bbclass: update missed sstate event

Alexandru-Cezar Sardan (2):
  gcc: changed multilib options handling
  gcc: enable multilib setup for powerpc64 arch

Baogen Shang (1):
  openssl: Fix pod2man des.pod error on Ubuntu 12.04

Bruce Ashfield (6):
  linux-yocto/3.10: fix qemuarm build failure
  linux-yocto/3.14: introduce versioned recipes
  linux-libc-headers: make compression format configurable
  linux-libc-headers: add 3.14 libc headers
  libc-headers: set TC default to 3.14
  linux-libc-headers: remove 3.10 recipe

Chong Lu (1):
  pytho

Re: [OE-core] [PATCH v2] udev-extraconf: update mount.sh to use /run/media instead of /media

2014-04-07 Thread Saul Wold

On 04/06/2014 03:46 PM, Denys Dmytriyenko wrote:

ping



This change is a little late for 1.6 as we are prepping for the final RC 
this week.  It's kind of an API change since it moves the mount location 
/media, should we be linking /media to /run/media?


There is also an issue with the Freescale PPC BSP, which has a bbappend 
for 1.0, so some coordination with them will be needed.


I can revisit this for 1.7 in a week or so.

Sau!


On Mon, Mar 31, 2014 at 11:54:11PM -0400, Denys Dmytriyenko wrote:

From: Denys Dmytriyenko 

This is done to work around the issue of auto-mounting block devices
(i.e. SD cards) when root filesystem is still in read-only mode and
creating /media/ mount-points by udev is not possible. That
is due to udev (/etc/rcS.d/S03udev) getting started earlier than
checkroot (/etc/rcS.d/S10checkroot.sh) gets a chance to re-mount the
rootfs as read-write.

Although, canonical FHS specifies /media/ as a mount point
for removable media devices, the latest 2.3 version was released in
2004 and since then FreeDesktop/udisks and other tools adopted the
new /run/media// location. That was done to overcome
read-only rootfs limitation, since /run is usually a tmpfs mounted
partition, plus avoid name-clash between users.

For our embedded systems environment we assume single-user operation
and hence simplify mount point to just /run/media/. But for
proper per-user mounting to /run/media//, some sort of
session management is required along with the tool like udisks, that
is out of scope of this simple udev-based auto-mounting.

Signed-off-by: Denys Dmytriyenko 
---
v2 - drop PR, bump PV, elaborate on session/user mounting option

  meta/recipes-core/udev/udev-extraconf/mount.sh | 14 +++---
  .../udev/{udev-extraconf_1.0.bb => udev-extraconf_1.1.bb}  |  2 --
  2 files changed, 7 insertions(+), 9 deletions(-)
  rename meta/recipes-core/udev/{udev-extraconf_1.0.bb => 
udev-extraconf_1.1.bb} (99%)

diff --git a/meta/recipes-core/udev/udev-extraconf/mount.sh 
b/meta/recipes-core/udev/udev-extraconf/mount.sh
index cb57e47..3e4f21f 100644
--- a/meta/recipes-core/udev/udev-extraconf/mount.sh
+++ b/meta/recipes-core/udev/udev-extraconf/mount.sh
@@ -20,7 +20,7 @@ done
  automount() { 
name="`basename "$DEVNAME"`"

-   ! test -d "/media/$name" && mkdir -p "/media/$name"
+   ! test -d "/run/media/$name" && mkdir -p "/run/media/$name"
# Silent util-linux's version of mounting auto
if [ "x`readlink $MOUNT`" = "x/bin/mount.util-linux" ] ;
then
@@ -38,12 +38,12 @@ automount() {
;;
esac

-   if ! $MOUNT -t auto $DEVNAME "/media/$name"
+   if ! $MOUNT -t auto $DEVNAME "/run/media/$name"
then
-   #logger "mount.sh/automount" "$MOUNT -t auto $DEVNAME 
\"/media/$name\" failed!"
-   rm_dir "/media/$name"
+   #logger "mount.sh/automount" "$MOUNT -t auto $DEVNAME 
\"/run/media/$name\" failed!"
+   rm_dir "/run/media/$name"
else
-   logger "mount.sh/automount" "Auto-mount of [/media/$name] 
successful"
+   logger "mount.sh/automount" "Auto-mount of [/run/media/$name] 
successful"
touch "/tmp/.automount-$name"
fi
  }
@@ -60,7 +60,7 @@ rm_dir() {

  # No ID_FS_TYPE for cdrom device, yet it should be mounted
  name="`basename "$DEVNAME"`"
-[ -e /sys/block/$name/device/media ] && media_type=`cat 
/sys/block/$name/device/media`
+[ -e /sys/block/$name/device/run/media ] && media_type=`cat 
/sys/block/$name/device/run/media`

  if [ "$ACTION" = "add" ] && [ -n "$DEVNAME" ] && [ -n "$ID_FS_TYPE" -o "$media_type" = 
"cdrom" ]; then
if [ -x "$PMOUNT" ]; then
@@ -87,5 +87,5 @@ if [ "$ACTION" = "remove" ] && [ -x "$UMOUNT" ] && [ -n 
"$DEVNAME" ]; then

# Remove empty directories from auto-mounter
name="`basename "$DEVNAME"`"
-   test -e "/tmp/.automount-$name" && rm_dir "/media/$name"
+   test -e "/tmp/.automount-$name" && rm_dir "/run/media/$name"
  fi
diff --git a/meta/recipes-core/udev/udev-extraconf_1.0.bb 
b/meta/recipes-core/udev/udev-extraconf_1.1.bb
similarity index 99%
rename from meta/recipes-core/udev/udev-extraconf_1.0.bb
rename to meta/recipes-core/udev/udev-extraconf_1.1.bb
index 3810b28..d69056d 100644
--- a/meta/recipes-core/udev/udev-extraconf_1.0.bb
+++ b/meta/recipes-core/udev/udev-extraconf_1.1.bb
@@ -4,8 +4,6 @@ LICENSE = "MIT"
  LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
  
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

-PR = "r16"
-
  SRC_URI = " \
 file://automount.rules \
 file://mount.sh \
--
1.9.1

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

--
___
Openembedded-core mailing

Re: [OE-core] export TARGET_LDFLAGS and native sstate

2014-04-07 Thread Mike Crowe
On Monday 07 April 2014 at 09:17:38 -0700, Chris Larson wrote:
> On Mon, Apr 7, 2014 at 8:53 AM, Mike Crowe  wrote:
> 
> > We're building for both ARM and MIPS-based MACHINEs in a single source
> > tree. This seems to result in us compiling (or luckily most of the time
> > resurrecting from sstate-cache) two different versions of all -native
> > packages due to different base hashes.
> >
> > It seems that this difference in base hashes is due to the exported
> > variable TARGET_LDFLAGS being different between the two CPUs:
> >
> > < export TARGET_LDFLAGS="-Wl,-O1  -Wl,--as-needed"
> > ---
> > > export TARGET_LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"
> >
> 
> Heh, this i another case of a likely completely unnecessary export.
> Software we build expects LDFLAGS to be used, not TARGET_LDFLAGS, so I
> can't imagine that anything is using this export. Of course, it's
> non-trivial to confirm that this is the case :)

It did strike me as an odd thing to be exporting. Given the name I assumed
it had something to do with building the toolchain. I notice though that
the gcc recipes explicitly export LDFLAGS_FOR_TARGET inside tasks based on
TARGET_LDFLAGS anyway so the toolchain "should be fine". :)

I'm happy to try our complete build without exporting TARGET_LDFLAGS as a
first step but I realise that probably wouldn't be enough proof.

Thanks.

Mike.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] export TARGET_LDFLAGS and native sstate

2014-04-07 Thread Mike Crowe
We're building for both ARM and MIPS-based MACHINEs in a single source
tree. This seems to result in us compiling (or luckily most of the time
resurrecting from sstate-cache) two different versions of all -native
packages due to different base hashes.

It seems that this difference in base hashes is due to the exported
variable TARGET_LDFLAGS being different between the two CPUs:

< export TARGET_LDFLAGS="-Wl,-O1  -Wl,--as-needed"
---
> export TARGET_LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"

which in turn is because TARGET_LINK_HASH_STYLE is explicitly set to "sysv"
on MIPS but allowed to be "gnu" on everything else.

Every time I switch back and forth between building ARM-based and
MIPS-based machines the do_populate_sysroot_setscene tasks run for each
required -native recipe.

If I modify native.bbclass to do:

 TARGET_LDFLAGS = "${BUILD_LDFLAGS}"

then the hashes match and this unnecessary sysroot population is avoided.

Is this a sensible thing to be doing? It does mean that TARGET_LDFLAGS
contains a lot of (presumably unnecessary) rpath shenanigans but perhaps
that doesn't matter. :(

Thanks.

Mike.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] python: Fix CVE-2014-1912

2014-04-07 Thread Maxin B. John
From: "Maxin B. John" 

A remote user can send specially crafted data to trigger a buffer overflow
in socket.recvfrom_into() and execute arbitrary code on the target system.
The code will run with the privileges of the target service.

This back-ported patch fixes CVE-2014-1912

Signed-off-by: Maxin B. John 
---
 .../python/python/python-2.7.3-CVE-2014-1912.patch |   26 
 meta/recipes-devtools/python/python_2.7.3.bb   |1 +
 2 files changed, 27 insertions(+)
 create mode 100644 
meta/recipes-devtools/python/python/python-2.7.3-CVE-2014-1912.patch

diff --git 
a/meta/recipes-devtools/python/python/python-2.7.3-CVE-2014-1912.patch 
b/meta/recipes-devtools/python/python/python-2.7.3-CVE-2014-1912.patch
new file mode 100644
index 000..02cc83d
--- /dev/null
+++ b/meta/recipes-devtools/python/python/python-2.7.3-CVE-2014-1912.patch
@@ -0,0 +1,26 @@
+Upstream-Status: Backport
+
+Reference: http://bugs.python.org/issue20246
+
+CVE-2014-1912: Python buffer overflow in socket.recvfrom_into()
+lets remote users execute arbitrary code.Original patch by Benjamin Peterson
+
+Signed-off-by: Maxin B. John 
+---
+diff -r 40fb60df4755 Modules/socketmodule.c
+--- a/Modules/socketmodule.c   Sun Jan 12 12:11:47 2014 +0200
 b/Modules/socketmodule.c   Mon Jan 13 16:36:35 2014 -0800
+@@ -2744,6 +2744,13 @@
+ recvlen = buflen;
+ }
+ 
++/* Check if the buffer is large enough */
++if (buflen < recvlen) {
++PyErr_SetString(PyExc_ValueError,
++"buffer too small for requested bytes");
++goto error;
++}
++
+ readlen = sock_recvfrom_guts(s, buf.buf, recvlen, flags, &addr);
+ if (readlen < 0) {
+ /* Return an error */
diff --git a/meta/recipes-devtools/python/python_2.7.3.bb 
b/meta/recipes-devtools/python/python_2.7.3.bb
index c7bb9b4..0d64172 100644
--- a/meta/recipes-devtools/python/python_2.7.3.bb
+++ b/meta/recipes-devtools/python/python_2.7.3.bb
@@ -35,6 +35,7 @@ SRC_URI += "\
   file://parallel-makeinst-create-bindir.patch \
   file://python-2.7.3-CVE-2013-1752-smtplib-fix.patch \
   file://python-fix-build-error-with-Readline-6.3.patch \
+  file://python-2.7.3-CVE-2014-1912.patch \
 "
 
 S = "${WORKDIR}/Python-${PV}"
-- 
1.7.10.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [dora][regression] mesa failed to build

2014-04-07 Thread Valentin Popa


Indeed the build failure was introduced by that patch, which enters a 
logical conflict with the bbappend file for mesa.
To remain compatible with the future releases I suggest to  not 
remove/add flags from/to EXTRA_OECONF explicitly, and make  use of what 
PACKAGECONFIG contains.
The first part of the __anonymous function from the bbappend file can be 
simply replaced with:


PACKAGECONFIG_remove = "egl"

and the second part with:

PROVIDES_remove = "virtual/libgles1 virtual/libgles2 virtual/egl"
and
PROVIDES_remove = "virtual/libgl" if mx6 is in SOC_FAMILY.



On 04/05/2014 07:50 AM, Robert Yang wrote:


Yes, seems related to the following one, add Valentin Popa in the loop:

commit bcfbddd8fa9760f681d7366c8d507fd0bef3a854
Author: Valentin Popa 
Date:   Thu Feb 27 11:51:17 2014 +0200

mesa: build fix for gallium-egl

// Robert

On 04/05/2014 12:38 PM, Otavio Salvador wrote:

Hello,

In one of our custom BSPs we saw a build failure in mesa:

| make[1]: Leaving directory
`.../build/tmp/work/cortexa9hf-vfp-neon-mx6-oel-linux-gnueabi/mesa/2_9.1.6-r0/build' 


| sed: can't read
.../build/tmp/work/cortexa9hf-vfp-neon-mx6-oel-linux-gnueabi/mesa/2_9.1.6-r0/image/usr/include/EGL/eglplatform.h: 


No such file or directory
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
.../build/tmp/work/cortexa9hf-vfp-neon-mx6-oel-linux-gnueabi/mesa/2_9.1.6-r0/temp/log.do_install.17155) 


recipe mesa-2_9.1.6-r0: task do_install: Failed
ERROR: Task 2643
(.../sources/poky/meta/recipes-graphics/mesa/mesa_9.1.6.bb,
do_install) failed with exit code '1'
recipe gnutls-2.12.23-r8.4: task do_configure: Succeeded

This seems not related to the bbappend we have in meta-fsl-arm[1], in
Dora. I think this came in today's changes in the branch.

1. 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-graphics/mesa/mesa_9.1.6.bbappend?h=dora


This builder has PRServer enabled.

As I am going to be traveling so won't have time to debug this bug I
preferred to report it so someone can debug.



--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] complex versioning scenario

2014-04-07 Thread Richard Purdie
On Mon, 2014-04-07 at 15:22 +0200, Steffen Sledz wrote:
> On 07.04.2014 14:37, Steffen Sledz wrote:
> > On 25.03.2014 16:03, Mark Hatle wrote:
> >> ...
> >> If the package 'requiring libfoo' has a DEPENDS += ... in it.. then yes, 
> >> it should have been rebuilt when the libfoo was rebuilt.
> > 
> > Unfortunately i can't confirm that.  :(
> > 
> > part of the real app recipe:
> > > snip <-
> > DEPENDS = "vala-native libdrtrace libdrhip libdrbcc jansson"
> > RDEPENDS_${PN} = "dropmodes"
> > > snap <-
> > 
> > part of the real resulting opkg control file for this app:
> > > snip <-
> > Depends: dropmodes, libglib-2.0-0 (>= 2.36.4), libdrhip1 (>= 
> > gitr27+42af787eb2), libjansson4 (>= 2.4), libc6 (>= 2.18)
> > > snap <-
> > 
> > I miss the runtime dependencies for libdrtrace and libdrbcc. Where are they 
> > gone?
> 
> Some additional info:
> > snip <-
> # objdump -p ./package/usr/lib/libdrhip.so.1.0.0
> 
> ./package/usr/lib/libdrhip.so.1.0.0: file format elf32-littlearm
> ...
> Dynamic Section:
>   NEEDED   libc.so.6
>   SONAME   libdrhip.so.1
> ...
> 
> # objdump -p ./package/usr/lib/libdrbcc.so.1.0.0
> 
> ./package/usr/lib/libdrbcc.so.1.0.0: file format elf32-littlearm
> ...
> Dynamic Section:
>   NEEDED   libdrtrace.so.0
>   NEEDED   libm.so.6
>   NEEDED   libreadline.so.6
>   NEEDED   libpthread.so.0
>   NEEDED   libc.so.6
>   SONAME   libdrbcc.so.1
> ...
> 
> # objdump -p ./package/usr/bin/drbccproxy
> 
> ./package/usr/bin/drbccproxy: file format elf32-littlearm
> ...
> Dynamic Section:
>   NEEDED   libdrhip.so.1
>   NEEDED   libdrbcc.so.0
>   NEEDED   libdrtrace.so.0
>   NEEDED   libgio-2.0.so.0
>   NEEDED   libgobject-2.0.so.0
>   NEEDED   libglib-2.0.so.0
>   NEEDED   libjansson.so.4
>   NEEDED   librt.so.1
>   NEEDED   libpthread.so.0
>   NEEDED   libc.so.6
> ...
> > snap <-
> 
> So it seems the data objdump shows are OK.
> 
> E.g. the app drbccproxy really has a dependency to a libdrbcc. But this is 
> not refelected in the control file.

At this point you'll probably have to look at the shlibs code in
package.bbclass and see why its not picking up the shlib dependencies
correctly for the packages...

It does appear there is some problem there but its hard to saw what
without a test case to reproduce.

Cheers,

Richard



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] complex versioning scenario

2014-04-07 Thread Steffen Sledz
On 07.04.2014 14:37, Steffen Sledz wrote:
> On 25.03.2014 16:03, Mark Hatle wrote:
>> ...
>> If the package 'requiring libfoo' has a DEPENDS += ... in it.. then yes, it 
>> should have been rebuilt when the libfoo was rebuilt.
> 
> Unfortunately i can't confirm that.  :(
> 
> part of the real app recipe:
> > snip <-
> DEPENDS = "vala-native libdrtrace libdrhip libdrbcc jansson"
> RDEPENDS_${PN} = "dropmodes"
> > snap <-
> 
> part of the real resulting opkg control file for this app:
> > snip <-
> Depends: dropmodes, libglib-2.0-0 (>= 2.36.4), libdrhip1 (>= 
> gitr27+42af787eb2), libjansson4 (>= 2.4), libc6 (>= 2.18)
> > snap <-
> 
> I miss the runtime dependencies for libdrtrace and libdrbcc. Where are they 
> gone?

Some additional info:
> snip <-
# objdump -p ./package/usr/lib/libdrhip.so.1.0.0

./package/usr/lib/libdrhip.so.1.0.0: file format elf32-littlearm
...
Dynamic Section:
  NEEDED   libc.so.6
  SONAME   libdrhip.so.1
...

# objdump -p ./package/usr/lib/libdrbcc.so.1.0.0

./package/usr/lib/libdrbcc.so.1.0.0: file format elf32-littlearm
...
Dynamic Section:
  NEEDED   libdrtrace.so.0
  NEEDED   libm.so.6
  NEEDED   libreadline.so.6
  NEEDED   libpthread.so.0
  NEEDED   libc.so.6
  SONAME   libdrbcc.so.1
...

# objdump -p ./package/usr/bin/drbccproxy

./package/usr/bin/drbccproxy: file format elf32-littlearm
...
Dynamic Section:
  NEEDED   libdrhip.so.1
  NEEDED   libdrbcc.so.0
  NEEDED   libdrtrace.so.0
  NEEDED   libgio-2.0.so.0
  NEEDED   libgobject-2.0.so.0
  NEEDED   libglib-2.0.so.0
  NEEDED   libjansson.so.4
  NEEDED   librt.so.1
  NEEDED   libpthread.so.0
  NEEDED   libc.so.6
...
> snap <-

So it seems the data objdump shows are OK.

E.g. the app drbccproxy really has a dependency to a libdrbcc. But this is not 
refelected in the control file.

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sl...@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] complex versioning scenario

2014-04-07 Thread Steffen Sledz
On 25.03.2014 16:03, Mark Hatle wrote:
> On 3/25/14, 5:31 AM, Steffen Sledz wrote:
>> On 24.03.2014 16:15, Martin Jansa wrote:
>>> On Mon, Mar 24, 2014 at 03:22:35PM +0100, Steffen Sledz wrote:
 On 24.03.2014 13:53, Richard Purdie wrote:
> On Mon, 2014-03-24 at 13:49 +0100, Steffen Sledz wrote:
>> On 24.03.2014 13:35, Richard Purdie wrote:
>>> On Mon, 2014-03-24 at 13:16 +0100, Steffen Sledz wrote:
 We've a complex versioning scenario here which leads me to my limits. 
 :(

 There are two recipes. One for a shared library and one for an 
 application using this library.

 Both use GNU autotools (so they have internal version information). 
 For continuous integration purposes both use AUTOREV.

 At the moment the recipes look like this:


  libfoo_git.bb - PR = "r7" PE = "2" 
 SRCREV="${AUTOREV}" PV = "gitr${SRCPV}" ...


  app_git.bb  DEPENDS = "... libfoo ..." PR 
 = "r10" PE = "1" SRCREV="${AUTOREV}" PV = "gitr${SRCPV}" ...


 Now we have the following problem. libfoo has some incompatible 
 changes in its interface (a new internal major version).

 In my opinion this should find its represenation in the package 
 versioning in a way that the dependency checker can guarantee that the 
 library and the application package match each other.
>>>
>>> It is generally impossible to directly compare two git hashes and 
>>> decide whether one is "greater" than the other. This is why most git 
>>> recipes have PV = "0.0+git${SRCPV}" so that you can change 0.0 when 
>>> something major changes. That way you can put a constraint in the 
>>> second recipe.
>>>
>>> This is a fundamental problem with git versioning and not something we 
>>> can fix generically.
>>
>> To have an order in the git based versions we use the PRSERV method. 
>> This works well.
>>
>> But this does not help here. The change in the library interface leads 
>> directly to a new version of the library package itself (e.g. from 
>> libfoo0_gitr100+somehash to libfoo0_gitr101+someotherhash). But i need 
>> something i can write into the DEPENDS list of the application. :(
>>
>> Steffen
>>
>> BTW: Where comes the 0 in libfoo0 from?
>
> debian.bbclass (debian package naming) which I believe in turn is derived 
> from the actual library version.
>
> Its a class specific implementation so you can't depend on it in version 
> information though.

 But where does it come from? A bb variable?
>>>
>>> SONAME header in library
>>>
>>> so if you're using debian.bbclass and change ABI then you should just 
>>> increase major version in SONAME (that way your foo will rdepend on libfoo0 
>>> until it's rebuilt against newer libfoo1).
>>
>> Thanx, this was the decisive hint.
>>
>> I've increased the version in the SONAME header of the library and the 
>> result is a libfoo1 package. :)
>>
>> But now i hit the next problem. The following rootfs stage results in this 
>> error:
>>
>> ---> snip <-
>> | Collected errors:
>> |  * satisfy_dependencies_for: Cannot satisfy the following dependencies for 
>> app:
>> |  *libfoo0 (>= gitr101+somehash) *
>> ---> snap <-
>>
>> Should the new build of libfoo1 trigger a new compile of all packages with 
>> DEPENDS containing libfoo?
>>
> 
> If the package 'requiring libfoo' has a DEPENDS += ... in it.. then yes, it 
> should have been rebuilt when the libfoo was rebuilt.

Unfortunately i can't confirm that.  :(

part of the real app recipe:
> snip <-
DEPENDS = "vala-native libdrtrace libdrhip libdrbcc jansson"
RDEPENDS_${PN} = "dropmodes"
> snap <-

part of the real resulting opkg control file for this app:
> snip <-
Depends: dropmodes, libglib-2.0-0 (>= 2.36.4), libdrhip1 (>= 
gitr27+42af787eb2), libjansson4 (>= 2.4), libc6 (>= 2.18)
> snap <-

I miss the runtime dependencies for libdrtrace and libdrbcc. Where are they 
gone?

-- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sl...@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 1/1] trace-cmd/kernelshark: update to 2.3.2 release (latest stable branch)

2014-04-07 Thread Richard Purdie
On Mon, 2014-04-07 at 15:10 +0300, Fathi Boudra wrote:
>  * drop all the patches - not needed anymore
>  * update SRCREV and PV to 2.3.2 tag
>  * drop PR
>  * update SRC_URI to use trace-cmd-stable-v2.3 branch
>  * drop EXTRA_OEMAKE - not needed
>  * update do_install and pass NO_PYTHON/prefix/plugin_dir
>  * update trace-input.c md5 sum - FSF address has been updated
>  * oe stylize the recipes

There is too much going on in this patch to make it easy to review. In
particular, style changes should be put into a separate patch. I'd like
to better understand why the patches aren't needed too. Were patches
merged upstream which accounted for these issues? including the docs?

Cheers,

Richard

> 
> Signed-off-by: Fathi Boudra 
> ---
>  .../{kernelshark_1.2.bb => kernelshark_2.3.2.bb}   | 32 
>  .../trace-cmd/trace-cmd/addldflags.patch   | 51 
>  .../trace-cmd/blktrace-api-compatibility.patch | 29 ---
>  .../trace-cmd/trace-cmd/make-docs-optional.patch   | 36 
>  ...dd-checks-for-invalid-pointers-to-fix-seg.patch | 61 --
>  ...o-not-call-stop_threads-if-doing-latency-.patch | 38 -
>  ...etting-plugin-to-nop-clears-data-before-i.patch | 96 
> --
>  .../{trace-cmd_1.2.bb => trace-cmd_2.3.2.bb}   | 27 ++
>  8 files changed, 23 insertions(+), 347 deletions(-)
>  rename meta/recipes-kernel/trace-cmd/{kernelshark_1.2.bb => 
> kernelshark_2.3.2.bb} (51%)
>  delete mode 100644 meta/recipes-kernel/trace-cmd/trace-cmd/addldflags.patch
>  delete mode 100644 
> meta/recipes-kernel/trace-cmd/trace-cmd/blktrace-api-compatibility.patch
>  delete mode 100644 
> meta/recipes-kernel/trace-cmd/trace-cmd/make-docs-optional.patch
>  delete mode 100644 
> meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-Add-checks-for-invalid-pointers-to-fix-seg.patch
>  delete mode 100644 
> meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-Do-not-call-stop_threads-if-doing-latency-.patch
>  delete mode 100644 
> meta/recipes-kernel/trace-cmd/trace-cmd/trace-cmd-Setting-plugin-to-nop-clears-data-before-i.patch
>  rename meta/recipes-kernel/trace-cmd/{trace-cmd_1.2.bb => 
> trace-cmd_2.3.2.bb} (41%)
> 
> diff --git a/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb 
> b/meta/recipes-kernel/trace-cmd/kernelshark_2.3.2.bb
> similarity index 51%
> rename from meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
> rename to meta/recipes-kernel/trace-cmd/kernelshark_2.3.2.bb
> index 9268a50..545244e 100644
> --- a/meta/recipes-kernel/trace-cmd/kernelshark_1.2.bb
> +++ b/meta/recipes-kernel/trace-cmd/kernelshark_2.3.2.bb
> @@ -2,28 +2,26 @@ SUMMARY = "Graphical trace viewer for Ftrace"
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
>  
> file://kernel-shark.c;beginline=6;endline=8;md5=2c22c965a649ddd7973d7913c5634a5e"
> -
> -SRCREV = "7055ffd37beeb44714e86a4abc703f7e175a0db5"
> -PR = "r3"
> -PV = "1.2+git${SRCPV}"
> -
>  DEPENDS = "gtk+"
> -RDEPENDS_${PN} = "trace-cmd"
> +SRCREV = "79e08f8edb38c4c5098486caaa87ca90ba00f547"
> +PV = "2.3.2"
>  
> -inherit pkgconfig pythonnative
> +SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git;branch=trace-cmd-stable-v2.3
>  \
> +"
>  
> -SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git \
> -   file://addldflags.patch \
> -   file://make-docs-optional.patch \
> -   file://blktrace-api-compatibility.patch"
>  S = "${WORKDIR}/git"
>  
> -EXTRA_OEMAKE = "'CC=${CC}' 'AR=${AR}' 'prefix=${prefix}' gui"
> -
> -FILESPATH = "${FILE_DIRNAME}/trace-cmd"
> +inherit pkgconfig pythonnative
>  
>  do_install() {
> - oe_runmake CC="${CC}" AR="${AR}" prefix="${prefix}" DESTDIR="${D}" 
> install_gui
> - rm -rf ${D}${datadir}/trace-cmd
> - rmdir ${D}${datadir}
> +${MAKE} NO_PYTHON=1 prefix=${prefix} 
> plugin_dir=${libdir}/trace-cmd/plugins DESTDIR=${D} install_gui
> +
> +# remove files already shipped in trace-cmd package
> +rm -f ${D}${bindir}/trace-cmd
> +rm -rf ${D}${libdir}/trace-cmd
> +rmdir ${D}${libdir}
>  }
> +
> +RDEPENDS_${PN} = "trace-cmd"
> +
> +FILESPATH = "${FILE_DIRNAME}/trace-cmd"
> diff --git a/meta/recipes-kernel/trace-cmd/trace-cmd/addldflags.patch 
> b/meta/recipes-kernel/trace-cmd/trace-cmd/addldflags.patch
> deleted file mode 100644
> index 14730db..000
> --- a/meta/recipes-kernel/trace-cmd/trace-cmd/addldflags.patch
> +++ /dev/null
> @@ -1,51 +0,0 @@
> -trace-cmd: Cross-compile fixes for LDFLAGS and include path
> -
> -Add ability for the Makefile to respect LDFLAGS.
> -Also remove hardcoded /usr/local/include include path.
> -
> -Upstream-Status: Accepted [Post 1.2: 
> 5f576e9af7ad706774d9764a9ae3989376797c0e]
> -
> -Signed-off-by: Richard Purdie 
> -Signed-off-by: Darren Hart 
> -
> 
> - Makefile |7 ---
> - 1 file changed, 4 insertions(+), 3 deletions(-)
> -
> -Index: git/Makefile
> -=

[OE-core] [PATCH] package.bbclass: Add CONFFILES to list of package specific variables

2014-04-07 Thread Richard Purdie
Changes to CONFFILES should change the sstate checksum. To make that happen,
it needs to be listed in the list of package specific variables, therefore
add it.

Signed-off-by: Richard Purdie 
---
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 0018a62..ea75918 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1847,7 +1847,7 @@ python package_depchains() {
 
 # Since bitbake can't determine which variables are accessed during package
 # iteration, we need to list them here:
-PACKAGEVARS = "FILES RDEPENDS RRECOMMENDS SUMMARY DESCRIPTION RSUGGESTS 
RPROVIDES RCONFLICTS PKG ALLOW_EMPTY pkg_postinst pkg_postrm INITSCRIPT_NAME 
INITSCRIPT_PARAMS DEBIAN_NOAUTONAME ALTERNATIVE PKGE PKGV PKGR USERADD_PARAM 
GROUPADD_PARAM"
+PACKAGEVARS = "FILES RDEPENDS RRECOMMENDS SUMMARY DESCRIPTION RSUGGESTS 
RPROVIDES RCONFLICTS PKG ALLOW_EMPTY pkg_postinst pkg_postrm INITSCRIPT_NAME 
INITSCRIPT_PARAMS DEBIAN_NOAUTONAME ALTERNATIVE PKGE PKGV PKGR USERADD_PARAM 
GROUPADD_PARAM CONFFILES"
 
 def gen_packagevar(d):
 ret = []


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 3/3] binconfig.bbclass: fix multilib file conflicts

2014-04-07 Thread Richard Purdie
On Mon, 2014-04-07 at 19:27 +0800, Ming Liu wrote:
> In most cases binconfig files conflict among multilib packages, to avoid
> that, use update-alternatives link *-config from real path with a
> PACKAGE_ARCH suffix.
> 
> Signed-off-by: Ming Liu 
> ---
>  meta/classes/binconfig.bbclass | 65 
> --
>  1 file changed, 56 insertions(+), 9 deletions(-)

This isn't going in, its complex and supports a minority use case.
binconfig should be dying out, not being extended and shored up like
this.

I'd also add this patch is buggy, its pure luck that update-alternatives
is available at rootfs generation time since its not in a visible
dependency.

So going forward I'd like to see patches which simply delete binconfig
scripts. Where there isn't a .pc alternative we should be adding them
and pushing them upstream.

Cheers,

Richard



-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 2/3] freetype: fix multilib header conflict - ftconfig.h

2014-04-07 Thread Ming Liu
ftconfig.h conflicts between 32-bit and 64-bit versions.

Signed-off-by: Ming Liu 
---
 meta/recipes-graphics/freetype/freetype_2.5.2.bb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/freetype/freetype_2.5.2.bb 
b/meta/recipes-graphics/freetype/freetype_2.5.2.bb
index b93453a..0c62a67 100644
--- a/meta/recipes-graphics/freetype/freetype_2.5.2.bb
+++ b/meta/recipes-graphics/freetype/freetype_2.5.2.bb
@@ -21,7 +21,7 @@ SRC_URI[sha256sum] = 
"4ff4bd393aa01071ec7b849d035508a505a78f88b2bcf25ff11e58e43c
 
 S = "${WORKDIR}/freetype-${PV}"
 
-inherit autotools-brokensep pkgconfig binconfig
+inherit autotools-brokensep pkgconfig binconfig multilib_header
 
 LIBTOOL = "${S}/builds/unix/${HOST_SYS}-libtool"
 EXTRA_OEMAKE = "'LIBTOOL=${LIBTOOL}'"
@@ -50,5 +50,9 @@ do_compile_prepend() {
${BUILD_CC} -o objs/apinames src/tools/apinames.c
 }
 
+do_install_append() {
+   oe_multilib_header freetype2/config/ftconfig.h
+}
+
 BBCLASSEXTEND = "native"
 
-- 
1.8.4.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 3/3] binconfig.bbclass: fix multilib file conflicts

2014-04-07 Thread Ming Liu
In most cases binconfig files conflict among multilib packages, to avoid
that, use update-alternatives link *-config from real path with a
PACKAGE_ARCH suffix.

Signed-off-by: Ming Liu 
---
 meta/classes/binconfig.bbclass | 65 --
 1 file changed, 56 insertions(+), 9 deletions(-)

diff --git a/meta/classes/binconfig.bbclass b/meta/classes/binconfig.bbclass
index 7158c8c..c5503b7 100644
--- a/meta/classes/binconfig.bbclass
+++ b/meta/classes/binconfig.bbclass
@@ -1,4 +1,4 @@
-FILES_${PN}-dev += "${bindir}/*-config"
+FILES_${PN}-dev += "${bindir}/*-config.${PACKAGE_ARCH}"
  
 # The namespaces can clash here hence the two step replace
 def get_binconfig_mangle(d):
@@ -31,14 +31,21 @@ BINCONFIG_GLOB ?= "*-config"
 PACKAGE_PREPROCESS_FUNCS += "binconfig_package_preprocess"
 
 binconfig_package_preprocess () {
-   for config in `find ${PKGD} -name '${BINCONFIG_GLOB}'`; do
-   sed -i \
-   -e 's:${STAGING_BASELIBDIR}:${base_libdir}:g;' \
-   -e 's:${STAGING_LIBDIR}:${libdir}:g;' \
-   -e 's:${STAGING_INCDIR}:${includedir}:g;' \
-   -e 's:${STAGING_DATADIR}:${datadir}:' \
-   -e 's:${STAGING_DIR_HOST}${prefix}:${prefix}:' \
-$config
+   for config in `find ${PKGD}${bindir} -name '${BINCONFIG_GLOB}'`; do
+   if [ -h $config ]; then
+   real_config=`readlink $config`
+   unlink $config
+   ( cd ${PKGD}${bindir} ; ln -sf 
$real_config.${PACKAGE_ARCH} $config.${PACKAGE_ARCH} )
+   else
+   sed -i \
+   -e 's:${STAGING_BASELIBDIR}:${base_libdir}:g;' \
+   -e 's:${STAGING_LIBDIR}:${libdir}:g;' \
+   -e 's:${STAGING_INCDIR}:${includedir}:g;' \
+   -e 's:${STAGING_DATADIR}:${datadir}:' \
+   -e 's:${STAGING_DIR_HOST}${prefix}:${prefix}:' \
+   $config
+   mv $config $config.${PACKAGE_ARCH}
+   fi
done
for lafile in `find ${PKGD} -name "*.la"` ; do
sed -i \
@@ -51,6 +58,46 @@ binconfig_package_preprocess () {
done
 }
 
+BINCONFIG_PRIORITY ?= 
"${@int(d.getVar('PV',1).split('-')[0].split('+')[0].split('.')[0]) * 1 + \
+   
int(d.getVar('PV',1).split('-')[0].split('+')[0].split('.')[1]) * 100 + \
+   
int(d.getVar('PV',1).split('-')[0].split('+')[0].split('.')[-1])}"
+
+PACKAGESPLITFUNCS_prepend = "populate_packages_binconfig "
+
+#
+# Fix binconfig conflicts among multilib packages
+#
+python populate_packages_binconfig () {
+import os, glob
+
+pkg = d.getVar('PN', True) + '-dev'
+dvar = d.getVar('PKGD', True)
+bindir = d.getVar('bindir', True)
+binconfig_glob = d.getVar('BINCONFIG_GLOB', True)
+binconfig_priority = d.getVar('BINCONFIG_PRIORITY', True)
+binconfig_setup_links = ""
+binconfig_remove_links = ""
+for file in glob.glob(dvar + bindir + os.sep + binconfig_glob + '.' + 
d.getVar('PACKAGE_ARCH', True)):
+binconfig_target = os.path.basename(file)
+binconfig_name = binconfig_target[:binconfig_target.find('.')]
+binconfig_link = bindir + os.sep + binconfig_name
+binconfig_setup_links += '\tupdate-alternatives --install %s %s %s 
%s\n' % (binconfig_link, binconfig_name, binconfig_target, binconfig_priority)
+binconfig_remove_links += '\tupdate-alternatives --remove  %s %s\n' % 
(binconfig_name, binconfig_target)
+
+if binconfig_setup_links:
+provider = d.getVar('VIRTUAL-RUNTIME_update-alternatives', True)
+if provider:
+d.appendVar('RDEPENDS_%s' % pkg, ' ' + d.getVar('MLPREFIX') + 
provider)
+
+postinst = d.getVar('pkg_postinst_%s' % pkg, True) or '#!/bin/sh\n'
+postinst += binconfig_setup_links
+d.setVar('pkg_postinst_%s' % pkg, postinst)
+
+postrm = d.getVar('pkg_postrm_%s' % pkg, True) or '#!/bin/sh\n'
+postrm += binconfig_remove_links
+d.setVar('pkg_postrm_%s' % pkg, postrm)
+}
+
 SYSROOT_PREPROCESS_FUNCS += "binconfig_sysroot_preprocess"
 
 binconfig_sysroot_preprocess () {
-- 
1.8.4.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 1/3] e2fsprogs: fix multilib header conflict - ext2_types.h

2014-04-07 Thread Ming Liu
ext2_types.h conflicts between 32-bit and 64-bit versions.

Signed-off-by: Ming Liu 
---
 meta/recipes-devtools/e2fsprogs/e2fsprogs.inc   | 3 +--
 meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb | 2 ++
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
index a34df37..99447c1 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs.inc
@@ -22,5 +22,4 @@ DEPENDS = "util-linux"
 SRC_URI = "${SOURCEFORGE_MIRROR}/e2fsprogs/e2fsprogs-${PV}.tar.gz \
file://mkdir.patch"
 
-inherit autotools gettext pkgconfig
-
+inherit autotools gettext pkgconfig multilib_header
diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb
index 3a5d6ee..2bdd724 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.9.bb
@@ -52,6 +52,8 @@ do_install () {
mv ${D}${base_libdir}/e2initrd_helper ${D}${libdir}
mv ${D}${base_libdir}/pkgconfig ${D}${libdir}
fi
+
+   oe_multilib_header ext2fs/ext2_types.h
 }
 
 RDEPENDS_e2fsprogs = "e2fsprogs-badblocks"
-- 
1.8.4.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH][review-request] toaster.bbclass: image file is missing a "/"

2014-04-07 Thread Cristiana Voicu
Relaced the key with the join between path and file name.

[YOCTO #6090]
Signed-off-by: Cristiana Voicu 
---
 meta/classes/toaster.bbclass |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/toaster.bbclass b/meta/classes/toaster.bbclass
index 9fb2cec..d2fa82d 100644
--- a/meta/classes/toaster.bbclass
+++ b/meta/classes/toaster.bbclass
@@ -153,7 +153,8 @@ python toaster_image_dumpdata() {
 for dirpath, dirnames, filenames in os.walk(deploy_dir_image):
 for fn in filenames:
 if fn.startswith(image_name):
-image_info_data[dirpath + fn] = os.stat(os.path.join(dirpath, 
fn)).st_size
+image_output = os.path.join(dirpath, fn)
+image_info_data[image_output] = os.stat(image_output).st_size
 
 bb.event.fire(bb.event.MetadataEvent("ImageFileSize",image_info_data), d)
 }
-- 
1.7.9.5

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 08/15] toaster.bbclass: image file is missing a "/"

2014-04-07 Thread Voicu, Cristiana
I will resend the patch directly to this mailing list, since it has been 
reviewed on toaster ml.
Cristiana

-Original Message-
From: openembedded-core-boun...@lists.openembedded.org 
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Richard 
Purdie
Sent: Friday, April 4, 2014 5:15 PM
To: Damian, Alexandru
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 08/15] toaster.bbclass: image file is missing a 
"/"

On Fri, 2014-04-04 at 15:05 +0100, Alex DAMIAN wrote:
> From: Cristiana Voicu 
> 
> Relaced the key with the join between path and file name.
> 
> [YOCTO #6090]
> 
> Signed-off-by: Cristiana Voicu 
> ---
>  meta/classes/toaster.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/toaster.bbclass 
> b/meta/classes/toaster.bbclass index 9fb2cec..d2fa82d 100644
> --- a/meta/classes/toaster.bbclass
> +++ b/meta/classes/toaster.bbclass
> --
> 1.9.1

This patch does not look right...

Cheers,

Richard

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] documentation.conf (LICENSE): tiny addition

2014-04-07 Thread Matthieu Crapet
Examples:

LICENSE = "MIT"
LICENSE = "GPLv2 & LGPLv2.1"
LICENSE = "AFL-2 | GPLv2+"
LICENSE = "MIT & BSD-3-Clause & BSD-2-Clause & PD"
LICENSE = "GPLv2 & (LGPLv2.1 | MPL-1.1 | BSD)"
LICENSE = "GPLv2+ & LGPLv2+ & ( (GPLv2+ & LGPLv2.1+) | (GPLv3+ & LGPLv3+) )"

Signed-off-by: Matthieu Crapet 
---
 meta/conf/documentation.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index 9d6e78f..7fa3f31 100644
--- a/meta/conf/documentation.conf
+++ b/meta/conf/documentation.conf
@@ -253,7 +253,7 @@ LAYERDIR[doc] = "When used inside the layer.conf 
configuration file, this variab
 LAYERVERSION[doc] = "Optionally specifies the version of a layer as a single 
number. This variable is used in the conf/layer.conf file and must be suffixed 
with the name of the specific layer."
 LEAD_SONAME[doc] = "Specifies the lead (or primary) compiled library file 
(.so) that the debian class applies its naming policy to given a recipe that 
packages multiple libraries."
 LIC_FILES_CHKSUM[doc] = "Checksums of the license text in the recipe source 
code."
-LICENSE[doc] = "The list of source licenses for the recipe."
+LICENSE[doc] = "The list of source licenses for the recipe. Logical operators 
'&' or '|' and parentheses can be used."
 LICENSE_PATH[doc] = "Path to additional licenses used during the build."
 LINUX_KERNEL_TYPE[doc] = "Defines the kernel type to be used in assembling the 
configuration."
 LINUX_VERSION[doc] = "The Linux version from kernel.org on which the Linux 
kernel image being built using the OpenEmbedded build system is based. You 
define this variable in the kernel recipe."
-- 
1.8.5.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core