[OE-core] [PATCH] meta: start to ignore the largefile distro feature

2017-03-06 Thread Andre McCurdy
The largefile distro feature has been enabled by default in oe-core
for a long time and, more recently, also in poky-tiny. Building
without the largefile distro feature receives little or no testing.
Many packages now enable LFS without exposing a configure option, so
there should be very little expectation that disabling the distro
feature will result in a distro which globally disables LFS.

Respecting the distro feature adds a maintenance over-head and may be
the source of configurations oddities (e.g. dbus-native currently
builds with LFS disabled for no clear reason - fixed by this commit).

Ignore the largefile distro feature more widely, as a first step
towards deprecating and eventually removing it.

Signed-off-by: Andre McCurdy 
---
 meta/recipes-bsp/grub/grub-efi_2.00.bb   |  6 +++---
 meta/recipes-bsp/grub/grub_2.00.bb   |  6 +++---
 meta/recipes-bsp/grub/grub_git.bb|  6 +++---
 meta/recipes-core/dbus/dbus_1.10.14.bb   |  4 ++--
 meta/recipes-devtools/cmake/cmake_3.7.2.bb   |  2 +-
 meta/recipes-devtools/dosfstools/dosfstools_2.11.bb  |  2 +-
 meta/recipes-devtools/dosfstools/dosfstools_4.1.bb   |  2 +-
 meta/recipes-devtools/pax-utils/pax-utils_1.2.2.bb   |  7 ---
 meta/recipes-devtools/perl/perl_5.24.1.bb| 13 -
 meta/recipes-extended/libarchive/libarchive_3.2.2.bb |  7 +++
 meta/recipes-extended/lighttpd/lighttpd_1.4.45.bb|  5 +++--
 11 files changed, 24 insertions(+), 36 deletions(-)

diff --git a/meta/recipes-bsp/grub/grub-efi_2.00.bb 
b/meta/recipes-bsp/grub/grub-efi_2.00.bb
index e050301..e12f1d7 100644
--- a/meta/recipes-bsp/grub/grub-efi_2.00.bb
+++ b/meta/recipes-bsp/grub/grub-efi_2.00.bb
@@ -31,9 +31,9 @@ inherit deploy
 CACHED_CONFIGUREVARS += "ac_cv_path_HELP2MAN="
 EXTRA_OECONF = "--with-platform=efi --disable-grub-mkfont \
 --enable-efiemu=no --program-prefix='' \
---enable-liblzma=no --enable-device-mapper=no 
--enable-libzfs=no"
-
-EXTRA_OECONF += "${@bb.utils.contains('DISTRO_FEATURES', 'largefile', 
'--enable-largefile', '--disable-largefile', d)}"
+--enable-liblzma=no --enable-device-mapper=no 
--enable-libzfs=no \
+--enable-largefile \
+"
 
 # ldm.c:114:7: error: trampoline generated for nested function 'hook' 
[-Werror=trampolines]
 # and many other places in the grub code when compiled with some native gcc 
compilers (specifically, gentoo)
diff --git a/meta/recipes-bsp/grub/grub_2.00.bb 
b/meta/recipes-bsp/grub/grub_2.00.bb
index 07e1d10..c382938 100644
--- a/meta/recipes-bsp/grub/grub_2.00.bb
+++ b/meta/recipes-bsp/grub/grub_2.00.bb
@@ -4,9 +4,9 @@ RDEPENDS_${PN} = "diffutils freetype grub-editenv"
 PR = "r1"
 
 EXTRA_OECONF = "--with-platform=pc --disable-grub-mkfont --program-prefix="" \
-   --enable-liblzma=no --enable-device-mapper=no 
--enable-libzfs=no"
-
-EXTRA_OECONF += "${@bb.utils.contains('DISTRO_FEATURES', 'largefile', 
'--enable-largefile', '--disable-largefile', d)}"
+--enable-liblzma=no --enable-device-mapper=no 
--enable-libzfs=no \
+--enable-largefile \
+"
 
 PACKAGES =+ "grub-editenv"
 
diff --git a/meta/recipes-bsp/grub/grub_git.bb 
b/meta/recipes-bsp/grub/grub_git.bb
index 27a5d1f..0a81e53 100644
--- a/meta/recipes-bsp/grub/grub_git.bb
+++ b/meta/recipes-bsp/grub/grub_git.bb
@@ -27,9 +27,9 @@ GRUBPLATFORM_aarch64 = "efi"
 GRUBPLATFORM ??= "pc"
 
 EXTRA_OECONF = "--with-platform=${GRUBPLATFORM} --disable-grub-mkfont 
--program-prefix="" \
---enable-liblzma=no --enable-device-mapper=no 
--enable-libzfs=no"
-
-EXTRA_OECONF += "${@bb.utils.contains('DISTRO_FEATURES', 'largefile', 
'--enable-largefile', '--disable-largefile', d)}"
+--enable-liblzma=no --enable-device-mapper=no 
--enable-libzfs=no \
+--enable-largefile \
+"
 
 do_install_append () {
 install -d ${D}${sysconfdir}/grub.d
diff --git a/meta/recipes-core/dbus/dbus_1.10.14.bb 
b/meta/recipes-core/dbus/dbus_1.10.14.bb
index 6354572..e1d7356 100644
--- a/meta/recipes-core/dbus/dbus_1.10.14.bb
+++ b/meta/recipes-core/dbus/dbus_1.10.14.bb
@@ -95,18 +95,18 @@ EXTRA_OECONF = "--disable-tests \
 --disable-xml-docs \
 --disable-doxygen-docs \
 --disable-libaudit \
+--enable-largefile \
 "
 
 EXTRA_OECONF_append_class-target = " SYSTEMCTL=${base_bindir}/systemctl"
 EXTRA_OECONF_append_class-native = " --disable-selinux"
 
-PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'largefile systemd 
x11', d)}"
+PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd x11', d)}"
 PACKAGECONFIG_class-native = ""
 PACKAGECONFIG_class-nativesdk = ""
 
 PACKAGECONFIG[systemd] = "--enable-systemd 
--with-systemdsystemunitdir=${systemd_system_unitdir},--disable-systemd 
--without-systemdsystemunitdir,systemd"
 PACKAGECONFIG[x11] = "--with-x 

[OE-core] [PATCH] dropbear: drop support for DSA host keys in dropbear init script

2017-03-06 Thread Andre McCurdy
Bring the dropbear init script into sync with the systemd service
file (dropbearkey.service supports RSA host keys only) and with
recent versions of openssh which deprecate DSA host keys.

  https://www.gentoo.org/support/news-items/2015-08-13-openssh-weak-keys.html

Signed-off-by: Andre McCurdy 
---
 meta/recipes-core/dropbear/dropbear/init | 36 ++--
 1 file changed, 6 insertions(+), 30 deletions(-)

diff --git a/meta/recipes-core/dropbear/dropbear/init 
b/meta/recipes-core/dropbear/dropbear/init
index 434bd6b..f6e1c46 100755
--- a/meta/recipes-core/dropbear/dropbear/init
+++ b/meta/recipes-core/dropbear/dropbear/init
@@ -40,49 +40,28 @@ done
 if [ $readonly_rootfs = "1" ]; then
   mkdir -p /var/lib/dropbear
   DROPBEAR_RSAKEY_DEFAULT="/var/lib/dropbear/dropbear_rsa_host_key"
-  DROPBEAR_DSSKEY_DEFAULT="/var/lib/dropbear/dropbear_dss_host_key"
 else
   DROPBEAR_RSAKEY_DEFAULT="/etc/dropbear/dropbear_rsa_host_key"
-  DROPBEAR_DSSKEY_DEFAULT="/etc/dropbear/dropbear_dss_host_key"
 fi
 
 test -z "$DROPBEAR_BANNER" || \
   DROPBEAR_EXTRA_ARGS="$DROPBEAR_EXTRA_ARGS -b $DROPBEAR_BANNER"
 test -n "$DROPBEAR_RSAKEY" || \
   DROPBEAR_RSAKEY=$DROPBEAR_RSAKEY_DEFAULT
-test -n "$DROPBEAR_DSSKEY" || \
-  DROPBEAR_DSSKEY=$DROPBEAR_DSSKEY_DEFAULT
-test -n "$DROPBEAR_KEYTYPES" || \
-  DROPBEAR_KEYTYPES="rsa"
 
 gen_keys() {
-for t in $DROPBEAR_KEYTYPES; do
-  case $t in
-rsa)
-if [ -f "$DROPBEAR_RSAKEY" -a ! -s "$DROPBEAR_RSAKEY" ]; then
-rm $DROPBEAR_RSAKEY || true
-fi
-test -f $DROPBEAR_RSAKEY || dropbearkey -t rsa -f $DROPBEAR_RSAKEY 
$DROPBEAR_RSAKEY_ARGS
-   ;;
-dsa)
-if [ -f "$DROPBEAR_DSSKEY" -a ! -s "$DROPBEAR_DSSKEY" ]; then
-rm $DROPBEAR_DSSKEY || true
-fi
-test -f $DROPBEAR_DSSKEY || dropbearkey -t dss -f $DROPBEAR_DSSKEY 
$DROPBEAR_DSSKEY_ARGS
-   ;;
-  esac
-done
+if [ -f "$DROPBEAR_RSAKEY" -a ! -s "$DROPBEAR_RSAKEY" ]; then
+rm $DROPBEAR_RSAKEY || true
+fi
+test -f $DROPBEAR_RSAKEY || dropbearkey -t rsa -f $DROPBEAR_RSAKEY 
$DROPBEAR_RSAKEY_ARGS
 }
 
 case "$1" in
   start)
echo -n "Starting $DESC: "
gen_keys
-   KEY_ARGS=""
-   test -f $DROPBEAR_DSSKEY && KEY_ARGS="$KEY_ARGS -d $DROPBEAR_DSSKEY"
-   test -f $DROPBEAR_RSAKEY && KEY_ARGS="$KEY_ARGS -r $DROPBEAR_RSAKEY"
start-stop-daemon -S -p $PIDFILE \
- -x "$DAEMON" -- $KEY_ARGS \
+ -x "$DAEMON" -- -r $DROPBEAR_RSAKEY \
-p "$DROPBEAR_PORT" $DROPBEAR_EXTRA_ARGS
echo "$NAME."
;;
@@ -95,11 +74,8 @@ case "$1" in
echo -n "Restarting $DESC: "
start-stop-daemon -K -x "$DAEMON" -p $PIDFILE
sleep 1
-   KEY_ARGS=""
-   test -f $DROPBEAR_DSSKEY && KEY_ARGS="$KEY_ARGS -d $DROPBEAR_DSSKEY"
-   test -f $DROPBEAR_RSAKEY && KEY_ARGS="$KEY_ARGS -r $DROPBEAR_RSAKEY"
start-stop-daemon -S -p $PIDFILE \
- -x "$DAEMON" -- $KEY_ARGS \
+ -x "$DAEMON" -- -r $DROPBEAR_RSAKEY \
-p "$DROPBEAR_PORT" $DROPBEAR_EXTRA_ARGS
echo "$NAME."
;;
-- 
1.9.1

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


Re: [OE-core] [PATCH] conf/machine/include: enable hardfloat by default for ARMv6 and above

2017-03-06 Thread Khem Raj
On Mon, Mar 6, 2017 at 2:51 PM Andre McCurdy  wrote:

> On Mon, Mar 6, 2017 at 2:37 PM, Khem Raj  wrote:
> > On Mon, Mar 6, 2017 at 1:47 PM, Andre McCurdy 
> wrote:
> >> Defaulting to softfp probably isn't the best choice anymore,
> >> especially as there are now ARM BSP layers which leave DEFAULTTUNE
> >> entirely up to the distro:
> >>
> >>
> https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html
> >>
> >
> > I like this patch and want to clarify that it changes the default ISA to
> thumb2
> > which we should use anyway due to size reasons and other distros use it
> as
> > default too.
>
> No, it doesn't.


That's right I wanted to say to make that default while you are at it

The choice between ARM and Thumb(2) is made by the
> ARM_INSTRUCTION_SET variable. Adding 't' to DEFAULTTUNE simply means
> that the ARM_INSTRUCTION_SET variable will not be ignored (it's really
> a long standing bug that we ever defined DEFAULTTUNE options for ARMv6
> and above which ignore ARM_INSTRUCTION_SET, but that's a separate
> topic).
>
> > I am not sure of we should change it for armv6 though. since some armv6
> > has t1 and some has t2 so lets leave that as it is.
>
> I'm not aware of any ARMv6 cores which don't support Thumb2. Do you
> have a reference?
>
> (But again, to be clear, this commit doesn't change the default in
> terms of instruction set - all builds will still use ARM).
>
> >> Signed-off-by: Andre McCurdy 
> >> ---
> >>  meta/conf/machine/include/arm/arch-armv6.inc   | 2 +-
> >>  meta/conf/machine/include/arm/arch-armv7a.inc  | 2 +-
> >>  meta/conf/machine/include/arm/arch-armv7ve.inc | 2 +-
> >>  meta/conf/machine/include/tune-arm1136jf-s.inc | 2 +-
> >>  meta/conf/machine/include/tune-cortexa15.inc   | 2 +-
> >>  meta/conf/machine/include/tune-cortexa17.inc   | 2 +-
> >>  meta/conf/machine/include/tune-cortexa5.inc| 2 +-
> >>  meta/conf/machine/include/tune-cortexa7.inc| 2 +-
> >>  meta/conf/machine/include/tune-cortexa8.inc| 2 +-
> >>  meta/conf/machine/include/tune-cortexa9.inc| 2 +-
> >>  10 files changed, 10 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/meta/conf/machine/include/arm/arch-armv6.inc
> b/meta/conf/machine/include/arm/arch-armv6.inc
> >> index 91f0f07..5e1f973 100644
> >> --- a/meta/conf/machine/include/arm/arch-armv6.inc
> >> +++ b/meta/conf/machine/include/arm/arch-armv6.inc
> >> @@ -1,4 +1,4 @@
> >> -DEFAULTTUNE ?= "armv6"
> >> +DEFAULTTUNE ?= "armv6thf"
> >>
> >>  TUNEVALID[armv6] = "Enable instructions for ARMv6"
> >>  TUNECONFLICTS[armv6] = "armv4 armv5"
> >> diff --git a/meta/conf/machine/include/arm/arch-armv7a.inc
> b/meta/conf/machine/include/arm/arch-armv7a.inc
> >> index 5446048..bad1c27 100644
> >> --- a/meta/conf/machine/include/arm/arch-armv7a.inc
> >> +++ b/meta/conf/machine/include/arm/arch-armv7a.inc
> >> @@ -1,4 +1,4 @@
> >> -DEFAULTTUNE ?= "armv7a"
> >> +DEFAULTTUNE ?= "armv7athf"
> >>
> >>  TUNEVALID[armv7a] = "Enable instructions for ARMv7-a"
> >>  TUNECONFLICTS[armv7a] = "armv4 armv5 armv6 armv7"
> >> diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc
> b/meta/conf/machine/include/arm/arch-armv7ve.inc
> >> index 42d8d04..4d9260f 100644
> >> --- a/meta/conf/machine/include/arm/arch-armv7ve.inc
> >> +++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
> >> @@ -1,4 +1,4 @@
> >> -DEFAULTTUNE ?= "armv7ve"
> >> +DEFAULTTUNE ?= "armv7vethf"
> >>
> >>  TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
> >>  TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
> >> diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc
> b/meta/conf/machine/include/tune-arm1136jf-s.inc
> >> index 53994ef..2cadbee 100644
> >> --- a/meta/conf/machine/include/tune-arm1136jf-s.inc
> >> +++ b/meta/conf/machine/include/tune-arm1136jf-s.inc
> >> @@ -1,4 +1,4 @@
> >> -DEFAULTTUNE ?= "armv6"
> >> +DEFAULTTUNE ?= "armv6thf"
> >>
> >>  require conf/machine/include/arm/arch-armv6.inc
> >>
> >> diff --git a/meta/conf/machine/include/tune-cortexa15.inc
> b/meta/conf/machine/include/tune-cortexa15.inc
> >> index 03de602..25e99f9 100644
> >> --- a/meta/conf/machine/include/tune-cortexa15.inc
> >> +++ b/meta/conf/machine/include/tune-cortexa15.inc
> >> @@ -1,4 +1,4 @@
> >> -DEFAULTTUNE ?= "armv7ve-neon"
> >> +DEFAULTTUNE ?= "armv7vethf-neon"
> >>
> >>  require conf/machine/include/arm/arch-armv7ve.inc
> >>
> >> diff --git a/meta/conf/machine/include/tune-cortexa17.inc
> b/meta/conf/machine/include/tune-cortexa17.inc
> >> index f659a62..40392f9 100644
> >> --- a/meta/conf/machine/include/tune-cortexa17.inc
> >> +++ b/meta/conf/machine/include/tune-cortexa17.inc
> >> @@ -1,4 +1,4 @@
> >> -DEFAULTTUNE ?= "armv7ve-neon"
> >> +DEFAULTTUNE ?= "armv7vethf-neon"
> >>
> >>  require conf/machine/include/arm/arch-armv7ve.inc
> >>
> >> diff --git a/meta/conf/machine/include/tune-cortexa5.inc
> b/meta/conf/machine/include/tune-cortexa5.inc
> >> index 93f9ca4..1f0cda6 100644

[OE-core] [PATCH v2] conf/machine/include: enable hardfloat by default for ARMv6 and above

2017-03-06 Thread Andre McCurdy
Defaulting to softfp probably isn't the best choice anymore,
especially as there are now ARM BSP layers which leave DEFAULTTUNE
entirely up to the distro:

  https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html

Also add 't' to the ARMv7 default DEFAULTTUNEs, since there's no
clear reason to default to ignoring ARM_INSTRUCTION_SET for ARMv7.

Signed-off-by: Andre McCurdy 
---
 meta/conf/machine/include/arm/arch-armv6.inc   | 2 +-
 meta/conf/machine/include/arm/arch-armv7a.inc  | 2 +-
 meta/conf/machine/include/arm/arch-armv7ve.inc | 2 +-
 meta/conf/machine/include/tune-arm1136jf-s.inc | 2 +-
 meta/conf/machine/include/tune-cortexa15.inc   | 2 +-
 meta/conf/machine/include/tune-cortexa17.inc   | 2 +-
 meta/conf/machine/include/tune-cortexa5.inc| 2 +-
 meta/conf/machine/include/tune-cortexa7.inc| 2 +-
 meta/conf/machine/include/tune-cortexa8.inc| 2 +-
 meta/conf/machine/include/tune-cortexa9.inc| 2 +-
 10 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/conf/machine/include/arm/arch-armv6.inc 
b/meta/conf/machine/include/arm/arch-armv6.inc
index 91f0f07..6c838e9 100644
--- a/meta/conf/machine/include/arm/arch-armv6.inc
+++ b/meta/conf/machine/include/arm/arch-armv6.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv6"
+DEFAULTTUNE ?= "armv6hf"
 
 TUNEVALID[armv6] = "Enable instructions for ARMv6"
 TUNECONFLICTS[armv6] = "armv4 armv5"
diff --git a/meta/conf/machine/include/arm/arch-armv7a.inc 
b/meta/conf/machine/include/arm/arch-armv7a.inc
index 5446048..bad1c27 100644
--- a/meta/conf/machine/include/arm/arch-armv7a.inc
+++ b/meta/conf/machine/include/arm/arch-armv7a.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a"
+DEFAULTTUNE ?= "armv7athf"
 
 TUNEVALID[armv7a] = "Enable instructions for ARMv7-a"
 TUNECONFLICTS[armv7a] = "armv4 armv5 armv6 armv7"
diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc 
b/meta/conf/machine/include/arm/arch-armv7ve.inc
index 42d8d04..4d9260f 100644
--- a/meta/conf/machine/include/arm/arch-armv7ve.inc
+++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve"
+DEFAULTTUNE ?= "armv7vethf"
 
 TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
 TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc 
b/meta/conf/machine/include/tune-arm1136jf-s.inc
index 53994ef..c5de63e 100644
--- a/meta/conf/machine/include/tune-arm1136jf-s.inc
+++ b/meta/conf/machine/include/tune-arm1136jf-s.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv6"
+DEFAULTTUNE ?= "armv6hf"
 
 require conf/machine/include/arm/arch-armv6.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa15.inc 
b/meta/conf/machine/include/tune-cortexa15.inc
index 03de602..25e99f9 100644
--- a/meta/conf/machine/include/tune-cortexa15.inc
+++ b/meta/conf/machine/include/tune-cortexa15.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve-neon"
+DEFAULTTUNE ?= "armv7vethf-neon"
 
 require conf/machine/include/arm/arch-armv7ve.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa17.inc 
b/meta/conf/machine/include/tune-cortexa17.inc
index f659a62..40392f9 100644
--- a/meta/conf/machine/include/tune-cortexa17.inc
+++ b/meta/conf/machine/include/tune-cortexa17.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve-neon"
+DEFAULTTUNE ?= "armv7vethf-neon"
 
 require conf/machine/include/arm/arch-armv7ve.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa5.inc 
b/meta/conf/machine/include/tune-cortexa5.inc
index 93f9ca4..1f0cda6 100644
--- a/meta/conf/machine/include/tune-cortexa5.inc
+++ b/meta/conf/machine/include/tune-cortexa5.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a-neon"
+DEFAULTTUNE ?= "armv7athf-neon"
 
 require conf/machine/include/arm/arch-armv7a.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa7.inc 
b/meta/conf/machine/include/tune-cortexa7.inc
index 52e06b8..52415d9 100644
--- a/meta/conf/machine/include/tune-cortexa7.inc
+++ b/meta/conf/machine/include/tune-cortexa7.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve-neon"
+DEFAULTTUNE ?= "armv7vethf-neon"
 
 require conf/machine/include/arm/arch-armv7ve.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa8.inc 
b/meta/conf/machine/include/tune-cortexa8.inc
index a831bd5..8ee8de9 100644
--- a/meta/conf/machine/include/tune-cortexa8.inc
+++ b/meta/conf/machine/include/tune-cortexa8.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a-neon"
+DEFAULTTUNE ?= "armv7athf-neon"
 
 require conf/machine/include/arm/arch-armv7a.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa9.inc 
b/meta/conf/machine/include/tune-cortexa9.inc
index 8b84e60..0cf323c 100644
--- a/meta/conf/machine/include/tune-cortexa9.inc
+++ b/meta/conf/machine/include/tune-cortexa9.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a-neon"
+DEFAULTTUNE ?= "armv7athf-neon"
 
 require conf/machine/include/arm/arch-armv7a.inc
 
-- 
1.9.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org

Re: [OE-core] [PATCH] conf/machine/include: enable hardfloat by default for ARMv6 and above

2017-03-06 Thread Andre McCurdy
On Mon, Mar 6, 2017 at 2:51 PM, Andre McCurdy  wrote:
> On Mon, Mar 6, 2017 at 2:37 PM, Khem Raj  wrote:
>> On Mon, Mar 6, 2017 at 1:47 PM, Andre McCurdy  wrote:
>>> Defaulting to softfp probably isn't the best choice anymore,
>>> especially as there are now ARM BSP layers which leave DEFAULTTUNE
>>> entirely up to the distro:
>>>
>>>   https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html
>>>
>>
>> I like this patch and want to clarify that it changes the default ISA to 
>> thumb2
>> which we should use anyway due to size reasons and other distros use it as
>> default too.
>
> No, it doesn't. The choice between ARM and Thumb(2) is made by the
> ARM_INSTRUCTION_SET variable. Adding 't' to DEFAULTTUNE simply means
> that the ARM_INSTRUCTION_SET variable will not be ignored (it's really
> a long standing bug that we ever defined DEFAULTTUNE options for ARMv6
> and above which ignore ARM_INSTRUCTION_SET, but that's a separate
> topic).
>
>> I am not sure of we should change it for armv6 though. since some armv6
>> has t1 and some has t2 so lets leave that as it is.
>
> I'm not aware of any ARMv6 cores which don't support Thumb2. Do you
> have a reference?

Well, google does find a few examples, so to avoid any possible risk
of somehow trying to use Thumb-1 I'll send a v2 which drops the 't'
for ARMv6.

> (But again, to be clear, this commit doesn't change the default in
> terms of instruction set - all builds will still use ARM).
>
>>> Signed-off-by: Andre McCurdy 
>>> ---
>>>  meta/conf/machine/include/arm/arch-armv6.inc   | 2 +-
>>>  meta/conf/machine/include/arm/arch-armv7a.inc  | 2 +-
>>>  meta/conf/machine/include/arm/arch-armv7ve.inc | 2 +-
>>>  meta/conf/machine/include/tune-arm1136jf-s.inc | 2 +-
>>>  meta/conf/machine/include/tune-cortexa15.inc   | 2 +-
>>>  meta/conf/machine/include/tune-cortexa17.inc   | 2 +-
>>>  meta/conf/machine/include/tune-cortexa5.inc| 2 +-
>>>  meta/conf/machine/include/tune-cortexa7.inc| 2 +-
>>>  meta/conf/machine/include/tune-cortexa8.inc| 2 +-
>>>  meta/conf/machine/include/tune-cortexa9.inc| 2 +-
>>>  10 files changed, 10 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/meta/conf/machine/include/arm/arch-armv6.inc 
>>> b/meta/conf/machine/include/arm/arch-armv6.inc
>>> index 91f0f07..5e1f973 100644
>>> --- a/meta/conf/machine/include/arm/arch-armv6.inc
>>> +++ b/meta/conf/machine/include/arm/arch-armv6.inc
>>> @@ -1,4 +1,4 @@
>>> -DEFAULTTUNE ?= "armv6"
>>> +DEFAULTTUNE ?= "armv6thf"
>>>
>>>  TUNEVALID[armv6] = "Enable instructions for ARMv6"
>>>  TUNECONFLICTS[armv6] = "armv4 armv5"
>>> diff --git a/meta/conf/machine/include/arm/arch-armv7a.inc 
>>> b/meta/conf/machine/include/arm/arch-armv7a.inc
>>> index 5446048..bad1c27 100644
>>> --- a/meta/conf/machine/include/arm/arch-armv7a.inc
>>> +++ b/meta/conf/machine/include/arm/arch-armv7a.inc
>>> @@ -1,4 +1,4 @@
>>> -DEFAULTTUNE ?= "armv7a"
>>> +DEFAULTTUNE ?= "armv7athf"
>>>
>>>  TUNEVALID[armv7a] = "Enable instructions for ARMv7-a"
>>>  TUNECONFLICTS[armv7a] = "armv4 armv5 armv6 armv7"
>>> diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc 
>>> b/meta/conf/machine/include/arm/arch-armv7ve.inc
>>> index 42d8d04..4d9260f 100644
>>> --- a/meta/conf/machine/include/arm/arch-armv7ve.inc
>>> +++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
>>> @@ -1,4 +1,4 @@
>>> -DEFAULTTUNE ?= "armv7ve"
>>> +DEFAULTTUNE ?= "armv7vethf"
>>>
>>>  TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
>>>  TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
>>> diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc 
>>> b/meta/conf/machine/include/tune-arm1136jf-s.inc
>>> index 53994ef..2cadbee 100644
>>> --- a/meta/conf/machine/include/tune-arm1136jf-s.inc
>>> +++ b/meta/conf/machine/include/tune-arm1136jf-s.inc
>>> @@ -1,4 +1,4 @@
>>> -DEFAULTTUNE ?= "armv6"
>>> +DEFAULTTUNE ?= "armv6thf"
>>>
>>>  require conf/machine/include/arm/arch-armv6.inc
>>>
>>> diff --git a/meta/conf/machine/include/tune-cortexa15.inc 
>>> b/meta/conf/machine/include/tune-cortexa15.inc
>>> index 03de602..25e99f9 100644
>>> --- a/meta/conf/machine/include/tune-cortexa15.inc
>>> +++ b/meta/conf/machine/include/tune-cortexa15.inc
>>> @@ -1,4 +1,4 @@
>>> -DEFAULTTUNE ?= "armv7ve-neon"
>>> +DEFAULTTUNE ?= "armv7vethf-neon"
>>>
>>>  require conf/machine/include/arm/arch-armv7ve.inc
>>>
>>> diff --git a/meta/conf/machine/include/tune-cortexa17.inc 
>>> b/meta/conf/machine/include/tune-cortexa17.inc
>>> index f659a62..40392f9 100644
>>> --- a/meta/conf/machine/include/tune-cortexa17.inc
>>> +++ b/meta/conf/machine/include/tune-cortexa17.inc
>>> @@ -1,4 +1,4 @@
>>> -DEFAULTTUNE ?= "armv7ve-neon"
>>> +DEFAULTTUNE ?= "armv7vethf-neon"
>>>
>>>  require conf/machine/include/arm/arch-armv7ve.inc
>>>
>>> diff --git a/meta/conf/machine/include/tune-cortexa5.inc 
>>> b/meta/conf/machine/include/tune-cortexa5.inc
>>> index 93f9ca4..1f0cda6 

Re: [OE-core] [PATCH] conf/machine/include: enable hardfloat by default for ARMv6 and above

2017-03-06 Thread Andre McCurdy
On Mon, Mar 6, 2017 at 2:37 PM, Khem Raj  wrote:
> On Mon, Mar 6, 2017 at 1:47 PM, Andre McCurdy  wrote:
>> Defaulting to softfp probably isn't the best choice anymore,
>> especially as there are now ARM BSP layers which leave DEFAULTTUNE
>> entirely up to the distro:
>>
>>   https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html
>>
>
> I like this patch and want to clarify that it changes the default ISA to 
> thumb2
> which we should use anyway due to size reasons and other distros use it as
> default too.

No, it doesn't. The choice between ARM and Thumb(2) is made by the
ARM_INSTRUCTION_SET variable. Adding 't' to DEFAULTTUNE simply means
that the ARM_INSTRUCTION_SET variable will not be ignored (it's really
a long standing bug that we ever defined DEFAULTTUNE options for ARMv6
and above which ignore ARM_INSTRUCTION_SET, but that's a separate
topic).

> I am not sure of we should change it for armv6 though. since some armv6
> has t1 and some has t2 so lets leave that as it is.

I'm not aware of any ARMv6 cores which don't support Thumb2. Do you
have a reference?

(But again, to be clear, this commit doesn't change the default in
terms of instruction set - all builds will still use ARM).

>> Signed-off-by: Andre McCurdy 
>> ---
>>  meta/conf/machine/include/arm/arch-armv6.inc   | 2 +-
>>  meta/conf/machine/include/arm/arch-armv7a.inc  | 2 +-
>>  meta/conf/machine/include/arm/arch-armv7ve.inc | 2 +-
>>  meta/conf/machine/include/tune-arm1136jf-s.inc | 2 +-
>>  meta/conf/machine/include/tune-cortexa15.inc   | 2 +-
>>  meta/conf/machine/include/tune-cortexa17.inc   | 2 +-
>>  meta/conf/machine/include/tune-cortexa5.inc| 2 +-
>>  meta/conf/machine/include/tune-cortexa7.inc| 2 +-
>>  meta/conf/machine/include/tune-cortexa8.inc| 2 +-
>>  meta/conf/machine/include/tune-cortexa9.inc| 2 +-
>>  10 files changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/meta/conf/machine/include/arm/arch-armv6.inc 
>> b/meta/conf/machine/include/arm/arch-armv6.inc
>> index 91f0f07..5e1f973 100644
>> --- a/meta/conf/machine/include/arm/arch-armv6.inc
>> +++ b/meta/conf/machine/include/arm/arch-armv6.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv6"
>> +DEFAULTTUNE ?= "armv6thf"
>>
>>  TUNEVALID[armv6] = "Enable instructions for ARMv6"
>>  TUNECONFLICTS[armv6] = "armv4 armv5"
>> diff --git a/meta/conf/machine/include/arm/arch-armv7a.inc 
>> b/meta/conf/machine/include/arm/arch-armv7a.inc
>> index 5446048..bad1c27 100644
>> --- a/meta/conf/machine/include/arm/arch-armv7a.inc
>> +++ b/meta/conf/machine/include/arm/arch-armv7a.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv7a"
>> +DEFAULTTUNE ?= "armv7athf"
>>
>>  TUNEVALID[armv7a] = "Enable instructions for ARMv7-a"
>>  TUNECONFLICTS[armv7a] = "armv4 armv5 armv6 armv7"
>> diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc 
>> b/meta/conf/machine/include/arm/arch-armv7ve.inc
>> index 42d8d04..4d9260f 100644
>> --- a/meta/conf/machine/include/arm/arch-armv7ve.inc
>> +++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv7ve"
>> +DEFAULTTUNE ?= "armv7vethf"
>>
>>  TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
>>  TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
>> diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc 
>> b/meta/conf/machine/include/tune-arm1136jf-s.inc
>> index 53994ef..2cadbee 100644
>> --- a/meta/conf/machine/include/tune-arm1136jf-s.inc
>> +++ b/meta/conf/machine/include/tune-arm1136jf-s.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv6"
>> +DEFAULTTUNE ?= "armv6thf"
>>
>>  require conf/machine/include/arm/arch-armv6.inc
>>
>> diff --git a/meta/conf/machine/include/tune-cortexa15.inc 
>> b/meta/conf/machine/include/tune-cortexa15.inc
>> index 03de602..25e99f9 100644
>> --- a/meta/conf/machine/include/tune-cortexa15.inc
>> +++ b/meta/conf/machine/include/tune-cortexa15.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv7ve-neon"
>> +DEFAULTTUNE ?= "armv7vethf-neon"
>>
>>  require conf/machine/include/arm/arch-armv7ve.inc
>>
>> diff --git a/meta/conf/machine/include/tune-cortexa17.inc 
>> b/meta/conf/machine/include/tune-cortexa17.inc
>> index f659a62..40392f9 100644
>> --- a/meta/conf/machine/include/tune-cortexa17.inc
>> +++ b/meta/conf/machine/include/tune-cortexa17.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv7ve-neon"
>> +DEFAULTTUNE ?= "armv7vethf-neon"
>>
>>  require conf/machine/include/arm/arch-armv7ve.inc
>>
>> diff --git a/meta/conf/machine/include/tune-cortexa5.inc 
>> b/meta/conf/machine/include/tune-cortexa5.inc
>> index 93f9ca4..1f0cda6 100644
>> --- a/meta/conf/machine/include/tune-cortexa5.inc
>> +++ b/meta/conf/machine/include/tune-cortexa5.inc
>> @@ -1,4 +1,4 @@
>> -DEFAULTTUNE ?= "armv7a-neon"
>> +DEFAULTTUNE ?= "armv7athf-neon"
>>
>>  require conf/machine/include/arm/arch-armv7a.inc
>>
>> diff --git a/meta/conf/machine/include/tune-cortexa7.inc 
>> 

Re: [OE-core] [PATCH] sanity.bbclass: allow s3 protocol when sanity checking MIRRORS, etc

2017-03-06 Thread Andre McCurdy
On Mon, Mar 6, 2017 at 2:36 PM, Burton, Ross  wrote:
>
> On 6 March 2017 at 22:34, Andre McCurdy  wrote:
>>
>>  protocols = ['http', 'ftp', 'file', 'https', \
>>   'git', 'gitsm', 'hg', 'osc', 'p4', 'svn', \
>> - 'bzr', 'cvs', 'npm', 'sftp', 'ssh']
>> + 'bzr', 'cvs', 'npm', 'sftp', 'ssh', 's3' ]
>
>
> Maybe bb.fetch2 needs a "list the protocols you support" method?

Yes. Although there should perhaps be a distinction between protocols
which can be used for MIRRORS etc and those which can not (I'm not
sure if the current list in the sanity.bbclass gets that right?).

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


Re: [OE-core] [PATCH] conf/machine/include: enable hardfloat by default for ARMv6 and above

2017-03-06 Thread Khem Raj
On Mon, Mar 6, 2017 at 1:47 PM, Andre McCurdy  wrote:
> Defaulting to softfp probably isn't the best choice anymore,
> especially as there are now ARM BSP layers which leave DEFAULTTUNE
> entirely up to the distro:
>
>   https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html
>

I like this patch and want to clarify that it changes the default ISA to thumb2
which we should use anyway due to size reasons and other distros use it as
default too.

I am not sure of we should change it for armv6 though. since some armv6
has t1 and some has t2 so lets leave that as it is.

> Signed-off-by: Andre McCurdy 
> ---
>  meta/conf/machine/include/arm/arch-armv6.inc   | 2 +-
>  meta/conf/machine/include/arm/arch-armv7a.inc  | 2 +-
>  meta/conf/machine/include/arm/arch-armv7ve.inc | 2 +-
>  meta/conf/machine/include/tune-arm1136jf-s.inc | 2 +-
>  meta/conf/machine/include/tune-cortexa15.inc   | 2 +-
>  meta/conf/machine/include/tune-cortexa17.inc   | 2 +-
>  meta/conf/machine/include/tune-cortexa5.inc| 2 +-
>  meta/conf/machine/include/tune-cortexa7.inc| 2 +-
>  meta/conf/machine/include/tune-cortexa8.inc| 2 +-
>  meta/conf/machine/include/tune-cortexa9.inc| 2 +-
>  10 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/meta/conf/machine/include/arm/arch-armv6.inc 
> b/meta/conf/machine/include/arm/arch-armv6.inc
> index 91f0f07..5e1f973 100644
> --- a/meta/conf/machine/include/arm/arch-armv6.inc
> +++ b/meta/conf/machine/include/arm/arch-armv6.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv6"
> +DEFAULTTUNE ?= "armv6thf"
>
>  TUNEVALID[armv6] = "Enable instructions for ARMv6"
>  TUNECONFLICTS[armv6] = "armv4 armv5"
> diff --git a/meta/conf/machine/include/arm/arch-armv7a.inc 
> b/meta/conf/machine/include/arm/arch-armv7a.inc
> index 5446048..bad1c27 100644
> --- a/meta/conf/machine/include/arm/arch-armv7a.inc
> +++ b/meta/conf/machine/include/arm/arch-armv7a.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7a"
> +DEFAULTTUNE ?= "armv7athf"
>
>  TUNEVALID[armv7a] = "Enable instructions for ARMv7-a"
>  TUNECONFLICTS[armv7a] = "armv4 armv5 armv6 armv7"
> diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc 
> b/meta/conf/machine/include/arm/arch-armv7ve.inc
> index 42d8d04..4d9260f 100644
> --- a/meta/conf/machine/include/arm/arch-armv7ve.inc
> +++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7ve"
> +DEFAULTTUNE ?= "armv7vethf"
>
>  TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
>  TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
> diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc 
> b/meta/conf/machine/include/tune-arm1136jf-s.inc
> index 53994ef..2cadbee 100644
> --- a/meta/conf/machine/include/tune-arm1136jf-s.inc
> +++ b/meta/conf/machine/include/tune-arm1136jf-s.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv6"
> +DEFAULTTUNE ?= "armv6thf"
>
>  require conf/machine/include/arm/arch-armv6.inc
>
> diff --git a/meta/conf/machine/include/tune-cortexa15.inc 
> b/meta/conf/machine/include/tune-cortexa15.inc
> index 03de602..25e99f9 100644
> --- a/meta/conf/machine/include/tune-cortexa15.inc
> +++ b/meta/conf/machine/include/tune-cortexa15.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7ve-neon"
> +DEFAULTTUNE ?= "armv7vethf-neon"
>
>  require conf/machine/include/arm/arch-armv7ve.inc
>
> diff --git a/meta/conf/machine/include/tune-cortexa17.inc 
> b/meta/conf/machine/include/tune-cortexa17.inc
> index f659a62..40392f9 100644
> --- a/meta/conf/machine/include/tune-cortexa17.inc
> +++ b/meta/conf/machine/include/tune-cortexa17.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7ve-neon"
> +DEFAULTTUNE ?= "armv7vethf-neon"
>
>  require conf/machine/include/arm/arch-armv7ve.inc
>
> diff --git a/meta/conf/machine/include/tune-cortexa5.inc 
> b/meta/conf/machine/include/tune-cortexa5.inc
> index 93f9ca4..1f0cda6 100644
> --- a/meta/conf/machine/include/tune-cortexa5.inc
> +++ b/meta/conf/machine/include/tune-cortexa5.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7a-neon"
> +DEFAULTTUNE ?= "armv7athf-neon"
>
>  require conf/machine/include/arm/arch-armv7a.inc
>
> diff --git a/meta/conf/machine/include/tune-cortexa7.inc 
> b/meta/conf/machine/include/tune-cortexa7.inc
> index 52e06b8..52415d9 100644
> --- a/meta/conf/machine/include/tune-cortexa7.inc
> +++ b/meta/conf/machine/include/tune-cortexa7.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7ve-neon"
> +DEFAULTTUNE ?= "armv7vethf-neon"
>
>  require conf/machine/include/arm/arch-armv7ve.inc
>
> diff --git a/meta/conf/machine/include/tune-cortexa8.inc 
> b/meta/conf/machine/include/tune-cortexa8.inc
> index a831bd5..8ee8de9 100644
> --- a/meta/conf/machine/include/tune-cortexa8.inc
> +++ b/meta/conf/machine/include/tune-cortexa8.inc
> @@ -1,4 +1,4 @@
> -DEFAULTTUNE ?= "armv7a-neon"
> +DEFAULTTUNE ?= "armv7athf-neon"
>
>  require conf/machine/include/arm/arch-armv7a.inc
>
> diff --git a/meta/conf/machine/include/tune-cortexa9.inc 
> 

Re: [OE-core] [PATCH] sanity.bbclass: allow s3 protocol when sanity checking MIRRORS, etc

2017-03-06 Thread Burton, Ross
On 6 March 2017 at 22:34, Andre McCurdy  wrote:

>  protocols = ['http', 'ftp', 'file', 'https', \
>   'git', 'gitsm', 'hg', 'osc', 'p4', 'svn', \
> - 'bzr', 'cvs', 'npm', 'sftp', 'ssh']
> + 'bzr', 'cvs', 'npm', 'sftp', 'ssh', 's3' ]
>

Maybe bb.fetch2 needs a "list the protocols you support" method?

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


[OE-core] [PATCH] sanity.bbclass: allow s3 protocol when sanity checking MIRRORS, etc

2017-03-06 Thread Andre McCurdy
Bitbake now supports an Amazon AWS S3 fetcher:

  
http://git.openembedded.org/bitbake/commit/?id=6fe07ed25457dd7952b60f4b2153d56b15d5eea6

Signed-off-by: Andre McCurdy 
---
 meta/classes/sanity.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 1fe172f..b5f4756 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -874,7 +874,7 @@ def check_sanity_everybuild(status, d):
 mirror_vars = ['MIRRORS', 'PREMIRRORS', 'SSTATE_MIRRORS']
 protocols = ['http', 'ftp', 'file', 'https', \
  'git', 'gitsm', 'hg', 'osc', 'p4', 'svn', \
- 'bzr', 'cvs', 'npm', 'sftp', 'ssh']
+ 'bzr', 'cvs', 'npm', 'sftp', 'ssh', 's3' ]
 for mirror_var in mirror_vars:
 mirrors = (d.getVar(mirror_var) or '').replace('\\n', ' ').split()
 
-- 
1.9.1

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


[OE-core] [PATCH] conf/machine/include: enable hardfloat by default for ARMv6 and above

2017-03-06 Thread Andre McCurdy
Defaulting to softfp probably isn't the best choice anymore,
especially as there are now ARM BSP layers which leave DEFAULTTUNE
entirely up to the distro:

  https://lists.yoctoproject.org/pipermail/yocto/2017-February/034637.html

Signed-off-by: Andre McCurdy 
---
 meta/conf/machine/include/arm/arch-armv6.inc   | 2 +-
 meta/conf/machine/include/arm/arch-armv7a.inc  | 2 +-
 meta/conf/machine/include/arm/arch-armv7ve.inc | 2 +-
 meta/conf/machine/include/tune-arm1136jf-s.inc | 2 +-
 meta/conf/machine/include/tune-cortexa15.inc   | 2 +-
 meta/conf/machine/include/tune-cortexa17.inc   | 2 +-
 meta/conf/machine/include/tune-cortexa5.inc| 2 +-
 meta/conf/machine/include/tune-cortexa7.inc| 2 +-
 meta/conf/machine/include/tune-cortexa8.inc| 2 +-
 meta/conf/machine/include/tune-cortexa9.inc| 2 +-
 10 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/meta/conf/machine/include/arm/arch-armv6.inc 
b/meta/conf/machine/include/arm/arch-armv6.inc
index 91f0f07..5e1f973 100644
--- a/meta/conf/machine/include/arm/arch-armv6.inc
+++ b/meta/conf/machine/include/arm/arch-armv6.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv6"
+DEFAULTTUNE ?= "armv6thf"
 
 TUNEVALID[armv6] = "Enable instructions for ARMv6"
 TUNECONFLICTS[armv6] = "armv4 armv5"
diff --git a/meta/conf/machine/include/arm/arch-armv7a.inc 
b/meta/conf/machine/include/arm/arch-armv7a.inc
index 5446048..bad1c27 100644
--- a/meta/conf/machine/include/arm/arch-armv7a.inc
+++ b/meta/conf/machine/include/arm/arch-armv7a.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a"
+DEFAULTTUNE ?= "armv7athf"
 
 TUNEVALID[armv7a] = "Enable instructions for ARMv7-a"
 TUNECONFLICTS[armv7a] = "armv4 armv5 armv6 armv7"
diff --git a/meta/conf/machine/include/arm/arch-armv7ve.inc 
b/meta/conf/machine/include/arm/arch-armv7ve.inc
index 42d8d04..4d9260f 100644
--- a/meta/conf/machine/include/arm/arch-armv7ve.inc
+++ b/meta/conf/machine/include/arm/arch-armv7ve.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve"
+DEFAULTTUNE ?= "armv7vethf"
 
 TUNEVALID[armv7ve] = "Enable instructions for ARMv7ve"
 TUNECONFLICTS[armv7ve] = "armv4 armv5 armv6 armv7 armv7a"
diff --git a/meta/conf/machine/include/tune-arm1136jf-s.inc 
b/meta/conf/machine/include/tune-arm1136jf-s.inc
index 53994ef..2cadbee 100644
--- a/meta/conf/machine/include/tune-arm1136jf-s.inc
+++ b/meta/conf/machine/include/tune-arm1136jf-s.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv6"
+DEFAULTTUNE ?= "armv6thf"
 
 require conf/machine/include/arm/arch-armv6.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa15.inc 
b/meta/conf/machine/include/tune-cortexa15.inc
index 03de602..25e99f9 100644
--- a/meta/conf/machine/include/tune-cortexa15.inc
+++ b/meta/conf/machine/include/tune-cortexa15.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve-neon"
+DEFAULTTUNE ?= "armv7vethf-neon"
 
 require conf/machine/include/arm/arch-armv7ve.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa17.inc 
b/meta/conf/machine/include/tune-cortexa17.inc
index f659a62..40392f9 100644
--- a/meta/conf/machine/include/tune-cortexa17.inc
+++ b/meta/conf/machine/include/tune-cortexa17.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve-neon"
+DEFAULTTUNE ?= "armv7vethf-neon"
 
 require conf/machine/include/arm/arch-armv7ve.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa5.inc 
b/meta/conf/machine/include/tune-cortexa5.inc
index 93f9ca4..1f0cda6 100644
--- a/meta/conf/machine/include/tune-cortexa5.inc
+++ b/meta/conf/machine/include/tune-cortexa5.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a-neon"
+DEFAULTTUNE ?= "armv7athf-neon"
 
 require conf/machine/include/arm/arch-armv7a.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa7.inc 
b/meta/conf/machine/include/tune-cortexa7.inc
index 52e06b8..52415d9 100644
--- a/meta/conf/machine/include/tune-cortexa7.inc
+++ b/meta/conf/machine/include/tune-cortexa7.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7ve-neon"
+DEFAULTTUNE ?= "armv7vethf-neon"
 
 require conf/machine/include/arm/arch-armv7ve.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa8.inc 
b/meta/conf/machine/include/tune-cortexa8.inc
index a831bd5..8ee8de9 100644
--- a/meta/conf/machine/include/tune-cortexa8.inc
+++ b/meta/conf/machine/include/tune-cortexa8.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a-neon"
+DEFAULTTUNE ?= "armv7athf-neon"
 
 require conf/machine/include/arm/arch-armv7a.inc
 
diff --git a/meta/conf/machine/include/tune-cortexa9.inc 
b/meta/conf/machine/include/tune-cortexa9.inc
index 8b84e60..0cf323c 100644
--- a/meta/conf/machine/include/tune-cortexa9.inc
+++ b/meta/conf/machine/include/tune-cortexa9.inc
@@ -1,4 +1,4 @@
-DEFAULTTUNE ?= "armv7a-neon"
+DEFAULTTUNE ?= "armv7athf-neon"
 
 require conf/machine/include/arm/arch-armv7a.inc
 
-- 
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] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Patrick Ohly
On Mon, 2017-03-06 at 21:58 +0200, Ed Bartosh wrote:
> On Mon, Mar 06, 2017 at 08:31:55PM +0100, Patrick Ohly wrote:
> > On Mon, 2017-03-06 at 19:50 +0200, Ed Bartosh wrote:
> > > On Mon, Mar 06, 2017 at 04:49:25PM +, Burton, Ross wrote:
> > > > On 6 March 2017 at 15:31, Ed Bartosh  wrote:
> > > > 
> > > > > +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> > > > >
> > > > 
> > > > $ ( [ -h / ] && echo something ); echo $?
> > > > 1
> > > > 
> > > > If the -h fails then this is still going to cause sstate_unpack_package 
> > > > to
> > > > trap.
> > > 
> > > I don't think it will as '&&' and '||' lists are among other special 
> > > cases where
> > > shell doesn't exits on error.
> > 
> > True, but if the clause happens to be the last one in a function or
> > script (for example, after restructuring code), then the return code of
> > that becomes non-zero, which isn't intended.
> 
> Exactly because of this I moved my changes up in the function in v2.

And someone else might accidentally move it down again, without
understanding the consequences. It's simply safer to be explicit, IMHO.
Not worth a v3, but perhaps in the future.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



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


Re: [OE-core] [PATCH V7] go: Add recipes for golang compilers and tools

2017-03-06 Thread Khem Raj
On Mon, Mar 6, 2017 at 12:51 PM, Burton, Ross  wrote:
>
> On 6 March 2017 at 18:46, Khem Raj  wrote:
>>
>> * This is converging the recipes for go from
>>   meta-virtualization and oe-meta-go
>
>
> In master-next, Richard has a patch to disable Go on musl.  Can you
> incorporate that too (or fix Go)?

Which arch is it failing for on musl ? I know I had issues with clang/musl
for go but I thought it was more related to clang then musl

I have seen Richard's patch. its ok for now.

>
> In mut I've picked his musl fix on top on v7 for testing.
>
> Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH V7] go: Add recipes for golang compilers and tools

2017-03-06 Thread Burton, Ross
On 6 March 2017 at 18:46, Khem Raj  wrote:

> * This is converging the recipes for go from
>   meta-virtualization and oe-meta-go
>

In master-next, Richard has a patch to disable Go on musl.  Can you
incorporate that too (or fix Go)?

In mut I've picked his musl fix on top on v7 for testing.

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


Re: [OE-core] [PATCH v2] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Burton, Ross
On 6 March 2017 at 17:50, Ed Bartosh  wrote:

> I don't think it will as '&&' and '||' lists are among other special cases
> where
> shell doesn't exits on error.
>

Ah, fair enough.  Another quirk of sh I wasn't aware of :)

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


Re: [OE-core] [PATCH v2] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Ed Bartosh
On Mon, Mar 06, 2017 at 08:31:55PM +0100, Patrick Ohly wrote:
> On Mon, 2017-03-06 at 19:50 +0200, Ed Bartosh wrote:
> > On Mon, Mar 06, 2017 at 04:49:25PM +, Burton, Ross wrote:
> > > On 6 March 2017 at 15:31, Ed Bartosh  wrote:
> > > 
> > > > +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> > > >
> > > 
> > > $ ( [ -h / ] && echo something ); echo $?
> > > 1
> > > 
> > > If the -h fails then this is still going to cause sstate_unpack_package to
> > > trap.
> > 
> > I don't think it will as '&&' and '||' lists are among other special cases 
> > where
> > shell doesn't exits on error.
> 
> True, but if the clause happens to be the last one in a function or
> script (for example, after restructuring code), then the return code of
> that becomes non-zero, which isn't intended.

Exactly because of this I moved my changes up in the function in v2.

> 
> $ cat test.sh 
> foo() {
> [ -h /foobar ] && echo 'fstab is a symlink'
> }
> 
> foo
> echo $?
> $ bash -xe test.sh 
> + set -e
> + foo
> + '[' -h /foobar ']'
> $ echo $?
> 1
> 
> Making the intend explicit with || true avoids that.
> 
> -- 
> Best Regards, Patrick Ohly
> 
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
> 
> 
> 

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


Re: [OE-core] [PATCH V7] go: Add recipes for golang compilers and tools

2017-03-06 Thread Matt Madison
On Fri, Mar 3, 2017 at 3:18 PM, Khem Raj  wrote:
> * This is converging the recipes for go from
>   meta-virtualization and oe-meta-go
>
> * Add recipes for go 1.7
>
> * go.bbclass is added to ease out writing
>   recipes for go packages
>
> * go-examples: Add an example, helloworld written in go
>   This should serve as temlate for writing go recipes


I have some specific comments below, but as a general question,
how about crosssdk and cross-canadian recipes for the toolchain?


Thanks,
-Matt

>
> Signed-off-by: Khem Raj 
> ---
>  meta/classes/go.bbclass|  72 +++
>  meta/classes/goarch.bbclass|  46 +
>  meta/recipes-devtools/go/go-1.4.inc|  16 ++
>  ...alignment-for-the-.rel.plt-section-on-32-.patch |  30 +++
>  .../go/go-1.4/016-armhf-elf-header.patch   |  24 +++
>  ...ckport-cmd-link-support-new-386-amd64-rel.patch | 225 
> +
>  meta/recipes-devtools/go/go-1.4/syslog.patch   |  62 ++
>  meta/recipes-devtools/go/go-1.6.inc|  19 ++
>  .../go/go-1.6/armhf-elf-header.patch   |  23 +++
>  .../go/go-1.6/fix-cc-handling.patch|  50 +
>  .../go/go-1.6/fix-target-cc-for-build.patch|  17 ++
>  meta/recipes-devtools/go/go-1.6/gotooldir.patch|  30 +++
>  .../go/go-1.6/split-host-and-target-build.patch|  63 ++
>  meta/recipes-devtools/go/go-1.6/syslog.patch   |  62 ++
>  meta/recipes-devtools/go/go-1.7.inc|  19 ++
>  .../go/go-1.7/armhf-elf-header.patch   |  23 +++
>  .../go/go-1.7/fix-cc-handling.patch|  50 +
>  .../go/go-1.7/fix-target-cc-for-build.patch|  17 ++
>  meta/recipes-devtools/go/go-1.7/gotooldir.patch|  30 +++
>  .../go/go-1.7/split-host-and-target-build.patch|  62 ++
>  meta/recipes-devtools/go/go-1.7/syslog.patch   |  62 ++
>  meta/recipes-devtools/go/go-common.inc |  22 ++
>  meta/recipes-devtools/go/go-cross.inc  |  10 +
>  meta/recipes-devtools/go/go-cross_1.7.bb   |   5 +
>  meta/recipes-devtools/go/go-native.inc |  54 +
>  meta/recipes-devtools/go/go-native_1.4.bb  |   2 +
>  meta/recipes-devtools/go/go.inc|  80 
>  meta/recipes-devtools/go/go_1.6.bb |   4 +
>  meta/recipes-devtools/go/go_1.7.bb |   2 +
>  .../go-examples/files/helloworld.go|  10 +
>  meta/recipes-extended/go-examples/go-examples.inc  |  10 +
>  .../go-examples/go-helloworld_0.1.bb   |  13 ++
>  32 files changed, 1214 insertions(+)
>  create mode 100644 meta/classes/go.bbclass
>  create mode 100644 meta/classes/goarch.bbclass
>  create mode 100644 meta/recipes-devtools/go/go-1.4.inc
>  create mode 100644 
> meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.4/016-armhf-elf-header.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.4/go-cross-backport-cmd-link-support-new-386-amd64-rel.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.4/syslog.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6.inc
>  create mode 100644 meta/recipes-devtools/go/go-1.6/armhf-elf-header.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6/fix-cc-handling.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.6/fix-target-cc-for-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6/gotooldir.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.6/split-host-and-target-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6/syslog.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7.inc
>  create mode 100644 meta/recipes-devtools/go/go-1.7/armhf-elf-header.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7/fix-cc-handling.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.7/fix-target-cc-for-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7/gotooldir.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.7/split-host-and-target-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7/syslog.patch
>  create mode 100644 meta/recipes-devtools/go/go-common.inc
>  create mode 100644 meta/recipes-devtools/go/go-cross.inc
>  create mode 100644 meta/recipes-devtools/go/go-cross_1.7.bb
>  create mode 100644 meta/recipes-devtools/go/go-native.inc
>  create mode 100644 meta/recipes-devtools/go/go-native_1.4.bb
>  create mode 100644 meta/recipes-devtools/go/go.inc
>  create mode 100644 meta/recipes-devtools/go/go_1.6.bb
>  create mode 100644 meta/recipes-devtools/go/go_1.7.bb
>  create mode 100644 meta/recipes-extended/go-examples/files/helloworld.go
>  create mode 100644 meta/recipes-extended/go-examples/go-examples.inc
>  create mode 100644 meta/recipes-extended/go-examples/go-helloworld_0.1.bb
>
> diff 

Re: [OE-core] [RFC/PATCH] boost: Fix issue with python-numpy

2017-03-06 Thread Moritz Fischer
Ross,

On Mon, Mar 6, 2017 at 1:23 PM, Burton, Ross  wrote:

> Making another option would definitely be desirable.

So would you apply the patch to remove it if not PACKAGECONFIG[numpy]?

Cheers,

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


Re: [OE-core] [PATCH v2] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Patrick Ohly
On Mon, 2017-03-06 at 19:50 +0200, Ed Bartosh wrote:
> On Mon, Mar 06, 2017 at 04:49:25PM +, Burton, Ross wrote:
> > On 6 March 2017 at 15:31, Ed Bartosh  wrote:
> > 
> > > +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> > >
> > 
> > $ ( [ -h / ] && echo something ); echo $?
> > 1
> > 
> > If the -h fails then this is still going to cause sstate_unpack_package to
> > trap.
> 
> I don't think it will as '&&' and '||' lists are among other special cases 
> where
> shell doesn't exits on error.

True, but if the clause happens to be the last one in a function or
script (for example, after restructuring code), then the return code of
that becomes non-zero, which isn't intended.

$ cat test.sh 
foo() {
[ -h /foobar ] && echo 'fstab is a symlink'
}

foo
echo $?
$ bash -xe test.sh 
+ set -e
+ foo
+ '[' -h /foobar ']'
$ echo $?
1

Making the intend explicit with || true avoids that.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.



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


Re: [OE-core] [PATCH] wic: Prevent duplicate entries on fstab

2017-03-06 Thread Ed Bartosh
On Mon, Mar 06, 2017 at 03:48:00PM -0300, Fabio Berton wrote:
> Hi Ed,
> 
> The main motivation to my patch is prevent to duplicate entries. For
> example, if I add to my fstab line:
> 
> LABEL=data   /dataauto defaults  0  1
> 
> and add to wsk file:
> 
> part /data --ondisk mmcblk0 --fstype=ext4 --label data --align 8192
> --size 500M --extra-space 0
> 
> Final fstab will have two entries for /data.
This can be easily avoided if you remove leading slash:
part data --ondisk mmcblk0 --fstype=ext4 --label data --align 8192 --size 500M 
--extra-space 0


> 
> In most Linux distros mount /boot partition, if we have kernel image
> or boot script to update we need to mount /boot partition. Why the
> reason to not mount /boot?
>
The code that skips / and /boot was brought to wic codebase more than 4
years ago: 
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=75c143a7aef46ecea07cf33edd2b1a0192e10149

I don't know exact reason to be honest. However, I think we need to be careful 
with this
kind of legacy. It doesn't mean we shouldn't remove it, but it should
not be done as a side effect of the patch addressing absolutely
different issue, I believe.

> >>>For qemuarm machines I get the error:
> >>>
> >>>| DEBUG: Executing python function set_image_size
> >>>| DEBUG: Python function set_image_size finished
> >>>| DEBUG: Executing shell function do_image_wic
> >>>| Error: Please build syslinux first

Sorry, missed this. It looks like you're trying to use plugin that
depends on syslinux. For example, directdisk.wks uses bootimg-pcbios,
which uses syslinux. It's x86 specific and should not be used on arm.

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


Re: [OE-core] [PATCH V7] go: Add recipes for golang compilers and tools

2017-03-06 Thread Khem Raj
On Mon, Mar 6, 2017 at 7:05 AM, Leonardo Sandoval
 wrote:
> For the moment, manually cutting & pasting patchtest results:
>
>
> * Issue Added patch file is missing Upstream-Status in the
> header [test_upstream_status_presence]
>   Suggested fixAdd Upstream-Status:  to the header of
> meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch
>  (possible values: Pending, Submitted, Accepted, Backport, Denied, 
> Inappropriate)
>
> * Issue A patch file has been added, but does not have a
> Signed-off-by tag [test_signed_off_by_presence]
>   Suggested fixSign off the added patch file
> (meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch)
>

Sent a v7 which fixes this
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] wic: Prevent duplicate entries on fstab

2017-03-06 Thread Fabio Berton

Hi Ed,

The main motivation to my patch is prevent to duplicate entries. For 
example, if I add to my fstab line:


LABEL=data   /dataauto defaults  0  1

and add to wsk file:

part /data --ondisk mmcblk0 --fstype=ext4 --label data --align 8192 
--size 500M --extra-space 0


Final fstab will have two entries for /data.

In most Linux distros mount /boot partition, if we have kernel image or 
boot script to update we need to mount /boot partition. Why the reason 
to not mount /boot?


I'll look into parser issue.

Fabio

On 03/06/2017 03:13 PM, Ed Bartosh wrote:

On Mon, Mar 06, 2017 at 11:00:59AM -0300, Fabio Berton wrote:

Same error with poky-contrib:ed/wic/wip, we need to add --fstype= to
part /boot line in all wks files.


Only if we want boot partitions to be added to fstab. Currently / and
/boot partitions are not added. Why do we want to change this?

BTW, your patch will make wic to parse the same fstab file several
times. Can you change this, please?


On 03/03/2017 10:49 AM, Burton, Ross wrote:

On 3 March 2017 at 12:12, Fabio Berton
> wrote:

Sorry for delay. This error for qemux86 is because common.wks.inc
and directdisk-gpt.wks files in scripts/lib/wic/canned-wks
directory doesn't have option --fstype= for part /boot.

For qemuarm machines I get the error:

| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_wic
| Error: Please build syslinux first


There's patches queued that will change the behaviour here and
likely cause your patch to not apply - can you rebase on top of
poky-contrib:ed/wic/wip and see what happens?  The build
dependency is now wic-tools.

Ross

--
___
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 V7] go: Add recipes for golang compilers and tools

2017-03-06 Thread Khem Raj
* This is converging the recipes for go from
  meta-virtualization and oe-meta-go

* Add recipes for go 1.7

* go.bbclass is added to ease out writing
  recipes for go packages

* go-examples: Add an example, helloworld written in go
  This should serve as temlate for writing go recipes

Signed-off-by: Khem Raj 
---
v4 -> v7
- Add missing SOB and Upstream-Status to patches

 meta/classes/go.bbclass|  72 +++
 meta/classes/goarch.bbclass|  46 +
 meta/recipes-devtools/go/go-1.4.inc|  16 ++
 ...alignment-for-the-.rel.plt-section-on-32-.patch |  33 +++
 .../go/go-1.4/016-armhf-elf-header.patch   |  24 +++
 ...ckport-cmd-link-support-new-386-amd64-rel.patch | 225 +
 meta/recipes-devtools/go/go-1.4/syslog.patch   |  62 ++
 meta/recipes-devtools/go/go-1.6.inc|  19 ++
 .../go/go-1.6/armhf-elf-header.patch   |  23 +++
 .../go/go-1.6/fix-cc-handling.patch|  50 +
 .../go/go-1.6/fix-target-cc-for-build.patch|  17 ++
 meta/recipes-devtools/go/go-1.6/gotooldir.patch|  30 +++
 .../go/go-1.6/split-host-and-target-build.patch|  63 ++
 meta/recipes-devtools/go/go-1.6/syslog.patch   |  62 ++
 meta/recipes-devtools/go/go-1.7.inc|  19 ++
 .../go/go-1.7/armhf-elf-header.patch   |  23 +++
 .../go/go-1.7/fix-cc-handling.patch|  50 +
 .../go/go-1.7/fix-target-cc-for-build.patch|  17 ++
 meta/recipes-devtools/go/go-1.7/gotooldir.patch|  30 +++
 .../go/go-1.7/split-host-and-target-build.patch|  62 ++
 meta/recipes-devtools/go/go-1.7/syslog.patch   |  62 ++
 meta/recipes-devtools/go/go-common.inc |  22 ++
 meta/recipes-devtools/go/go-cross.inc  |  10 +
 meta/recipes-devtools/go/go-cross_1.7.bb   |   5 +
 meta/recipes-devtools/go/go-native.inc |  54 +
 meta/recipes-devtools/go/go-native_1.4.bb  |   2 +
 meta/recipes-devtools/go/go.inc|  80 
 meta/recipes-devtools/go/go_1.6.bb |   4 +
 meta/recipes-devtools/go/go_1.7.bb |   2 +
 .../go-examples/files/helloworld.go|  10 +
 meta/recipes-extended/go-examples/go-examples.inc  |  10 +
 .../go-examples/go-helloworld_0.1.bb   |  13 ++
 32 files changed, 1217 insertions(+)
 create mode 100644 meta/classes/go.bbclass
 create mode 100644 meta/classes/goarch.bbclass
 create mode 100644 meta/recipes-devtools/go/go-1.4.inc
 create mode 100644 
meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch
 create mode 100644 meta/recipes-devtools/go/go-1.4/016-armhf-elf-header.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.4/go-cross-backport-cmd-link-support-new-386-amd64-rel.patch
 create mode 100644 meta/recipes-devtools/go/go-1.4/syslog.patch
 create mode 100644 meta/recipes-devtools/go/go-1.6.inc
 create mode 100644 meta/recipes-devtools/go/go-1.6/armhf-elf-header.patch
 create mode 100644 meta/recipes-devtools/go/go-1.6/fix-cc-handling.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.6/fix-target-cc-for-build.patch
 create mode 100644 meta/recipes-devtools/go/go-1.6/gotooldir.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.6/split-host-and-target-build.patch
 create mode 100644 meta/recipes-devtools/go/go-1.6/syslog.patch
 create mode 100644 meta/recipes-devtools/go/go-1.7.inc
 create mode 100644 meta/recipes-devtools/go/go-1.7/armhf-elf-header.patch
 create mode 100644 meta/recipes-devtools/go/go-1.7/fix-cc-handling.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.7/fix-target-cc-for-build.patch
 create mode 100644 meta/recipes-devtools/go/go-1.7/gotooldir.patch
 create mode 100644 
meta/recipes-devtools/go/go-1.7/split-host-and-target-build.patch
 create mode 100644 meta/recipes-devtools/go/go-1.7/syslog.patch
 create mode 100644 meta/recipes-devtools/go/go-common.inc
 create mode 100644 meta/recipes-devtools/go/go-cross.inc
 create mode 100644 meta/recipes-devtools/go/go-cross_1.7.bb
 create mode 100644 meta/recipes-devtools/go/go-native.inc
 create mode 100644 meta/recipes-devtools/go/go-native_1.4.bb
 create mode 100644 meta/recipes-devtools/go/go.inc
 create mode 100644 meta/recipes-devtools/go/go_1.6.bb
 create mode 100644 meta/recipes-devtools/go/go_1.7.bb
 create mode 100644 meta/recipes-extended/go-examples/files/helloworld.go
 create mode 100644 meta/recipes-extended/go-examples/go-examples.inc
 create mode 100644 meta/recipes-extended/go-examples/go-helloworld_0.1.bb

diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
new file mode 100644
index 00..e6ea996e9d
--- /dev/null
+++ b/meta/classes/go.bbclass
@@ -0,0 +1,72 @@
+inherit goarch
+
+GOROOT_class-native = "${STAGING_LIBDIR_NATIVE}/go"
+GOROOT = "${STAGING_LIBDIR_NATIVE}/${TARGET_SYS}/go"
+GOBIN_FINAL_class-native = 

Re: [OE-core] [PATCH] wic: Prevent duplicate entries on fstab

2017-03-06 Thread Ed Bartosh
On Mon, Mar 06, 2017 at 11:00:59AM -0300, Fabio Berton wrote:
> Same error with poky-contrib:ed/wic/wip, we need to add --fstype= to
> part /boot line in all wks files.
> 
Only if we want boot partitions to be added to fstab. Currently / and
/boot partitions are not added. Why do we want to change this?

BTW, your patch will make wic to parse the same fstab file several
times. Can you change this, please?

> 
> On 03/03/2017 10:49 AM, Burton, Ross wrote:
> >
> >On 3 March 2017 at 12:12, Fabio Berton
> > >> wrote:
> >
> >Sorry for delay. This error for qemux86 is because common.wks.inc
> >and directdisk-gpt.wks files in scripts/lib/wic/canned-wks
> >directory doesn't have option --fstype= for part /boot.
> >
> >For qemuarm machines I get the error:
> >
> >| DEBUG: Executing python function set_image_size
> >| DEBUG: Python function set_image_size finished
> >| DEBUG: Executing shell function do_image_wic
> >| Error: Please build syslinux first
> >
> >
> >There's patches queued that will change the behaviour here and
> >likely cause your patch to not apply - can you rebase on top of
> >poky-contrib:ed/wic/wip and see what happens?  The build
> >dependency is now wic-tools.
> >
> >Ross
> 

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


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


Re: [OE-core] [PATCH v2] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Ed Bartosh
On Mon, Mar 06, 2017 at 04:49:25PM +, Burton, Ross wrote:
> On 6 March 2017 at 15:31, Ed Bartosh  wrote:
> 
> > +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> >
> 
> $ ( [ -h / ] && echo something ); echo $?
> 1
> 
> If the -h fails then this is still going to cause sstate_unpack_package to
> trap.

I don't think it will as '&&' and '||' lists are among other special cases where
shell doesn't exits on error.

Here is a proof:

$ cat test.sh

set -e

trap 'ouch!' ERR

foo() {
[ -h /etc/fstab ] && echo 'fstab is a symlink'
echo 'end of foo'
}

foo
echo $?

$ $ sh -e test.sh
end of foo
0


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


Re: [OE-core] something seems to have happened to "gpgme" in latest oe-core

2017-03-06 Thread Mark Hatle
FYI, I'm experiencing the same issue on master.

--Mark

On 2/20/17 11:40 AM, Burton, Ross wrote:
> 
> On 20 February 2017 at 11:54, Robert P. J. Day  > wrote:
>>   gpgme config.log attached.
> 
> cc1: warning: include location "/usr/include/python2.7" is unsafe for
> cross-compilation [-Wpoison-system-directories]
> 
> It decided to try looking on your host for Python libraries for some reason. 
> You'll have to dig into configure.ac  to figure out why 
> (or
> just turn Python explicitly off).
> 
> Ross
> 
> 

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


Re: [OE-core] [PATCH v2] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Burton, Ross
On 6 March 2017 at 15:31, Ed Bartosh  wrote:

> +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
>

$ ( [ -h / ] && echo something ); echo $?
1

If the -h fails then this is still going to cause sstate_unpack_package to
trap.

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


Re: [OE-core] [jethro][PATCH] Forklift OpenSSL 1.0.k to Jethro

2017-03-06 Thread akuster808



On 03/05/2017 07:20 PM, Rebecca Chang Swee Fun wrote:

From: "Chang, Rebecca Swee Fun" 

Hi all,

This is an version upgrade for OpenSSL from 1.0.2h to 1.0.2k.
The upgrade was forklifted from OE-Core master branch to
Jethro branch and remove upstream dependencies to new bbclasses.

The details of CVEs are mentioned in the patch commit message.

The main purpose of this forklifting effort is to make sure
OpenSSL shipped in BSPs is updated.
Due to OpenSSL version
fork in Jethro, it is difficult to do purely "git cherry-pick"
and resolving conflicts everywhere.


Its not difficult, its just time consuming.


This is main reason I opted for forklifting approach.
We have discussed updating openssl as the method for managing this 
package in stable branches and it was met with lots of resistance. 
Seeing this is Jethro ( nearly 2 yrs old), I would suspect this is a 
much harder sell to make.





This is the first time I did an upgrade for OpenSSL. Please
help to review and provide feedbacks if this approach is not
feasible.
The feasible call is on the stable branch maintainer and oe-core layer 
maintainers.


per policy, these changes would have to propagate through the other 
stable branches first if we didn't want to make an exception.


- armin


  I'm looking forward to learn from everyone of you.

Thank you very much.

Regards,
Rebecca

Chang, Rebecca Swee Fun (1):
   openssl: upgrade 1.0.2h -> 1.0.2k

  meta/recipes-connectivity/openssl/openssl.inc  |  104 +-
  .../openssl/openssl/0002-CVE-2017-3731.patch   |   53 +
  .../openssl/openssl/CVE-2016-2177.patch|  286 --
  .../openssl/openssl/CVE-2016-2178.patch|   51 -
  .../openssl/openssl/CVE-2016-2179.patch|  255 --
  .../openssl/openssl/CVE-2016-2180.patch|   44 -
  .../openssl/openssl/CVE-2016-2181_p1.patch |   91 -
  .../openssl/openssl/CVE-2016-2181_p2.patch |  239 -
  .../openssl/openssl/CVE-2016-2181_p3.patch |   30 -
  .../openssl/openssl/CVE-2016-2182.patch|   70 -
  .../openssl/openssl/CVE-2016-6302.patch|   53 -
  .../openssl/openssl/CVE-2016-6303.patch|   36 -
  .../openssl/openssl/CVE-2016-6304.patch|   75 -
  .../openssl/openssl/CVE-2016-6306.patch|   71 -
  .../openssl/openssl/CVE-2016-8610.patch|  124 -
  .../Use-SHA256-not-MD5-as-default-digest.patch |   69 +
  .../openssl/crypto_use_bigint_in_x86-64_perl.patch |   33 -
  .../openssl/openssl/debian/ca.patch|2 +-
  .../openssl/openssl/debian/version-script.patch| 4663 
  .../openssl/debian1.0.2/version-script.patch   |   31 +-
  .../openssl/openssl/fix-cipher-des-ede3-cfb1.patch |2 +-
  .../openssl/openssl/openssl-c_rehash.sh|  222 +
  .../openssl/openssl-util-perlpath.pl-cwd.patch |   34 +
  .../openssl/openssl/openssl_fix_for_x32.patch  |4 +-
  .../openssl/openssl/parallel.patch |   17 +-
  .../recipes-connectivity/openssl/openssl_1.0.2h.bb |   82 -
  .../recipes-connectivity/openssl/openssl_1.0.2k.bb |   64 +
  27 files changed, 5200 insertions(+), 1605 deletions(-)
  create mode 100644 
meta/recipes-connectivity/openssl/openssl/0002-CVE-2017-3731.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2177.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2178.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2179.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2180.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2181_p1.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2181_p2.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2181_p3.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-2182.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-6302.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-6303.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-6304.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-6306.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/CVE-2016-8610.patch
  create mode 100644 
meta/recipes-connectivity/openssl/openssl/Use-SHA256-not-MD5-as-default-digest.patch
  delete mode 100644 
meta/recipes-connectivity/openssl/openssl/crypto_use_bigint_in_x86-64_perl.patch
  create mode 100644 
meta/recipes-connectivity/openssl/openssl/debian/version-script.patch
  create mode 100644 
meta/recipes-connectivity/openssl/openssl/openssl-c_rehash.sh
  create mode 100644 
meta/recipes-connectivity/openssl/openssl/openssl-util-perlpath.pl-cwd.patch
  delete mode 100644 meta/recipes-connectivity/openssl/openssl_1.0.2h.bb
  create mode 100644 

[OE-core] [PATCH v2] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Ed Bartosh
.siginfo files are not being accessed from local or NFS-mounted
sstate mirrors when sstate package is installed, so their atime
is not updated. If sstate mirror is cleaned based on access time,
they get deleted, even though they are still being used.

Updated atime of .siginfo symlinks with 'touch -a'. This command
dereferences symlinks pointing to the local mirror and updates
atime of the .siginfo file on the mirror.

[YOCTO #10857]

Signed-off-by: Ed Bartosh 
---
 meta/classes/sstate.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 23dda08..e415f68 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -747,6 +747,8 @@ python sstate_sign_package () {
 #
 sstate_unpack_package () {
tar -xvzf ${SSTATE_PKG}
+   # update .siginfo atime on local/NFS mirror
+   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
# Use "! -w ||" to return true for read only files
[ ! -w ${SSTATE_PKG} ] || touch --no-dereference ${SSTATE_PKG}
[ ! -w ${SSTATE_PKG}.sig ] || [ ! -e ${SSTATE_PKG}.sig ] || touch 
--no-dereference ${SSTATE_PKG}.sig
-- 
2.1.4

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


[OE-core] Yocto Project Status WW10’17

2017-03-06 Thread Jolley, Stephen K
Current Dev Position: YP 2.3 M3

Next Deadline: YP 2.3 M3 by Feb. 27, 2017


*** FEATURE FREEZE for 2.3 is now in effect. ***


SWAT team rotation: Todor -> Tracy on Mar. 4, 2017.

SWAT team rotation: Tracy -> Alejandro on Mar. 11, 2017.

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

·2.3 M3 has not yet build but progress is being made on 
stabilizing/merging the patches.

·As promised, the codename for 2.4 will be announced now and will be 
‘rocko’

·We have been hit with a number of problems around minimal builds of 
eSDK, where there were problems in the autobuilder implementation of this, 
minimal eSDKs themselves and changes to the testing infrastructure for minimal 
eSDKs. With so many moving pieces it's taken Ross/RP several days to unwind the 
problems and fix them. The good news is this issue is now resolved.

·We are not going to make the move from smart to dnf in 2.3, there 
simply isn’t enough development time left and the feature isn’t ready.

·We have merged ovmf, the queued wic changes, many queued version 
updates, some selftest speedup optimizations, 4.10 kernel changes, the YP 
compatible testing script, and many other patches.

·Still pending are:

o   Merging go into OE-Core?

o   Separate out elderly GPLv2 into a separate layer?

Go continues to suffer build failures, I have a patchset for gplv2 ready for 
testing and have posted on the openembedded-architecture list about that change.

·Since we’re into the stabilization phase of 2.3, planning for 2.4 will 
be beginning soon and we’re starting to plan out 2.4 in the bugzilla. If you 
have suggestions for 2.4, please ensure they are in bugzilla.


Proposed upcoming dot releases:

YP 2.1.3 Cut off May 15, 2017

YP 2.1.3 Release by May 26, 2017

YP 2.2.2 Cut off May 29, 2017

YP 2.2.2 Release by June 9, 2017


Key YP 2.3 Dates:

YP 2.3 M3 Release is Mar. 10, 2017 (Will be a few weeks late.)

YP 2.3 M4 Cutoff is April 10, 2017

YP 2.3 M4 Release is May 5, 2017


Tracking Metrics:

WDD 2737 (last week 2744)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.3_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.3_Features


[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•   Work Telephone:(503) 712-0534
•Cell:   (208) 244-4460
• Email:stephen.k.jol...@intel.com

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


Re: [OE-core] [morty][PATCH] busybox: refresh the flock patch

2017-03-06 Thread John, Maxin
Hi Armin,

It looks like this fell through the cracks. Please consider this for morty.

-Original Message-
From: openembedded-core-boun...@lists.openembedded.org 
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Maxin B. 
John
Sent: Tuesday, January 17, 2017 6:21 PM
To: openembedded-core@lists.openembedded.org
Subject: [OE-core] [morty][PATCH] busybox: refresh the flock patch

Upstream accepted the flock fix with some improvements. Backport those changes.

Signed-off-by: Maxin B. John 
---
 ...e-the-behaviour-of-c-parameter-to-match-u.patch | 77 ++
 1 file changed, 34 insertions(+), 43 deletions(-)

diff --git 
a/meta/recipes-core/busybox/busybox/0001-flock-update-the-behaviour-of-c-parameter-to-match-u.patch
 
b/meta/recipes-core/busybox/busybox/0001-flock-update-the-behaviour-of-c-parameter-to-match-u.patch
index 8bcbd73..78520f0 100644
--- 
a/meta/recipes-core/busybox/busybox/0001-flock-update-the-behaviour-of-c-parameter-to-match-u.patch
+++ b/meta/recipes-core/busybox/busybox/0001-flock-update-the-behaviour-
+++ of-c-parameter-to-match-u.patch
@@ -1,35 +1,24 @@
-From 198f18addf1d814c2fefcb492f3b9fbd221669bb Mon Sep 17 00:00:00 2001
-From: "Maxin B. John" 
-Date: Wed, 20 Apr 2016 18:24:45 +0300
-Subject: [PATCH] flock: update the behaviour of -c parameter to match upstream
-
-In upstream, -c 'PROG ARGS' means "run sh -c 'PROG ARGS'"
+From e1d426fd65c00a6d01a10d85edf8a294ae8a2d2b Mon Sep 17 00:00:00 2001
+From: Denys Vlasenko 
+Date: Sun, 24 Apr 2016 18:19:49 +0200
+Subject: [PATCH] flock: fix -c; improve error handling of fork+exec
 
 function old new   delta
-flock_main   286 377 +91
-.rodata   155849  155890 +41
+flock_main   254 334 +80
 
-Upstream-Status: Submitted
-[ http://lists.busybox.net/pipermail/busybox/2016-April/084142.html ]
+Upstream-Status: Backport
 
+Signed-off-by: Denys Vlasenko 
 Signed-off-by: Maxin B. John 
 ---
- util-linux/flock.c | 20 ++--
- 1 file changed, 14 insertions(+), 6 deletions(-)
+ util-linux/flock.c | 19 +--
+ 1 file changed, 17 insertions(+), 2 deletions(-)
 
 diff --git a/util-linux/flock.c b/util-linux/flock.c -index 05a747f..c85a25d 
100644
+index 05a747f..539a835 100644
 --- a/util-linux/flock.c
 +++ b/util-linux/flock.c
-@@ -20,6 +20,7 @@ int flock_main(int argc, char **argv) 
MAIN_EXTERNALLY_VISIBLE;
- int flock_main(int argc UNUSED_PARAM, char **argv)
- {
-   int mode, opt, fd;
-+char *cmd_args[4];
-   enum {
-   OPT_s = (1 << 0),
-   OPT_x = (1 << 1),
-@@ -57,7 +58,6 @@ int flock_main(int argc UNUSED_PARAM, char **argv)
+@@ -57,7 +57,6 @@ int flock_main(int argc UNUSED_PARAM, char **argv)
/* If it is "flock FILE -c PROG", then -c isn't caught by getopt32:
 * we use "+" in order to support "flock -opt FILE PROG -with-opts",
 * we need to remove -c by hand.
@@ -37,35 +26,37 @@ index 05a747f..c85a25d 100644
 */
if (argv[0]
 && argv[0][0] == '-'
-@@ -65,7 +65,10 @@ int flock_main(int argc UNUSED_PARAM, char **argv)
-   || (ENABLE_LONG_OPTS && strcmp(argv[0] + 1, "-command") == 0)
+@@ -66,6 +65,9 @@ int flock_main(int argc UNUSED_PARAM, char **argv)
)
) {
--  argv++;
-+if (argc != optind + 3)
-+bb_error_msg_and_die("-c requires exactly one command argument");
-+else
-+argv++;
+   argv++;
++  if (argv[1])
++  bb_error_msg_and_die("-c takes only one argument");
++  opt |= OPT_c;
}
  
if (OPT_s == LOCK_SH && OPT_x == LOCK_EX && OPT_n == LOCK_NB && OPT_u 
== LOCK_UN) { -@@ -89,9 +92,14 @@ int flock_main(int argc UNUSED_PARAM, char 
**argv)
-   return EXIT_FAILURE;
+@@ -90,8 +92,21 @@ int flock_main(int argc UNUSED_PARAM, char **argv)
bb_perror_nomsg_and_die();
}
--
+ 
 -  if (argv[0])
--  return spawn_and_wait(argv);
--
-+if (argv[0]) {
-+cmd_args[0] = getenv("SHELL");
-+if (!cmd_args[0])
-+cmd_args[0] = (char*)DEFAULT_SHELL;
-+cmd_args[1] = (char*)"-c";
-+cmd_args[2] = argv[0];
-+cmd_args[3] = NULL;
-+return spawn_and_wait(cmd_args);
-+}
++  if (argv[0]) {
++  if (!(opt & OPT_c)) {
++  int rc = spawn_and_wait(argv);
++  if (rc < 0)
++  bb_simple_perror_msg(argv[0]);
++  return rc;
++  }
++  /* -c 'PROG ARGS' means "run sh -c 'PROG ARGS'" */
++  argv -= 2;
++  argv[0] = 

Re: [OE-core] [PATCH 1/1] bash: 4.3.30 -> 4.4

2017-03-06 Thread Burton, Ross
The loadable package is empty when I do a build, do these have some
floating build dependency?

Ross

On 22 February 2017 at 02:25, Hongxu Jia  wrote:

> From: Zheng Ruoqin 
>
> 1) Upgrade bash from 4.3.30 to 4.4
> 2) Delete 1 patche below, since they are integrated upstream.
>fix-run-intl.patch
> 3) Modify 2 patches below to make it compatible with new version
>fix-run-coproc-run-heredoc-run-execscript-run-test-f.patch
>test-output.patch
> 4) Add 1 patche below to solve pkgconfig sanity error
>0001-patch-to-obtain-pkgconfig-sanity.patch
>
> Signed-off-by: Zheng Ruoqin 
>
> 5) Delete CVE-2016-9401.patch which backported from 4.4
>
> 6) Update patches from upstream to 4.4
>
> 7) Add ${PN}-loadable for loadable builtins which is new features in Bash
> 4.4
>--
>a.  `make install' now installs the example loadable builtins and a set
> of
>bash headers to use when developing new loadable builtins.
>
>b.  `enable -f' now attempts to call functions named
> BUILTIN_builtin_load when
>loading BUILTIN, and BUILTIN_builtin_unload when deleting it.  This
> allows
>loadable builtins to run initialization and cleanup code.
>
>c.  There is a new BASH_LOADABLES_PATH variable containing a list of
> directories
>where the `enable -f' command looks for shared objects containing
> loadable
>builtins.
>--
>
> 8) Fix loadable builtins `uname' could not be parsed by rpmdeps correctly:
>--
>$ recipe-sysroot-native/usr/lib/rpm/bin/rpmdeps-oecore --macros \
>recipe-sysroot-native/usr/lib/rpm/macros --define '_rpmfc_magic_path \
>recipe-sysroot-native/usr/share/misc/magic.mgc' --rpmpopt \
>recipe-sysroot-native/usr/lib/rpm/rpmpopt
> packages-split/bash/usr/lib64/bash/uname
>
>|packages-split/bash/usr/lib64/bash/uname Provides: )(64bit
>|packages-split/bash/usr/lib64/bash/uname Provides: elf(buildid) =
> 7186059a5a6b11ec38493b53072c3a62edf7e05c
>--
>
>The incorrected "Provides: )(64bit" could not be parsed by rpmbuild.
>--
>| DEBUG: Executing shell function BUILDSPEC
>| error: line 56: Dependency ")(64bit" must begin with alpha-numeric,
> '_' or '/': Provides: )(64bit
>| error: Package has no %description: bash-4.4-r0.core2_64
>--
>
> Signed-off-by: Hongxu Jia 
> ---
>  ...e-builtins-uname-could-not-be-parsed-by-r.patch |  89 +
>  .../0001-patch-to-obtain-pkgconfig-sanity.patch|  28 +
>  .../recipes-extended/bash/bash/CVE-2016-9401.patch |  50 
>  ...roc-run-heredoc-run-execscript-run-test-f.patch | 137
> ++---
>  meta/recipes-extended/bash/bash/fix-run-intl.patch | 110
> -
>  meta/recipes-extended/bash/bash/test-output.patch  |  20 ++-
>  meta/recipes-extended/bash/bash_4.3.30.bb  |  72 ---
>  meta/recipes-extended/bash/bash_4.4.bb |  66 ++
>  8 files changed, 209 insertions(+), 363 deletions(-)
>  create mode 100644 meta/recipes-extended/bash/bash/0001-The-loadable-
> builtins-uname-could-not-be-parsed-by-r.patch
>  create mode 100644 meta/recipes-extended/bash/bash/0001-patch-to-obtain-
> pkgconfig-sanity.patch
>  delete mode 100644 meta/recipes-extended/bash/bash/CVE-2016-9401.patch
>  delete mode 100644 meta/recipes-extended/bash/bash/fix-run-intl.patch
>  delete mode 100644 meta/recipes-extended/bash/bash_4.3.30.bb
>  create mode 100644 meta/recipes-extended/bash/bash_4.4.bb
>
> diff --git a/meta/recipes-extended/bash/bash/0001-The-loadable-
> builtins-uname-could-not-be-parsed-by-r.patch
> b/meta/recipes-extended/bash/bash/0001-The-loadable-
> builtins-uname-could-not-be-parsed-by-r.patch
> new file mode 100644
> index 000..79d9e4e
> --- /dev/null
> +++ b/meta/recipes-extended/bash/bash/0001-The-loadable-
> builtins-uname-could-not-be-parsed-by-r.patch
> @@ -0,0 +1,89 @@
> +rename uname to workaround name confliction in rpmnsProbe
> +
> +The loadable builtins `uname' could not be parsed by
> +rpmdeps correctly:
> +--
> +$recipe-sysroot-native/usr/lib/rpm/bin/rpmdeps-oecore --macros \
> +recipe-sysroot-native/usr/lib/rpm/macros --define '_rpmfc_magic_path \
> +recipe-sysroot-native/usr/share/misc/magic.mgc' --rpmpopt \
> +recipe-sysroot-native/usr/lib/rpm/rpmpopt packages-split/bash/usr/lib64/
> bash/uname
> +
> +|packages-split/bash/usr/lib64/bash/uname Provides: )(64bit
> +|packages-split/bash/usr/lib64/bash/uname Provides: elf(buildid) =
> 7186059a5a6b11ec38493b53072c3a62edf7e05c
> +--
> +
> +The incorrected "Provides: )(64bit" could not be parsed by rpmbuild.
> +--
> +| DEBUG: Executing shell function BUILDSPEC
> +| error: line 56: Dependency ")(64bit" must begin with alpha-numeric, '_'
> or '/': Provides: )(64bit
> +| error: Package has no %description: bash-4.4-r0.core2_64
> 

[OE-core] [PATCH v3 1/4] qemu: Improve and add PACKAGECONFIG options

2017-03-06 Thread Nathan Rossi
Move the '--disable-bluez' and '--disable-iscsi' options to
PACKAGECONFIG. And added the ${BLUEZ} dependency.

Fix up the 'gcrypt' option to depend on 'libgcrypt' instead of gcrypt.
This is the expected dependency as noted in the QEMU configure help.

Handle the '--audio-drv-list' option inside the PACKAGECONFIG[alsa]
args. The previous setting uses a ',' to denote the options for the arg
however a space inside quotes is also acceptable and allows the arg to
be used into the PACKAGECONFIG flag.

Signed-off-by: Nathan Rossi 
---
 meta/recipes-devtools/qemu/qemu.inc | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 2b82e8fd02..1857786917 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -6,7 +6,7 @@ RDEPENDS_${PN}_class-target += "bash"
 RDEPENDS_${PN}-ptest = "bash make"
 
 require qemu-targets.inc
-inherit autotools pkgconfig ptest
+inherit autotools pkgconfig ptest bluetooth
 BBCLASSEXTEND = "native nativesdk"
 
 # QEMU_TARGETS is overridable variable
@@ -26,7 +26,7 @@ SRC_URI_append_class-native = "\
 file://cpus.c-qemu_cpu_kick_thread_debugging.patch \
 "
 
-EXTRA_OECONF += "--target-list=${@get_qemu_target_list(d)} --disable-werror  
--disable-bluez --disable-libiscsi --with-system-pixman 
--extra-cflags='${CFLAGS}'"
+EXTRA_OECONF += "--target-list=${@get_qemu_target_list(d)} --disable-werror  
--with-system-pixman --extra-cflags='${CFLAGS}'"
 
 EXTRA_OECONF_class-nativesdk = "--target-list=${@get_qemu_target_list(d)} 
--disable-werror"
 EXTRA_OECONF_append_class-native = " --python=${USRBINPATH}/python2"
@@ -120,17 +120,17 @@ PACKAGECONFIG[curses] = 
"--enable-curses,--disable-curses,ncurses,"
 PACKAGECONFIG[gtk+] = "--enable-gtk --with-gtkabi=3.0 
--enable-vte,--disable-gtk --disable-vte,gtk+3 vte"
 PACKAGECONFIG[libcap-ng] = "--enable-cap-ng,--disable-cap-ng,libcap-ng,"
 PACKAGECONFIG[ssh2] = "--enable-libssh2,--disable-libssh2,libssh2,"
-PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,gcrypt,"
+PACKAGECONFIG[gcrypt] = "--enable-gcrypt,--disable-gcrypt,libgcrypt,"
 PACKAGECONFIG[nettle] = "--enable-nettle,--disable-nettle,nettle"
 PACKAGECONFIG[libusb] = "--enable-libusb,--disable-libusb,libusb1"
 PACKAGECONFIG[fdt] = "--enable-fdt,--disable-fdt,dtc"
-PACKAGECONFIG[alsa] = ",,alsa-lib"
+PACKAGECONFIG[alsa] = "--audio-drv-list='oss alsa',,alsa-lib"
 PACKAGECONFIG[glx] = "--enable-opengl,--disable-opengl,mesa"
 PACKAGECONFIG[lzo] = "--enable-lzo,--disable-lzo,lzo"
 PACKAGECONFIG[numa] = "--enable-numa,--disable-numa,numactl"
 PACKAGECONFIG[gnutls] = "--enable-gnutls,--disable-gnutls,gnutls"
 PACKAGECONFIG[bzip2] = "--enable-bzip2,--disable-bzip2,bzip2"
-
-EXTRA_OECONF += "${@bb.utils.contains('PACKAGECONFIG', 'alsa', 
'--audio-drv-list=oss,alsa', '', d)}"
+PACKAGECONFIG[bluez] = "--enable-bluez,--disable-bluez,${BLUEZ}"
+PACKAGECONFIG[libiscsi] = "--enable-libiscsi,--disable-libiscsi"
 
 INSANE_SKIP_${PN} = "arch"
-- 
2.11.0

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


[OE-core] [PATCH v3 2/4] qemu: Consolidate EXTRA_OECONF

2017-03-06 Thread Nathan Rossi
Consolidate the configure options into the EXTRA_OECONF variable,
including merging any native(sdk) specific options.

This consolidation also makes the use of 'system' pixman in the
nativesdk case, this is desirable as the QEMU internal pixman may not be
available (using QEMU git as opposed to tarball) and pixman is already
in DEPENDS. Additionally the QEMU configure recommends to use the system
pixman if available.

Additionally move the options specified in the do_configure into the
EXTRA_OECONF variable. And flesh out all the target directories.

Signed-off-by: Nathan Rossi 
---
 meta/recipes-devtools/qemu/qemu.inc | 23 +++
 1 file changed, 19 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 1857786917..72430cc6fd 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -26,9 +26,24 @@ SRC_URI_append_class-native = "\
 file://cpus.c-qemu_cpu_kick_thread_debugging.patch \
 "
 
-EXTRA_OECONF += "--target-list=${@get_qemu_target_list(d)} --disable-werror  
--with-system-pixman --extra-cflags='${CFLAGS}'"
-
-EXTRA_OECONF_class-nativesdk = "--target-list=${@get_qemu_target_list(d)} 
--disable-werror"
+EXTRA_OECONF = " \
+--prefix=${prefix} \
+--bindir=${bindir} \
+--includedir=${includedir} \
+--libdir=${libdir} \
+--mandir=${mandir} \
+--datadir=${datadir} \
+--docdir=${docdir}/${BPN} \
+--sysconfdir=${sysconfdir} \
+--libexecdir=${libexecdir} \
+--localstatedir=${localstatedir} \
+--with-confsuffix=/${BPN} \
+--disable-strip \
+--disable-werror \
+--target-list=${@get_qemu_target_list(d)} \
+--with-system-pixman \
+--extra-cflags='${CFLAGS}' \
+"
 EXTRA_OECONF_append_class-native = " --python=${USRBINPATH}/python2"
 
 EXTRA_OEMAKE_append_class-native = " LD='${LD}' AR='${AR}' 
OBJCOPY='${OBJCOPY}' LDFLAGS='${LDFLAGS}'"
@@ -62,7 +77,7 @@ do_configure() {
KVMOPTS="${KVMENABLE}"
 fi
 
-${S}/configure --prefix=${prefix} --sysconfdir=${sysconfdir} 
--libexecdir=${libexecdir} --localstatedir=${localstatedir} --disable-strip 
${EXTRA_OECONF} $KVMOPTS
+${S}/configure ${EXTRA_OECONF} $KVMOPTS
 test ! -e ${S}/target-i386/beginend_funcs.sh || chmod a+x 
${S}/target-i386/beginend_funcs.sh
 }
 
-- 
2.11.0

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


[OE-core] [PATCH v3 3/4] qemu: Convert KVMOPTS to PACKAGECONFIG

2017-03-06 Thread Nathan Rossi
Move the KVMOPTS configuration checks and option setting to a
PACKAGECONFIG option.

This also changes the checking of KVM support on the host build machine
so that it is processed as a PACKAGECONFIG _remove for class-native
only. The darwin/mingw32 overrides are kept and applied as _remove
overrides.

Signed-off-by: Nathan Rossi 
---
 meta/recipes-devtools/qemu/qemu.inc | 26 --
 1 file changed, 12 insertions(+), 14 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 72430cc6fd..5bd41d0d90 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -65,19 +65,8 @@ do_configure_prepend_class-native() {
"${S}"/Makefile "${S}"/Makefile.target
 }
 
-KVMENABLE = "--enable-kvm"
-KVMENABLE_darwin = "--disable-kvm"
-KVMENABLE_mingw32 = "--disable-kvm"
-
 do_configure() {
-# Handle distros such as CentOS 5 32-bit that do not have kvm support
-KVMOPTS="--disable-kvm"
-if [ "${PN}" != "qemu-native" -a "${PN}" != "nativesdk-qemu" ] \
-   || [ -f /usr/include/linux/kvm.h ] ; then
-   KVMOPTS="${KVMENABLE}"
-fi
-
-${S}/configure ${EXTRA_OECONF} $KVMOPTS
+${S}/configure ${EXTRA_OECONF}
 test ! -e ${S}/target-i386/beginend_funcs.sh || chmod a+x 
${S}/target-i386/beginend_funcs.sh
 }
 
@@ -115,10 +104,18 @@ do_install_append() {
 
 PACKAGECONFIG ??= " \
fdt sdl \
+   fdt sdl kvm \
${@bb.utils.filter('DISTRO_FEATURES', 'alsa xen', d)} \
"
-PACKAGECONFIG_class-native ??= "fdt alsa uuid"
-PACKAGECONFIG_class-nativesdk ??= "fdt sdl"
+PACKAGECONFIG_class-native ??= "fdt alsa uuid kvm"
+PACKAGECONFIG_class-nativesdk ??= "fdt sdl kvm"
+
+# Handle distros such as CentOS 5 32-bit that do not have kvm support
+PACKAGECONFIG_class-native_remove = "${@'kvm' if not 
os.path.exists('/usr/include/linux/kvm.h') else ''}"
+
+# Disable kvm on targets that do not support it
+PACKAGECONFIG_remove_darwin = "kvm"
+PACKAGECONFIG_remove_mingw32 = "kvm"
 
 PACKAGECONFIG[sdl] = "--enable-sdl,--disable-sdl,libsdl"
 PACKAGECONFIG[virtfs] = "--enable-virtfs --enable-attr,--disable-virtfs,libcap 
attr,"
@@ -147,5 +144,6 @@ PACKAGECONFIG[gnutls] = 
"--enable-gnutls,--disable-gnutls,gnutls"
 PACKAGECONFIG[bzip2] = "--enable-bzip2,--disable-bzip2,bzip2"
 PACKAGECONFIG[bluez] = "--enable-bluez,--disable-bluez,${BLUEZ}"
 PACKAGECONFIG[libiscsi] = "--enable-libiscsi,--disable-libiscsi"
+PACKAGECONFIG[kvm] = "--enable-kvm,--disable-kvm"
 
 INSANE_SKIP_${PN} = "arch"
-- 
2.11.0

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


[OE-core] [PATCH v3 4/4] qemu: Move recipe version specific patches and features to recipe

2017-03-06 Thread Nathan Rossi
Move all the version specific patches, overrides and configuration that
are in qemu.inc to the versioned QEMU recipe.

This includes moving patches that target the versioned recipe, ptest
configuration (which is not available in QEMU by default) and the
installing of the powerpc_rom.bin.  All these patches/files are also
only located in the FILESEXTRAPATHS that is valid from the recipe file
and not from qemu.inc itself.

The purpose of this change is to make the qemu.inc re-usable for
multiple versions of QEMU as well as forks and recipes that intend to
provide custom patches.

Signed-off-by: Nathan Rossi 
---
 meta/recipes-devtools/qemu/qemu.inc  | 30 +-
 meta/recipes-devtools/qemu/qemu_2.8.0.bb | 31 ++-
 2 files changed, 31 insertions(+), 30 deletions(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 5bd41d0d90..85b344c960 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -3,29 +3,14 @@ HOMEPAGE = "http://qemu.org;
 LICENSE = "GPLv2 & LGPLv2.1"
 DEPENDS = "glib-2.0 zlib pixman"
 RDEPENDS_${PN}_class-target += "bash"
-RDEPENDS_${PN}-ptest = "bash make"
 
 require qemu-targets.inc
-inherit autotools pkgconfig ptest bluetooth
+inherit autotools pkgconfig bluetooth
 BBCLASSEXTEND = "native nativesdk"
 
 # QEMU_TARGETS is overridable variable
 QEMU_TARGETS ?= "arm aarch64 i386 mips mipsel mips64 mips64el ppc sh4 x86_64"
 
-SRC_URI = "\
-file://powerpc_rom.bin \
-file://disable-grabs.patch \
-file://exclude-some-arm-EABI-obsolete-syscalls.patch \
-file://wacom.patch \
-file://add-ptest-in-makefile.patch \
-file://run-ptest \
-"
-
-SRC_URI_append_class-native = "\
-file://fix-libcap-header-issue-on-some-distro.patch \
-file://cpus.c-qemu_cpu_kick_thread_debugging.patch \
-"
-
 EXTRA_OECONF = " \
 --prefix=${prefix} \
 --bindir=${bindir} \
@@ -70,22 +55,9 @@ do_configure() {
 test ! -e ${S}/target-i386/beginend_funcs.sh || chmod a+x 
${S}/target-i386/beginend_funcs.sh
 }
 
-do_compile_ptest() {
-   make buildtest-TESTS
-}
-
-do_install_ptest() {
-   cp -rL ${B}/tests ${D}${PTEST_PATH}
-   find ${D}${PTEST_PATH}/tests -type f -name "*.[Sshcod]" | xargs -i rm 
-rf {}
-
-   cp ${S}/tests/Makefile.include ${D}${PTEST_PATH}/tests
-}
-
 do_install () {
export STRIP="true"
autotools_do_install
-   install -d ${D}${datadir}/qemu
-   install -m 0755 ${WORKDIR}/powerpc_rom.bin ${D}${datadir}/qemu
 }
 
 # The following fragment will create a wrapper for qemu-mips user emulation
diff --git a/meta/recipes-devtools/qemu/qemu_2.8.0.bb 
b/meta/recipes-devtools/qemu/qemu_2.8.0.bb
index ce475e02cb..7bb4d06fb9 100644
--- a/meta/recipes-devtools/qemu/qemu_2.8.0.bb
+++ b/meta/recipes-devtools/qemu/qemu_2.8.0.bb
@@ -1,9 +1,20 @@
 require qemu.inc
 
+inherit ptest
+
+RDEPENDS_${PN}-ptest = "bash make"
+
 LIC_FILES_CHKSUM = "file://COPYING;md5=441c28d2cf86e15a37fa47e15a72fbac \
 
file://COPYING.LIB;endline=24;md5=c04def7ae38850e7d3ef548588159913"
 
-SRC_URI += "file://configure-fix-Darwin-target-detection.patch \
+SRC_URI += " \
+file://powerpc_rom.bin \
+file://disable-grabs.patch \
+file://exclude-some-arm-EABI-obsolete-syscalls.patch \
+file://wacom.patch \
+file://add-ptest-in-makefile.patch \
+file://run-ptest \
+file://configure-fix-Darwin-target-detection.patch \
 file://qemu-enlarge-env-entry-size.patch \
 file://no-valgrind.patch \
 file://pathlimit.patch \
@@ -19,6 +30,11 @@ SRC_URI += " \
 file://0004-Add-support-for-VM-suspend-resume-for-TPM-TIS.patch \
 "
 
+SRC_URI_append_class-native = " \
+file://fix-libcap-header-issue-on-some-distro.patch \
+file://cpus.c-qemu_cpu_kick_thread_debugging.patch \
+"
+
 SRC_URI =+ "http://wiki.qemu-project.org/download/${BP}.tar.bz2;
 
 SRC_URI[md5sum] = "17940dce063b6ce450a12e719a6c9c43"
@@ -30,4 +46,17 @@ COMPATIBLE_HOST_mipsarchn64 = "null"
 do_install_append() {
 # Prevent QA warnings about installed ${localstatedir}/run
 if [ -d ${D}${localstatedir}/run ]; then rmdir ${D}${localstatedir}/run; fi
+install -Dm 0755 ${WORKDIR}/powerpc_rom.bin ${D}${datadir}/qemu
+}
+
+do_compile_ptest() {
+   make buildtest-TESTS
 }
+
+do_install_ptest() {
+   cp -rL ${B}/tests ${D}${PTEST_PATH}
+   find ${D}${PTEST_PATH}/tests -type f -name "*.[Sshcod]" | xargs -i rm 
-rf {}
+
+   cp ${S}/tests/Makefile.include ${D}${PTEST_PATH}/tests
+}
+
-- 
2.11.0

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


[OE-core] [PATCH v3 0/4] Make qemu.inc useful for generic use

2017-03-06 Thread Nathan Rossi
This series is intended to make the qemu.inc more generic and useful for
other recipes to use. This is achieved by moving version specific
patches, task steps and ptest support into the qemu_*.bb recipe,
additionally improvements are made to the PACKAGECONFIG options and
changes to the configure step are made to allow for the configuration to
be more complete as well as easier to override/modify.
---
Changes in v2:
 * Rebased on top of current master
 * Updated changes for QEMU 2.8.0 recipe
Changes in v3:
 * Rebased on top of current master


Nathan Rossi (4):
  qemu: Improve and add PACKAGECONFIG options
  qemu: Consolidate EXTRA_OECONF
  qemu: Convert KVMOPTS to PACKAGECONFIG
  qemu: Move recipe version specific patches and features to recipe

 meta/recipes-devtools/qemu/qemu.inc  | 83 +---
 meta/recipes-devtools/qemu/qemu_2.8.0.bb | 31 +++-
 2 files changed, 64 insertions(+), 50 deletions(-)

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


[OE-core] [PATCH 3/5] selftest: test wic efi image in qemu

2017-03-06 Thread Ed Bartosh
Added test_qemu_efi test case to wic test suite.

It uses ovmf qemu extention to test mkefidisk image.

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/selftest/wic.py | 14 ++
 1 file changed, 14 insertions(+)

diff --git a/meta/lib/oeqa/selftest/wic.py b/meta/lib/oeqa/selftest/wic.py
index b7fe52f..dcb88ba 100644
--- a/meta/lib/oeqa/selftest/wic.py
+++ b/meta/lib/oeqa/selftest/wic.py
@@ -547,3 +547,17 @@ part /etc --source rootfs --ondisk mmcblk0 --fstype=ext4 
--exclude-path bin/ --r
 status, output = qemu.run_serial(cmd)
 self.assertEqual(1, status, 'Failed to run command "%s": %s' % 
(cmd, output))
 self.assertEqual(output, '/dev/root /\r\n/dev/vda3 /mnt')
+
+def test_qemu_efi(self):
+"""Test core-image-minimal efi image under qemu"""
+config = 'IMAGE_FSTYPES = "wic"\nWKS_FILE = "mkefidisk.wks"\n'
+self.append_config(config)
+self.assertEqual(0, bitbake('core-image-minimal ovmf').status)
+self.remove_config(config)
+
+with runqemu('core-image-minimal', ssh=False,
+ runqemuparams='ovmf', image_fstype='wic') as qemu:
+cmd = "grep vda. /proc/partitions  |wc -l"
+status, output = qemu.run_serial(cmd)
+self.assertEqual(1, status, 'Failed to run command "%s": %s' % 
(cmd, output))
+self.assertEqual(output, '3')
-- 
2.1.4

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


[OE-core] [PATCH 5/5] selftest: remove extra backslashes from debug output

2017-03-06 Thread Ed Bartosh
Remove unneeded backslashes from the format strings that
caused debug output to look confusing:

2017-03-06 16:52:42,428 - selftest.base - DEBUG - Removing from: ...
\IMAGE_FSTYPES = "wic"
WKS_FILE = "mkefidisk.wks"

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/selftest/base.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/base.py b/meta/lib/oeqa/selftest/base.py
index 26c93f9..47a8ea8 100644
--- a/meta/lib/oeqa/selftest/base.py
+++ b/meta/lib/oeqa/selftest/base.py
@@ -163,7 +163,7 @@ be re-executed from a clean environment to ensure accurate 
results.")
 
 # remove data from /conf/selftest.inc
 def remove_config(self, data):
-self.log.debug("Removing from: %s\n\%s\n" % (self.testinc_path, data))
+self.log.debug("Removing from: %s\n%s\n" % (self.testinc_path, data))
 ftools.remove_from_file(self.testinc_path, data)
 
 # write to meta-sefltest/recipes-test//test_recipe.inc
@@ -206,7 +206,7 @@ be re-executed from a clean environment to ensure accurate 
results.")
 
 # remove data from /conf/bblayers.inc
 def remove_bblayers_config(self, data):
-self.log.debug("Removing from: %s\n\%s\n" % 
(self.testinc_bblayers_path, data))
+self.log.debug("Removing from: %s\n%s\n" % 
(self.testinc_bblayers_path, data))
 ftools.remove_from_file(self.testinc_bblayers_path, data)
 
 # write to /conf/machine.inc
-- 
2.1.4

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


[OE-core] [PATCH 4/5] qemurunner.py: ignore decode errors

2017-03-06 Thread Ed Bartosh
qemu output can contain control characters. This cause qemurunner
API to crash when decoding the output to utf-8:

Traceback (most recent call last):
  File "/usr/lib64/python3.4/threading.py", line 911, in _bootstrap_inner
self.run()
  File "meta/lib/oeqa/utils/qemurunner.py", line 472, in run
threading.Thread.run(self)
  File "/usr/lib64/python3.4/threading.py", line 859, in run
self._target(*self._args, **self._kwargs)
  File "meta/lib/oeqa/utils/qemurunner.py", line 465, in threadtarget
self.eventloop()
  File "meta/lib/oeqa/utils/qemurunner.py", line 526, in eventloop
self.logfunc(data)
  File "meta/lib/oeqa/utils/qemurunner.py", line 77, in log
msg = msg.decode("utf-8")
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xda in position 0:
unexpected end of data

Added errors='ignore' to decode call to fix this.

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/utils/qemurunner.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 19f0f92..59dc11d 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -74,7 +74,7 @@ class QemuRunner:
 if self.logfile:
 # It is needed to sanitize the data received from qemu
 # because is possible to have control characters
-msg = msg.decode("utf-8")
+msg = msg.decode("utf-8", errors='ignore')
 msg = re_control_char.sub('', msg)
 with codecs.open(self.logfile, "a", encoding="utf-8") as f:
 f.write("%s" % msg)
-- 
2.1.4

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


[OE-core] [PATCH 2/5] targetcontrol: add image_fstype argument to commands.runqemu

2017-03-06 Thread Ed Bartosh
qemu runner picks up first fsimage type from the hard-coded
list of supported types. This makes it impossible to test
particular image type unless it's not ext4(first type in
the hardcoded list of types).

Added image_fstypes argument to commands.runqemu and QemuTarget
__init__ to specify type of the image to run qemu with.

This will be used to pass wic image type to test efi wic images.

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/targetcontrol.py  | 4 ++--
 meta/lib/oeqa/utils/commands.py | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index dbd2c7c..0ad3a6b 100644
--- a/meta/lib/oeqa/targetcontrol.py
+++ b/meta/lib/oeqa/targetcontrol.py
@@ -113,11 +113,11 @@ class QemuTarget(BaseTarget):
 
 supported_image_fstypes = ['ext3', 'ext4', 'cpio.gz', 'wic']
 
-def __init__(self, d):
+def __init__(self, d, image_fstype=None):
 
 super(QemuTarget, self).__init__(d)
 
-self.image_fstype = self.get_image_fstype(d)
+self.image_fstype = image_fstype or self.get_image_fstype(d)
 self.qemulog = os.path.join(self.testdir, "qemu_boot_log.%s" % 
self.datetime)
 self.rootfs = os.path.join(d.getVar("DEPLOY_DIR_IMAGE"),  
d.getVar("IMAGE_LINK_NAME") + '.' + self.image_fstype)
 self.kernel = os.path.join(d.getVar("DEPLOY_DIR_IMAGE"), 
d.getVar("KERNEL_IMAGETYPE", False) + '-' + d.getVar('MACHINE', False) + '.bin')
diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 73ede23..82c5908 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -218,7 +218,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True, runqemuparams=''):
+def runqemu(pn, ssh=True, runqemuparams='', image_fstype=None):
 
 import bb.tinfoil
 import bb.build
@@ -240,7 +240,7 @@ def runqemu(pn, ssh=True, runqemuparams=''):
 logger.propagate = False
 logdir = recipedata.getVar("TEST_LOG_DIR")
 
-qemu = oeqa.targetcontrol.QemuTarget(recipedata)
+qemu = oeqa.targetcontrol.QemuTarget(recipedata, image_fstype)
 finally:
 # We need to shut down tinfoil early here in case we actually want
 # to run tinfoil-using utilities with the running QEMU instance.
-- 
2.1.4

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


[OE-core] [PATCH 1/5] qemurunner: add runqemuparams argument to commands.runqemu

2017-03-06 Thread Ed Bartosh
Added possibility to pass additional runqemu parameters
down the stack of APIs:
 commands.runqemu -> QemuTarget.start -> QemuRunner.start

This will be used to pass ovmf parameter in testing of
efi wic images under qemu.

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/targetcontrol.py| 4 ++--
 meta/lib/oeqa/utils/commands.py   | 4 ++--
 meta/lib/oeqa/utils/qemurunner.py | 4 ++--
 meta/lib/oeqa/utils/qemutinyrunner.py | 2 +-
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index d1f441f..dbd2c7c 100644
--- a/meta/lib/oeqa/targetcontrol.py
+++ b/meta/lib/oeqa/targetcontrol.py
@@ -176,8 +176,8 @@ class QemuTarget(BaseTarget):
 bb.note("Qemu log file: %s" % self.qemulog)
 super(QemuTarget, self).deploy()
 
-def start(self, params=None, ssh=True, extra_bootparams=None):
-if self.runner.start(params, get_ip=ssh, 
extra_bootparams=extra_bootparams):
+def start(self, params=None, ssh=True, extra_bootparams=None, 
runqemuparams=''):
+if self.runner.start(params, get_ip=ssh, 
extra_bootparams=extra_bootparams, runqemuparams=runqemuparams):
 if ssh:
 self.ip = self.runner.ip
 self.server_ip = self.runner.server_ip
diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 0425c9f..73ede23 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -218,7 +218,7 @@ def create_temp_layer(templayerdir, templayername, 
priority=999, recipepathspec=
 
 
 @contextlib.contextmanager
-def runqemu(pn, ssh=True):
+def runqemu(pn, ssh=True, runqemuparams=''):
 
 import bb.tinfoil
 import bb.build
@@ -260,7 +260,7 @@ def runqemu(pn, ssh=True):
 try:
 qemu.deploy()
 try:
-qemu.start(ssh=ssh)
+qemu.start(ssh=ssh, runqemuparams=runqemuparams)
 except bb.build.FuncFailed:
 raise Exception('Failed to start QEMU - see the logs in %s' % 
logdir)
 
diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 21bc35a..19f0f92 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -95,7 +95,7 @@ class QemuRunner:
 self._dump_host()
 raise SystemExit
 
-def start(self, qemuparams = None, get_ip = True, extra_bootparams = None):
+def start(self, qemuparams = None, get_ip = True, extra_bootparams = None, 
runqemuparams=''):
 if self.display:
 os.environ["DISPLAY"] = self.display
 # Set this flag so that Qemu doesn't do any grabs as SDL grabs
@@ -136,7 +136,7 @@ class QemuRunner:
 self.origchldhandler = signal.getsignal(signal.SIGCHLD)
 signal.signal(signal.SIGCHLD, self.handleSIGCHLD)
 
-launch_cmd = 'runqemu snapshot '
+launch_cmd = 'runqemu snapshot %s ' % runqemuparams
 if self.use_kvm:
 logger.info('Using kvm for runqemu')
 launch_cmd += 'kvm '
diff --git a/meta/lib/oeqa/utils/qemutinyrunner.py 
b/meta/lib/oeqa/utils/qemutinyrunner.py
index d554f0d..ec52473 100644
--- a/meta/lib/oeqa/utils/qemutinyrunner.py
+++ b/meta/lib/oeqa/utils/qemutinyrunner.py
@@ -60,7 +60,7 @@ class QemuTinyRunner(QemuRunner):
 with open(self.logfile, "a") as f:
 f.write("%s" % msg)
 
-def start(self, qemuparams = None, ssh=True, extra_bootparams=None):
+def start(self, qemuparams = None, ssh=True, extra_bootparams=None, 
runqemuparams=''):
 
 if self.display:
 os.environ["DISPLAY"] = self.display
-- 
2.1.4

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


[OE-core] [PATCH 0/5] test efi images in qemu

2017-03-06 Thread Ed Bartosh
Hi,

This patchset adds testing of efi images in qemu to the wic test suite,
related oe-selftest API changes and small improvements.

The following changes since commit 4188e53f803aefdb26768abfad591283662cd27e:

  poky: make 4.10 the qemu* default (2017-03-04 23:19:03 +)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ed/wic/wip
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ed/wic/wip

Ed Bartosh (5):
  qemurunner: add runqemuparams argument to commands.runqemu
  targetcontrol: add image_fstype argument to commands.runqemu
  selftest: test wic efi image in qemu
  qemurunner.py: ignore decode errors
  selftest: remove extra backslashes from debug output

 meta/lib/oeqa/selftest/base.py|  4 ++--
 meta/lib/oeqa/selftest/wic.py | 14 ++
 meta/lib/oeqa/targetcontrol.py|  8 
 meta/lib/oeqa/utils/commands.py   |  6 +++---
 meta/lib/oeqa/utils/qemurunner.py |  6 +++---
 meta/lib/oeqa/utils/qemutinyrunner.py |  2 +-
 6 files changed, 27 insertions(+), 13 deletions(-)

--
Regards,
Ed

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


Re: [OE-core] [PATCH] pulseaudio: 9.0 -> 10.0

2017-03-06 Thread Burton, Ross
On 27 February 2017 at 11:40, Burton, Ross  wrote:

> Typical. :/  Thanks for trying, I must have something locally that
> triggers it.
>

So I grabbed scanelf to look into this quickly:

scanelf: scanelf_file_textrels(): ELF pulseaudio has TEXTREL markings but
doesnt appear to have any real TEXTREL's !?

Sigh.  Tooling bug.

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


Re: [OE-core] [PATCH V7] go: Add recipes for golang compilers and tools

2017-03-06 Thread Leonardo Sandoval
For the moment, manually cutting & pasting patchtest results:


* Issue Added patch file is missing Upstream-Status in the
header [test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of
meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch
 (possible values: Pending, Submitted, Accepted, Backport, Denied, 
Inappropriate)

* Issue A patch file has been added, but does not have a
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file
(meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch)




On Fri, 2017-03-03 at 15:18 -0800, Khem Raj wrote:
> * This is converging the recipes for go from
>   meta-virtualization and oe-meta-go
> 
> * Add recipes for go 1.7
> 
> * go.bbclass is added to ease out writing
>   recipes for go packages
> 
> * go-examples: Add an example, helloworld written in go
>   This should serve as temlate for writing go recipes
> 
> Signed-off-by: Khem Raj 
> ---
>  meta/classes/go.bbclass|  72 +++
>  meta/classes/goarch.bbclass|  46 +
>  meta/recipes-devtools/go/go-1.4.inc|  16 ++
>  ...alignment-for-the-.rel.plt-section-on-32-.patch |  30 +++
>  .../go/go-1.4/016-armhf-elf-header.patch   |  24 +++
>  ...ckport-cmd-link-support-new-386-amd64-rel.patch | 225 
> +
>  meta/recipes-devtools/go/go-1.4/syslog.patch   |  62 ++
>  meta/recipes-devtools/go/go-1.6.inc|  19 ++
>  .../go/go-1.6/armhf-elf-header.patch   |  23 +++
>  .../go/go-1.6/fix-cc-handling.patch|  50 +
>  .../go/go-1.6/fix-target-cc-for-build.patch|  17 ++
>  meta/recipes-devtools/go/go-1.6/gotooldir.patch|  30 +++
>  .../go/go-1.6/split-host-and-target-build.patch|  63 ++
>  meta/recipes-devtools/go/go-1.6/syslog.patch   |  62 ++
>  meta/recipes-devtools/go/go-1.7.inc|  19 ++
>  .../go/go-1.7/armhf-elf-header.patch   |  23 +++
>  .../go/go-1.7/fix-cc-handling.patch|  50 +
>  .../go/go-1.7/fix-target-cc-for-build.patch|  17 ++
>  meta/recipes-devtools/go/go-1.7/gotooldir.patch|  30 +++
>  .../go/go-1.7/split-host-and-target-build.patch|  62 ++
>  meta/recipes-devtools/go/go-1.7/syslog.patch   |  62 ++
>  meta/recipes-devtools/go/go-common.inc |  22 ++
>  meta/recipes-devtools/go/go-cross.inc  |  10 +
>  meta/recipes-devtools/go/go-cross_1.7.bb   |   5 +
>  meta/recipes-devtools/go/go-native.inc |  54 +
>  meta/recipes-devtools/go/go-native_1.4.bb  |   2 +
>  meta/recipes-devtools/go/go.inc|  80 
>  meta/recipes-devtools/go/go_1.6.bb |   4 +
>  meta/recipes-devtools/go/go_1.7.bb |   2 +
>  .../go-examples/files/helloworld.go|  10 +
>  meta/recipes-extended/go-examples/go-examples.inc  |  10 +
>  .../go-examples/go-helloworld_0.1.bb   |  13 ++
>  32 files changed, 1214 insertions(+)
>  create mode 100644 meta/classes/go.bbclass
>  create mode 100644 meta/classes/goarch.bbclass
>  create mode 100644 meta/recipes-devtools/go/go-1.4.inc
>  create mode 100644 
> meta/recipes-devtools/go/go-1.4/0001-cmd-ld-set-alignment-for-the-.rel.plt-section-on-32-.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.4/016-armhf-elf-header.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.4/go-cross-backport-cmd-link-support-new-386-amd64-rel.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.4/syslog.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6.inc
>  create mode 100644 meta/recipes-devtools/go/go-1.6/armhf-elf-header.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6/fix-cc-handling.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.6/fix-target-cc-for-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6/gotooldir.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.6/split-host-and-target-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.6/syslog.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7.inc
>  create mode 100644 meta/recipes-devtools/go/go-1.7/armhf-elf-header.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7/fix-cc-handling.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.7/fix-target-cc-for-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7/gotooldir.patch
>  create mode 100644 
> meta/recipes-devtools/go/go-1.7/split-host-and-target-build.patch
>  create mode 100644 meta/recipes-devtools/go/go-1.7/syslog.patch
>  create mode 100644 meta/recipes-devtools/go/go-common.inc
>  create mode 100644 meta/recipes-devtools/go/go-cross.inc
>  create mode 100644 meta/recipes-devtools/go/go-cross_1.7.bb
>  

Re: [OE-core] [PATCH v2] busybox: 1.24.1 -> 1.26.2

2017-03-06 Thread Burton, Ross
On 9 February 2017 at 10:33, zhengrq  wrote:

> 1) Upgrade busybox from 1.24.1 to 1.26.2
>

With busybox 1.24.1, the busybox package contains a /bin/sh ->
busybox.nosuid symlink and update-alternatives knows about the /bin/sh ->
busybox.nosuid alternative.

With 1.26.2, this binary doesn't exist anymore in the package and /bin/sh
is linked to busybox.suid at rootfs time.

sh being suid doesn't look right *at all*.  There are upstream changes to
make installing these binary names options, so it's quite likely that we're
just missing them in defconfig.

Also  makefile-fix-backport.patch was listed as a backported patch, so why
do we need to rebase it?  What's the current upstream-status, as you
deleted that from the patch?  Was it fixed in a different way in 1.26.2 so
the patch can be dropped?

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


Re: [OE-core] [PATCH] wic: Prevent duplicate entries on fstab

2017-03-06 Thread Fabio Berton
Same error with poky-contrib:ed/wic/wip, we need to add --fstype= to 
part /boot line in all wks files.



On 03/03/2017 10:49 AM, Burton, Ross wrote:


On 3 March 2017 at 12:12, Fabio Berton > wrote:


Sorry for delay. This error for qemux86 is because common.wks.inc
and directdisk-gpt.wks files in scripts/lib/wic/canned-wks
directory doesn't have option --fstype= for part /boot.

For qemuarm machines I get the error:

| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_wic
| Error: Please build syslinux first


There's patches queued that will change the behaviour here and likely 
cause your patch to not apply - can you rebase on top of 
poky-contrib:ed/wic/wip and see what happens?  The build dependency is 
now wic-tools.


Ross


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


Re: [OE-core] Fwd: [PATCH] busybox: conditional inclusion of login utilities

2017-03-06 Thread David Vincent
On lundi 6 mars 2017 13:48:22 CET Burton, Ross wrote:
> On 6 March 2017 at 08:31, David Vincent  wrote:
> > +   ${@["", "file://login-utilities.cfg"][(d.getVar('VIRTUAL-
> > RUNTIME_login_manager') == 'busybox')]} \
> 
> VIRTUAL_RUNTIME can be set per-image, so you can't do this.
> 
> Ross

I just copied the lines already present in the recipe (and I also forgot to 
modify the git version on a side note) :

${@[””, "file://init.cfg"][(d.getVar('VIRTUAL-RUNTIME_init_manager', True) == 
'busybox')]} \
 ${@["", "file://mdev.cfg"][(d.getVar('VIRTUAL-RUNTIME_dev_manager', True) == 
'busybox-mdev')]} \

So, what should be the proper way to conditionally include these fragments ?

I don't know for init and dev managers, but for login-utilities, my use case 
is that I don't want busybox to provide adduser/addgroup/... if I already have 
these provided by another package (e.g. Shadow).

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


Re: [OE-core] [PATCH] slang: add ptest

2017-03-06 Thread Burton, Ross
On 2 March 2017 at 17:29, Stefan Strogin  wrote:

> +   cp -r ${S}/src/test ${D}${PTEST_PATH}/
> +   mkdir ${D}${PTEST_PATH}/objs
> +   cp ${S}/src/objs/libslang.a ${D}${PTEST_PATH}/objs/
>

Why?

If this is because the tests need sltest, that's already been built and is
in the package: just patch the Makefile instead.  It's also huge, so I'd be
tempted to say we should strip sltest as enabling ptest for slang causes
slang-dbg to increase by 2MB.

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


Re: [OE-core] [PATCH] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Ed Bartosh
On Mon, Mar 06, 2017 at 11:14:49AM +, Burton, Ross wrote:
> On 1 March 2017 at 14:28, Ed Bartosh  wrote:
> 
> > +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> >
> 
> I think you need to end this with || true to eat the failure if the test
> fails.

Thank you for pointing out to this.
I guess it should work also if I move this line up. I'll send v2 soon.

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


Re: [OE-core] Fwd: [PATCH] busybox: conditional inclusion of login utilities

2017-03-06 Thread Burton, Ross
On 6 March 2017 at 08:31, David Vincent  wrote:

> +   ${@["", "file://login-utilities.cfg"][(d.getVar('VIRTUAL-
> RUNTIME_login_manager') == 'busybox')]} \
>

VIRTUAL_RUNTIME can be set per-image, so you can't do this.

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


Re: [OE-core] [RFC/PATCH] boost: Fix issue with python-numpy

2017-03-06 Thread Burton, Ross
On 4 March 2017 at 16:26, Moritz Fischer  wrote:

> Maybe making it another PACKAGECONFIG[numpy] option
> would be desirable?
>

Making another option would definitely be desirable.

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


Re: [OE-core] [PATCH v2] ghostscript: build and install libgs

2017-03-06 Thread Burton, Ross
On 6 March 2017 at 08:13, Andrew Shadura 
wrote:

> Build and install libgs library, which is a build dependency
> of a few other libraries, such as libspectre.
>
> We don't want to ship the executable binaries, only the library and its
> headers, hence oe_runmake install-so + rm -rf, not e.g. oe_libinstall.
>

This fails when security flags are enabled:

|
/data/poky-master/tmp/work/corei7-64-poky-linux/ghostscript/9.20-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/6.3.0/ld:
./soobj/ttfmain.o: relocation R_X86_64_PC32 against symbol
`st_ttfInterpreter' can not be used when making a shared object; recompile
with -fPIC
|
/data/poky-master/tmp/work/corei7-64-poky-linux/ghostscript/9.20-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/6.3.0/ld:
final link failed: Bad value

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


Re: [OE-core] libglu: dependency on x11

2017-03-06 Thread Burton, Ross
On 5 March 2017 at 18:35, Gabriel Huau  wrote:

> I thought it was possible to have an implementation of libGL.so without
> X11, for example by using Wayland or any other Window System, I didn't know
> that the libGL was tied to X11 (on Linux). Also, I didn't see any specific
> X11 code in the libGLU so I was a bit confused by the dependency on both
> OpenGL and x11.
>
> Non-X11 OpenGL implementations are generally EGL, which has an abstraction
for the display type.

I guess you can try removing the x11 dependency in GLU and see what
happens...  there may be no X specific code but X assumptions if it's using
the GLX API.

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


Re: [OE-core] [PATCH] sstate.bbclass: update .siginfo atime

2017-03-06 Thread Burton, Ross
On 1 March 2017 at 14:28, Ed Bartosh  wrote:

> +   [ -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
>

I think you need to end this with || true to eat the failure if the test
fails.

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


[OE-core] [PATCH] mesa: Upgrade 17.0.0 -> 17.0.1

2017-03-06 Thread Jussi Kukkonen
This is a bug fix release and first non-development release in 17.0
branch. There are ~50 bug fix commits (plus a few release script
commits).

Signed-off-by: Jussi Kukkonen 
---
 meta/recipes-graphics/mesa/{mesa-gl_17.0.0.bb => mesa-gl_17.0.1.bb} | 0
 meta/recipes-graphics/mesa/{mesa_17.0.0.bb => mesa_17.0.1.bb}   | 4 ++--
 2 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/mesa/{mesa-gl_17.0.0.bb => mesa-gl_17.0.1.bb} 
(100%)
 rename meta/recipes-graphics/mesa/{mesa_17.0.0.bb => mesa_17.0.1.bb} (83%)

diff --git a/meta/recipes-graphics/mesa/mesa-gl_17.0.0.bb 
b/meta/recipes-graphics/mesa/mesa-gl_17.0.1.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_17.0.0.bb
rename to meta/recipes-graphics/mesa/mesa-gl_17.0.1.bb
diff --git a/meta/recipes-graphics/mesa/mesa_17.0.0.bb 
b/meta/recipes-graphics/mesa/mesa_17.0.1.bb
similarity index 83%
rename from meta/recipes-graphics/mesa/mesa_17.0.0.bb
rename to meta/recipes-graphics/mesa/mesa_17.0.1.bb
index 6576e3c..9e491c2 100644
--- a/meta/recipes-graphics/mesa/mesa_17.0.0.bb
+++ b/meta/recipes-graphics/mesa/mesa_17.0.1.bb
@@ -5,8 +5,8 @@ SRC_URI = "ftp://ftp.freedesktop.org/pub/mesa/mesa-${PV}.tar.xz 
\
file://disable-asm-on-non-gcc.patch \
file://0001-Use-wayland-scanner-in-the-path.patch \
 "
-SRC_URI[md5sum] = "932e4171a86b14940c06812356486155"
-SRC_URI[sha256sum] = 
"39db3d59700159add7f977307d12a7dfe016363e760ad82280ac4168ea668481"
+SRC_URI[md5sum] = "6a7e768241846c8c69bbadbf904dcc58"
+SRC_URI[sha256sum] = 
"96fd70ef5f31d276a17e424e7e1bb79447ccbbe822b56844213ef932e7ad1b0c"
 
 #because we cannot rely on the fact that all apps will use pkgconfig,
 #make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
-- 
2.1.4

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


Re: [OE-core] [meta-networking][PATCH] wireshark: update to 2.2.5

2017-03-06 Thread Oleksandr Kravchuk
Please ignore. Mistakenly sent to wrong mailing list.

On 6 March 2017 at 10:22, Oleksandr Kravchuk <
oleksandr.kravc...@pelagicore.com> wrote:

> Signed-off-by: Oleksandr Kravchuk 
> ---
>  .../wireshark/{wireshark_2.2.4.bb => wireshark_2.2.5.bb}  |
> 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>  rename meta-networking/recipes-support/wireshark/{wireshark_2.2.4.bb =>
> wireshark_2.2.5.bb} (95%)
>
> diff --git a/meta-networking/recipes-support/wireshark/wireshark_2.2.4.bb
> b/meta-networking/recipes-support/wireshark/wireshark_2.2.5.bb
> similarity index 95%
> rename from meta-networking/recipes-support/wireshark/wireshark_2.2.4.bb
> rename to meta-networking/recipes-support/wireshark/wireshark_2.2.5.bb
> index 29dfbfe..03ae3b9 100644
> --- a/meta-networking/recipes-support/wireshark/wireshark_2.2.4.bb
> +++ b/meta-networking/recipes-support/wireshark/wireshark_2.2.5.bb
> @@ -10,8 +10,8 @@ SRC_URI = "https://2.na.dl.wireshark.
> org/src/all-versions/${BP}.tar.bz2"
>
>  PE = "1"
>
> -SRC_URI[md5sum] = "6d0878ba931ea379f6e675d4cba6536b"
> -SRC_URI[sha256sum] = "42a7fb35eed5a32478153e24601a28
> 4bb50148b7ba919c3e8452652f4c2a3911"
> +SRC_URI[md5sum] = "749e7ca7606ae7df5c1ca8c62f93ff31"
> +SRC_URI[sha256sum] = "75dd88d3d6336559e5b0b72077d8a7
> 72a988197d571f00029986225fef609ac8"
>
>  inherit autotools pkgconfig perlnative
>
> --
> 2.7.4
>
>


-- 
Yes, this is my signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [meta-networking][PATCH] wireshark: update to 2.2.5

2017-03-06 Thread Oleksandr Kravchuk
Signed-off-by: Oleksandr Kravchuk 
---
 .../wireshark/{wireshark_2.2.4.bb => wireshark_2.2.5.bb}  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-networking/recipes-support/wireshark/{wireshark_2.2.4.bb => 
wireshark_2.2.5.bb} (95%)

diff --git a/meta-networking/recipes-support/wireshark/wireshark_2.2.4.bb 
b/meta-networking/recipes-support/wireshark/wireshark_2.2.5.bb
similarity index 95%
rename from meta-networking/recipes-support/wireshark/wireshark_2.2.4.bb
rename to meta-networking/recipes-support/wireshark/wireshark_2.2.5.bb
index 29dfbfe..03ae3b9 100644
--- a/meta-networking/recipes-support/wireshark/wireshark_2.2.4.bb
+++ b/meta-networking/recipes-support/wireshark/wireshark_2.2.5.bb
@@ -10,8 +10,8 @@ SRC_URI = 
"https://2.na.dl.wireshark.org/src/all-versions/${BP}.tar.bz2;
 
 PE = "1"
 
-SRC_URI[md5sum] = "6d0878ba931ea379f6e675d4cba6536b"
-SRC_URI[sha256sum] = 
"42a7fb35eed5a32478153e24601a284bb50148b7ba919c3e8452652f4c2a3911"
+SRC_URI[md5sum] = "749e7ca7606ae7df5c1ca8c62f93ff31"
+SRC_URI[sha256sum] = 
"75dd88d3d6336559e5b0b72077d8a772a988197d571f00029986225fef609ac8"
 
 inherit autotools pkgconfig perlnative
 
-- 
2.7.4

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


[OE-core] Fwd: [PATCH] initscripts: Populate volatile from existing file

2017-03-06 Thread David Vincent
Ping

--  Forwarded Message  --

Subject: [PATCH] initscripts: Populate volatile from existing file
Date: mercredi 25 janvier 2017, 12:35:52 CET
From: David Vincent 
To: openembedded-core@lists.openembedded.org
CC: David Vincent 

In some cases, it may be useful to populate a volatile file from an
existing one, e.g. a file in a read-only rootfs that may be edited in a
read-write destination.

To provide this behavior, creation of volatile files has been updated to
copy a file which has been given in the  field. If set to
none, the current behavior is preserved.

Signed-off-by: David Vincent 
---
 .../initscripts/initscripts-1.0/populate-volatile.sh | 16 +
+--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/initscripts/initscripts-1.0/populate-
volatile.sh b/meta/recipes-core/initscripts/initscripts-1.0/populate-
volatile.sh
index 22a71ecaae..35316ec2ba 100755
--- a/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
+++ b/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
@@ -25,8 +25,18 @@ COREDEF="00_core"
 [ "${VERBOSE}" != "no" ] && echo "Populating volatile Filesystems."
 
 create_file() {
+   EXEC=""
+   [ -z "$2" ] && {
+   EXEC="
+   touch \"$1\";
+   "
+   } || {
+   EXEC="
+   cp \"$2\" \"$1\";
+   "
+   }
EXEC="
-   touch \"$1\";
+   ${EXEC}
chown ${TUSER}.${TGROUP} $1 || echo \"Failed to set owner -${TUSER}- 
for -
$1-.\" >/dev/tty0 2>&1;
chmod ${TMODE} $1 || echo \"Failed to set mode -${TMODE}- for -$1-.\" >/
dev/tty0 2>&1 "
 
@@ -187,7 +197,9 @@ apply_cfgfile() {
 
case "${TTYPE}" in
"f")  [ "${VERBOSE}" != "no" ] && echo "Creating file 
-${TNAME}-."
-   create_file "${TNAME}"
+   TSOURCE="$TLTARGET"
+   [ "${TSOURCE}" = "none" ] && TSOURCE=""
+   create_file "${TNAME}" "${TSOURCE}" &
;;
"d")  [ "${VERBOSE}" != "no" ] && echo "Creating 
directory -$
{TNAME}-."
mk_dir "${TNAME}"
-- 
2.11.0


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


[OE-core] Fwd: [PATCH] openssl: Fix symlink creation

2017-03-06 Thread David Vincent
Ping

--  Forwarded Message  --

Subject: [PATCH] openssl: Fix symlink creation
Date: lundi 23 janvier 2017, 14:59:16 CET
From: David Vincent 
To: openembedded-core@lists.openembedded.org
CC: David Vincent 

Symlinking the openssl configuration file at install time results in
errors when overriding it using an external package which also provides
openssl-conf. This should be done as a postinstall task for such
packages.

Signed-off-by: David Vincent 
---
 meta/recipes-connectivity/openssl/openssl.inc | 13 -
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssl/openssl.inc b/meta/recipes-
connectivity/openssl/openssl.inc
index 5cca019e1d..696b564cdd 100644
--- a/meta/recipes-connectivity/openssl/openssl.inc
+++ b/meta/recipes-connectivity/openssl/openssl.inc
@@ -201,7 +201,6 @@ do_install () {
   ${D}${sysconfdir}/ssl/
ln -sf ${sysconfdir}/ssl/certs ${D}${libdir}/ssl/certs
ln -sf ${sysconfdir}/ssl/private ${D}${libdir}/ssl/private
-   ln -sf ${sysconfdir}/ssl/openssl.cnf ${D}${libdir}/ssl/openssl.cnf
 }
 
 do_install_ptest () {
@@ -245,4 +244,16 @@ do_install_append_class-native() {
OPENSSL_ENGINES=${libdir}/ssl/engines
 }
 
+pkg_postinst_openssl-conf () {
+#!/bin/sh
+if [ -e $D${libdir}/ssl/openssl.cnf ]; then
+   rm -f $D${libdir}/ssl/openssl.cnf
+fi
+
+# If openssl-conf is installed before openssl, we must ensure that the 
symlink
+# destination exists
+mkdir -p $D${libdir}/ssl/
+ln -s ${sysconfdir}/ssl/openssl.cnf $D${libdir}/ssl/openssl.cnf
+}
+
 BBCLASSEXTEND = "native nativesdk"
-- 
2.11.0


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


[OE-core] [PATCH v4 2/3] core-image: Set default sshd configuration

2017-03-06 Thread David Vincent
When selecting OpenSSH as ssh server provider instead of dropbear, also
install the correct configuration depending on whether the final rootfs
is read-only or not.

Signed-off-by: David Vincent 
---
 meta/classes/core-image.bbclass | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/core-image.bbclass b/meta/classes/core-image.bbclass
index 8431440db4..d1f643d920 100644
--- a/meta/classes/core-image.bbclass
+++ b/meta/classes/core-image.bbclass
@@ -41,7 +41,7 @@ FEATURE_PACKAGES_tools-sdk = "packagegroup-core-sdk 
packagegroup-core-standalone
 FEATURE_PACKAGES_nfs-server = "packagegroup-core-nfs-server"
 FEATURE_PACKAGES_nfs-client = "packagegroup-core-nfs-client"
 FEATURE_PACKAGES_ssh-server-dropbear = "packagegroup-core-ssh-dropbear"
-FEATURE_PACKAGES_ssh-server-openssh = "packagegroup-core-ssh-openssh"
+FEATURE_PACKAGES_ssh-server-openssh = "packagegroup-core-ssh-openssh 
${SSHD_CONFIG}"
 FEATURE_PACKAGES_hwcodecs = "${MACHINE_HWCODECS}"
 
 
@@ -52,6 +52,7 @@ IMAGE_FEATURES_REPLACES_ssh-server-openssh = 
"ssh-server-dropbear"
 # IMAGE_FEATURES_CONFLICTS_foo = 'bar1 bar2'
 # An error exception would be raised if both image features foo and bar1(or 
bar2) are included
 
+SSHD_CONFIG ??= 
"${@bb.utils.contains('IMAGE_FEATURES','read-only-rootfs','openssh-sshd-config-readonly','openssh-sshd-config',d)}"
 MACHINE_HWCODECS ??= ""
 
 CORE_IMAGE_BASE_INSTALL = '\
-- 
2.12.0

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


[OE-core] [PATCH v4 1/3] openssh: Package server configuration

2017-03-06 Thread David Vincent
Split sshd configuration for read-write/read-only rootfs in two distinct
packages. Also, add a package dependency between openssh-sshd package
and a provider of sshd-config.

Signed-off-by: David Vincent 
---
 meta/recipes-connectivity/openssh/openssh_7.4p1.bb | 51 ++
 1 file changed, 42 insertions(+), 9 deletions(-)

diff --git a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb 
b/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
index c8093d4e2b..0afc4bd948 100644
--- a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
@@ -91,13 +91,17 @@ do_compile_ptest() {
 }
 
 do_install_append () {
-   if [ "${@bb.utils.filter('DISTRO_FEATURES', 'pam', d)}" ]; then
+   # Create default config files
+   install -m 0644 ${D}${sysconfdir}/ssh/sshd_config 
${D}${sysconfdir}/ssh/sshd_config_default
+   rm -f ${D}${sysconfdir}/ssh/sshd_config
+
+   if [ "${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam', '', d)}" = 
"pam" ]; then
install -D -m 0644 ${WORKDIR}/sshd ${D}${sysconfdir}/pam.d/sshd
-   sed -i -e 's:#UsePAM no:UsePAM yes:' 
${D}${sysconfdir}/ssh/sshd_config
+   sed -i -e 's:#UsePAM no:UsePAM yes:' 
${D}${sysconfdir}/ssh/sshd_config_default
fi
 
-   if [ "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}" ]; then
-   sed -i -e 's:#X11Forwarding no:X11Forwarding yes:' 
${D}${sysconfdir}/ssh/sshd_config
+   if [ "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11', '', d)}" = 
"x11" ]; then
+   sed -i -e 's:#X11Forwarding no:X11Forwarding yes:' 
${D}${sysconfdir}/ssh/sshd_config_default
fi
 
install -d ${D}${sysconfdir}/init.d
@@ -110,7 +114,7 @@ do_install_append () {
 
# Create config files for read-only rootfs
install -d ${D}${sysconfdir}/ssh
-   install -m 644 ${D}${sysconfdir}/ssh/sshd_config 
${D}${sysconfdir}/ssh/sshd_config_readonly
+   install -m 644 ${D}${sysconfdir}/ssh/sshd_config_default 
${D}${sysconfdir}/ssh/sshd_config_readonly
sed -i '/HostKey/d' ${D}${sysconfdir}/ssh/sshd_config_readonly
echo "HostKey /var/run/ssh/ssh_host_rsa_key" >> 
${D}${sysconfdir}/ssh/sshd_config_readonly
echo "HostKey /var/run/ssh/ssh_host_dsa_key" >> 
${D}${sysconfdir}/ssh/sshd_config_readonly
@@ -134,30 +138,59 @@ do_install_ptest () {
 
 ALLOW_EMPTY_${PN} = "1"
 
-PACKAGES =+ "${PN}-keygen ${PN}-scp ${PN}-ssh ${PN}-sshd ${PN}-sftp ${PN}-misc 
${PN}-sftp-server"
+PACKAGES =+ "${PN}-keygen ${PN}-scp ${PN}-ssh ${PN}-sshd-config 
${PN}-sshd-config-readonly ${PN}-sshd ${PN}-sftp ${PN}-misc ${PN}-sftp-server"
 FILES_${PN}-scp = "${bindir}/scp.${BPN}"
 FILES_${PN}-ssh = "${bindir}/ssh.${BPN} ${sysconfdir}/ssh/ssh_config"
+FILES_${PN}-sshd-config = "${sysconfdir}/ssh/sshd_config_default"
+FILES_${PN}-sshd-config-readonly = "${sysconfdir}/ssh/sshd_config_readonly"
 FILES_${PN}-sshd = "${sbindir}/sshd ${sysconfdir}/init.d/sshd 
${systemd_unitdir}/system"
-FILES_${PN}-sshd += "${sysconfdir}/ssh/moduli ${sysconfdir}/ssh/sshd_config 
${sysconfdir}/ssh/sshd_config_readonly ${sysconfdir}/default/volatiles/99_sshd 
${sysconfdir}/pam.d/sshd"
+FILES_${PN}-sshd += "${sysconfdir}/ssh/moduli 
${sysconfdir}/default/volatiles/99_sshd ${sysconfdir}/pam.d/sshd"
 FILES_${PN}-sftp = "${bindir}/sftp"
 FILES_${PN}-sftp-server = "${libexecdir}/sftp-server"
 FILES_${PN}-misc = "${bindir}/ssh* ${libexecdir}/ssh*"
 FILES_${PN}-keygen = "${bindir}/ssh-keygen"
 
 RDEPENDS_${PN} += "${PN}-scp ${PN}-ssh ${PN}-sshd ${PN}-keygen"
-RDEPENDS_${PN}-sshd += "${PN}-keygen ${@bb.utils.contains('DISTRO_FEATURES', 
'pam', 'pam-plugin-keyinit pam-plugin-loginuid', '', d)}"
+RDEPENDS_${PN}-sshd += "${PN}-keygen sshd-config 
${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'pam-plugin-keyinit 
pam-plugin-loginuid', '', d)}"
 RDEPENDS_${PN}-ptest += "${PN}-sftp ${PN}-misc ${PN}-sftp-server make"
 
 RPROVIDES_${PN}-ssh = "ssh"
+RPROVIDES_${PN}-sshd-config = "sshd-config"
+RPROVIDES_${PN}-sshd-config-readonly = "sshd-config"
 RPROVIDES_${PN}-sshd = "sshd"
 
 RCONFLICTS_${PN} = "dropbear"
+RCONFLICTS_${PN}-sshd-config = "${PN}-sshd-config-readonly"
+RCONFLICTS_${PN}-sshd-config-readonly = "${PN}-sshd-config"
 RCONFLICTS_${PN}-sshd = "dropbear"
 RCONFLICTS_${PN}-keygen = "ssh-keygen"
 
-CONFFILES_${PN}-sshd = "${sysconfdir}/ssh/sshd_config"
+CONFFILES_${PN}-sshd-config = "${sysconfdir}/ssh/sshd_config_default"
+CONFFILES_${PN}-sshd-config-readonly = "${sysconfdir}/ssh/sshd_config_readonly"
 CONFFILES_${PN}-ssh = "${sysconfdir}/ssh/ssh_config"
 
+pkg_postinst_${PN}-sshd-config () {
+#!/bin/sh
+if [ -e $D${sysconfdir}/ssh/sshd_config ]; then
+rm $D${sysconfdir}/ssh/sshd_config
+fi
+
+# Make sure destination directory exists, before creating the symlink
+mkdir -p $D${sysconfdir}/ssh
+ln -s sshd_config_default $D${sysconfdir}/ssh/sshd_config
+}
+
+pkg_postinst_${PN}-sshd-config-readonly () {
+#!/bin/sh
+if [ 

[OE-core] [PATCH v4 0/3] openssh: Package server configuration

2017-03-06 Thread David Vincent
This serie of patches provides a way to package OpenSSH sshd
configuration. This way, it should be easier to change the configuration
either in distro and/or BSP layers.

It also simplifies management of configuration for r/o rootfs.

David Vincent (3):
  openssh: Package server configuration
  core-image: Set default sshd configuration
  rootfs-postcommands: Modify ssh-related commands

 meta/classes/core-image.bbclass|  3 +-
 meta/classes/rootfs-postcommands.bbclass   | 17 +++-
 meta/recipes-connectivity/openssh/openssh_7.4p1.bb | 51 ++
 3 files changed, 50 insertions(+), 21 deletions(-)

-- 
2.12.0

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


[OE-core] Fwd: [PATCH] busybox: conditional inclusion of login utilities

2017-03-06 Thread David Vincent
Ping

--  Forwarded Message  --

Subject: [PATCH] busybox: conditional inclusion of login utilities
Date: jeudi 26 janvier 2017, 17:45:18 CET
From: David Vincent 
To: openembedded-core@lists.openembedded.org
CC: David Vincent 

If busybox is not selected as login manager, do not include the fragment
containing the corresponding utilities.

Signed-off-by: David Vincent 
---
 meta/recipes-core/busybox/busybox_1.24.1.bb | 2 +-
 meta/recipes-core/busybox/busybox_git.bb| 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/busybox/busybox_1.24.1.bb b/meta/recipes-core/
busybox/busybox_1.24.1.bb
index afb69d13e6..7d994dc10d 100644
--- a/meta/recipes-core/busybox/busybox_1.24.1.bb
+++ b/meta/recipes-core/busybox/busybox_1.24.1.bb
@@ -25,7 +25,7 @@ SRC_URI = "http://www.busybox.net/downloads/busybox-$
{PV}.tar.bz2;name=tarball \
file://run-ptest \
file://inetd.conf \
file://inetd \
-   file://login-utilities.cfg \
+   ${@["", "file://login-utilities.cfg"][(d.getVar('VIRTUAL-
RUNTIME_login_manager') == 'busybox')]} \
file://recognize_connmand.patch \
file://busybox-cross-menuconfig.patch \
file://0001-Use-CC-when-linking-instead-of-LD-and-use-CFLAGS-
and.patch \
diff --git a/meta/recipes-core/busybox/busybox_git.bb b/meta/recipes-core/
busybox/busybox_git.bb
index c2ee3e6c4b..4213ef4b1e 100644
--- a/meta/recipes-core/busybox/busybox_git.bb
+++ b/meta/recipes-core/busybox/busybox_git.bb
@@ -31,7 +31,7 @@ SRC_URI = "git://busybox.net/busybox.git \
file://run-ptest \
file://inetd.conf \
file://inetd \
-   file://login-utilities.cfg \
+   ${@["", "file://login-utilities.cfg"][(d.getVar('VIRTUAL-
RUNTIME_login_manager') == 'busybox')]} \
file://recognize_connmand.patch \
file://busybox-cross-menuconfig.patch \
file://0001-Use-CC-when-linking-instead-of-LD-and-use-CFLAGS-
and.patch \
-- 
2.11.0


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


[OE-core] [PATCH v2] ghostscript: build and install libgs

2017-03-06 Thread Andrew Shadura
From: Joshua Lock 

Build and install libgs library, which is a build dependency
of a few other libraries, such as libspectre.

We don't want to ship the executable binaries, only the library and its
headers, hence oe_runmake install-so + rm -rf, not e.g. oe_libinstall.

Signed-off-by: Joshua Lock 
Signed-off-by: Andrew Shadura 
---
 meta/recipes-extended/ghostscript/ghostscript_9.20.bb | 17 -
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/ghostscript/ghostscript_9.20.bb 
b/meta/recipes-extended/ghostscript/ghostscript_9.20.bb
index 210e9a7..3c95ed9 100644
--- a/meta/recipes-extended/ghostscript/ghostscript_9.20.bb
+++ b/meta/recipes-extended/ghostscript/ghostscript_9.20.bb
@@ -70,15 +70,17 @@ do_configure_prepend () {
mkdir -p soobj
if [ -e ${WORKDIR}/objarch.h ]; then
cp ${WORKDIR}/objarch.h obj/arch.h
+   cp ${WORKDIR}/objarch.h soobj/arch.h
fi
 }
 
 do_configure_append () {
# copy tools from the native ghostscript build
if [ "${PN}" != "ghostscript-native" ]; then
-   mkdir -p obj/aux soobj
+   mkdir -p obj/aux soobj/aux
for i in genarch genconf mkromfs echogs gendev genht; do
cp ${STAGING_BINDIR_NATIVE}/ghostscript-${PV}/$i 
obj/aux/$i
+   cp ${STAGING_BINDIR_NATIVE}/ghostscript-${PV}/$i 
soobj/aux/$i
done
fi
 }
@@ -96,6 +98,10 @@ do_compile_class-native () {
 done
 }
 
+do_compile_class-target_append () {
+oe_runmake so
+}
+
 do_install_class-native () {
 install -d ${D}${bindir}/ghostscript-${PV}
 for i in genarch genconf mkromfs echogs gendev genht; do
@@ -103,4 +109,13 @@ do_install_class-native () {
 done
 }
 
+do_install_class-target_append () {
+oe_runmake install-so DESTDIR=${D}
+rm -rf ${D}${bindir}
+}
+
+PACKAGES =+ "${PN}-lib"
+
+FILES_${PN}-lib = "${libdir}/lib*.so.*"
+
 BBCLASSEXTEND = "native"
-- 
1.8.3.1

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