from:"nick83ola"

[OE-core] Update layer compatibility to Dunfell

2020-01-08 Thread nick83ola

Hi,
is it time to update the layer compatibility for meta* to dunfell?

Especially because after change

commit 9702544b3e75d761d86cae7e8b36f3f2625b68ce
Author: Denys Dmytriyenko 
Date:   Thu Nov 14 19:40:07 2019 -0500

distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES,
rename

a lot of recipes start throwing warnings.

The change

commit 98e34b71ef54fdada2fdc199905f8f2dfae7e933
Author: Scott Rifenbark 
Date:   Wed Dec 11 13:02:24 2019 -0800
poky.ent: Updated variables for YP 3.1

already changed the release name

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

Re: [OE-core] Oe-core: python and BBCLASSEXTEND = "native nativesdk"

2019-11-19 Thread nick83ola

Something on the line of:

diff --git a/meta/classes/python3native.bbclass
b/meta/classes/python3native.bbclass
index d98fb4c758..e5bde4a0f1 100644
--- a/meta/classes/python3native.bbclass
+++ b/meta/classes/python3native.bbclass
@@ -24,3 +24,5 @@ export PYTHONNOUSERSITE = "1"

 # autoconf macros will use their internal default preference otherwise
 export PYTHON
+
+BBCLASSEXTEND = "native nativesdk"
\ No newline at end of file
diff --git a/meta/classes/pythonnative.bbclass
b/meta/classes/pythonnative.bbclass
index 0e9019d1e2..1fe8d29a14 100644
--- a/meta/classes/pythonnative.bbclass
+++ b/meta/classes/pythonnative.bbclass
@@ -25,3 +25,5 @@ export PYTHONNOUSERSITE = "1"

 # autoconf macros will use their internal default preference otherwise
 export PYTHON
+
+BBCLASSEXTEND = "native nativesdk"
\ No newline at end of file
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Oe-core: python and BBCLASSEXTEND = "native nativesdk"

2019-11-19 Thread nick83ola

Dear Openembedded developer,

a lot of python recipes need to add the

BBCLASSEXTEND = "native nativesdk"

To the recipe to build the native version of the package.
Wouldn't be better to add it to the pythonnative.bbclass by default?

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

[OE-core] Fwd: [meta][PATCH] ofono: run oe-stylize over recipe

2019-10-10 Thread nick83ola

Hi Ross,
yes I was thinking the same thing.
Also the init file has some issue.

Last thing: there's any particular reason why is better to use a tar.gz
instead of git?
Because git makes creating patches a lot easier.

Thanks
Nick

On Fri, 4 Oct 2019 at 16:46, Ross Burton  wrote:

> On 03/10/2019 17:40, Nicola Lunghi wrote:
> > From: Nicola Lunghi 
> >
> > Variable ordering changed slightly and add the SRC_URI to the inc file
>
> If you're tidying up the recipe we might as well merge the bb and inc
> file, as the inc is pointless.
>
> 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] [oe-core] [BUG] patch linux-firmware: bump to 20190618 breaks package index

2019-08-12 Thread nick83ola

Hi all
after this patch I got a ton of errors regarding Package version went backwards

Cheers
Nicola Lunghi

ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-src went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-dbg went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-ralink-license went backwards which
would break package feeds from (1:0.0+git0+711d3297ba-r0 to
0:20190618-r0) [version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-ralink went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-mt7601u-license went backwards
which would break package feeds from (1:0.0+git0+711d3297ba-r0 to
0:20190618-r0) [version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-mt7601u went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-radeon-license went backwards which
would break package feeds from (1:0.0+git0+711d3297ba-r0 to
0:20190618-r0) [version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-radeon went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-marvell-license went backwards
which would break package feeds from (1:0.0+git0+711d3297ba-r0 to
0:20190618-r0) [version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-pcie8897 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-pcie8997 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8686 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8688 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8787 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8797 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8801 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8887 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-sd8897 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-usb8997 went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to 0:20190618-r0)
[version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-ti-connectivity-license went
backwards which would break package feeds from
(1:0.0+git0+711d3297ba-r0 to 0:20190618-r0) [version-going-backwards]
ERROR: linux-firmware-20190618-r0 do_packagedata: QA Issue: Package
version for package linux-firmware-wlcommon went backwards which would
break package feeds from (1:0.0+git0+711d3297ba-r0 to

Re: [OE-core] [PATCH v2 2/3] rng-tools: 6.6->6.7

2019-06-12 Thread nick83ola

Hi,
Ok I will clean it up and re-submit it (also because it will need
another patch that I'm testing now)

Thanks
Nicola Lunghi

On Thu, 6 Jun 2019 at 17:20, Burton, Ross  wrote:
>
> The patches you're adding all need your Signed-off-by alongside the
> Upstream-Status, specifically
> 0008-configure-If-the-libc-is-lacking-argp-use-libargp.patch doesn't
> have a Sob or U-S.
>
> For the patches that are submitted, please add the pull request:
>
> Upstream-Status: Submitted [https://github.com/nhorman/rng-tools/pull/66]
>
> This lets us find the patches in the future.
>
> Ross
>
> On Thu, 6 Jun 2019 at 16:18, Nicola Lunghi  wrote:
> >
> > update rng-tools to release 6.7
> >
> > - add new option to compile with pkcs11/libp11 (added in 6.7)
> >
> > - submitted the following yocto patches upstream (and added as backports):
> > 0001-If-the-libc-is-lacking-argp-use-libargp.patch \
> > 0002-Add-argument-to-control-the-libargp-dependency.patch \
> > -> squashed in 
> > 0008-configure-If-the-libc-is-lacking-argp-use-libargp.patch
> > underquote.patch
> > -> 0010-Fix-underquoted-m4-entry.-This-causes-a-failure-if-g.patch
> > rng-tools-5-fix-textrels-on-PIC-x86.patch
> > -> 0009-Fix-assemby-textrels-on-rdrand_asm.S-on-PIC-x86.patch
> >
> > - the following patch has been merged upstream: remove
> > 0001-configure.ac-fix-typo.patch
> >
> > - backport the following patches from master
> > 0001-Remove-superfluous-variables.patch
> > 0002-Fix-a-few-typos-in-log-messages.patch
> > 0003-Fix-up-some-compile-warnings.patch
> > 0004-Fix-a-race-condition-on-shutdown.patch
> > 0005-rngd-prioritize-faster-sources-of-entropy.patch
> > 0006-rngd_jitter-replace-non-standard-pthread_yield-with-.patch
> > 0007-Make-rngd_pkcs11.c-explicitly-link-against-libcrypto.patch
> >
> > Signed-off-by: Nicola Lunghi 
> > ---
> >  ...the-libc-is-lacking-argp-use-libargp.patch |  60 --
> >  .../0001-Remove-superfluous-variables.patch   |  28 +++
> >  .../0001-configure.ac-fix-typo.patch  |  27 ---
> >  ...nt-to-control-the-libargp-dependency.patch |  95 --
> >  ...0002-Fix-a-few-typos-in-log-messages.patch |  48 +
> >  .../0003-Fix-up-some-compile-warnings.patch   | 172 ++
> >  ...004-Fix-a-race-condition-on-shutdown.patch |  55 ++
> >  ...prioritize-faster-sources-of-entropy.patch |  72 
> >  ...ace-non-standard-pthread_yield-with-.patch |  27 +++
> >  c-explicitly-link-against-libcrypto.patch |  73 
> >  ...the-libc-is-lacking-argp-use-libargp.patch | 103 +++
> >  ...textrels-on-rdrand_asm.S-on-PIC-x86.patch} |   8 +-
> >  ...4-entry.-This-causes-a-failure-if-g.patch} |  16 +-
> >  .../{rng-tools_6.6.bb => rng-tools_6.7.bb}|  18 +-
> >  14 files changed, 602 insertions(+), 200 deletions(-)
> >  delete mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0001-Remove-superfluous-variables.patch
> >  delete mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0001-configure.ac-fix-typo.patch
> >  delete mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0002-Add-argument-to-control-the-libargp-dependency.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0002-Fix-a-few-typos-in-log-messages.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0003-Fix-up-some-compile-warnings.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0004-Fix-a-race-condition-on-shutdown.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0005-rngd-prioritize-faster-sources-of-entropy.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0006-rngd_jitter-replace-non-standard-pthread_yield-with-.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0007-Make-rngd_pkcs11.c-explicitly-link-against-libcrypto.patch
> >  create mode 100644 
> > meta/recipes-support/rng-tools/rng-tools/0008-configure-If-the-libc-is-lacking-argp-use-libargp.patch
> >  rename 
> > meta/recipes-support/rng-tools/rng-tools/{rng-tools-5-fix-textrels-on-PIC-x86.patch
> >  => 0009-Fix-assemby-textrels-on-rdrand_asm.S-on-PIC-x86.patch} (94%)
> >  rename meta/recipes-support/rng-tools/rng-tools/{underquote.patch => 
> > 0010-Fix-underquoted-m4-entry.-This-causes-a-failure-if-g.patch} (77%)
> >  rename meta/recipes-support/rng-tools/{rng-tools_6.6.bb => 
> > rng-tools_6.7.bb} (72%)
> >
> > diff --git 
> > a/meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
> >  
> > b/meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
> > deleted file mode 100644
> > index 06d1d94369..00
> > --- 
> > a/meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
> > +++ /dev/null
> > @@ -1,60 +0,0

Re: [OE-core] [PATCH v2 1/3] rng-tools: recipe cleanup

2019-06-06 Thread nick83ola

posted v2 of this with an extra patch please ignore

On Thu, 6 Jun 2019 at 16:18, Nicola Lunghi  wrote:
>
> - add missing DESCRIPTION, AUTHOR, HOMEPAGE
> - cleanup DEPENDS
> - fix variable ordering as per https://www.openembedded.org/wiki/Styleguide
> - remove unneeded checks for systemd, sysvinit in do_install
>
> Signed-off-by: Nicola Lunghi 
> ---
>  .../rng-tools/rng-tools_6.6.bb| 63 ++-
>  1 file changed, 33 insertions(+), 30 deletions(-)
>
> diff --git a/meta/recipes-support/rng-tools/rng-tools_6.6.bb 
> b/meta/recipes-support/rng-tools/rng-tools_6.6.bb
> index 6796c9be9e..41959a2695 100644
> --- a/meta/recipes-support/rng-tools/rng-tools_6.6.bb
> +++ b/meta/recipes-support/rng-tools/rng-tools_6.6.bb
> @@ -1,58 +1,61 @@
>  SUMMARY = "Random number generator daemon"
> +DESCRIPTION = "Check and feed random data from hardware device to kernel"
> +AUTHOR = "Philipp Rumpf, Jeff Garzik , \
> +  Henrique de Moraes Holschuh "
> +HOMEPAGE = "https://github.com/nhorman/rng-tools;
> +BUGTRACKER = "https://github.com/nhorman/rng-tools/issues;
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> -
> -SRC_URI = "git://github.com/nhorman/rng-tools.git \
> -   file://0001-If-the-libc-is-lacking-argp-use-libargp.patch \
> -   file://0002-Add-argument-to-control-the-libargp-dependency.patch \
> -   file://underquote.patch \
> -   file://rng-tools-5-fix-textrels-on-PIC-x86.patch \
> -   file://0001-configure.ac-fix-typo.patch \
> -   file://init \
> -   file://default \
> -   file://rngd.service \
> +DEPENDS = "sysfsutils"
> +
> +SRC_URI = "\
> +git://github.com/nhorman/rng-tools.git \
> +file://0001-If-the-libc-is-lacking-argp-use-libargp.patch \
> +file://0002-Add-argument-to-control-the-libargp-dependency.patch \
> +file://underquote.patch \
> +file://rng-tools-5-fix-textrels-on-PIC-x86.patch \
> +file://0001-configure.ac-fix-typo.patch \
> +file://init \
> +file://default \
> +file://rngd.service \
>  "
>  SRCREV = "4ebc21d6f387bb7b4b3f6badc429e27b21c0a6ee"
> +
>  S = "${WORKDIR}/git"
>
>  inherit autotools update-rc.d systemd pkgconfig
>
> -DEPENDS = " \
> -   sysfsutils \
> -  "
> -
>  PACKAGECONFIG ??= "libgcrypt libjitterentropy"
>  PACKAGECONFIG_libc-musl = "libargp libjitterentropy"
> +
>  PACKAGECONFIG[libargp] = "--with-libargp,--without-libargp,argp-standalone,"
>  PACKAGECONFIG[libgcrypt] = "--with-libgcrypt,--without-libgcrypt,libgcrypt,"
>  PACKAGECONFIG[libjitterentropy] = 
> "--enable-jitterentropy,--disable-jitterentropy,libjitterentropy"
>  PACKAGECONFIG[nistbeacon] = "--with-nistbeacon,--without-nistbeacon,curl 
> libxml2 openssl"
>
> +INITSCRIPT_NAME = "rng-tools"
> +INITSCRIPT_PARAMS = "start 03 2 3 4 5 . stop 30 0 6 1 ."
> +
> +SYSTEMD_SERVICE_${PN} = "rngd.service"
> +
>  # Refer autogen.sh in rng-tools
>  do_configure_prepend() {
>  cp ${S}/README.md ${S}/README
>  }
>
>  do_install_append() {
> -# Only install the init script when 'sysvinit' is in DISTRO_FEATURES.
> -if ${@bb.utils.contains('DISTRO_FEATURES', 'sysvinit', 'true', 'false', 
> d)}; then
> -install -d "${D}${sysconfdir}/init.d"
> -install -m 0755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/rng-tools
> -sed -i -e 's,/etc/,${sysconfdir}/,' -e 's,/usr/sbin/,${sbindir}/,' \
> -${D}${sysconfdir}/init.d/rng-tools
> +install -d "${D}${sysconfdir}/init.d"
> +install -m 0755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/rng-tools
> +sed -i -e 's,/etc/,${sysconfdir}/,' -e 's,/usr/sbin/,${sbindir}/,' \
> +${D}${sysconfdir}/init.d/rng-tools
>
> +# Only install the default script when 'sysvinit' is in DISTRO_FEATURES.
> +if ${@bb.utils.contains('DISTRO_FEATURES', 'sysvinit', 'true', 'false', 
> d)}; then
>  install -d "${D}${sysconfdir}/default"
>  install -m 0644 ${WORKDIR}/default 
> ${D}${sysconfdir}/default/rng-tools
>  fi
>
> -if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', 
> d)}; then
> -install -d ${D}${systemd_unitdir}/system
> -install -m 644 ${WORKDIR}/rngd.service ${D}${systemd_unitdir}/system
> -sed -i -e 's,@SBINDIR@,${sbindir},g' 
> ${D}${systemd_unitdir}/system/rngd.service
> -fi
> +install -d ${D}${systemd_unitdir}/system
> +install -m 644 ${WORKDIR}/rngd.service ${D}${systemd_unitdir}/system
> +sed -i -e 's,@SBINDIR@,${sbindir},g' 
> ${D}${systemd_unitdir}/system/rngd.service
>  }
> -
> -INITSCRIPT_NAME = "rng-tools"
> -INITSCRIPT_PARAMS = "start 03 2 3 4 5 . stop 30 0 6 1 ."
> -
> -SYSTEMD_SERVICE_${PN} = "rngd.service"
> --
> 2.20.1
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/2] rng-tools: 6.6->6.7

2019-06-06 Thread nick83ola

posted v2 of this with an extra patch please ignore

On Thu, 6 Jun 2019 at 11:41, Nicola Lunghi  wrote:
>
> update rng-tools to release 6.7
>
> - add new option to compile with pkcs11/libp11 (added in 6.7)
>
> - submitted the following yocto patches upstream (and added as backports):
> 0001-If-the-libc-is-lacking-argp-use-libargp.patch \
> 0002-Add-argument-to-control-the-libargp-dependency.patch \
> -> squashed in 
> 0008-configure-If-the-libc-is-lacking-argp-use-libargp.patch
> underquote.patch
> -> 0010-Fix-underquoted-m4-entry.-This-causes-a-failure-if-g.patch
> rng-tools-5-fix-textrels-on-PIC-x86.patch
> -> 0009-Fix-assemby-textrels-on-rdrand_asm.S-on-PIC-x86.patch
>
> - the following patch has been merged upstream: remove
> 0001-configure.ac-fix-typo.patch
>
> - backport the following patches from master
> 0001-Remove-superfluous-variables.patch
> 0002-Fix-a-few-typos-in-log-messages.patch
> 0003-Fix-up-some-compile-warnings.patch
> 0004-Fix-a-race-condition-on-shutdown.patch
> 0005-rngd-prioritize-faster-sources-of-entropy.patch
> 0006-rngd_jitter-replace-non-standard-pthread_yield-with-.patch
> 0007-Make-rngd_pkcs11.c-explicitly-link-against-libcrypto.patch
>
> Signed-off-by: Nicola Lunghi 
> ---
>  ...the-libc-is-lacking-argp-use-libargp.patch |  60 --
>  .../0001-Remove-superfluous-variables.patch   |  28 +++
>  .../0001-configure.ac-fix-typo.patch  |  27 ---
>  ...nt-to-control-the-libargp-dependency.patch |  95 --
>  ...0002-Fix-a-few-typos-in-log-messages.patch |  48 +
>  .../0003-Fix-up-some-compile-warnings.patch   | 172 ++
>  ...004-Fix-a-race-condition-on-shutdown.patch |  55 ++
>  ...prioritize-faster-sources-of-entropy.patch |  72 
>  ...ace-non-standard-pthread_yield-with-.patch |  27 +++
>  c-explicitly-link-against-libcrypto.patch |  73 
>  ...the-libc-is-lacking-argp-use-libargp.patch | 103 +++
>  ...textrels-on-rdrand_asm.S-on-PIC-x86.patch} |   8 +-
>  ...4-entry.-This-causes-a-failure-if-g.patch} |  16 +-
>  .../{rng-tools_6.6.bb => rng-tools_6.7.bb}|  18 +-
>  14 files changed, 602 insertions(+), 200 deletions(-)
>  delete mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0001-Remove-superfluous-variables.patch
>  delete mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0001-configure.ac-fix-typo.patch
>  delete mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0002-Add-argument-to-control-the-libargp-dependency.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0002-Fix-a-few-typos-in-log-messages.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0003-Fix-up-some-compile-warnings.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0004-Fix-a-race-condition-on-shutdown.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0005-rngd-prioritize-faster-sources-of-entropy.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0006-rngd_jitter-replace-non-standard-pthread_yield-with-.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0007-Make-rngd_pkcs11.c-explicitly-link-against-libcrypto.patch
>  create mode 100644 
> meta/recipes-support/rng-tools/rng-tools/0008-configure-If-the-libc-is-lacking-argp-use-libargp.patch
>  rename 
> meta/recipes-support/rng-tools/rng-tools/{rng-tools-5-fix-textrels-on-PIC-x86.patch
>  => 0009-Fix-assemby-textrels-on-rdrand_asm.S-on-PIC-x86.patch} (94%)
>  rename meta/recipes-support/rng-tools/rng-tools/{underquote.patch => 
> 0010-Fix-underquoted-m4-entry.-This-causes-a-failure-if-g.patch} (77%)
>  rename meta/recipes-support/rng-tools/{rng-tools_6.6.bb => rng-tools_6.7.bb} 
> (72%)
>
> diff --git 
> a/meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
>  
> b/meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
> deleted file mode 100644
> index 06d1d94369..00
> --- 
> a/meta/recipes-support/rng-tools/rng-tools/0001-If-the-libc-is-lacking-argp-use-libargp.patch
> +++ /dev/null
> @@ -1,60 +0,0 @@
> -From 06ba71887f667d45dd231a782a2751f36e8fe025 Mon Sep 17 00:00:00 2001
> -From: Christopher Larson 
> -Date: Mon, 15 Feb 2016 15:59:58 -0700
> -Subject: [PATCH 1/4] If the libc is lacking argp, use libargp
> -
> -Patch pulled from Gentoo:
> -
> -On glibc systems, argp is provided by libc.  However, on
> -uclibc and other systems which lack argp in their C library,
> -argp might be provided by a stand alone library, libargp.
> -This patch adds tests to the build system to find who provides
> -argp.
> -
> -X-Gentoo-Bug: 292191
> -X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=292191
> -Reported-by: Ed Wildgoose 
> -Signed-off-by: Anthony G.

Re: [OE-core] OE-Core status with gcc9

2019-06-06 Thread nick83ola

Probably is not an issue for ie-core but gcc-9 is also breaking all
the openjdk8 build on meta-java

Can this be postponed a bit?

Thanks
Nicola Lunghi

On Thu, 6 Jun 2019 at 09:11, Yu, Mingli  wrote:
>
>
>
> On 2019年05月27日 15:53, Khem Raj wrote:
> > On Sun, May 26, 2019 at 10:17 AM Khem Raj  wrote:
> >>
> >> On Mon, May 13, 2019 at 8:39 PM Khem Raj  wrote:
> >>>
> >>> On Sun, May 12, 2019 at 1:14 PM Khem Raj  wrote:
> 
>  On Sun, May 12, 2019 at 6:21 AM Richard Purdie
>   wrote:
> >
> > I've run some tests and think we're now down to one remaining issue
> > with gcc 9:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/579
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/55/builds/145
> >
> 
>  Assembler is not liking what gcc9 is generating
> 
>  HOSTCC scripts/kconfig/conf.o
>  /tmp/ccnMW5be.s: Assembler messages:
>  /tmp/ccnMW5be.s: Internal error (Segmentation fault).
> 
>  I wonder if its a common case or specific here?
>  I will try to reproduce it as well
> 
> >>>
> >>> I am able to get a .s file which crashes assembler on
> >>> qemu. Same file assembles ok with mips cross assembler
> >>> so next I want to get hold of a mips hardware and try
> >>> it on the real h/w, meanwhile if someone has easy access
> >>> to mips and can load core-image-sato-sdk on it then I can
> >>> provide the asm file which crashes assembler
> >>>
> >> got some more time to narrow it down.
> >> works with musl+gcc-9
> >> works with glibc+clang-8
> >> works with musl+Clang-8
> >>
> >> so only glibc+gcc-9 combo is one which exhibits the issue
> >>
> >
> > I have sent a workaound for this which we can try out.
> > https://patchwork.openembedded.org/patch/161674/
>
> Failed to build llvm with gcc9 for qemuppc as below:
> | collect2: fatal error: ld terminated with signal 11 [Segmentation
> fault], core dumped
>
> Thanks,
>
> >
> > which is a kernel "make scripts" segfaulting on target on mips and
> > hence failing to build kernel modules. If we can get that one fixed
> > we're good from an OE-Core perspective to move to gcc 9.
> >
> > I have to recognise the work Khem has put in getting us this close!
> >
> > Cheers,
> >
> > Richard
> >
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] nginx: fix kill path in nginx systemd unit file

2019-05-27 Thread nick83ola

Thanks (and sorry again)

On Fri, 24 May 2019 at 17:27, akuster808  wrote:
>
>
>
> On 5/24/19 7:36 AM, Nicola Lunghi wrote:
> > Signed-off-by: Nicola Lunghi 
> > ---
> >  meta-webserver/recipes-httpd/nginx/files/nginx.service | 2 +-
> >  meta-webserver/recipes-httpd/nginx/nginx.inc   | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
>
> Wrong mailing list.
>
> please send to openembedded-de...@lists.openembedded.org
>
> >
> > diff --git a/meta-webserver/recipes-httpd/nginx/files/nginx.service 
> > b/meta-webserver/recipes-httpd/nginx/files/nginx.service
> > index c6fc0495f..9a6ca9651 100644
> > --- a/meta-webserver/recipes-httpd/nginx/files/nginx.service
> > +++ b/meta-webserver/recipes-httpd/nginx/files/nginx.service
> > @@ -8,7 +8,7 @@ PIDFile=/run/nginx/nginx.pid
> >  ExecStartPre=@SBINDIR@/nginx -t
> >  ExecStart=@SBINDIR@/nginx
> >  ExecReload=@SBINDIR@/nginx -s reload
> > -ExecStop=@BINDIR@/kill -s QUIT $MAINPID
> > +ExecStop=@BASE_BINDIR@/kill -s QUIT $MAINPID
> >  PrivateTmp=true
> >
> >  [Install]
> > diff --git a/meta-webserver/recipes-httpd/nginx/nginx.inc 
> > b/meta-webserver/recipes-httpd/nginx/nginx.inc
> > index 29e7efc14..c4c776e37 100644
> > --- a/meta-webserver/recipes-httpd/nginx/nginx.inc
> > +++ b/meta-webserver/recipes-httpd/nginx/nginx.inc
> > @@ -134,7 +134,7 @@ do_install () {
> >  sed -i -e 's,@SYSCONFDIR@,${sysconfdir},g' \
> >  -e 's,@LOCALSTATEDIR@,${localstatedir},g' \
> >  -e 's,@SBINDIR@,${sbindir},g' \
> > --e 's,@BINDIR@,${bindir},g' \
> > +-e 's,@BASE_BINDIR@,${base_bindir},g' \
> >  ${D}${systemd_unitdir}/system/nginx.service
> >  fi
> >  }
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [oe][meta-webserver][PATCH 1/2] nginx: update to version 1.17.0

2019-05-27 Thread nick83ola

Done

Thanks
Nicola Lunghi

On Fri, 24 May 2019 at 17:14, Randy MacLeod  wrote:
>
> Nicola,
>
> Please re-send to:
> openembedded-de...@lists.openembedded.org
> rather than:
> openembedded-core@lists.openembedded.org
>
> Did you read:
>   https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
> If so maybe we need to improve the howto.
>
> Thanks.
> ../Randy
>
> On 5/24/19 10:44 AM, Nicola Lunghi wrote:
> > Signed-off-by: Nicola Lunghi 
> > ---
> >   meta-webserver/recipes-httpd/nginx/nginx_1.15.7.bb | 6 --
> >   meta-webserver/recipes-httpd/nginx/nginx_1.17.0.bb | 6 ++
> >   2 files changed, 6 insertions(+), 6 deletions(-)
> >   delete mode 100644 meta-webserver/recipes-httpd/nginx/nginx_1.15.7.bb
> >   create mode 100644 meta-webserver/recipes-httpd/nginx/nginx_1.17.0.bb
> >
> > diff --git a/meta-webserver/recipes-httpd/nginx/nginx_1.15.7.bb 
> > b/meta-webserver/recipes-httpd/nginx/nginx_1.15.7.bb
> > deleted file mode 100644
> > index 5e6dc33e9..0
> > --- a/meta-webserver/recipes-httpd/nginx/nginx_1.15.7.bb
> > +++ /dev/null
> > @@ -1,6 +0,0 @@
> > -require nginx.inc
> > -
> > -LIC_FILES_CHKSUM = "file://LICENSE;md5=3691402cc54ce09f800ca348634a2dfe"
> > -
> > -SRC_URI[md5sum] = "719b2e3d416f111fecc9db6625553658"
> > -SRC_URI[sha256sum] = 
> > "8f22ea2f6c0e0a221b6ddc02b6428a3ff708e2ad55f9361102b1c9f4142bdf93"
> > diff --git a/meta-webserver/recipes-httpd/nginx/nginx_1.17.0.bb 
> > b/meta-webserver/recipes-httpd/nginx/nginx_1.17.0.bb
> > new file mode 100644
> > index 0..8774a87ff
> > --- /dev/null
> > +++ b/meta-webserver/recipes-httpd/nginx/nginx_1.17.0.bb
> > @@ -0,0 +1,6 @@
> > +require nginx.inc
> > +
> > +LIC_FILES_CHKSUM = "file://LICENSE;md5=52e384aaac868b755b93ad5535e2d075"
> > +
> > +SRC_URI[md5sum] = "56767fd62302508295b31adc48b99a59"
> > +SRC_URI[sha256sum] = 
> > "e21b5d06cd53e86afb94f0b3678e0abb0c0f011433471fa3d895cefa65ae0fab"
> >
>
>
> --
> # Randy MacLeod
> # Wind River Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] connman: fix segfault with musl >2.21

2019-05-23 Thread nick83ola

Hi Andre,

in glibc freeaddrinfo is checking for null

https://github.molgen.mpg.de/git-mirror/glibc/blob/20003c49884422da7ffbc459cdeee768a6fee07b/sysdeps/posix/getaddrinfo.c#L2663-L2674

void
freeaddrinfo (struct addrinfo *ai)
{
struct addrinfo *p;

while (ai != NULL)
{
p = ai;
ai = ai->ai_next;
free (p->ai_canonname);
free (p);
}
}

that is why I put it into the musl specific patches.
But ok I will repost it putting it in the generic SRC_URI.

regarding the 2.21 -> yes is a typo.

Thanks
Nicola Lunghi


On Thu, 23 May 2019 at 10:18, André Draszik  wrote:
>
> On Thu, 2019-05-23 at 08:47 +0100, Nicola Lunghi wrote:
> > musl > 2.21 changed the implementation of the freeaddrinfo() function
> > not allowing anymore to pass null pointers to it.
> > This was causing a segmentation fault in connman.
> > ---
> >  ...-gweb-fix-segfault-with-musl-v1.1.21.patch | 34 +++
> >  .../connman/connman_1.37.bb   |  5 ++-
> >  2 files changed, 38 insertions(+), 1 deletion(-)
> >  create mode 100644 
> > meta/recipes-connectivity/connman/connman/0003-gweb-fix-segfault-with-musl-v1.1.21.patch
> >
> > diff --git 
> > a/meta/recipes-connectivity/connman/connman/0003-gweb-fix-segfault-with-musl-v1.1.21.patch
> >  b/meta/recipes-
> > connectivity/connman/connman/0003-gweb-fix-segfault-with-musl-v1.1.21.patch
> > new file mode 100644
> > index 00..43b43bc9f8
> > --- /dev/null
> > +++ 
> > b/meta/recipes-connectivity/connman/connman/0003-gweb-fix-segfault-with-musl-v1.1.21.patch
> > @@ -0,0 +1,34 @@
> > +From f0a8c69971b30ea7ca255bb885fdd1179fa5d298 Mon Sep 17 00:00:00 2001
> > +From: Nicola Lunghi 
> > +Date: Thu, 23 May 2019 07:55:25 +0100
> > +Subject: [PATCH] gweb: fix segfault with musl v1.1.21
> > +
> > +In musl > 1.1.21 freeaddrinfo() implementation changed and
> > +was causing a segmentation fault on recent Yocto using musl.
> > +
> > +See this commit:
> > +
> > + 
> > https://git.musl-libc.org/cgit/musl/commit/src/network/freeaddrinfo.c?id=d1395c43c019aec6b855cf3c656bf47c8a719e7f
> > +
> > +Upstream-Status: Submitted
> > +---
> > + gweb/gweb.c | 3 ++-
> > + 1 file changed, 2 insertions(+), 1 deletion(-)
> > +
> > +diff --git a/gweb/gweb.c b/gweb/gweb.c
> > +index 393afe0a..12fcb1d8 100644
> > +--- a/gweb/gweb.c
> >  b/gweb/gweb.c
> > +@@ -1274,7 +1274,8 @@ static bool is_ip_address(const char *host)
> > + addr = NULL;
> > +
> > + result = getaddrinfo(host, NULL, , );
> > +-freeaddrinfo(addr);
> > ++if(!result)
> > ++freeaddrinfo(addr);
> > +
> > + return result == 0;
> > + }
> > +--
> > +2.19.1
> > +
> > diff --git a/meta/recipes-connectivity/connman/connman_1.37.bb 
> > b/meta/recipes-connectivity/connman/connman_1.37.bb
> > index 2cf904cd85..f52b21cae3 100644
> > --- a/meta/recipes-connectivity/connman/connman_1.37.bb
> > +++ b/meta/recipes-connectivity/connman/connman_1.37.bb
> > @@ -7,7 +7,10 @@ SRC_URI  = 
> > "${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
> >  file://no-version-scripts.patch \
> >  "
> >
> > -SRC_URI_append_libc-musl = " 
> > file://0002-resolve-musl-does-not-implement-res_ninit.patch"
> > +SRC_URI_append_libc-musl = " \
> > +file://0002-resolve-musl-does-not-implement-res_ninit.patch \
> > +file://0003-gweb-fix-segfault-with-musl-v1.1.21.patch \
> > +"
>
> This fix is not musl specific.
>
> Cheers,
> Andre'
>
> >
> >  SRC_URI[md5sum] = "75012084f14fb63a84b116e66c6e94fb"
> >  SRC_URI[sha256sum] = 
> > "6ce29b3eb0bb16a7387bc609c39455fd13064bdcde5a4d185fab3a0c71946e16"
> > --
> > 2.19.1
> >
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] image-buildinfo: make the build file shell compatible

2019-01-23 Thread nick83ola

sorry here is the correct file



# Build Configuration  #

DISTRO="esw-space-controller"
DISTRO_VERSION="2.6"
TARGET_SYS="arm-poky-linux-musleabi"
MACHINE="bumblebee-cl-imx7"


# Layer Revisions  #

BBLAYERS_meta="HEAD:eddff2b361928e88e3628ebc22a1a0ebb119e01b:modified"
BBLAYERS_meta-poky="HEAD:eddff2b361928e88e3628ebc22a1a0ebb119e01b:modified"
BBLAYERS_meta-freescale="HEAD:15a354ee592866a61a893562760ef84bf8fe5e4d:"
BBLAYERS_meta-ti="master:fb8bfa61d74e49d1a436612b07bdb69c1bdd350f:"
BBLAYERS_meta-jci-bsp-bumblebee="HEAD:1e293e40a21840fb42abb6d188d23867afb5e9b2:"
BBLAYERS_meta-oe="HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-networking="HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-python="HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-webserver="HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-swupd="HEAD:ed8911cc40b5164af0715f471ee204ea9a3d3491:"
BBLAYERS_meta-tpm="HEAD:393db42323515a65e554a6b2ed05f7ffcc958e3f:"
BBLAYERS_meta-security="HEAD:393db42323515a65e554a6b2ed05f7ffcc958e3f:"
BBLAYERS_meta-perl="HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-gplv2="HEAD:aabc30f3bd03f97326fb8596910b94639fea7575:"
BBLAYERS_meta-jci-app-esw="contrib/nlunghi/SPACE-557:5a8aea37191e603b1bba74222ad236f7a3e5cc93:modified"
BBLAYERS_meta-eclipse-smarthome="HEAD:e91f8808ea1a16f5f03359631c58a782067e7884:"
BBLAYERS_meta-java="HEAD:99d16707d03898fe9fd5b4fee32f6417825a9e6a:"
BBLAYERS_meta-jci-app-bumblebee="contrib/nlunghi/proxy-rest:57f09dd7147d1dae5caf681114b5087bf7957bbf:"
BBLAYERS_meta-nick="master:3987b1f760a25941168f6c0277a0c49b46f5c723:modified"
BBLAYERS_workspace="::modified"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] image-buildinfo: make the build file shell compatible

2019-01-23 Thread nick83ola

example of the new format:


# Build Configuration
   #

DISTRO="esw-space-controller"
DISTRO_VERSION="2.6"
TARGET_SYS="arm-poky-linux-musleabi"
MACHINE="bumblebee-cl-imx7"


# Layer Revisions
   #

BBLAYERS_meta:HEAD:eddff2b361928e88e3628ebc22a1a0ebb119e01b:modified"
BBLAYERS_meta-poky:HEAD:eddff2b361928e88e3628ebc22a1a0ebb119e01b:modified"
BBLAYERS_meta-freescale:HEAD:15a354ee592866a61a893562760ef84bf8fe5e4d:"
BBLAYERS_meta-ti:master:fb8bfa61d74e49d1a436612b07bdb69c1bdd350f:"
BBLAYERS_meta-jci-bsp-bumblebee:HEAD:1e293e40a21840fb42abb6d188d23867afb5e9b2:"
BBLAYERS_meta-oe:HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-networking:HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-python:HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-webserver:HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-swupd:HEAD:ed8911cc40b5164af0715f471ee204ea9a3d3491:"
BBLAYERS_meta-tpm:HEAD:393db42323515a65e554a6b2ed05f7ffcc958e3f:"
BBLAYERS_meta-security:HEAD:393db42323515a65e554a6b2ed05f7ffcc958e3f:"
BBLAYERS_meta-perl:HEAD:ff6bead1624a1e261408516b3d064a04aab5f592:"
BBLAYERS_meta-gplv2:HEAD:aabc30f3bd03f97326fb8596910b94639fea7575:"
BBLAYERS_meta-eclipse-smarthome:HEAD:e91f8808ea1a16f5f03359631c58a782067e7884:"
BBLAYERS_meta-java:HEAD:99d16707d03898fe9fd5b4fee32f6417825a9e6a:"
BBLAYERS_meta-nick:master:3987b1f760a25941168f6c0277a0c49b46f5c723:modified"
BBLAYERS_workspace:::modified"

On Wed, 23 Jan 2019 at 12:14, nick83ola  wrote:
>
> this patch permit to simplify extracting build information from
> the /etc/build file from a script, f ex shell or python.
>
> Signed-off-by: Nicola Lunghi 
> ---
>  meta/classes/image-buildinfo.bbclass | 25 +++--
>  1 file changed, 11 insertions(+), 14 deletions(-)
>
> diff --git a/meta/classes/image-buildinfo.bbclass
> b/meta/classes/image-buildinfo.bbclass
> index 94c585d4cd..3ef6ad129d 100644
> --- a/meta/classes/image-buildinfo.bbclass
> +++ b/meta/classes/image-buildinfo.bbclass
> @@ -23,7 +23,7 @@ def image_buildinfo_outputvars(vars, d):
>  value = d.getVar(var) or ""
>  if (d.getVarFlag(var, 'type') == "list"):
>  value = oe.utils.squashspaces(value)
> -ret += "%s = %s\n" % (var, value)
> +ret += '%s="%s"\n' % (var, value)
>  return ret.rstrip('\n')
>
>  # Gets git branch's status (clean or dirty)
> @@ -40,12 +40,12 @@ def get_layer_git_status(path):
>  # Silently treat errors as "modified", without checking for the
>  # (expected) return code 1 in a modified git repo. For example, we 
> get
>  # output and a 129 return code when a layer isn't a git repo at all.
> -return "-- modified"
> +return "modified"
>
>  # Returns layer revisions along with their respective status
>  def get_layer_revs(d):
>  layers = (d.getVar("BBLAYERS") or "").split()
> -medadata_revs = ["%-17s = %s:%s %s" % (os.path.basename(i), \
> +medadata_revs = ['BBLAYERS_%s="%s:%s:%s"' % (os.path.basename(i), \
>  base_get_metadata_git_branch(i, None).strip(), \
>  base_get_metadata_git_revision(i, None), \
>  get_layer_git_status(i)) \
> @@ -66,19 +66,16 @@ python buildinfo () {
>  return
>  with open(d.expand('${IMAGE_ROOTFS}${IMAGE_BUILDINFO_FILE}'),
> 'w') as build:
>  build.writelines((
> -'''---
> -Build Configuration:  |
> 
> -''',
> +'\n',
> +'# Build Configuration  #\n',
> +'\n',
>  buildinfo_target(d),
> -'''
> 
> -Layer Revisions:  |
> 
> -''',
> +'\n\n',
> +'\n',
> +'# Layer Revisions  #\n',
> +'\n',
>  get_layer_revs(d),
> -'''
> -'''
> +'\n',
> ))
>  }
>
> --
> 2.19.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] image-buildinfo: make the build file shell compatible

2019-01-23 Thread nick83ola

this patch permit to simplify extracting build information from
the /etc/build file from a script, f ex shell or python.

Signed-off-by: Nicola Lunghi 
---
 meta/classes/image-buildinfo.bbclass | 25 +++--
 1 file changed, 11 insertions(+), 14 deletions(-)

diff --git a/meta/classes/image-buildinfo.bbclass
b/meta/classes/image-buildinfo.bbclass
index 94c585d4cd..3ef6ad129d 100644
--- a/meta/classes/image-buildinfo.bbclass
+++ b/meta/classes/image-buildinfo.bbclass
@@ -23,7 +23,7 @@ def image_buildinfo_outputvars(vars, d):
 value = d.getVar(var) or ""
 if (d.getVarFlag(var, 'type') == "list"):
 value = oe.utils.squashspaces(value)
-ret += "%s = %s\n" % (var, value)
+ret += '%s="%s"\n' % (var, value)
 return ret.rstrip('\n')

 # Gets git branch's status (clean or dirty)
@@ -40,12 +40,12 @@ def get_layer_git_status(path):
 # Silently treat errors as "modified", without checking for the
 # (expected) return code 1 in a modified git repo. For example, we get
 # output and a 129 return code when a layer isn't a git repo at all.
-return "-- modified"
+return "modified"

 # Returns layer revisions along with their respective status
 def get_layer_revs(d):
 layers = (d.getVar("BBLAYERS") or "").split()
-medadata_revs = ["%-17s = %s:%s %s" % (os.path.basename(i), \
+medadata_revs = ['BBLAYERS_%s="%s:%s:%s"' % (os.path.basename(i), \
 base_get_metadata_git_branch(i, None).strip(), \
 base_get_metadata_git_revision(i, None), \
 get_layer_git_status(i)) \
@@ -66,19 +66,16 @@ python buildinfo () {
 return
 with open(d.expand('${IMAGE_ROOTFS}${IMAGE_BUILDINFO_FILE}'),
'w') as build:
 build.writelines((
-'''---
-Build Configuration:  |

-''',
+'\n',
+'# Build Configuration  #\n',
+'\n',
 buildinfo_target(d),
-'''

-Layer Revisions:  |

-''',
+'\n\n',
+'\n',
+'# Layer Revisions  #\n',
+'\n',
 get_layer_revs(d),
-'''
-'''
+'\n',
))
 }

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

[OE-core] [poky][meta][os-release] Error building after commit c539765288bf3bc2c8578e037ce8fc9c2323b745

2018-09-17 Thread nick83ola

Hi,
after this patch I get this build error.
If I revert this all disappear.


system: docker image from crops (ubuntu 16.04)

Regards
Nicola Lunghi

=

ERROR: os-release-1.0-r0 do_install: Function failed: do_install (log file
is located at
/workspace/vegas-demo/build-imx7/tmp/work/all-poky-linux/os-release/1.0-r0/temp/log.do_install.169)

ERROR: Logfile of failure stored in:
/workspace/vegas-demo/build-imx7/tmp/work/all-poky-linux/os-release/1.0-r0/temp/log.do_install.169

Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['virtual:native:/workspace/vegas-demo/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',
'/workspace/vegas-demo/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:
do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['pseudo-native',
'quilt-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| mv:
'/workspace/vegas-demo/build-imx7/tmp/work/all-poky-linux/os-release/1.0-r0/image/etc/os-release'
and
'/workspace/vegas-demo/build-imx7/tmp/work/all-poky-linux/os-release/1.0-r0/image/usr/lib/os-release'
are the same file
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/workspace/vegas-demo/build-imx7/tmp/work/all-poky-linux/os-release/1.0-r0/temp/log.do_install.169)

ERROR: Task
(/workspace/vegas-demo/poky/meta/recipes-core/os-release/os-release.bb:do_install)
failed with exit code
'1'

NOTE: Tasks Summary: Attempted 3835 tasks of which 3834 didn't need to be
rerun and 1 failed.
NOTE: Writing buildhistory

==


commit c539765288bf3bc2c8578e037ce8fc9c2323b745
Author: Joshua Lock 
Date:   Tue Sep 4 16:50:00 2018 +0100

os-release: fix to install in the expected location

os-release (5) recommends that the os-release file be installed in
/usr/lib/os-release and that /etc/os-release be a relative symlink to
it.

(From OE-Core rev: 4feb8614ee25a3d3ceb7f5187120a1256a993155)

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 

diff --git a/meta/recipes-core/os-release/os-release.bb
b/meta/recipes-core/os-release/os-release.bb
index f988704756..bf4f815a10 100644
--- a/meta/recipes-core/os-release/os-release.bb
+++ b/meta/recipes-core/os-release/os-release.bb
@@ -1,7 +1,7 @@
 inherit allarch

 SUMMARY = "Operating system identification"
-DESCRIPTION = "The /etc/os-release file contains operating system
identification data."
+DESCRIPTION = "The /usr/lib/os-release file contains operating system
identification data."
 LICENSE = "MIT"
 INHIBIT_DEFAULT_DEPS = "1"

@@ -42,6 +42,9 @@ python do_compile () {
 do_compile[vardeps] += "${OS_RELEASE_FIELDS}"

 do_install () {
-install -d ${D}${sysconfdir}
-install -m 0644 os-release ${D}${sysconfdir}/
+install -d ${D}${libdir} ${D}${sysconfdir}
+install -m 0644 os-release ${D}${libdir}/
+lnr ${D}${libdir}/os-release ${D}${sysconfdir}/os-release
 }
+
+FILES_${PN} += "${libdir}/os-release"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [meta-oe][poky][PATCH v2] systemd: resolved linked even if the option is disabled

2018-07-17 Thread nick83ola

Hi

commit 00e4662e55f66570cae29240c22b4d74b79d3ca5
> Author: Maxin B. John  
> Date:   Mon Jun 12 18:10:21 2017 +0300
>
> systemd: enable resolved and networkd
>
> Enable systemd-resolved and systemd-networkd by default.
> Make it co-exist with connman and  Fix associated problems
> in read-only rootfs.
>
>
This part of the patch does nothing with the current version of systemd (or
does the wrong thing)


else
sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf -
- - - ../run/systemd/resolve/resolv.conf%g"
${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
+   ln -s ../run/systemd/resolve/resolv.conf
${D}${sysconfdir}/resolv-conf.systemd
fi

the check here was

 if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
apart from the part that the check is REVERSED ...
if the PACKAGECONFIG doesn't contain the resolved option systemd-resolved
is not build and no modification is done on the /lib/tmpfiles/etc/conf

see
https://github.com/systemd/systemd/blob/46659f7deb962f55c728e70597e37c2a3ab6326d/tmpfiles.d/etc.conf.m4#L16
m4_ifdef(`ENABLE_RESOLVE',
L! /etc/resolv.conf - - - - ../run/systemd/resolve/stub-resolv.conf
)m4_dnl

So the else branch can be safely removed.



>   commit 669edd04432f8e76e32bd7f34f4d9aa63eef4038
> Author: Khem Raj  
> Date:   Fri Dec 16 14:07:31 2016 -0800
>
> systemd: point to correct resolv.conf when resolved is enabled
>
> latest systemd has changed the resolved defaults which points to
> 127.0.0.53 port 53 on local network. If someone wants to use
> host-local IP address then it can be pointed to copy in /lib/systemd
>
> (From OE-Core rev: 99d1199fd0961f94732a1a533d66472ca17cf6f5)
>
> Signed-off-by: Khem Raj  
> Signed-off-by: Ross Burton 
> 
> Signed-off-by: Richard Purdie 
> 
>
>
So here the error was introduced! read this patch carefully
If you read the deleted comment it was saying:
*if resolved is disabled*,
But this patch reverse it to

systemd: point to correct resolv.conf when resolved *is enabled*

if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
-   # *if resolved is disabled*, it won't handle the link of
resolv.conf, so
-   # set it up ourselves
-   ln -s ../run/resolv.conf ${D}${sysconfdir}/resolv.conf
-   echo '*L! ${sysconfdir}/resolv.conf - - - -
../run/resolv.conf'* >>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
-   echo 'f /run/resolv.conf 0644 root root'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
+   echo* 'L! ${sysconfdir}/resolv.conf - - - -
../run/systemd/resolve/resolv.conf'*
>>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
+   echo 'd /run/systemd/resolve 0755 root root -'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
+   echo 'f /run/systemd/resolve/resolv.conf 0644 root root'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
+   ln -s ../run/systemd/resolve/resolv.conf
${D}${sysconfdir}/resolv.conf
+   else
+   sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf -
- - - ../run/systemd/resolve/resolv.conf%g"
${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
fi
install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON
${D}${systemd_unitdir}/systemd-sysv-install
 }







> commit b80da02ce9b683f96393fe0ea1f5f1a5f1a07c89
> Author: Christopher Larson 
> 
> Date:   Wed Nov 4 20:19:19 2015 -0700
>
> systemd: arrange for volatile /etc/resolv.conf
>
> On sysvinit systems, volatiles is configured to make /etc/resolv.conf
> symlink
> to a file in a volatile path, which lets us write to /etc/resolv.conf
> for
> read-only-rootfs. For systemd, this isn't set up unless we enable
> systemd-resolved, which we don't by default. When it's not enabled,
> create the
> /etc/resolv.conf symlink and ensure the volatile path is created on
> boot with
> tmpfiles.d.
>
>
+   if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
+   # if resolved is disabled, it won't handle the link of
resolv.conf, so
+   # set it up ourselves
+   ln -s ../run/resolv.conf ${D}${sysconfdir}/resolv.conf
+   echo 'L! ${sysconfdir}/resolv.conf - - - -
../run/resolv.conf' >>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
+   echo 'f /run/resolv.conf 0644 root root'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
+   fi
install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON
${D}${systemd_unitdir}/systemd-sysv-install
 }

This patch was the right one the following
669edd04432f8e76e32bd7f34f4d9aa63eef4038 reversed the sense of the switch

Regards
Nicola Lunghi


> Best Regards,
> Chen Qi
>
>
> On 07/16/2018 04:17 PM, Nicola Lunghi wrote:
>
> From: Nicola Lunghi  
>
> if resolved option is not selected the package systemd-resolved
> is not installed so it cannot

Re: [OE-core] [meta-oe][poky][PATCH v2] systemd: resolved linked even if the option is disabled

2018-07-17 Thread nick83ola

Hi Chen Qi,
Thanks I didn't see your previous response.
I will have a look and post my considerations.

Best Regards
Nicola Lunghi

On Mon, 16 Jul 2018 at 10:09, ChenQi  wrote:

> Hi Nicola,
>
> As I replied on poky mailing list to this patch, you need to first check
> the following three commits.
>
> commit 00e4662e55f66570cae29240c22b4d74b79d3ca5
> Author: Maxin B. John  
> Date:   Mon Jun 12 18:10:21 2017 +0300
>
> systemd: enable resolved and networkd
>
> Enable systemd-resolved and systemd-networkd by default.
> Make it co-exist with connman and  Fix associated problems
> in read-only rootfs.
>
> Fixes [YOCTO #11331]
>
> (From OE-Core rev: d9b6d538e3d81ab0d5e7b7b6adecef555d782217)
>
> Signed-off-by: Maxin B. John 
> 
> Signed-off-by: Richard Purdie 
> 
>
> commit 669edd04432f8e76e32bd7f34f4d9aa63eef4038
> Author: Khem Raj  
> Date:   Fri Dec 16 14:07:31 2016 -0800
>
> systemd: point to correct resolv.conf when resolved is enabled
>
> latest systemd has changed the resolved defaults which points to
> 127.0.0.53 port 53 on local network. If someone wants to use
> host-local IP address then it can be pointed to copy in /lib/systemd
>
> (From OE-Core rev: 99d1199fd0961f94732a1a533d66472ca17cf6f5)
>
> Signed-off-by: Khem Raj  
> Signed-off-by: Ross Burton 
> 
> Signed-off-by: Richard Purdie 
> 
>
> commit b80da02ce9b683f96393fe0ea1f5f1a5f1a07c89
> Author: Christopher Larson 
> 
> Date:   Wed Nov 4 20:19:19 2015 -0700
>
> systemd: arrange for volatile /etc/resolv.conf
>
> On sysvinit systems, volatiles is configured to make /etc/resolv.conf
> symlink
> to a file in a volatile path, which lets us write to /etc/resolv.conf
> for
> read-only-rootfs. For systemd, this isn't set up unless we enable
> systemd-resolved, which we don't by default. When it's not enabled,
> create the
> /etc/resolv.conf symlink and ensure the volatile path is created on
> boot with
> tmpfiles.d.
>
> (From OE-Core rev: 7f087f161e8942bcd35f88999dfca418f01cd7fa)
>
> Signed-off-by: Christopher Larson 
> 
> Signed-off-by: Ross Burton 
> 
> Signed-off-by: Richard Purdie 
> 
>
> Best Regards,
> Chen Qi
>
>
> On 07/16/2018 04:17 PM, Nicola Lunghi wrote:
>
> From: Nicola Lunghi  
>
> if resolved option is not selected the package systemd-resolved
> is not installed so it cannot provide an alternative for
> resolv.conf
>
> In this recipe the previous check was instead reversing the check (note the 
> !).
>
> This patch avoid messing with resol.conf link if resolved is disabled in
> the package config.
>
> This in particular if we compile systemd with musl where systemd-resolved
> cannot be compiled.
>
> Signed-off-by: Nicola Lunghi  
> ---
>  meta/recipes-core/systemd/systemd_237.bb | 8 +++-
>  1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-core/systemd/systemd_237.bb 
> b/meta/recipes-core/systemd/systemd_237.bb
> index 3efca33e73..bd6dcef637 100644
> --- a/meta/recipes-core/systemd/systemd_237.bb
> +++ b/meta/recipes-core/systemd/systemd_237.bb
> @@ -258,14 +258,11 @@ do_install() {
>   if [ -s ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf ]; then
>   ${@bb.utils.contains('PACKAGECONFIG', 'networkd', ':', 'sed -i 
> -e "\$ad /run/systemd/netif/links 0755 root root -" 
> ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf', d)}
>   fi
> - if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true', 'false', 
> d)}; then
> + if ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true', 'false', 
> d)}; then
>   echo 'L! ${sysconfdir}/resolv.conf - - - - 
> ../run/systemd/resolve/resolv.conf' 
> >>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
>   echo 'd /run/systemd/resolve 0755 root root -' 
> >>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
>   echo 'f /run/systemd/resolve/resolv.conf 0644 root root' 
> >>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
>   ln -s ../run/systemd/resolve/resolv.conf 
> ${D}${sysconfdir}/resolv-conf.systemd
> - else
> - sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf - - - 
> - ../run/systemd/resolve/resolv.conf%g" 
> ${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
> - ln -s ../run/systemd/resolve/resolv.conf 
> ${D}${sysconfdir}/resolv-conf.systemd
>   fi
>   install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON 
> ${D}${systemd_unitdir}/systemd-sysv-install
>
> @@ -539,7 +536,7 @@ python __anonymous() {
>  # TODO:
>  # u-a for runlevel and telinit
>
> -ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel resolv-conf"
> +ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel"
>
>  ALTERNATIVE_TARGET[init] = "${rootlibexecdir}/systemd/systemd"
>  ALTERNATIVE_LINK_NAME[init] = "${base_sbindir}/init"
> @@ -565,6 +562,7 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
>  ALTERNATIVE_LINK_NAME[runlevel] =

Re: [OE-core] [HELP] ptest & ptest

2018-07-16 Thread nick83ola

Thanks I'll have a look at those


On Mon, 16 Jul 2018 at 15:19, Tim Orling  wrote:

>
> http://cgit.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python-cryptography_2.2.2.bb
>
> http://cgit.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python-pygpgme_0.3.bb
> On Mon, Jul 16, 2018 at 1:41 AM nick83ola  wrote:
>
>> Hi Alex,
>> thanks for your response.
>>
>> Do you or anyone else have an example about an actual python package that
>> use ptest (possibily using distutils/nose/py.test)?
>>
>> Thanks
>> Nick
>>
>> On Tue, 26 Jun 2018 at 16:07, Alexander Kanavin 
>> wrote:
>>
>>> The Yocto documentation has general information:
>>>
>>>
>>> https://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#testing-packages-with-ptest
>>>
>>> Alex
>>>
>>>
>>> 2018-06-26 14:57 GMT+02:00 nick83ola :
>>> > Hi all,
>>> >
>>> > I have a python3 package that launch a py.test test suite from
>>> > setup.py and I have created a recipe for it using setuptools3
>>> >
>>> > Anyone has some hint about how to add a ptest target to run the tests
>>> > into the final image (or better in a qemu test image)?
>>> >
>>> > there are some recipe/documentation that I can look at about creating
>>> > -ptest target for python packages?
>>> >
>>> > Regards
>>> > Nicola Lunghi
>>> > --
>>> > ___
>>> > 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
>>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [HELP] ptest & ptest

2018-07-16 Thread nick83ola

Hi Alex,
thanks for your response.

Do you or anyone else have an example about an actual python package that
use ptest (possibily using distutils/nose/py.test)?

Thanks
Nick

On Tue, 26 Jun 2018 at 16:07, Alexander Kanavin 
wrote:

> The Yocto documentation has general information:
>
>
> https://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#testing-packages-with-ptest
>
> Alex
>
>
> 2018-06-26 14:57 GMT+02:00 nick83ola :
> > Hi all,
> >
> > I have a python3 package that launch a py.test test suite from
> > setup.py and I have created a recipe for it using setuptools3
> >
> > Anyone has some hint about how to add a ptest target to run the tests
> > into the final image (or better in a qemu test image)?
> >
> > there are some recipe/documentation that I can look at about creating
> > -ptest target for python packages?
> >
> > Regards
> > Nicola Lunghi
> > --
> > ___
> > 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] [HELP] ptest & ptest

2018-06-26 Thread nick83ola

Hi all,

I have a python3 package that launch a py.test test suite from
setup.py and I have created a recipe for it using setuptools3

Anyone has some hint about how to add a ptest target to run the tests
into the final image (or better in a qemu test image)?

there are some recipe/documentation that I can look at about creating
-ptest target for python packages?

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

Re: [OE-core] [oe][meta-oe][PATCH 1/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

2018-06-01 Thread nick83ola

Thanks
Sorry for that I will submit everything to the right mailing list :-)

Nick

On 25 May 2018 at 20:19, Randy MacLeod  wrote:
> On 05/25/2018 10:14 AM, nick83ola wrote:
>>
>> The openembedded recipe for mosquitto doesn't provide a default
>> configuration file.
>>
>> Also it install a bunch of examples.
>>
>> This series of patches provide a "default" configuration file and setup
>> logging.
>
>
> The mosquitto recipe is part of meta-openembedded:
> http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb?h=master
>
> so send a patch to:
>   openembedded-de...@lists.openembedded.org
>
> Also, patches in email attachments are not the right format, see:
>https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>
>
> Thanks for working on the patch and good luck,
>
> ../Randy
>
>>
>>
>> Cheers
>>
>> Nicola Lunghi
>>
>>
>>
>>
>
>
> --
> # Randy MacLeod
> # Wind River Linux
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [poky][PATCH][REPOST] systemd: resolved linked even if the option is disabled

2018-05-31 Thread nick83ola

Repost this patch due to wrong formatting

--

systemd: resolved linked even if the option is disabled

in the do_install function in systemd recipe the condition to check
if the resolved option is selected is reversed (wrong !).
This is for example true if we compile systemd with musl instead of
glibc (every poky-image-minimal recipe).

Also no link should be created if the option is not selected
nor an ALTERNATIVE set.

Signed-off-by: Nicola Lunghi 
---
 meta/recipes-core/systemd/systemd_237.bb | 8 +++-
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_237.bb
b/meta/recipes-core/systemd/systemd_237.bb
index 2e6558ded1..2eea6af508 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -256,14 +256,11 @@ do_install() {
 if [ -s ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf ]; then
 ${@bb.utils.contains('PACKAGECONFIG', 'networkd', ':', 'sed
-i -e "\$ad /run/systemd/netif/links 0755 root root -"
${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf', d)}
 fi
-if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
+if ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
 echo 'L! ${sysconfdir}/resolv.conf - - - -
../run/systemd/resolve/resolv.conf'
>>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
 echo 'd /run/systemd/resolve 0755 root root -'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
 echo 'f /run/systemd/resolve/resolv.conf 0644 root root'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
 ln -s ../run/systemd/resolve/resolv.conf
${D}${sysconfdir}/resolv-conf.systemd
-else
-sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf - -
- - ../run/systemd/resolve/resolv.conf%g"
${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
-ln -s ../run/systemd/resolve/resolv.conf
${D}${sysconfdir}/resolv-conf.systemd
 fi
 install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON
${D}${systemd_unitdir}/systemd-sysv-install

@@ -537,7 +534,7 @@ python __anonymous() {
 # TODO:
 # u-a for runlevel and telinit

-ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel resolv-conf"
+ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel"

 ALTERNATIVE_TARGET[init] = "${rootlibexecdir}/systemd/systemd"
 ALTERNATIVE_LINK_NAME[init] = "${base_sbindir}/init"
@@ -563,6 +560,7 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
 ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"

+ALTERNATIVE_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
'resolved', 'resolv-conf', '', d)}"
 ALTERNATIVE_TARGET[resolv-conf] = "${sysconfdir}/resolv-conf.systemd"
 ALTERNATIVE_LINK_NAME[resolv-conf] = "${sysconfdir}/resolv.conf"
 ALTERNATIVE_PRIORITY[resolv-conf] ?= "50"
-- 
2.17.0
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Fwd: [poky][PATCH] systemd: resolved linked even if the option is disabled

2018-05-30 Thread nick83ola

-- Forwarded message --
From: nick83ola 
Date: 30 May 2018 at 14:24
Subject: [poky][PATCH] systemd: resolved linked even if the option is disabled
To: p...@yoctoproject.org


systemd: resolved linked even if the option is disabled

in the do_install function in systemd recipe the condition to check
if the resolved option is selected is reversed (wrong !).
This is for example true if we compile systemd with musl instead of
glibc (every poky-image-minimal recipe).

Also no link should be created if the option is not selected
nor an ALTERNATIVE set.

Signed-off-by: Nicola Lunghi 
---
 meta/recipes-core/systemd/systemd_237.bb | 8 +++-
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_237.bb
b/meta/recipes-core/systemd/systemd_237.bb
index 2e6558ded1..2eea6af508 100644
--- a/meta/recipes-core/systemd/systemd_237.bb
+++ b/meta/recipes-core/systemd/systemd_237.bb
@@ -256,14 +256,11 @@ do_install() {
 if [ -s ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf ]; then
 ${@bb.utils.contains('PACKAGECONFIG', 'networkd', ':', 'sed
-i -e "\$ad /run/systemd/netif/links 0755 root root -"
${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf', d)}
 fi
-if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
+if ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true',
'false', d)}; then
 echo 'L! ${sysconfdir}/resolv.conf - - - -
../run/systemd/resolve/resolv.conf'
>>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
 echo 'd /run/systemd/resolve 0755 root root -'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
 echo 'f /run/systemd/resolve/resolv.conf 0644 root root'
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
 ln -s ../run/systemd/resolve/resolv.conf
${D}${sysconfdir}/resolv-conf.systemd
-else
-sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf - -
- - ../run/systemd/resolve/resolv.conf%g"
${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
-ln -s ../run/systemd/resolve/resolv.conf
${D}${sysconfdir}/resolv-conf.systemd
 fi
 install -Dm 0755 ${S}/src/systemctl/systemd-sysv-install.SKELETON
${D}${systemd_unitdir}/systemd-sysv-install

@@ -537,7 +534,7 @@ python __anonymous() {
 # TODO:
 # u-a for runlevel and telinit

-ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel resolv-conf"
+ALTERNATIVE_${PN} = "init halt reboot shutdown poweroff runlevel"

 ALTERNATIVE_TARGET[init] = "${rootlibexecdir}/systemd/systemd"
 ALTERNATIVE_LINK_NAME[init] = "${base_sbindir}/init"
@@ -563,6 +560,7 @@ ALTERNATIVE_TARGET[runlevel] = "${base_bindir}/systemctl"
 ALTERNATIVE_LINK_NAME[runlevel] = "${base_sbindir}/runlevel"
 ALTERNATIVE_PRIORITY[runlevel] ?= "300"

+ALTERNATIVE_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
'resolved', 'resolv-conf', '', d)}"
 ALTERNATIVE_TARGET[resolv-conf] = "${sysconfdir}/resolv-conf.systemd"
 ALTERNATIVE_LINK_NAME[resolv-conf] = "${sysconfdir}/resolv.conf"
 ALTERNATIVE_PRIORITY[resolv-conf] ?= "50"
--
2.17.0




-- 

P.S. Le informazioni trasmesse attraverso la presente comunicazione
sono di esclusiva
spettanza dell'effettivo destinatario. Nel caso in cui le stesse
raggiungessero, per
qualunque motivo, soggetti non interessati, questi ultimi vorranno
darne immediata
notizia al mittente. In ogni caso, eventuali soggetti diversi dai
legittimi destinatari
della presente comunicazione e dei dati contenuti negli allegati, possono essere
sanzionati ai sensi del T.U. sul trattamento dei dati personali d.lgs.
196/2003, sia ai
sensi dell'art. 616 del Codice Penale che disciplina la violazione del
segreto sulla
corrispondenza.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] hostapd defconfig: update defconfig from 2.6 hostapd package

2018-05-30 Thread nick83ola

hostapd defconfig: update defconfig from 2.6 hostapd package

the previous implementation of this recipe use a very old
defconfig from hostapd 0.7.3
Update it with the latest version and add some option
from debian defconfig

Signed-off-by: Nicola Lunghi 
---
 .../hostapd/hostapd/defconfig | 273 +++---
 1 file changed, 236 insertions(+), 37 deletions(-)

diff --git a/meta-oe/recipes-connectivity/hostapd/hostapd/defconfig
b/meta-oe/recipes-connectivity/hostapd/hostapd/defconfig
index 278964017..f958db431 100644
--- a/meta-oe/recipes-connectivity/hostapd/hostapd/defconfig
+++ b/meta-oe/recipes-connectivity/hostapd/hostapd/defconfig
@@ -15,30 +15,33 @@ CONFIG_DRIVER_HOSTAP=y
 # Driver interface for wired authenticator
 CONFIG_DRIVER_WIRED=y

-# Driver interface for madwifi driver
-#CONFIG_DRIVER_MADWIFI=y
-#CFLAGS += -I../../madwifi # change to the madwifi source directory
-
-# Driver interface for Prism54 driver
-CONFIG_DRIVER_PRISM54=y
-
 # Driver interface for drivers using the nl80211 kernel interface
 CONFIG_DRIVER_NL80211=y
+
+# QCA vendor extensions to nl80211
+CONFIG_DRIVER_NL80211_QCA=y
+
+# driver_nl80211.c requires libnl. If you are compiling it yourself
+# you may need to point hostapd to your version of libnl.
+#
+#CFLAGS += -I$
+#LIBS += -L$
+
+# Use libnl v2.0 (or 3.0) libraries.
+#CONFIG_LIBNL20=y
+
+# Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is ignored)
 CONFIG_LIBNL32=y
-# driver_nl80211.c requires a rather new libnl (version 1.1) which may not be
-# shipped with your distribution yet. If that is the case, you need to build
-# newer libnl version and point the hostapd build to use it.
-#LIBNL=/usr/src/libnl
-#CFLAGS += -I$(LIBNL)/include
-#LIBS += -L$(LIBNL)/lib

 # Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
 #CONFIG_DRIVER_BSD=y
 #CFLAGS += -I/usr/local/include
 #LIBS += -L/usr/local/lib
+#LIBS_p += -L/usr/local/lib
+#LIBS_c += -L/usr/local/lib

 # Driver interface for no driver (e.g., RADIUS server only)
-#CONFIG_DRIVER_NONE=y
+CONFIG_DRIVER_NONE=y

 # IEEE 802.11F/IAPP
 CONFIG_IAPP=y
@@ -50,14 +53,14 @@ CONFIG_RSN_PREAUTH=y
 CONFIG_PEERKEY=y

 # IEEE 802.11w (management frame protection)
-# This version is an experimental implementation based on IEEE 802.11w/D1.0
-# draft and is subject to change since the standard has not yet been finalized.
-# Driver support is also needed for IEEE 802.11w.
-#CONFIG_IEEE80211W=y
+CONFIG_IEEE80211W=y

 # Integrated EAP server
 CONFIG_EAP=y

+# EAP Re-authentication Protocol (ERP) in integrated EAP server
+CONFIG_ERP=y
+
 # EAP-MD5 for the integrated EAP server
 CONFIG_EAP_MD5=y

@@ -77,46 +80,53 @@ CONFIG_EAP_GTC=y
 CONFIG_EAP_TTLS=y

 # EAP-SIM for the integrated EAP server
-#CONFIG_EAP_SIM=y
+CONFIG_EAP_SIM=y

 # EAP-AKA for the integrated EAP server
-#CONFIG_EAP_AKA=y
+CONFIG_EAP_AKA=y

 # EAP-AKA' for the integrated EAP server
 # This requires CONFIG_EAP_AKA to be enabled, too.
-#CONFIG_EAP_AKA_PRIME=y
+CONFIG_EAP_AKA_PRIME=y

 # EAP-PAX for the integrated EAP server
-#CONFIG_EAP_PAX=y
+CONFIG_EAP_PAX=y

 # EAP-PSK for the integrated EAP server (this is _not_ needed for WPA-PSK)
-#CONFIG_EAP_PSK=y
+CONFIG_EAP_PSK=y
+
+# EAP-pwd for the integrated EAP server (secure authentication with a password)
+CONFIG_EAP_PWD=y

 # EAP-SAKE for the integrated EAP server
-#CONFIG_EAP_SAKE=y
+CONFIG_EAP_SAKE=y

 # EAP-GPSK for the integrated EAP server
-#CONFIG_EAP_GPSK=y
+CONFIG_EAP_GPSK=y
 # Include support for optional SHA256 cipher suite in EAP-GPSK
-#CONFIG_EAP_GPSK_SHA256=y
+CONFIG_EAP_GPSK_SHA256=y

 # EAP-FAST for the integrated EAP server
-# Note: Default OpenSSL package does not include support for all the
-# functionality needed for EAP-FAST. If EAP-FAST is enabled with OpenSSL,
-# the OpenSSL library must be patched (openssl-0.9.9-session-ticket.patch)
-# to add the needed functions.
-#CONFIG_EAP_FAST=y
+# Note: If OpenSSL is used as the TLS library, OpenSSL 1.0 or newer is needed
+# for EAP-FAST support. Older OpenSSL releases would need to be patched, e.g.,
+# with openssl-0.9.8x-tls-extensions.patch, to add the needed functions.
+CONFIG_EAP_FAST=y

 # Wi-Fi Protected Setup (WPS)
 CONFIG_WPS=y
 # Enable UPnP support for external WPS Registrars
-#CONFIG_WPS_UPNP=y
+CONFIG_WPS_UPNP=y
+# Enable WPS support with NFC config method
+CONFIG_WPS_NFC=y

 # EAP-IKEv2
-#CONFIG_EAP_IKEV2=y
+CONFIG_EAP_IKEV2=y

 # Trusted Network Connect (EAP-TNC)
-#CONFIG_EAP_TNC=y
+CONFIG_EAP_TNC=y
+
+# EAP-EKE for the integrated EAP server
+CONFIG_EAP_EKE=y

 # PKCS#12 (PFX) support (used to read private key and certificate file from
 # a file that usually has extension .p12 or .pfx)
@@ -130,16 +140,205 @@ CONFIG_RADIUS_SERVER=y
 CONFIG_IPV6=y

 # IEEE Std 802.11r-2008 (Fast BSS Transition)
-#CONFIG_IEEE80211R=y
+CONFIG_IEEE80211R=y

 # Use the hostapd's IEEE 802.11 authentication (ACL), but without
-# the IEEE 802.11 Management capability (e.g., madwifi or FreeBSD/net80211)
-CONFIG_DRIVER_RADIUS_ACL=y
+#

[OE-core] [oe][meta-oe][PATCH 3/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

2018-05-25 Thread nick83ola


From 816446fd199a16948f83263ad7a2e6ff6ff004b1 Mon Sep 17 00:00:00 2001
From: Nicola Lunghi 
Date: Fri, 25 May 2018 14:34:13 +0100
Subject: [PATCH 3/3] mosquitto_1.4.14: add log file

enable logging by default and create the necessary
files/folder

Change-Id: I68a23e891e5bc928c33634c92d0b9faa8db624aa
Signed-off-by: Nicola Lunghi 
---
 .../mosquitto/files/mosquitto-yocto.conf   |  1 +
 .../mosquitto/mosquitto_1.4.14.bb  | 14 ++
 2 files changed, 15 insertions(+)

diff --git a/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf b/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf
index 9b43323f3..a695d5429 100644
--- a/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf
+++ b/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf
@@ -1,4 +1,5 @@
 pid_file @LOCALSTATEDIR@/run/mosquitto.pid
+log_dest file @LOCALSTATEDIR@/log/mosquitto/mosquitto.log
 
 # Place your local configuration in /etc/mosquitto/conf.d/
 include_dir @SYSCONFDIR@/mosquitto/conf.d
diff --git a/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb b/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
index ce21379f6..5155655c5 100644
--- a/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
+++ b/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
@@ -55,6 +55,18 @@ do_install() {
 # create an empty conf.d directory to make mosquitto happy
 install -d ${D}${sysconfdir}/mosquitto/conf.d
 
+if [ ${@bb.utils.filter('DISTRO_FEATURES','sysvinit',d)} ]; then
+install -d ${D}${sysconfdir}/default/volatiles
+echo "d mosquitto mosquitto 0755 ${localstatedir}/log/mosquitto none" \
+> ${D}${sysconfdir}/default/volatiles/10_mosquitto
+elif [ ${@bb.utils.filter('DISTRO_FEATURES','systemd',d)} ]; then
+install -d ${D}${sysconfdir}/tmpfiles.d
+echo "d ${localstatedir}/log/mosquitto 0755 mosquitto mosquitto -" \
+ > ${D}${sysconfdir}/tmpfiles.d/mosquitto.conf
+else
+bbfatal "could not create mosquitto log directory missing systemd or sysvinit"
+fi
+
 install -d ${D}${systemd_unitdir}/system/
 install -m 0644 ${WORKDIR}/mosquitto.service ${D}${systemd_unitdir}/system/
 
@@ -74,6 +86,8 @@ FILES_${PN} = "${sbindir}/mosquitto \
${sysconfdir}/mosquitto \
${sysconfdir}/init.d \
${systemd_unitdir}/system/mosquitto.service \
+   ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', '${sysconfdir}/tmpfiles.d/mosquitto.conf', '', d)} \
+   ${@bb.utils.contains('DISTRO_FEATURES', 'sysvinit', '${sysconfdir}/default/volatiles/10_mosquitto', '', d)} \
 "
 CONFFILES_${PN} += "${sysconfdir}/mosquitto"
 
-- 
2.17.0

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

[OE-core] [oe][meta-oe][PATCH 2/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

2018-05-25 Thread nick83ola


From 26e6331d18edf7849776d1937b63074e8017b6cb Mon Sep 17 00:00:00 2001
From: Nicola Lunghi 
Date: Fri, 25 May 2018 14:32:34 +0100
Subject: [PATCH 2/3] mosquitto_1.4.14: add default configuration file

this patch implement the following changes:
-add a mosquitto configuration file to the recipe to make simpler to
 use with bbappends
-create a conf.d directory where to puth customized configuration files

Change-Id: I2ee2d3c533f53450249de3556925c4b4b2fffda8
Signed-off-by: Nicola Lunghi 
---
 .../mosquitto/files/mosquitto-yocto.conf  |  4 
 .../mosquitto/mosquitto_1.4.14.bb | 11 +++
 2 files changed, 15 insertions(+)
 create mode 100644 meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf

diff --git a/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf b/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf
new file mode 100644
index 0..9b43323f3
--- /dev/null
+++ b/meta-oe/recipes-connectivity/mosquitto/files/mosquitto-yocto.conf
@@ -0,0 +1,4 @@
+pid_file @LOCALSTATEDIR@/run/mosquitto.pid
+
+# Place your local configuration in /etc/mosquitto/conf.d/
+include_dir @SYSCONFDIR@/mosquitto/conf.d
diff --git a/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb b/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
index 76eb79b9f..ce21379f6 100644
--- a/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
+++ b/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
@@ -14,6 +14,7 @@ SRC_URI = "http://mosquitto.org/files/source/mosquitto-${PV}.tar.gz \
file://0001-config.mk-allow-prefix-mandir-localedir-from-environ.patch \
file://0002-uthash-remove-in-tree-version.patch \
file://0003-remove-example-files.patch \
+   file://mosquitto-yocto.conf \
file://mosquitto.service \
file://mosquitto.init \
 "
@@ -45,6 +46,15 @@ do_install() {
 install -d ${D}${libdir}
 install -m 0644 lib/libmosquitto.a ${D}${libdir}/
 
+install -d ${D}${sysconfdir}/mosquitto
+install -m 0644 ${WORKDIR}/mosquitto-yocto.conf ${D}${sysconfdir}/mosquitto/mosquitto.conf
+sed -i -e 's,@LOCALSTATEDIR@,${localstatedir},g' \
+-e 's,@SYSCONFDIR@,${sysconfdir},g' \
+${D}${sysconfdir}/mosquitto/mosquitto.conf
+
+# create an empty conf.d directory to make mosquitto happy
+install -d ${D}${sysconfdir}/mosquitto/conf.d
+
 install -d ${D}${systemd_unitdir}/system/
 install -m 0644 ${WORKDIR}/mosquitto.service ${D}${systemd_unitdir}/system/
 
@@ -65,6 +75,7 @@ FILES_${PN} = "${sbindir}/mosquitto \
${sysconfdir}/init.d \
${systemd_unitdir}/system/mosquitto.service \
 "
+CONFFILES_${PN} += "${sysconfdir}/mosquitto"
 
 FILES_libmosquitto1 = "${libdir}/libmosquitto.so.1"
 
-- 
2.17.0

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

[OE-core] [oe][meta-oe][PATCH 1/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

2018-05-25 Thread nick83ola

The openembedded recipe for mosquitto doesn't provide a default
configuration file.

Also it install a bunch of examples.

This series of patches provide a "default" configuration file and setup
logging.


Cheers

Nicola Lunghi
From 1e62b706ce335194680782b4e5f200a0123718fe Mon Sep 17 00:00:00 2001
From: Nicola Lunghi 
Date: Fri, 25 May 2018 14:20:08 +0100
Subject: [PATCH 1/3] mosquitto: remove example files from installation

The mosquitto makefile install a lot of example configuration files
on the image: remove those

Change-Id: I4d8af864f955ea5dc34a34ff11a7d3013aefbeda
Signed-off-by: Nicola Lunghi 
---
 .../files/0003-remove-example-files.patch | 35 +++
 .../mosquitto/mosquitto_1.4.14.bb |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 meta-oe/recipes-connectivity/mosquitto/files/0003-remove-example-files.patch

diff --git a/meta-oe/recipes-connectivity/mosquitto/files/0003-remove-example-files.patch b/meta-oe/recipes-connectivity/mosquitto/files/0003-remove-example-files.patch
new file mode 100644
index 0..a5566a074
--- /dev/null
+++ b/meta-oe/recipes-connectivity/mosquitto/files/0003-remove-example-files.patch
@@ -0,0 +1,35 @@
+From f0e97c16fe0d49f61e5da0aa884f4f7d5a911e90 Mon Sep 17 00:00:00 2001
+From: Nicola Lunghi 
+Date: Mon, 26 Mar 2018 12:21:43 +0100
+Subject: [PATCH] removed example files
+
+---
+ Makefile | 9 -
+ 1 file changed, 9 deletions(-)
+
+diff --git a/Makefile b/Makefile
+index 1fc0805..76f81b1 100644
+--- a/Makefile
 b/Makefile
+@@ -39,18 +39,9 @@ install : mosquitto
+ ifeq ($(WITH_DOCS),yes)
+ 	set -e; for d in ${DOCDIRS}; do $(MAKE) -C $${d} install; done
+ endif
+-	$(INSTALL) -d ${DESTDIR}/etc/mosquitto
+-	$(INSTALL) -m 644 mosquitto.conf ${DESTDIR}/etc/mosquitto/mosquitto.conf.example
+-	$(INSTALL) -m 644 aclfile.example ${DESTDIR}/etc/mosquitto/aclfile.example
+-	$(INSTALL) -m 644 pwfile.example ${DESTDIR}/etc/mosquitto/pwfile.example
+-	$(INSTALL) -m 644 pskfile.example ${DESTDIR}/etc/mosquitto/pskfile.example
+ 
+ uninstall :
+ 	set -e; for d in ${DIRS}; do $(MAKE) -C $${d} uninstall; done
+-	rm -f ${DESTDIR}/etc/mosquitto/mosquitto.conf
+-	rm -f ${DESTDIR}/etc/mosquitto/aclfile.example
+-	rm -f ${DESTDIR}/etc/mosquitto/pwfile.example
+-	rm -f ${DESTDIR}/etc/mosquitto/pskfile.example
+ 
+ dist : reallyclean
+ 	set -e; for d in ${DISTDIRS}; do $(MAKE) -C $${d} dist; done
+-- 
+2.14.1
+
diff --git a/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb b/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
index 13ce3811d..76eb79b9f 100644
--- a/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
+++ b/meta-oe/recipes-connectivity/mosquitto/mosquitto_1.4.14.bb
@@ -13,6 +13,7 @@ DEPENDS = "uthash"
 SRC_URI = "http://mosquitto.org/files/source/mosquitto-${PV}.tar.gz \
file://0001-config.mk-allow-prefix-mandir-localedir-from-environ.patch \
file://0002-uthash-remove-in-tree-version.patch \
+   file://0003-remove-example-files.patch \
file://mosquitto.service \
file://mosquitto.init \
 "
-- 
2.17.0

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

[OE-core] Update layer compatibility to Dunfell

Re: [OE-core] Oe-core: python and BBCLASSEXTEND = "native nativesdk"

[OE-core] Oe-core: python and BBCLASSEXTEND = "native nativesdk"

[OE-core] Fwd: [meta][PATCH] ofono: run oe-stylize over recipe

[OE-core] [oe-core] [BUG] patch linux-firmware: bump to 20190618 breaks package index

Re: [OE-core] [PATCH v2 2/3] rng-tools: 6.6->6.7

Re: [OE-core] [PATCH v2 1/3] rng-tools: recipe cleanup

Re: [OE-core] [PATCH 2/2] rng-tools: 6.6->6.7

Re: [OE-core] OE-Core status with gcc9

Re: [OE-core] [PATCH] nginx: fix kill path in nginx systemd unit file

Re: [OE-core] [oe][meta-webserver][PATCH 1/2] nginx: update to version 1.17.0

Re: [OE-core] [PATCH] connman: fix segfault with musl >2.21

Re: [OE-core] [PATCH] image-buildinfo: make the build file shell compatible

Re: [OE-core] [PATCH] image-buildinfo: make the build file shell compatible

[OE-core] [PATCH] image-buildinfo: make the build file shell compatible

[OE-core] [poky][meta][os-release] Error building after commit c539765288bf3bc2c8578e037ce8fc9c2323b745

Re: [OE-core] [meta-oe][poky][PATCH v2] systemd: resolved linked even if the option is disabled

Re: [OE-core] [meta-oe][poky][PATCH v2] systemd: resolved linked even if the option is disabled

Re: [OE-core] [HELP] ptest & ptest

Re: [OE-core] [HELP] ptest & ptest

[OE-core] [HELP] ptest & ptest

Re: [OE-core] [oe][meta-oe][PATCH 1/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

[OE-core] [poky][PATCH][REPOST] systemd: resolved linked even if the option is disabled

[OE-core] Fwd: [poky][PATCH] systemd: resolved linked even if the option is disabled

[OE-core] [PATCH] hostapd defconfig: update defconfig from 2.6 hostapd package

[OE-core] [oe][meta-oe][PATCH 3/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

[OE-core] [oe][meta-oe][PATCH 2/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

[OE-core] [oe][meta-oe][PATCH 1/3] Mosquitto add a mosquitto conf and logging to the default mosquitto recipe

28 matches

Site Navigation

Mail list logo

Footer information