Re: [OE-core] [PATCH v1] postinst-intercepts: check tool presence in intercept hooks

[ChenQi]

Under which circumstances will the tools be absent?
And why do you check the existence of files for some the the existence 
of directories for others?


Best Regards,
Chen Qi

On 06/26/2019 06:13 AM, Sinan Kaya wrote:

do_rootfs: The postinstall intercept hook 'update_udev_hwdb'
do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed
do_rootfs: The postinstall intercept hook 'update_icon_cache' failed
do_rootfs: The postinstall intercept hook 'update_icon_cache' failed

Signed-off-by: Sinan Kaya 
---
  scripts/postinst-intercepts/update_font_cache|  6 --
  .../postinst-intercepts/update_gio_module_cache  | 10 +++---
  scripts/postinst-intercepts/update_icon_cache| 16 +---
  scripts/postinst-intercepts/update_pixbuf_cache  |  5 -
  scripts/postinst-intercepts/update_udev_hwdb |  6 --
  5 files changed, 28 insertions(+), 15 deletions(-)

diff --git a/scripts/postinst-intercepts/update_font_cache 
b/scripts/postinst-intercepts/update_font_cache
index 3053c7065f4..954acbb41b2 100644
--- a/scripts/postinst-intercepts/update_font_cache
+++ b/scripts/postinst-intercepts/update_font_cache
@@ -5,5 +5,7 @@
  
  set -e
  
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D -E ${fontconfigcacheenv} $D${libexecdir}/${binprefix}fc-cache --sysroot=$D --system-only ${fontconfigcacheparams}

-chown -R root:root $D${fontconfigcachedir}
+if [ -f $D${libexecdir}/${binprefix}fc-cache ]; then
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D -E ${fontconfigcacheenv} 
$D${libexecdir}/${binprefix}fc-cache --sysroot=$D --system-only 
${fontconfigcacheparams}
+   chown -R root:root $D${fontconfigcachedir}
+fi
diff --git a/scripts/postinst-intercepts/update_gio_module_cache 
b/scripts/postinst-intercepts/update_gio_module_cache
index c87fa85db9e..e8483cb0bf5 100644
--- a/scripts/postinst-intercepts/update_gio_module_cache
+++ b/scripts/postinst-intercepts/update_gio_module_cache
@@ -5,7 +5,11 @@
  
  set -e
  
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D $D${libexecdir}/${binprefix}gio-querymodules $D${libdir}/gio/modules/

+if [ -f $D${libexecdir}/${binprefix}gio-querymodules ]; then
+
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libexecdir}/${binprefix}gio-querymodules $D${libdir}/gio/modules/
+
+   [ ! -e $D${libdir}/gio/modules/giomodule.cache ] ||
+   chown root:root $D${libdir}/gio/modules/giomodule.cache
+fi
  
-[ ! -e $D${libdir}/gio/modules/giomodule.cache ] ||

-   chown root:root $D${libdir}/gio/modules/giomodule.cache
diff --git a/scripts/postinst-intercepts/update_icon_cache 
b/scripts/postinst-intercepts/update_icon_cache
index 212209a9daf..a67ff7ef970 100644
--- a/scripts/postinst-intercepts/update_icon_cache
+++ b/scripts/postinst-intercepts/update_icon_cache
@@ -5,12 +5,14 @@
  
  set -e
  
-# update native pixbuf loaders

-$STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders 
--update-cache
+if [ -d $STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0 ]; then
+   # update native pixbuf loaders
+   
$STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders 
--update-cache
  
-for icondir in $D/usr/share/icons/*/ ; do

-if [ -d $icondir ] ; then
-gtk-update-icon-cache -fqt  $icondir
-fi
-done
+   for icondir in $D/usr/share/icons/*/ ; do
+   if [ -d $icondir ] ; then
+   gtk-update-icon-cache -fqt  $icondir
+   fi
+   done
+fi
  
diff --git a/scripts/postinst-intercepts/update_pixbuf_cache b/scripts/postinst-intercepts/update_pixbuf_cache

index ea12814474e..166422e5c37 100644
--- a/scripts/postinst-intercepts/update_pixbuf_cache
+++ b/scripts/postinst-intercepts/update_pixbuf_cache
@@ -8,6 +8,9 @@ set -e
  export GDK_PIXBUF_MODULEDIR=$D${libdir}/gdk-pixbuf-2.0/2.10.0/loaders
  export GDK_PIXBUF_FATAL_LOADER=1
  
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D $D${libdir}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders \

+if [ -d $D${libdir}/gdk-pixbuf-2.0 ]; then
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libdir}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders \
  >$GDK_PIXBUF_MODULEDIR/../loaders.cache && \
  sed -i -e "s:$D::g" $GDK_PIXBUF_MODULEDIR/../loaders.cache
+fi
+
diff --git a/scripts/postinst-intercepts/update_udev_hwdb 
b/scripts/postinst-intercepts/update_udev_hwdb
index c4fb2bffcbf..7b6e38338f3 100644
--- a/scripts/postinst-intercepts/update_udev_hwdb
+++ b/scripts/postinst-intercepts/update_udev_hwdb
@@ -5,5 +5,7 @@
  
  set -e
  
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D $D${libexecdir}/${binprefix}udevadm hwdb --update --root $D

-chown root:root $D${sysconfdir}/udev/hwdb.bin
+if [ -d $D/lib/udev/hwdb.d ]; then
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libexecdir}/${binprefix}udevadm hwdb --update --root $D
+   chown root:root $D${sysconfdir}/udev/hwdb.bin
+fi



--
___
Openembedded-core mailing list

[OE-core] [PATCH v1] postinst-intercepts: check tool presence in intercept hooks

[Sinan Kaya]

do_rootfs: The postinstall intercept hook 'update_udev_hwdb'
do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed
do_rootfs: The postinstall intercept hook 'update_icon_cache' failed
do_rootfs: The postinstall intercept hook 'update_icon_cache' failed

Signed-off-by: Sinan Kaya 
---
 scripts/postinst-intercepts/update_font_cache|  6 --
 .../postinst-intercepts/update_gio_module_cache  | 10 +++---
 scripts/postinst-intercepts/update_icon_cache| 16 +---
 scripts/postinst-intercepts/update_pixbuf_cache  |  5 -
 scripts/postinst-intercepts/update_udev_hwdb |  6 --
 5 files changed, 28 insertions(+), 15 deletions(-)

diff --git a/scripts/postinst-intercepts/update_font_cache 
b/scripts/postinst-intercepts/update_font_cache
index 3053c7065f4..954acbb41b2 100644
--- a/scripts/postinst-intercepts/update_font_cache
+++ b/scripts/postinst-intercepts/update_font_cache
@@ -5,5 +5,7 @@
 
 set -e
 
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D -E ${fontconfigcacheenv} 
$D${libexecdir}/${binprefix}fc-cache --sysroot=$D --system-only 
${fontconfigcacheparams}
-chown -R root:root $D${fontconfigcachedir}
+if [ -f $D${libexecdir}/${binprefix}fc-cache ]; then
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D -E ${fontconfigcacheenv} 
$D${libexecdir}/${binprefix}fc-cache --sysroot=$D --system-only 
${fontconfigcacheparams}
+   chown -R root:root $D${fontconfigcachedir}
+fi
diff --git a/scripts/postinst-intercepts/update_gio_module_cache 
b/scripts/postinst-intercepts/update_gio_module_cache
index c87fa85db9e..e8483cb0bf5 100644
--- a/scripts/postinst-intercepts/update_gio_module_cache
+++ b/scripts/postinst-intercepts/update_gio_module_cache
@@ -5,7 +5,11 @@
 
 set -e
 
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libexecdir}/${binprefix}gio-querymodules $D${libdir}/gio/modules/
+if [ -f $D${libexecdir}/${binprefix}gio-querymodules ]; then
+
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libexecdir}/${binprefix}gio-querymodules $D${libdir}/gio/modules/
+
+   [ ! -e $D${libdir}/gio/modules/giomodule.cache ] ||
+   chown root:root $D${libdir}/gio/modules/giomodule.cache
+fi
 
-[ ! -e $D${libdir}/gio/modules/giomodule.cache ] ||
-   chown root:root $D${libdir}/gio/modules/giomodule.cache
diff --git a/scripts/postinst-intercepts/update_icon_cache 
b/scripts/postinst-intercepts/update_icon_cache
index 212209a9daf..a67ff7ef970 100644
--- a/scripts/postinst-intercepts/update_icon_cache
+++ b/scripts/postinst-intercepts/update_icon_cache
@@ -5,12 +5,14 @@
 
 set -e
 
-# update native pixbuf loaders
-$STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders 
--update-cache
+if [ -d $STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0 ]; then
+   # update native pixbuf loaders
+   
$STAGING_DIR_NATIVE/${libdir_native}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders 
--update-cache
 
-for icondir in $D/usr/share/icons/*/ ; do
-if [ -d $icondir ] ; then
-gtk-update-icon-cache -fqt  $icondir
-fi
-done
+   for icondir in $D/usr/share/icons/*/ ; do
+   if [ -d $icondir ] ; then
+   gtk-update-icon-cache -fqt  $icondir
+   fi
+   done
+fi
 
diff --git a/scripts/postinst-intercepts/update_pixbuf_cache 
b/scripts/postinst-intercepts/update_pixbuf_cache
index ea12814474e..166422e5c37 100644
--- a/scripts/postinst-intercepts/update_pixbuf_cache
+++ b/scripts/postinst-intercepts/update_pixbuf_cache
@@ -8,6 +8,9 @@ set -e
 export GDK_PIXBUF_MODULEDIR=$D${libdir}/gdk-pixbuf-2.0/2.10.0/loaders
 export GDK_PIXBUF_FATAL_LOADER=1
 
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libdir}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders \
+if [ -d $D${libdir}/gdk-pixbuf-2.0 ]; then
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libdir}/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders \
 >$GDK_PIXBUF_MODULEDIR/../loaders.cache && \
 sed -i -e "s:$D::g" $GDK_PIXBUF_MODULEDIR/../loaders.cache
+fi
+
diff --git a/scripts/postinst-intercepts/update_udev_hwdb 
b/scripts/postinst-intercepts/update_udev_hwdb
index c4fb2bffcbf..7b6e38338f3 100644
--- a/scripts/postinst-intercepts/update_udev_hwdb
+++ b/scripts/postinst-intercepts/update_udev_hwdb
@@ -5,5 +5,7 @@
 
 set -e
 
-PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libexecdir}/${binprefix}udevadm hwdb --update --root $D
-chown root:root $D${sysconfdir}/udev/hwdb.bin
+if [ -d $D/lib/udev/hwdb.d ]; then
+   PSEUDO_UNLOAD=1 ${binprefix}qemuwrapper -L $D 
$D${libexecdir}/${binprefix}udevadm hwdb --update --root $D
+   chown root:root $D${sysconfdir}/udev/hwdb.bin
+fi
-- 
2.21.0

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

Re: [OE-core] [yocto] Yocto Project Status WW26'19

[akuster808]

On 6/25/19 10:22 AM, sjolley.yp...@gmail.com wrote:
>
> Current Dev Position: YP 2.8 M2
>
> Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019
>
>  
>
> SWAT Team Rotation:
>
>   * SWAT lead is currently: Ross
>   * SWAT team rotation: Ross -> Amanda on June 28, 2019
>   * SWAT team rotation: Amanda -> Chen on July, 5, 2019
>
So how do we handle holiday coverage? July 4th is a US holiday.

- armin
>
>  *
>   * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>  
>
> Next Team Meetings:
>
>   * Bug Triage meeting Thursday June 27th at 7:30am PDT
> (https://zoom.us/j/454367603)
>   * Monthly Project Meeting Tuesday July 2nd at 8am PDT
> (https://zoom.us/j/990892712)  
>   * Twitch - Next event is Tuesday 9th July at 8am PDT
> (https://www.twitch.tv/yocto_project)
>
>  
>
> Key Status/Updates:
>
>   * 2.8 M1 has been released.
>   * Mailing lists issues are continuing to be worked on as a top priority.
>   * We have a new “newcomer” bug category which are bugs suited to
> someone new to the project. These can be seen here:
> https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
>   * Several key reproducibility fixes have merged, thanks Joshua!
>   * The autobuilder has suffered stability issues with its NFS setup,
> seemingly related to the increased load from the new servers.
> We’re monitoring changes, hoping they fix the issue.
>   * We had significant problems with the versioning of libcrypt in
> recent distros which resulted in the need for a new uninative
> release. This fixes autobuilder builds.
>
>  
>
> Planned Releases for YP 2.8:
>
>   * M2 Cutoff 14th July
>   * M2 Release 26th July
>   * M3 Cutoff (Feature Freeze) 25th Aug
>   * M3 Release 6th Sept
>   * M4 Cutoff 30th Sept
>   * 2.8 (M4) Final Release 25th Oct
>
>  
>
> Planned upcoming dot releases:
>
>   * YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1
> is done but is pending the new uninative changes.
>   * YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
> before 2.8 M2
>
>  
>
> Tracking Metrics:
>
>   * WDD 2482 (last week
> 2479)(https://wiki.yoctoproject.org/charts/combo.html)
>   * Poky Patch Metrics  
>   o Total patches found: 1509 (last week 1511)
>   o Patches in the Pending State: 638 (42%) [last week 641 (43%)]
>
>  
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features
>
>  
>
> The Status reports are now stored on the wiki at:
> https://wiki.yoctoproject.org/wiki/Weekly_Status
>
>  
>
> [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 Project Manager*
>
> (    *Cell*:    (208) 244-4460
>
> * *Email*:  _sjolley.yp...@gmail.com
> _
>
>  
>
>

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

Re: [OE-core] [PATCH] libnotify: Remove obsolete dependency on dbus-glib

[Adrian Bunk]

On Tue, Jun 25, 2019 at 02:09:02PM -0400, Randy MacLeod wrote:
> On 6/25/19 1:26 PM, Adrian Bunk wrote:
> > Upstream stopped using it in 2010.
> > 
> > Signed-off-by: Adrian Bunk 
> > ---
> >   meta/recipes-gnome/libnotify/libnotify_0.7.8.bb | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb 
> > b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
> > index 82c137ca33..1c9084d919 100644
> > --- a/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
> > +++ b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
> > @@ -4,7 +4,7 @@ SECTION = "libs"
> >   LICENSE = "LGPLv2.1"
> >   LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
> > -DEPENDS = "dbus gtk+3 dbus-glib"
> > +DEPENDS = "dbus gtk+3 glib-2.0"
> >   inherit gnomebase gtk-doc distro_features_check gobject-introspection
> >   # depends on gtk+3
> > 
> 
> Nice.
> 
> Are you doing a manual inspection and analysis or
> something more automated that you can share as a script/workflow?

Manual.

I was curious what it would take to remove dbus-glib from oe-core.
This doesn't seem to be easy right now, but these were some trivial 
cases where all that was needed was to remove the dependency.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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

Re: [OE-core] [PATCH] libnotify: Remove obsolete dependency on dbus-glib

[Randy MacLeod]

On 6/25/19 1:26 PM, Adrian Bunk wrote:

Upstream stopped using it in 2010.

Signed-off-by: Adrian Bunk 
---
  meta/recipes-gnome/libnotify/libnotify_0.7.8.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb 
b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
index 82c137ca33..1c9084d919 100644
--- a/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
+++ b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
@@ -4,7 +4,7 @@ SECTION = "libs"
  LICENSE = "LGPLv2.1"
  LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
  
-DEPENDS = "dbus gtk+3 dbus-glib"

+DEPENDS = "dbus gtk+3 glib-2.0"
  
  inherit gnomebase gtk-doc distro_features_check gobject-introspection

  # depends on gtk+3



Nice.

Are you doing a manual inspection and analysis or
something more automated that you can share as a script/workflow?

--
# Randy MacLeod
# Wind River Linux
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] mesa: Add support for the lima PACKAGECONFIG

[Alistair Francis]

Signed-off-by: Alistair Francis 
---
 meta/recipes-graphics/mesa/mesa.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-graphics/mesa/mesa.inc 
b/meta/recipes-graphics/mesa/mesa.inc
index 3ecfb8506c..5bbd13bca2 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -113,6 +113,9 @@ PACKAGECONFIG[gallium-llvm] = "-Dllvm=true 
-Dshared-llvm=true, -Dllvm=false, llv
 export WANT_LLVM_RELEASE = "${MESA_LLVM_RELEASE}"
 PACKAGECONFIG[xa]  = "-Dgallium-xa=true, -Dgallium-xa=false"
 
+PACKAGECONFIG[lima] = ""
+GALLIUMDRIVERS_append ="${@bb.utils.contains('PACKAGECONFIG', 'lima', ',lima', 
'', d)}"
+
 OSMESA = "${@bb.utils.contains('PACKAGECONFIG', 'gallium', 'gallium', 
'classic', d)}"
 PACKAGECONFIG[osmesa] = "-Dosmesa=${OSMESA},-Dosmesa=none"
 
-- 
2.21.0

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

[OE-core] [PATCH] libnotify: Remove obsolete dependency on dbus-glib

[Adrian Bunk]

Upstream stopped using it in 2010.

Signed-off-by: Adrian Bunk 
---
 meta/recipes-gnome/libnotify/libnotify_0.7.8.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb 
b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
index 82c137ca33..1c9084d919 100644
--- a/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
+++ b/meta/recipes-gnome/libnotify/libnotify_0.7.8.bb
@@ -4,7 +4,7 @@ SECTION = "libs"
 LICENSE = "LGPLv2.1"
 LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34"
 
-DEPENDS = "dbus gtk+3 dbus-glib"
+DEPENDS = "dbus gtk+3 glib-2.0"
 
 inherit gnomebase gtk-doc distro_features_check gobject-introspection
 # depends on gtk+3
-- 
2.17.1

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

[OE-core] [PATCH] cups: Remove unnecessary dependency on dbus-glib

[Adrian Bunk]

Signed-off-by: Adrian Bunk 
---
 meta/recipes-extended/cups/cups.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-extended/cups/cups.inc 
b/meta/recipes-extended/cups/cups.inc
index 5010f0861f..46fb2dded3 100644
--- a/meta/recipes-extended/cups/cups.inc
+++ b/meta/recipes-extended/cups/cups.inc
@@ -2,7 +2,7 @@ SUMMARY = "An Internet printing system for Unix"
 HOMEPAGE = "https://www.cups.org/;
 SECTION = "console/utils"
 LICENSE = "GPLv2 & LGPLv2"
-DEPENDS = "gnutls libpng jpeg dbus dbus-glib zlib libusb1"
+DEPENDS = "gnutls libpng jpeg dbus zlib libusb1"
 
 SRC_URI = 
"https://github.com/apple/cups/releases/download/v${PV}/${BP}-source.tar.gz \
file://use_echo_only_in_init.patch \
-- 
2.17.1

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

[OE-core] [PATCH] python3-dbus: Remove obsolete dependency on dbus-glib

[Adrian Bunk]

Upstream stopped using it in 1.2.6.

Signed-off-by: Adrian Bunk 
---
 meta/recipes-devtools/python/python3-dbus_1.2.8.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python3-dbus_1.2.8.bb 
b/meta/recipes-devtools/python/python3-dbus_1.2.8.bb
index c9bf8df42d..923da3c00a 100644
--- a/meta/recipes-devtools/python/python3-dbus_1.2.8.bb
+++ b/meta/recipes-devtools/python/python3-dbus_1.2.8.bb
@@ -3,7 +3,7 @@ SECTION = "devel/python"
 HOMEPAGE = "http://www.freedesktop.org/Software/dbus;
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b03240518994df6d8c974675675e5ca4"
-DEPENDS = "expat dbus dbus-glib virtual/libintl"
+DEPENDS = "expat dbus glib-2.0 virtual/libintl"
 
 SRC_URI = 
"http://dbus.freedesktop.org/releases/dbus-python/dbus-python-${PV}.tar.gz \
 "
-- 
2.17.1

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

[OE-core] [PATCH] bluez5: Remove obsolete dependency on dbus-glib

[Adrian Bunk]

Upstream stopped using it in 2008.

Signed-off-by: Adrian Bunk 
---
 meta/recipes-connectivity/bluez5/bluez5.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/bluez5/bluez5.inc 
b/meta/recipes-connectivity/bluez5/bluez5.inc
index 8f321638ce..28aaeea418 100644
--- a/meta/recipes-connectivity/bluez5/bluez5.inc
+++ b/meta/recipes-connectivity/bluez5/bluez5.inc
@@ -6,7 +6,7 @@ LICENSE = "GPLv2+ & LGPLv2.1+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=12f884d2ae1ff87c09e5b7ccc2c4ca7e \
 file://COPYING.LIB;md5=fb504b67c50331fc78734fed90fb0e09 \
 
file://src/main.c;beginline=1;endline=24;md5=9bc54b93cd7e17bf03f52513f39f926e"
-DEPENDS = "dbus-glib glib-2.0"
+DEPENDS = "dbus glib-2.0"
 PROVIDES += "bluez-hcidump"
 RPROVIDES_${PN} += "bluez-hcidump"
 
-- 
2.17.1

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

[OE-core] Yocto Project Status WW26'19

[sjolley.yp.pm]

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Ross
*   SWAT team rotation: Ross -> Amanda on June 28, 2019
*   SWAT team rotation: Amanda -> Chen on July, 5, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday June 27th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 2nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday 9th July at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   2.8 M1 has been released.
*   Mailing lists issues are continuing to be worked on as a top
priority.
*   We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*   Several key reproducibility fixes have merged, thanks Joshua!
*   The autobuilder has suffered stability issues with its NFS setup,
seemingly related to the increased load from the new servers. We're
monitoring changes, hoping they fix the issue.
*   We had significant problems with the versioning of libcrypt in
recent distros which resulted in the need for a new uninative release. This
fixes autobuilder builds.

 

Planned Releases for YP 2.8:

*   M2 Cutoff 14th July
*   M2 Release 26th July
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept
*   2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1
is done but is pending the new uninative changes.
*   YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

*   WDD 2482 (last week 2479) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1509 (last week 1511)
*   Patches in the Pending State: 638 (42%) [last week 641 (43%)]

 

Key Status Links for YP:

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

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

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

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[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 Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

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

[OE-core] [PATCH] mesa: Update 19.1.0 -> 19.1.1

[Fabio Berton]

Mesa 19.1.1 is a bug fix release which fixes bugs found since the
19.1.0 release.

For a complete changelog see:
https://www.mesa3d.org/relnotes/19.1.1.html

Signed-off-by: Fabio Berton 
---
 .../mesa/{mesa-gl_19.1.0.bb => mesa-gl_19.1.1.bb} | 0
 meta/recipes-graphics/mesa/{mesa_19.1.0.bb => mesa_19.1.1.bb} | 4 ++--
 2 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/mesa/{mesa-gl_19.1.0.bb => mesa-gl_19.1.1.bb} 
(100%)
 rename meta/recipes-graphics/mesa/{mesa_19.1.0.bb => mesa_19.1.1.bb} (84%)

diff --git a/meta/recipes-graphics/mesa/mesa-gl_19.1.0.bb 
b/meta/recipes-graphics/mesa/mesa-gl_19.1.1.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_19.1.0.bb
rename to meta/recipes-graphics/mesa/mesa-gl_19.1.1.bb
diff --git a/meta/recipes-graphics/mesa/mesa_19.1.0.bb 
b/meta/recipes-graphics/mesa/mesa_19.1.1.bb
similarity index 84%
rename from meta/recipes-graphics/mesa/mesa_19.1.0.bb
rename to meta/recipes-graphics/mesa/mesa_19.1.1.bb
index 05c315349c..1a34a6577b 100644
--- a/meta/recipes-graphics/mesa/mesa_19.1.0.bb
+++ b/meta/recipes-graphics/mesa/mesa_19.1.1.bb
@@ -6,8 +6,8 @@ SRC_URI = 
"https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
file://0003-Allow-enable-DRI-without-DRI-drivers.patch \
"
 
-SRC_URI[md5sum] = "090cd351cf938fc1729dee983520216a"
-SRC_URI[sha256sum] = 
"2a6c3af3a803389183168e449c536304cf03e0f82c4c9333077933543b9d02f3"
+SRC_URI[md5sum] = "07cd8cd79de28ec1a374ee3a06e47789"
+SRC_URI[sha256sum] = 
"72114b16b4a84373b2acda060fe2bb1d45ea2598efab3ef2d44bdeda74f15581"
 
 #because we cannot rely on the fact that all apps will use pkgconfig,
 #make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
-- 
2.20.1

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

[OE-core] [PATCH v4] oe_syslog.py: Handle syslogd/klogd restart race

[Jon Mason]

syslogd and klogd can occasionally take too long to restart, which
causes tests to fail by starting before the log daemons are ready.  To
work around this problem, poll for up to 30 seconds on the processes to
verify the old ones are killed and the new ones are up and running.
Similarly, add checks for rsyslogd and systemd-journald to possibly
catch issues with those daemons.

[YOCTO #13379]

Signed-off-by: Jon Mason 
---
 meta/lib/oeqa/runtime/cases/oe_syslog.py | 68 
 1 file changed, 59 insertions(+), 9 deletions(-)

diff --git a/meta/lib/oeqa/runtime/cases/oe_syslog.py 
b/meta/lib/oeqa/runtime/cases/oe_syslog.py
index 0f5f9f43ca..0f79e5a0f3 100644
--- a/meta/lib/oeqa/runtime/cases/oe_syslog.py
+++ b/meta/lib/oeqa/runtime/cases/oe_syslog.py
@@ -6,6 +6,7 @@ from oeqa.runtime.case import OERuntimeTestCase
 from oeqa.core.decorator.depends import OETestDepends
 from oeqa.core.decorator.data import skipIfDataVar
 from oeqa.runtime.decorator.package import OEHasPackage
+import time
 
 class SyslogTest(OERuntimeTestCase):
 
@@ -21,6 +22,53 @@ class SyslogTest(OERuntimeTestCase):
 
 class SyslogTestConfig(OERuntimeTestCase):
 
+def verif_not_running(self, pids):
+for pid in pids:
+status, err_output = self.target.run('kill -0 %s' %pid)
+if not status:
+self.logger.debug("previous %s is still running" %pid)
+return 1
+
+def verify_running(self, names):
+pids = []
+for name in names:
+status, pid = self.target.run('pidof %s' %name)
+if status:
+self.logger.debug("%s is not running" %name)
+return 1, pids
+pids.append(pid)
+return 0, pids
+
+
+def restart_sanity(self, names, restart_cmd):
+status, original_pids = self.verify_running(names)
+if status:
+return 1
+
+status, output = self.target.run(restart_cmd)
+
+# Always check for an error, most likely a race between shutting down 
and starting up
+timeout = time.time() + 30
+
+while time.time() < timeout:
+# Verify the previous ones are no longer running
+status = self.verif_not_running(original_pids)
+if status:
+continue
+
+status, pids = self.verify_running(names)
+if status:
+continue
+
+# Everything is fine now, so exit to continue the test
+status = 0
+break
+
+msg = ('Could not restart %s service. Status and output: %s and %s'
+   %(names, status, output))
+self.assertEqual(status, 0, msg)
+
+
 @OETestDepends(['oe_syslog.SyslogTest.test_syslog_running'])
 def test_syslog_logger(self):
 status, output = self.target.run('logger foobar')
@@ -37,12 +85,16 @@ class SyslogTestConfig(OERuntimeTestCase):
' Output: %s ' % output)
 self.assertEqual(status, 0, msg=msg)
 
+
 @OETestDepends(['oe_syslog.SyslogTest.test_syslog_running'])
 def test_syslog_restart(self):
-if "systemd" != self.tc.td.get("VIRTUAL-RUNTIME_init_manager", ""):
-(_, _) = self.target.run('/etc/init.d/syslog restart')
-else:
-(_, _) = self.target.run('systemctl restart syslog.service')
+status = self.restart_sanity(['systemd-journald'], 'systemctl restart 
syslog.service')
+if status:
+status = self.restart_sanity(['rsyslogd'], '/etc/init.d/rsyslog 
restart')
+if status:
+status = self.restart_sanity(['syslogd', 'klogd'], 
'/etc/init.d/syslog restart')
+else:
+self.logger.info("No syslog found to restart, ignoring")
 
 
 @OETestDepends(['oe_syslog.SyslogTestConfig.test_syslog_logger'])
@@ -52,10 +104,8 @@ class SyslogTestConfig(OERuntimeTestCase):
 def test_syslog_startup_config(self):
 cmd = 'echo "LOGFILE=/var/log/test" >> /etc/syslog-startup.conf'
 self.target.run(cmd)
-status, output = self.target.run('/etc/init.d/syslog restart')
-msg = ('Could not restart syslog service. Status and output:'
-   ' %s and %s' % (status,output))
-self.assertEqual(status, 0, msg)
+
+self.test_syslog_restart()
 
 cmd = 'logger foobar && grep foobar /var/log/test'
 status,output = self.target.run(cmd)
@@ -64,4 +114,4 @@ class SyslogTestConfig(OERuntimeTestCase):
 
 cmd = "sed -i 's#LOGFILE=/var/log/test##' /etc/syslog-startup.conf"
 self.target.run(cmd)
-self.target.run('/etc/init.d/syslog restart')
+self.test_syslog_restart()
-- 
2.21.0

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

[OE-core] [PATCH v2 2/2] oeqa/buildoptions: check that Fortran code actually cross-compiles

[Ross Burton]

Don't just test that we can build the cross-compiler, but test that it actually
can cross-compile some Fortran.

The quadmath dependency is now handled in gcc-runtime and isn't needed in this
test (as per local.conf.sample.extended changes).

There's also no need to build libgfortran explicitly, as fortran-helloworld 
depends on it.

Signed-off-by: Ross Burton 
---
 meta/lib/oeqa/selftest/cases/buildoptions.py | 7 ++-
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/buildoptions.py 
b/meta/lib/oeqa/selftest/cases/buildoptions.py
index 3ad65b40341..6a5378d3ff6 100644
--- a/meta/lib/oeqa/selftest/cases/buildoptions.py
+++ b/meta/lib/oeqa/selftest/cases/buildoptions.py
@@ -162,17 +162,14 @@ class ArchiverTest(OESelftestTestCase):
 self.assertTrue((g.glob(src_file_glob) and g.glob(tar_file_glob)), 
"Couldn't find .src.rpm and .tar.gz files under %s/allarch*/xcursor*" % 
deploy_dir_src)
 
 class ToolchainOptions(OESelftestTestCase):
-
 def test_toolchain_fortran(self):
 """
-Test whether we can enable and build fortran and its supporting 
libraries
+Test that Fortran works by building a Hello, World binary.
 """
 
 features = 'FORTRAN_forcevariable = ",fortran"\n'
-features += 'RUNTIMETARGET_append_pn-gcc-runtime = " libquadmath"\n'
 self.write_config(features)
-
-bitbake('gcc-runtime libgfortran')
+bitbake('fortran-helloworld')
 
 class SourceMirroring(OESelftestTestCase):
 # Can we download everything from the Yocto Sources Mirror over http only
-- 
2.11.0

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

[OE-core] [PATCH v2 1/2] fortran-helloworld: add a very dumb Fortran Hello World for testing

[Ross Burton]

For future runtime testing something more complex is preferred but this is
sufficient to exercise the cross compiler.

Signed-off-by: Ross Burton 
---
 meta-selftest/recipes-test/fortran/files/hello.f95 |  5 +
 .../recipes-test/fortran/fortran-helloworld.bb | 25 ++
 2 files changed, 30 insertions(+)
 create mode 100644 meta-selftest/recipes-test/fortran/files/hello.f95
 create mode 100644 meta-selftest/recipes-test/fortran/fortran-helloworld.bb

diff --git a/meta-selftest/recipes-test/fortran/files/hello.f95 
b/meta-selftest/recipes-test/fortran/files/hello.f95
new file mode 100644
index 000..a0745fc64d7
--- /dev/null
+++ b/meta-selftest/recipes-test/fortran/files/hello.f95
@@ -0,0 +1,5 @@
+program helloworld
+
+  print * , "Hello World!"
+
+end program helloworld
diff --git a/meta-selftest/recipes-test/fortran/fortran-helloworld.bb 
b/meta-selftest/recipes-test/fortran/fortran-helloworld.bb
new file mode 100644
index 000..97313d7e249
--- /dev/null
+++ b/meta-selftest/recipes-test/fortran/fortran-helloworld.bb
@@ -0,0 +1,25 @@
+SUMMARY = "Fortran Hello World"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+
+DEPENDS = "libgfortran"
+
+SRC_URI = "file://hello.f95"
+
+# These set flags that Fortran doesn't support
+SECURITY_CFLAGS = ""
+SECURITY_LDFLAGS = ""
+
+do_compile() {
+   ${HOST_PREFIX}gfortran ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS} ${LDFLAGS} 
${WORKDIR}/hello.f95 -o ${B}/fortran-hello
+}
+
+do_install() {
+   install -d ${D}${bindir}
+   install ${B}/fortran-hello ${D}${bindir}
+}
+
+python () {
+if not d.getVar("FORTRAN"):
+raise bb.parse.SkipRecipe("Fortran isn't enabled")
+}
\ No newline at end of file
-- 
2.11.0

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

Re: [OE-core] [PATCH v2 1/2] update-alternatives.bbclass: run update-alternatives firstly in postinst script

[Richard Purdie]

On Tue, 2019-06-25 at 20:44 +0800, Robert Yang wrote:
> Recipes like postfix run command newaliases in postinst, but newaliases is
> installed as newaliases.postfix, it needs run update-alternatives to update it
> to newaliases, so there was an error when installed postinst on target.
> 
> Fixed:
> $ opkg install postfix
> Configuring postfix.
> ///var/lib/opkg/info/postfix.postinst: line 4: newaliases: command not found
> 
> Run update-alternatives firstly will fix the problem. And handle busybox as an
> exception since it needs set basic tools such as sed command firstly, 
> otherwise
> update-alternatives doesn't work.
> 
> Signed-off-by: Robert Yang 
> ---
>  meta/classes/update-alternatives.bbclass | 13 +++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/update-alternatives.bbclass 
> b/meta/classes/update-alternatives.bbclass
> index b702e77..9ab9298 100644
> --- a/meta/classes/update-alternatives.bbclass
> +++ b/meta/classes/update-alternatives.bbclass
> @@ -265,6 +265,7 @@ python populate_packages_updatealternatives () {
>  if not update_alternatives_enabled(d):
>  return
>  
> +bpn = d.getVar('BPN')
>  # Do actual update alternatives processing
>  for pkg in (d.getVar('PACKAGES') or "").split():
>  # Create post install/removal scripts
> @@ -284,8 +285,16 @@ python populate_packages_updatealternatives () {
>  
>  bb.note('adding update-alternatives calls to postinst/prerm for 
> %s' % pkg)
>  bb.note('%s' % alt_setup_links)
> -postinst = d.getVar('pkg_postinst_%s' % pkg) or '#!/bin/sh\n'
> -postinst += alt_setup_links
> +postinst = d.getVar('pkg_postinst_%s' % pkg)
> +if postinst:
> +# Busybox needs handle basic tools such as sed command
> +# firstly, otherwise, update-alternatives doesn't work.
> +if bpn == 'busybox':
> +postinst += alt_setup_links
> +else:
> +postinst = alt_setup_links + postinst
> +else:
> +postinst = '#!/bin/sh\n' + alt_setup_links
>  d.setVar('pkg_postinst_%s' % pkg, postinst)
>  
>  bb.note('%s' % alt_remove_links)

We don't write classes like this. We could just keep piling special
cases one on top of the other and it becomes a horrible unmaintainable
mess. I therefore don't want to see recipes "special cased" like this
in core code and we need to find another, better way to handle this.

Cheers,

Richard



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

[OE-core] [PATCH] bitbake.conf: Stop exporting TARGET_ flags variables

[Mike Crowe]

Way back in
http://lists.openembedded.org/pipermail/openembedded-core/2014-April/210138.html
a few of us discussed not exporting TARGET_LDFLAGS. There seemed to be
support for this idea, and I modified our tree to not do so. I then seem to
have dropped the ball. :( We've been running like that for over five years,
and not observed any problems.

It seems sensible to stop exporting TARGET_CPPFLAGS, TARGET_CFLAGS and
TARGET_CXXFLAGS too.

I've successfully compile-tested core-image-minimal and core-image-sato for
x86_64 and qemuarm64 with these changes.

Signed-off-by: Mike Crowe 
---
 meta/conf/bitbake.conf | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 4b907d6820..5e93f5c223 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -569,17 +569,17 @@ PATCHRESOLVE = "noop"
 export BUILD_CPPFLAGS = "-isystem${STAGING_INCDIR_NATIVE}"
 BUILDSDK_CPPFLAGS = ""
 export CPPFLAGS = "${TARGET_CPPFLAGS}"
-export TARGET_CPPFLAGS = ""
+TARGET_CPPFLAGS = ""
 
 export BUILD_CFLAGS = "${BUILD_CPPFLAGS} ${BUILD_OPTIMIZATION}"
 BUILDSDK_CFLAGS = "${BUILDSDK_CPPFLAGS} ${BUILD_OPTIMIZATION} 
${DEBUG_PREFIX_MAP}"
 export CFLAGS = "${TARGET_CFLAGS}"
-export TARGET_CFLAGS = "${TARGET_CPPFLAGS} ${SELECTED_OPTIMIZATION}"
+TARGET_CFLAGS = "${TARGET_CPPFLAGS} ${SELECTED_OPTIMIZATION}"
 
 export BUILD_CXXFLAGS = "${BUILD_CFLAGS}"
 BUILDSDK_CXXFLAGS = "${BUILDSDK_CFLAGS}"
 export CXXFLAGS = "${TARGET_CXXFLAGS}"
-export TARGET_CXXFLAGS = "${TARGET_CFLAGS}"
+TARGET_CXXFLAGS = "${TARGET_CFLAGS}"
 
 export BUILD_LDFLAGS = "-L${STAGING_LIBDIR_NATIVE} \
 -L${STAGING_BASE_LIBDIR_NATIVE} \
@@ -601,7 +601,7 @@ TARGET_LINK_HASH_STYLE ?= 
"${@['-Wl,--hash-style=gnu',''][d.getVar('LINKER_HASH_
 ASNEEDED ?= "-Wl,--as-needed"
 
 export LDFLAGS = "${TARGET_LDFLAGS}"
-export TARGET_LDFLAGS = "-Wl,-O1 ${TARGET_LINK_HASH_STYLE} ${ASNEEDED}"
+TARGET_LDFLAGS = "-Wl,-O1 ${TARGET_LINK_HASH_STYLE} ${ASNEEDED}"
 
 # Pass parallel make options to the compile task
 EXTRA_OEMAKE_prepend_task-compile = "${PARALLEL_MAKE} "
-- 
2.20.1

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

Re: [OE-core] [PATCH 1/4] cve-update-db: New recipe to update CVE database

[Burton, Ross]

On Tue, 25 Jun 2019 at 09:49, Pierre Le Magourou  wrote:
> > Also, the CVE db is updated using this custom task without link to
> > do_fetch, which means a fetchall task would not update the database for
> > off line NO_NETWORK builds.
> >
> > Could the task be added as dependency to do_fetch() or are there some other
> > side effects?
> >
>
> Yes I can do that, I don't think this will cause side effects.

Oh, you'll also want to set the proxies appropriately.

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

Re: [OE-core] [PATCHv3] cmake.bbclass: pass mandatory compiler flags through CMAKE__COMPILER_ARG1

[Nikolai Merinov via Openembedded-core]

Hi Richard,

Can you help me to understand how I can reproduce this issue on local build? I 
want to try to debug it.

Regards,
Nikolai

- Original Message -
From: "Richard Purdie" 
To: "n merinov" 
Cc: "openembedded-core" 
Sent: Tuesday, June 25, 2019 1:03:11 PM
Subject: Re: [OE-core] [PATCHv3] cmake.bbclass: pass mandatory compiler flags 
through CMAKE__COMPILER_ARG1

On Mon, 2019-06-24 at 13:24 +0300, Nikolai Merinov via Openembedded-
core wrote:
> Patch updated with "Signed-off-by" field as required by automatic
> checks.
> 
> - Original Message -
> From: "openembedded-core" 
> To: "Khem Raj" 
> Cc: "openembedded-core" 
> Sent: Thursday, June 20, 2019 7:16:07 PM
> Subject: [OE-core] [PATCHv2] cmake.bbclass: pass mandatory compiler
> flags through CMAKE__COMPILER_ARG1
> 
> Hi,
> 
> Updated patch for the current "master" branch is attached.
> 
> > have you also tried building SDK and see if these changes are
> > reflected in SDK as well ?
> 
> I checked that the changes reflected in the Extensible SDK for the
> "core-image-sato" image of the poky.
> 
> Regards,
> Nikolai
> 
> - Original Message -
> From: "Khem Raj" 
> To: "n merinov" , "openembedded-core" <
> openembedded-core@lists.openembedded.org>
> Sent: Tuesday, May 21, 2019 1:41:46 AM
> Subject: Re: [OE-core] [PATCH] cmake.bbclass: pass mandatory compiler
> flags through CMAKE__COMPILER_ARG1
> 
> On 5/14/19 8:04 AM, Nikolai Merinov wrote:
> > The CMake takes mandatory compiler arguments from the following
> > variables:
> > - CMAKE_SYSROOT -- path to sysroot that should be passed to
> > compiler.
> > - CMAKE__COMPILER_TARGET -- target architecture, used for
> > compilers
> >that supports several targets through command line options.
> >e.g. "clang --target ${CMAKE_C_COMPILER_TARGET}".
> > - CMAKE__COMPILER_EXTERNAL_TOOLCHAIN -- path to external
> > toolchain,
> >used for compilers that support build with external toolchain.
> >e.g. "clang --gcc-toolchain
> > ${CMAKE_C_COMPILER_EXTERNAL_TOOLCHAIN}".
> > - CMAKE__COMPILER_ARG1 -- other mandatory arguments to a
> > compiler
> >command.
> > 
> > CMAKE__COMPILER_ARG1 is the most suitable variable to pass
> > mandatory
> > arguments, that belongs to CC variable with other build systems, to
> > a
> > compiler.
> > 
> > Additionally usage of CMAKE__COMPILER_ARG1 instead of
> > CMAKE__FLAGS reduce the risk that a variable can be overrided
> > by
> > CMakeLists.txt files.
> 
I'm afraid this caused a number of build failures and selftest issues:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/236

(most of the selftest failures there for example are from this, as is 
https://autobuilder.yoctoproject.org/typhoon/#/builders/69/builds/746/steps/7/logs/step7b
)

Cheers,

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

[OE-core] [PATCH][thud 2/2] glibc: backport CVE fixes

[Ross Burton]

Backport the fixes for several CVEs from the 2.28 stable branch:
- CVE-2016-10739
- CVE-2018-19591
- CVE-2019-9169

Signed-off-by: Ross Burton 
---
 meta/recipes-core/glibc/glibc/CVE-2016-10739.patch | 232 +
 meta/recipes-core/glibc/glibc/CVE-2018-19591.patch |  48 +
 meta/recipes-core/glibc/glibc/CVE-2019-9169.patch  |  40 
 meta/recipes-core/glibc/glibc_2.28.bb  |   4 +-
 4 files changed, 323 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2016-10739.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2018-19591.patch
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2019-9169.patch

diff --git a/meta/recipes-core/glibc/glibc/CVE-2016-10739.patch 
b/meta/recipes-core/glibc/glibc/CVE-2016-10739.patch
new file mode 100644
index 000..7eb55d6663d
--- /dev/null
+++ b/meta/recipes-core/glibc/glibc/CVE-2016-10739.patch
@@ -0,0 +1,232 @@
+CVE: CVE-2016-10739
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+From 8e92ca5dd7a7e38a4dddf1ebc4e1e8f0cb27e4aa Mon Sep 17 00:00:00 2001
+From: Florian Weimer 
+Date: Mon, 21 Jan 2019 08:59:42 +0100
+Subject: [PATCH] resolv: Reformat inet_addr, inet_aton to GNU style
+
+(cherry picked from commit 5e30b8ef0758763effa115634e0ed7d8938e4bc0)
+---
+ ChangeLog  |   5 ++
+ resolv/inet_addr.c | 192 -
+ 2 files changed, 106 insertions(+), 91 deletions(-)
+
+diff --git a/resolv/inet_addr.c b/resolv/inet_addr.c
+index 022f7ea084..32f58b0e13 100644
+--- a/resolv/inet_addr.c
 b/resolv/inet_addr.c
+@@ -1,3 +1,21 @@
++/* Legacy IPv4 text-to-address functions.
++   Copyright (C) 2019 Free Software Foundation, Inc.
++   This file is part of the GNU C Library.
++
++   The GNU C Library is free software; you can redistribute it and/or
++   modify it under the terms of the GNU Lesser General Public
++   License as published by the Free Software Foundation; either
++   version 2.1 of the License, or (at your option) any later version.
++
++   The GNU C Library is distributed in the hope that it will be useful,
++   but WITHOUT ANY WARRANTY; without even the implied warranty of
++   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
++   Lesser General Public License for more details.
++
++   You should have received a copy of the GNU Lesser General Public
++   License along with the GNU C Library; if not, see
++   .  */
++
+ /*
+  * Copyright (c) 1983, 1990, 1993
+  *The Regents of the University of California.  All rights reserved.
+@@ -78,105 +96,97 @@
+ #include 
+ #include 
+ 
+-/*
+- * Ascii internet address interpretation routine.
+- * The value returned is in network order.
+- */
++/* ASCII IPv4 Internet address interpretation routine.  The value
++   returned is in network order.  */
+ in_addr_t
+-__inet_addr(const char *cp) {
+-  struct in_addr val;
++__inet_addr (const char *cp)
++{
++  struct in_addr val;
+ 
+-  if (__inet_aton(cp, ))
+-  return (val.s_addr);
+-  return (INADDR_NONE);
++  if (__inet_aton (cp, ))
++return val.s_addr;
++  return INADDR_NONE;
+ }
+ weak_alias (__inet_addr, inet_addr)
+ 
+-/*
+- * Check whether "cp" is a valid ascii representation
+- * of an Internet address and convert to a binary address.
+- * Returns 1 if the address is valid, 0 if not.
+- * This replaces inet_addr, the return value from which
+- * cannot distinguish between failure and a local broadcast address.
+- */
++/* Check whether "cp" is a valid ASCII representation of an IPv4
++   Internet address and convert it to a binary address.  Returns 1 if
++   the address is valid, 0 if not.  This replaces inet_addr, the
++   return value from which cannot distinguish between failure and a
++   local broadcast address.  */
+ int
+-__inet_aton(const char *cp, struct in_addr *addr)
++__inet_aton (const char *cp, struct in_addr *addr)
+ {
+-  static const in_addr_t max[4] = { 0x, 0xff, 0x, 0xff };
+-  in_addr_t val;
+-  char c;
+-  union iaddr {
+-uint8_t bytes[4];
+-uint32_t word;
+-  } res;
+-  uint8_t *pp = res.bytes;
+-  int digit;
+-
+-  int saved_errno = errno;
+-  __set_errno (0);
+-
+-  res.word = 0;
+-
+-  c = *cp;
+-  for (;;) {
+-  /*
+-   * Collect number up to ``.''.
+-   * Values are specified as for C:
+-   * 0x=hex, 0=octal, isdigit=decimal.
+-   */
+-  if (!isdigit(c))
+-  goto ret_0;
+-  {
+-  char *endp;
+-  unsigned long ul = strtoul (cp, (char **) , 0);
+-  if (ul == ULONG_MAX && errno == ERANGE)
+-  goto ret_0;
+-  if (ul > 0xul)
+-  goto ret_0;
+-  val = ul;
+-  digit = cp != 

[OE-core] [PATCH][thud 1/2] lighttpd: fix CVE-2019-11072

[Ross Burton]

Signed-off-by: Ross Burton 
---
 .../lighttpd/lighttpd/fix-http-parseopts.patch | 51 ++
 meta/recipes-extended/lighttpd/lighttpd_1.4.51.bb  |  1 +
 2 files changed, 52 insertions(+)
 create mode 100644 
meta/recipes-extended/lighttpd/lighttpd/fix-http-parseopts.patch

diff --git a/meta/recipes-extended/lighttpd/lighttpd/fix-http-parseopts.patch 
b/meta/recipes-extended/lighttpd/lighttpd/fix-http-parseopts.patch
new file mode 100644
index 000..f3a0402c4be
--- /dev/null
+++ b/meta/recipes-extended/lighttpd/lighttpd/fix-http-parseopts.patch
@@ -0,0 +1,51 @@
+CVE: CVE-2019-11072
+Upstream-Status: Backport
+Signed-off-by: Ross Burton 
+
+From 32120d5b8b3203fc21ccb9eafb0eaf824bb59354 Mon Sep 17 00:00:00 2001
+From: Glenn Strauss 
+Date: Wed, 10 Apr 2019 11:28:10 -0400
+Subject: [PATCH] [core] fix abort in http-parseopts (fixes #2945)
+
+fix abort in server.http-parseopts with url-path-2f-decode enabled
+
+(thx stze)
+
+x-ref:
+  "Security - SIGABRT during GET request handling with url-path-2f-decode 
enabled"
+  https://redmine.lighttpd.net/issues/2945
+---
+ src/burl.c| 6 --
+ src/t/test_burl.c | 2 ++
+ 2 files changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/src/burl.c b/src/burl.c
+index 51182628..c4b928fd 100644
+--- a/src/burl.c
 b/src/burl.c
+@@ -252,8 +252,10 @@ static int burl_normalize_2F_to_slash_fix (buffer *b, int 
qs, int i)
+ }
+ }
+ if (qs >= 0) {
+-memmove(s+j, s+qs, blen - qs);
+-j += blen - qs;
++const int qslen = blen - qs;
++memmove(s+j, s+qs, (size_t)qslen);
++qs = j;
++j += qslen;
+ }
+ buffer_string_set_length(b, j);
+ return qs;
+diff --git a/src/t/test_burl.c b/src/t/test_burl.c
+index 7be9be50..f7a16815 100644
+--- a/src/t/test_burl.c
 b/src/t/test_burl.c
+@@ -97,6 +97,8 @@ static void test_burl_normalize (void) {
+ flags |= HTTP_PARSEOPT_URL_NORMALIZE_PATH_2F_DECODE;
+ run_burl_normalize(psrc, ptmp, flags, __LINE__, 
CONST_STR_LEN("/a/b?c=/"), CONST_STR_LEN("/a/b?c=/"));
+ run_burl_normalize(psrc, ptmp, flags, __LINE__, 
CONST_STR_LEN("/a/b?c=%2f"), CONST_STR_LEN("/a/b?c=/"));
++run_burl_normalize(psrc, ptmp, flags, __LINE__, CONST_STR_LEN("%2f?"), 
CONST_STR_LEN("/?"));
++run_burl_normalize(psrc, ptmp, flags, __LINE__, CONST_STR_LEN("/%2f?"), 
CONST_STR_LEN("//?"));
+ run_burl_normalize(psrc, ptmp, flags, __LINE__, CONST_STR_LEN("/a%2fb"), 
CONST_STR_LEN("/a/b"));
+ run_burl_normalize(psrc, ptmp, flags, __LINE__, CONST_STR_LEN("/a%2Fb"), 
CONST_STR_LEN("/a/b"));
+ run_burl_normalize(psrc, ptmp, flags, __LINE__, 
CONST_STR_LEN("/a%2fb?c=/"), CONST_STR_LEN("/a/b?c=/"));
diff --git a/meta/recipes-extended/lighttpd/lighttpd_1.4.51.bb 
b/meta/recipes-extended/lighttpd/lighttpd_1.4.51.bb
index f28fd2f6905..5c828da5b06 100644
--- a/meta/recipes-extended/lighttpd/lighttpd_1.4.51.bb
+++ b/meta/recipes-extended/lighttpd/lighttpd_1.4.51.bb
@@ -18,6 +18,7 @@ SRC_URI = 
"http://download.lighttpd.net/lighttpd/releases-1.4.x/lighttpd-${PV}.t
 file://lighttpd \
 file://lighttpd.service \
 file://0001-Use-pkg-config-for-pcre-dependency-instead-of-config.patch 
\
+file://fix-http-parseopts.patch \
 "
 
 SRC_URI[md5sum] = "6e68c19601af332fa3c5f174245f59bf"
-- 
2.11.0

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

Re: [OE-core] [PATCH v5 06/13] go.bbclass: ptest cleanup and improvements

[Matt Madison]

On Fri, Jun 21, 2019 at 2:08 AM Yu, Mingli  wrote:
>
> Hi Matt,
>
> I noticed your commit is the latest update for go-dep ptest. But the
> go-dep ptest doesn't work in my environment. I'm trying to figure out
> what's wrong is here though I didn't know much about go.

I went back over the commits, and I don't think I did anything with
go-dep specifically. I can see that the tests are failing for it, and
it looks like it's because go-dep's test programs make some
assumptions about the environment.  For one thing, it needs the go
compiler installed. It also looks like it's expecting some source
files to be present... in other words, it's not really designed for a
cross-build setup, with tests run on the cross-built target. It could
be messy to work around that, and I'm not sure how useful it would be
anyway, seeing as how go-dep is more of a build tool.  Might be better
to just disable ptests for it completely.

BTW, you can have the test programs generate verbose output by setting
GOPTESTFLAGS = "-test.v" in the recipe, which will add that flag to
their invocation in the wrapper script, or by manually running the
test program on the target and passing that flag (cd into the
directory where the test program is located, then run it with
-test.v).

Regards,
-Matt

>
> BTW, Could you help to check?
>
> root@qemux86-64:~# cd /usr/lib64/go-dep/ptest/
> root@qemux86-64:/usr/lib64/go-dep/ptest# cat run-ptest
> #!/bin/sh
> RC=0
> run_test() (
>  cd "$1"
>  ./$2 ; echo $? >&3) | sed -r -e"s,^(PASS|SKIP|FAIL)$,\1:
> $1/$2," >&4) 3>&1) | (read rc; exit $rc)) 4>&1
>  exit $?)
> run_test github.com/golang/dep/cmd/dep dep.test || RC=1
> exit $RC
> root@qemux86-64:/usr/lib64/go-dep/ptest# ./run-ptest
> building testdep failed: exit status 1
> can't load package: package .: no Go files in
> /usr/lib64/go-dep/ptest/github.com/golang/dep/cmd/dep
> root@qemux86-64:/usr/lib64/go-dep/ptest#
>
> Thanks,
>
> On 2018年03月05日 05:09, Matt Madison wrote:
> > * Don't enable verbose test output (-test.v)
> >by default, as it generates too much noise
> >for automated results parsing
> >
> > * Override do_install_ptest_base in the bbclass,
> >so recipes can provide their own modifications
> >with do_install_ptest.
> >
> > * Improve the generated run-ptest script to better
> >handle large numbers of tests, and to generate
> >'status: test name' output similar to Automake
> >tests.
> >
> > * Install all non-vendored 'testdata' directories
> >from the source into the ptest package, as some
> >packages share test data among multiple tests.
> >
> > Signed-off-by: Matt Madison 
> > ---
> >   meta/classes/go.bbclass | 87 
> > +
> >   1 file changed, 51 insertions(+), 36 deletions(-)
> >
> > diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
> > index afd68b5951..a51ba3e9f0 100644
> > --- a/meta/classes/go.bbclass
> > +++ b/meta/classes/go.bbclass
> > @@ -26,7 +26,7 @@ GO_LDFLAGS ?= '-ldflags="${GO_RPATH} ${GO_LINKMODE} 
> > -extldflags '${GO_EXTLDFLAGS
> >   export GOBUILDFLAGS ?= "-v ${GO_LDFLAGS}"
> >   export GOPATH_OMIT_IN_ACTIONID ?= "1"
> >   export GOPTESTBUILDFLAGS ?= "${GOBUILDFLAGS} -c"
> > -export GOPTESTFLAGS ?= "-test.v"
> > +export GOPTESTFLAGS ?= ""
> >   GOBUILDFLAGS_prepend_task-compile = "${GO_PARALLEL_BUILD} "
> >
> >   export GO = "${HOST_PREFIX}go"
> > @@ -76,7 +76,7 @@ go_list_packages() {
> >   }
> >
> >   go_list_package_tests() {
> > -${GO} list -f '{{.ImportPath}} {{.TestGoFiles}}' ${GOBUILDFLAGS} 
> > ${GO_INSTALL} | \
> > + ${GO} list -f '{{.ImportPath}} {{.TestGoFiles}}' ${GOBUILDFLAGS} 
> > ${GO_INSTALL} | \
> >   grep -v '\[\]$' | \
> >   egrep -v '${GO_INSTALL_FILTEROUT}' | \
> >   awk '{ print $1 }'
> > @@ -100,15 +100,16 @@ go_do_compile() {
> >   do_compile[dirs] =+ "${GOTMPDIR}"
> >   do_compile[cleandirs] = "${B}/bin ${B}/pkg"
> >
> > -do_compile_ptest() {
> > +do_compile_ptest_base() {
> >   export TMPDIR="${GOTMPDIR}"
> > -rm -f ${B}/.go_compiled_tests.list
> > + rm -f ${B}/.go_compiled_tests.list
> >   go_list_package_tests | while read pkg; do
> >   cd ${B}/src/$pkg
> >   ${GO} test ${GOPTESTBUILDFLAGS} $pkg
> >   find . -mindepth 1 -maxdepth 1 -type f -name '*.test' -exec 
> > echo $pkg/{} \; | \
> >   sed -e's,/\./,/,'>> ${B}/.go_compiled_tests.list
> >   done
> > + do_compile_ptest
> >   }
> >   do_compile_ptest_base[dirs] =+ "${GOTMPDIR}"
> >
> > @@ -124,40 +125,54 @@ go_do_install() {
> >   fi
> >   }
> >
> > -do_install_ptest_base() {
> > -test -f "${B}/.go_compiled_tests.list" || exit 0
> > -tests=""
> > -while read test; do
> > -tests="$tests${tests:+ }${test%.test}"
> > -testdir=`dirname $test`
> > -install -d ${D}${PTEST_PATH}/$testdir
> > -install -m 0755 ${B}/src/$test ${D}${PTEST_PATH}/$test
> > -if [ -d 

[OE-core] [PATCH v2 0/2] meta: Fixes for update-alternatives.bbclass and gtk-icon-cache.bbclass

[Robert Yang]

* V2
  - The patch for update-alternatives.bbclass makes update-alternatives runs 
firstly
before other postinst scripts, since other postinst may run the tool which 
is
installed by the package itself (e.g., newaliases is installed as
newaliases.postfix, and update-alternatives will update it to newaliases). 
But this
broke busybox' on target install, since update-alternatives requires some
basic tools such as sed, there was a neat way in busybox' postinst to fix
this problem, the v2 makes busybox' postinst script run firstly before
update-alternatives.

Testinfo:
MACHINE = "qemux86"
PACKAGE_CLASSES = "package_ipk package_rpm" (or "package_rpm package_ipk")
TESTIMAGE_AUTO = "1"
$ bitbake core-image-sato core-image-minimal

The tests are OK.

* V1
  - Initial version

// Robert

The following changes since commit 4bb3e8f98e2bbfcb20f1b32d2b7674d1a6cb47be:

  local.conf.sample.extended: remove redundant RUNTIMETARGET assignment 
(2019-06-24 17:32:37 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib rbt/post
  http://cgit.openembedded.org//log/?h=rbt/post

Robert Yang (2):
  update-alternatives.bbclass: run update-alternatives firstly in
postinst script
  gtk-icon-cache.bbclass: Depends on gtk+3

 meta/classes/gtk-icon-cache.bbclass  | 14 ++
 meta/classes/update-alternatives.bbclass | 13 +++--
 2 files changed, 21 insertions(+), 6 deletions(-)

-- 
2.7.4

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

[OE-core] [PATCH v2 2/2] gtk-icon-cache.bbclass: Depends on gtk+3

[Robert Yang]

The gtk-update-icon-cache is provided by gtk+3, gdk-pixbuf-query-loaders is
provided by gdk-pixbuf, and gtk+3 depends on gdk-pixbuf, so depends on gtk+3
can fix the problems.

Signed-off-by: Robert Yang 
---
 meta/classes/gtk-icon-cache.bbclass | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/meta/classes/gtk-icon-cache.bbclass 
b/meta/classes/gtk-icon-cache.bbclass
index 66fe781..4e60fe6 100644
--- a/meta/classes/gtk-icon-cache.bbclass
+++ b/meta/classes/gtk-icon-cache.bbclass
@@ -4,6 +4,11 @@ DEPENDS +=" ${@['hicolor-icon-theme', '']['${BPN}' == 
'hicolor-icon-theme']} gtk
 
 PACKAGE_WRITE_DEPS += "gtk+3-native gdk-pixbuf-native"
 
+inherit distro_features_check
+ANY_OF_DISTRO_FEATURES = "${GTK3DISTROFEATURES}"
+
+DEPENDS += "gtk+3"
+
 gtk_icon_cache_postinst() {
 if [ "x$D" != "x" ]; then
$INTERCEPT_DIR/postinst_intercept update_icon_cache ${PKG} \
@@ -45,10 +50,11 @@ python populate_packages_append () {
 if not os.path.exists(icon_dir):
 continue
 
-bb.note("adding hicolor-icon-theme dependency to %s" % pkg)
-rdepends = ' ' + d.getVar('MLPREFIX', False) + "hicolor-icon-theme"
-d.appendVar('RDEPENDS_%s' % pkg, rdepends)
-
+for dep in ('hicolor-icon-theme', 'gtk+3'):
+bb.note("Adding %s dependency to %s" % (dep, pkg))
+rdepends = ' ' + d.getVar('MLPREFIX', False) + dep
+d.appendVar('RDEPENDS_%s' % pkg, rdepends)
+
 bb.note("adding gtk-icon-cache postinst and postrm scripts to %s" % 
pkg)
 
 postinst = d.getVar('pkg_postinst_%s' % pkg)
-- 
2.7.4

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

[OE-core] [PATCH v2 1/2] update-alternatives.bbclass: run update-alternatives firstly in postinst script

[Robert Yang]

Recipes like postfix run command newaliases in postinst, but newaliases is
installed as newaliases.postfix, it needs run update-alternatives to update it
to newaliases, so there was an error when installed postinst on target.

Fixed:
$ opkg install postfix
Configuring postfix.
///var/lib/opkg/info/postfix.postinst: line 4: newaliases: command not found

Run update-alternatives firstly will fix the problem. And handle busybox as an
exception since it needs set basic tools such as sed command firstly, otherwise
update-alternatives doesn't work.

Signed-off-by: Robert Yang 
---
 meta/classes/update-alternatives.bbclass | 13 +++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/meta/classes/update-alternatives.bbclass 
b/meta/classes/update-alternatives.bbclass
index b702e77..9ab9298 100644
--- a/meta/classes/update-alternatives.bbclass
+++ b/meta/classes/update-alternatives.bbclass
@@ -265,6 +265,7 @@ python populate_packages_updatealternatives () {
 if not update_alternatives_enabled(d):
 return
 
+bpn = d.getVar('BPN')
 # Do actual update alternatives processing
 for pkg in (d.getVar('PACKAGES') or "").split():
 # Create post install/removal scripts
@@ -284,8 +285,16 @@ python populate_packages_updatealternatives () {
 
 bb.note('adding update-alternatives calls to postinst/prerm for 
%s' % pkg)
 bb.note('%s' % alt_setup_links)
-postinst = d.getVar('pkg_postinst_%s' % pkg) or '#!/bin/sh\n'
-postinst += alt_setup_links
+postinst = d.getVar('pkg_postinst_%s' % pkg)
+if postinst:
+# Busybox needs handle basic tools such as sed command
+# firstly, otherwise, update-alternatives doesn't work.
+if bpn == 'busybox':
+postinst += alt_setup_links
+else:
+postinst = alt_setup_links + postinst
+else:
+postinst = '#!/bin/sh\n' + alt_setup_links
 d.setVar('pkg_postinst_%s' % pkg, postinst)
 
 bb.note('%s' % alt_remove_links)
-- 
2.7.4

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

Re: [OE-core] [PATCH] python: make 'python' install everything instead of just the interpretter

[Alejandro Enedino Hernandez Samaniego]

Hey Ross,

On 6/20/19 7:53 AM, Ross Burton wrote:

Follow the python3 behaviour, and common sense, by making 'python' install
python-modules instead of python-core.  This means a user installing python gets
all of Python, instead of just a fraction of the library.

[ YOCTO #13402 ]

Signed-off-by: Ross Burton 
---
  meta/recipes-devtools/python/python_2.7.16.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/python_2.7.16.bb 
b/meta/recipes-devtools/python/python_2.7.16.bb
index d70342fe3a6..5f387b8af11 100644
--- a/meta/recipes-devtools/python/python_2.7.16.bb
+++ b/meta/recipes-devtools/python/python_2.7.16.bb
@@ -162,7 +162,7 @@ py_package_preprocess () {
  PACKAGES_remove = "${PN}"
  
  # manual dependency additions

-RPROVIDES_${PN}-core = "${PN}"
+RPROVIDES_${PN}-modules = "${PN}"


Is it just me or we already had this?, maybe we had this only for python3


Alejandro



  RRECOMMENDS_${PN}-core_append_class-nativesdk = " nativesdk-python-modules"
  RRECOMMENDS_${PN}-crypt = "openssl"
  

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

Re: [OE-core] [PATCH] scons: fix conflict during do_rootfs

[Adrian Bunk]

On Mon, Jun 24, 2019 at 05:29:37PM +0800, changqing...@windriver.com wrote:
> From: Changqing Li 
> 
> fix below error:
> file /usr/bin/scons conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/scons-3.0.5 conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/scons-configure-cache conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/scons-configure-cache-3.0.5 conflicts between attempted 
> installs of python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/scons-time conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/scons-time-3.0.5 conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/sconsign conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
> file /usr/bin/sconsign-3.0.5 conflicts between attempted installs of 
> python-scons-3.0.5-r0.core2_32 and python3-scons-3.0.5-r0.core2_32
>...

Could this be solved with an RCONFLICTS between the packages?

Installing either on the target is anyways rarely wanted,
the main usecase is the -native at build time.

This would also handle the case if python-scons gets removed from
oe-core but gets added to some other layer.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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

Re: [OE-core] [PATCH v2] lttng-modules: Backport patches to fix compilation failures since kernel v5.1

[He Zhe]

On 6/25/19 4:04 PM, richard.pur...@linuxfoundation.org wrote:
> On Tue, 2019-06-25 at 15:59 +0800, He Zhe wrote:
>> On 6/12/19 6:57 AM, Bruce Ashfield wrote:
>>> On Tue, Jun 11, 2019 at 6:50 PM Richard Purdie
>>>  wrote:
 On Tue, 2019-06-11 at 17:03 +0800, zhe...@windriver.com wrote:
> From: He Zhe 
>
> For the moment,
> 0001~0004 are on master branch only.
> 0005~0007 are on stable-2.11 branch, but v2.11 has not been
> released
> yet.
>
> Signed-off-by: He Zhe 
> ---
> v2: Correct a typo in SOB for 0001*.patch
 I just discussed this with lttng upstream maintainers a little.
 We're
 going to have continual tension between keeping lttng-modules up
 to
 date and new kernel versions.

 How about we also have a git version of this particular recipe
 which
 has a DEFAULT_PREFERENCE = "-1" but people can opt into with a
 PREFERRED_VERSION when using newer kernels?

 That should keep people using very recent kernels happy, let us
 use a
 stable release version and avoid us adding/removing large
 patchsets on
 a semi regular basis?

 Would you be willing to try/submit such a git recipe?
>>> This makes sense to me as well, since I'm one of the folks that
>>> runs
>>> into this issue the most. In fact, I've been carrying a local _git
>>> version of the lttng recipe for over a year, since I didn't feel
>>> like
>>> getting into the _git versus release tarballs debate. This solution
>>> should avoid that debate and keep all the different versions of
>>> kernels moving along.
>> Hi Bruce and Richard,
>>
>> BTW, how about using git for all cases so that people don't have to
>> maintain a
>> tarball locally? Though I don't have the background knowledge of that
>> git vs
>> tarball debate mentioned above.
> The overhead of tarball releases is much lower than git trees for each
> piece of software so I'd prefer to have tarball recipes where we can,
> it does lead to faster builds.

Got it, thanks.

Zhe

>
> Cheers,
>
> Richard
>
>
>

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

Re: [OE-core] [PATCH v2] efibootmgr: Pass correct flags to compiler from pkg-config

[Adrian Bunk]

On Mon, Jun 24, 2019 at 11:01:21PM -0700, Khem Raj wrote:
> efivar.h is in usr/include/efirvar directory so it should be
> added to include search path via -I to compiler cmdline to fix
> 
> make[1]: *** No rule to make target 'efivar.h', needed by 'efibootmgr.o'.  
> Stop.
> | make[1]: *** Waiting for unfinished jobs
> 
> When running clang to generate dependencies -MM -MG -MF it still
> parses the compile unit and complains if certain header is not found
> where as gcc does not do that, hence the compile error is only seen
> when compiling with clang.
> 
> FIx is use a weak default assignment for PKGS var which is used by
> pkg-config to deduce compiler flags, this helps in getting right
> -I flags even for dep step
>...
> +Upstream-Status: Pending
>...

It would be better to backport the upstream fix instead:
https://github.com/rhboot/efibootmgr/commit/97668ae0bce776a36ea2001dea63d376be8274ac

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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

Re: [OE-core] [PATCH 1/4] cve-update-db: New recipe to update CVE database

[Pierre Le Magourou]

Hi,

> Also, the CVE db is updated using this custom task without link to
> do_fetch, which means a fetchall task would not update the database for
> off line NO_NETWORK builds.
>
> Could the task be added as dependency to do_fetch() or are there some other
> side effects?
>

Yes I can do that, I don't think this will cause side effects.

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

Re: [OE-core] [PATCH v2] lttng-modules: Backport patches to fix compilation failures since kernel v5.1

[richard . purdie]

On Tue, 2019-06-25 at 15:59 +0800, He Zhe wrote:
> 
> On 6/12/19 6:57 AM, Bruce Ashfield wrote:
> > On Tue, Jun 11, 2019 at 6:50 PM Richard Purdie
> >  wrote:
> > > On Tue, 2019-06-11 at 17:03 +0800, zhe...@windriver.com wrote:
> > > > From: He Zhe 
> > > > 
> > > > For the moment,
> > > > 0001~0004 are on master branch only.
> > > > 0005~0007 are on stable-2.11 branch, but v2.11 has not been
> > > > released
> > > > yet.
> > > > 
> > > > Signed-off-by: He Zhe 
> > > > ---
> > > > v2: Correct a typo in SOB for 0001*.patch
> > > I just discussed this with lttng upstream maintainers a little.
> > > We're
> > > going to have continual tension between keeping lttng-modules up
> > > to
> > > date and new kernel versions.
> > > 
> > > How about we also have a git version of this particular recipe
> > > which
> > > has a DEFAULT_PREFERENCE = "-1" but people can opt into with a
> > > PREFERRED_VERSION when using newer kernels?
> > > 
> > > That should keep people using very recent kernels happy, let us
> > > use a
> > > stable release version and avoid us adding/removing large
> > > patchsets on
> > > a semi regular basis?
> > > 
> > > Would you be willing to try/submit such a git recipe?
> > This makes sense to me as well, since I'm one of the folks that
> > runs
> > into this issue the most. In fact, I've been carrying a local _git
> > version of the lttng recipe for over a year, since I didn't feel
> > like
> > getting into the _git versus release tarballs debate. This solution
> > should avoid that debate and keep all the different versions of
> > kernels moving along.
> 
> Hi Bruce and Richard,
> 
> BTW, how about using git for all cases so that people don't have to
> maintain a
> tarball locally? Though I don't have the background knowledge of that
> git vs
> tarball debate mentioned above.

The overhead of tarball releases is much lower than git trees for each
piece of software so I'd prefer to have tarball recipes where we can,
it does lead to faster builds.

Cheers,

Richard


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

Re: [OE-core] [PATCHv3] cmake.bbclass: pass mandatory compiler flags through CMAKE__COMPILER_ARG1

[Richard Purdie]

On Mon, 2019-06-24 at 13:24 +0300, Nikolai Merinov via Openembedded-
core wrote:
> Patch updated with "Signed-off-by" field as required by automatic
> checks.
> 
> - Original Message -
> From: "openembedded-core" 
> To: "Khem Raj" 
> Cc: "openembedded-core" 
> Sent: Thursday, June 20, 2019 7:16:07 PM
> Subject: [OE-core] [PATCHv2] cmake.bbclass: pass mandatory compiler
> flags through CMAKE__COMPILER_ARG1
> 
> Hi,
> 
> Updated patch for the current "master" branch is attached.
> 
> > have you also tried building SDK and see if these changes are
> > reflected in SDK as well ?
> 
> I checked that the changes reflected in the Extensible SDK for the
> "core-image-sato" image of the poky.
> 
> Regards,
> Nikolai
> 
> - Original Message -
> From: "Khem Raj" 
> To: "n merinov" , "openembedded-core" <
> openembedded-core@lists.openembedded.org>
> Sent: Tuesday, May 21, 2019 1:41:46 AM
> Subject: Re: [OE-core] [PATCH] cmake.bbclass: pass mandatory compiler
> flags through CMAKE__COMPILER_ARG1
> 
> On 5/14/19 8:04 AM, Nikolai Merinov wrote:
> > The CMake takes mandatory compiler arguments from the following
> > variables:
> > - CMAKE_SYSROOT -- path to sysroot that should be passed to
> > compiler.
> > - CMAKE__COMPILER_TARGET -- target architecture, used for
> > compilers
> >that supports several targets through command line options.
> >e.g. "clang --target ${CMAKE_C_COMPILER_TARGET}".
> > - CMAKE__COMPILER_EXTERNAL_TOOLCHAIN -- path to external
> > toolchain,
> >used for compilers that support build with external toolchain.
> >e.g. "clang --gcc-toolchain
> > ${CMAKE_C_COMPILER_EXTERNAL_TOOLCHAIN}".
> > - CMAKE__COMPILER_ARG1 -- other mandatory arguments to a
> > compiler
> >command.
> > 
> > CMAKE__COMPILER_ARG1 is the most suitable variable to pass
> > mandatory
> > arguments, that belongs to CC variable with other build systems, to
> > a
> > compiler.
> > 
> > Additionally usage of CMAKE__COMPILER_ARG1 instead of
> > CMAKE__FLAGS reduce the risk that a variable can be overrided
> > by
> > CMakeLists.txt files.
> 
I'm afraid this caused a number of build failures and selftest issues:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/236

(most of the selftest failures there for example are from this, as is 
https://autobuilder.yoctoproject.org/typhoon/#/builders/69/builds/746/steps/7/logs/step7b
)

Cheers,

Richard

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

Re: [OE-core] [PATCH v2] lttng-modules: Backport patches to fix compilation failures since kernel v5.1

[He Zhe]

On 6/12/19 6:57 AM, Bruce Ashfield wrote:
> On Tue, Jun 11, 2019 at 6:50 PM Richard Purdie
>  wrote:
>> On Tue, 2019-06-11 at 17:03 +0800, zhe...@windriver.com wrote:
>>> From: He Zhe 
>>>
>>> For the moment,
>>> 0001~0004 are on master branch only.
>>> 0005~0007 are on stable-2.11 branch, but v2.11 has not been released
>>> yet.
>>>
>>> Signed-off-by: He Zhe 
>>> ---
>>> v2: Correct a typo in SOB for 0001*.patch
>> I just discussed this with lttng upstream maintainers a little. We're
>> going to have continual tension between keeping lttng-modules up to
>> date and new kernel versions.
>>
>> How about we also have a git version of this particular recipe which
>> has a DEFAULT_PREFERENCE = "-1" but people can opt into with a
>> PREFERRED_VERSION when using newer kernels?
>>
>> That should keep people using very recent kernels happy, let us use a
>> stable release version and avoid us adding/removing large patchsets on
>> a semi regular basis?
>>
>> Would you be willing to try/submit such a git recipe?
> This makes sense to me as well, since I'm one of the folks that runs
> into this issue the most. In fact, I've been carrying a local _git
> version of the lttng recipe for over a year, since I didn't feel like
> getting into the _git versus release tarballs debate. This solution
> should avoid that debate and keep all the different versions of
> kernels moving along.

Hi Bruce and Richard,

BTW, how about using git for all cases so that people don't have to maintain a
tarball locally? Though I don't have the background knowledge of that git vs
tarball debate mentioned above.

Zhe

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

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

[OE-core] [PATCH] systemd-bootconf: Make is machine specific

[Ricardo Ribalda Delgado]

APPEND is usually attached to a machine. This patch avoids multiconfig
errors such as:

| NOTE: Direct dependencies are 
['multiconfig:qt5022:/workdir/repo/poky/meta/recipes-core/glibc/glibc_2.29.bb:do_populate_sysroot',
 
'multiconfig:qt5022:virtual:native:/workdir/repo/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot',
 
'multiconfig:qt5022:/workdir/repo/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
 
'multiconfig:qt5022:/workdir/repo/poky/meta/recipes-devtools/gcc/gcc-cross_8.3.bb:do_populate_sysroot',
 
'multiconfig:qt5022:/workdir/repo/poky/meta/recipes-devtools/gcc/gcc-runtime_8.3.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['glibc', 'pseudo-native', 
'quilt-native', 'gcc-cross-x86_64', 'gcc-runtime', 'libgcc', 
'linux-libc-headers', 'libtool-native', 'texinfo-dummy-native', 
'libmpc-native', 'flex-native', 'automake-native', 'zlib-native', 
'mpfr-native', 'gmp-native', 'binutils-cross-x86_64', 'xz-native', 
'autoconf-native', 'gnu-config-native', 'gettext-minimal-native', 'm4-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| install: cannot stat 'loader.conf': No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_install (log file is located at 
/workdir/build/tmp/work/bobcat-poky-linux/systemd-bootconf/1.00-r0/temp/log.do_install.737)
NOTE: recipe systemd-bootconf-1.00-r0: task do_install: Failed
ERROR: Task 
(multiconfig:qt5022:/workdir/repo/poky/meta/recipes-core/systemd/systemd-bootconf_1.00.bb:do_install)
 failed with exit code '1'

Signed-off-by: Ricardo Ribalda Delgado 
---
 meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/systemd/systemd-bootconf_1.00.bb 
b/meta/recipes-core/systemd/systemd-bootconf_1.00.bb
index e9c2466456..d13b8c518f 100644
--- a/meta/recipes-core/systemd/systemd-bootconf_1.00.bb
+++ b/meta/recipes-core/systemd/systemd-bootconf_1.00.bb
@@ -3,6 +3,7 @@ LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384
 SUMMARY = "Basic systemd-boot configuration files"
 
 RPROVIDES_${PN} += "virtual/systemd-bootconf"
+PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 inherit systemd-boot-cfg
 
-- 
2.20.1

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

[OE-core] [PATCH 0/1] target-sdk-provides-dummy: add libperl.so.5 64bit

[Chen Qi]

*** BLURB HERE ***
The following changes since commit 67266331b0f557c01cde1cc1b1a1de7197443a6c:

  local.conf.sample.extended: remove redundant RUNTIMETARGET assignment 
(2019-06-24 17:34:25 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib ChenQi/target-sdk-perl-64
  
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/target-sdk-perl-64

Chen Qi (1):
  target-sdk-provides-dummy: add libperl.so.5 64bit

 meta/recipes-core/meta/target-sdk-provides-dummy.bb | 1 +
 1 file changed, 1 insertion(+)

-- 
1.9.1

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

[OE-core] [PATCH 1/1] target-sdk-provides-dummy: add libperl.so.5 64bit

[Chen Qi]

With postgresql added to IMAGE_INSTALL, we will get the following
error when building for 64bit BSPs.

  Problem: package postgresql-11.3-r0.corei7_64 requires libperl.so.5()(64bit), 
but none of the providers can be installed

A previous patch has added libperl.so.5 to DUMMY_PROVIDES, but this
is not enough. Because for 64bit BSP, it should also provide 
libperl.so.5()(64bit).

Signed-off-by: Chen Qi 
---
 meta/recipes-core/meta/target-sdk-provides-dummy.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/meta/target-sdk-provides-dummy.bb 
b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
index b5e8c0f..c33cb80 100644
--- a/meta/recipes-core/meta/target-sdk-provides-dummy.bb
+++ b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
@@ -47,6 +47,7 @@ DUMMYPROVIDES = "\
 /usr/bin/env \
 /usr/bin/perl \
 libperl.so.5 \
+libperl.so.5()(64bit) \
 pkgconfig \
 pkgconfig-dev \
 pkgconfig-src \
-- 
1.9.1

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

[OE-core] [PATCH v2] efibootmgr: Pass correct flags to compiler from pkg-config

[Khem Raj]

efivar.h is in usr/include/efirvar directory so it should be
added to include search path via -I to compiler cmdline to fix

make[1]: *** No rule to make target 'efivar.h', needed by 'efibootmgr.o'.  Stop.
| make[1]: *** Waiting for unfinished jobs

When running clang to generate dependencies -MM -MG -MF it still
parses the compile unit and complains if certain header is not found
where as gcc does not do that, hence the compile error is only seen
when compiling with clang.

FIx is use a weak default assignment for PKGS var which is used by
pkg-config to deduce compiler flags, this helps in getting right
-I flags even for dep step

Signed-off-by: Khem Raj 
Cc: Ross Burton 
---
 ...failts-Set-PKGS-to-efivar-by-default.patch | 33 +++
 meta/recipes-bsp/efibootmgr/efibootmgr_17.bb  |  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 
meta/recipes-bsp/efibootmgr/efibootmgr/0001-Make.defailts-Set-PKGS-to-efivar-by-default.patch

diff --git 
a/meta/recipes-bsp/efibootmgr/efibootmgr/0001-Make.defailts-Set-PKGS-to-efivar-by-default.patch
 
b/meta/recipes-bsp/efibootmgr/efibootmgr/0001-Make.defailts-Set-PKGS-to-efivar-by-default.patch
new file mode 100644
index 00..415012d64c
--- /dev/null
+++ 
b/meta/recipes-bsp/efibootmgr/efibootmgr/0001-Make.defailts-Set-PKGS-to-efivar-by-default.patch
@@ -0,0 +1,33 @@
+From f6c3154810938506c13e22d16935ae4d07e911dc Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 24 Jun 2019 22:27:21 -0700
+Subject: [PATCH] Make.defailts: Set PKGS to efivar by default
+
+This ensures that when make dep is run then pkg-config logic can add
+efivar related variables to cflags and ldflags
+
+Fixes
+make[1]: *** No rule to make target 'efivar.h', needed by 'efibootmgr.o'.  
Stop.
+
+Upstream-Status: Pending
+Signed-off-by: Khem Raj 
+---
+ Make.defaults | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Make.defaults b/Make.defaults
+index c4c0592..d75c6f4 100644
+--- a/Make.defaults
 b/Make.defaults
+@@ -32,7 +32,7 @@ AR   := $(CROSS_COMPILE)gcc-ar
+ NM:= $(CROSS_COMPILE)gcc-nm
+ RANLIB:= $(CROSS_COMPILE)gcc-ranlib
+ 
+-PKGS  =
++PKGS  ?= efivar
+ 
+ SUBDIR_CFLAGS ?=
+ clang_cflags =
+-- 
+2.22.0
+
diff --git a/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb 
b/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb
index 0e5a81e316..835c7b3b81 100644
--- a/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb
+++ b/meta/recipes-bsp/efibootmgr/efibootmgr_17.bb
@@ -12,6 +12,7 @@ COMPATIBLE_HOST = "(i.86|x86_64|arm|aarch64).*-linux"
 
 SRC_URI = "git://github.com/rhinstaller/efibootmgr.git;protocol=https \
file://0001-remove-extra-decl.patch \
+   file://0001-Make.defailts-Set-PKGS-to-efivar-by-default.patch \
   "
 SRCREV = "e067160ecef8208e1944002e5d50b275733211fb"
 
-- 
2.22.0

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