Re: [yocto] Yocto Project changes in progress

[Zoran Stojsavljevic]

Very interesting, indeed! Newer knew that Richard (Purdie) is/was
INTEL employee!?

This announcement gives several (conspiracy?) theories... Some
official, some unofficial. ;-)

As independent thinker... IMHO.

Time Will Tell!

Zoran Stojsavljevic
___

On Mon, May 7, 2018 at 11:53 PM, Jeff Osier-Mixon  wrote:
> Hello everyone. I'd like to briefly address rumors around Richard Purdie's
> transition from Intel to a more neutral position, and Intel's reduction in
> resources for the project.
>
> We set up the Yocto Project in 2010 through Linux Foundation, with over 20
> member organizations, so it would function as a true open source project -
> neutral, unbiased, and well distributed. Those things are what make open
> source projects less vulnerable to any one person or company. This is
> actually a very exciting transitional time for the project, and all existing
> member organizations are fully behind the project. We will let people know
> details as they are available.
>
> Meanwhile, the 2.5 "Sumo" release is on the way and should be released soon,
> the 2.6 planning process has started in earnest (please participate!), and
> we are excited to see what the future has in store for the project.
>
> --
> Jeffrey “Jefro” Osier-Mixon, Intel Corporation
> Open Source Community Ecosystem Strategist
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Status WW19’18

[akuster808]

On 05/07/2018 08:01 AM, Jolley, Stephen K wrote:
>
> Current Dev Position: YP 2.5 is in QA.
>
> Next Deadline: YP 2.5 M4 release is 4/27/18
>
>  
>
> SWAT Team Rotation:
>
> · SWAT lead is currently: Stephano
>
I am covering this week for stephano.
- armin
>
> · SWAT team rotation: Stephano -> Maxin  on May 11, 2018
>


> · SWAT team rotation: Maxin-> Armin on May 18, 2018
>
> · https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>  
>
> Key Status/Updates:
>
> · 2.5 rc1 should be due from QA early this week. It is 96%
> complete. See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status
>
> · The need for any rc2 is still to be determined when the
> report is complete.
>
> · The technical call on 1st May started discussions on 2.6
> planning. Some threads were started on the openembedded-architecture
> mailing list for some of the topics which need discussion. The email
> linked to below details the planning process we will be following
> along with some of the possible ideas for 2.6:
> http://lists.openembedded.org/pipermail/openembedded-core/2018-April/150040.html
>
> · A further 2.6 planning meeting will be scheduled at the same
> time as the original meeting on 15th May to continue the discussion
> (8am PST, 4pm GMT).
>
> · We have started merging patches into master again to clear
> some of the backlog, particularly the recipe upgrades. This improved
> the overall patch count in metrics below.
>
>  
>
> Planned upcoming dot releases:
>
> · YP 2.3.4 (Pyro) will be built after 2.5
>
> · YP 2.2.4 (Morty) will be built after 2.5
>
> · YP 2.4.3 (Rocko) is planned for post YP 2.5
>
>  
>
> Key YP 2.5 Dates are:
>
> · YP 2.5 M4 release of 4/27/18
>
>  
>
> Tracking Metrics:
>
> · WDD 2550 (last week
> 2508)(https://wiki.yoctoproject.org/charts/combo.html)
>
> · Patches  
>
> o    Total patches found: 1590 (last week 1635)
>
> o    Percentage of patches in the Pending State: 47% (last week 46%)
>
>  
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.5_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*
>
> *INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *
>
> (    *Cell*:    (208) 244-4460
>
> * *Email*: _stephen.k.jolley@intel.com_
>
>  
>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project changes in progress

[Jeff Osier-Mixon]

 Hello everyone. I'd like to briefly address rumors around Richard Purdie's
transition from Intel to a more neutral position, and Intel's reduction in
resources for the project.

We set up the Yocto Project in 2010 through Linux Foundation, with over 20
member organizations, so it would function as a true open source project -
neutral, unbiased, and well distributed. Those things are what make open
source projects less vulnerable to any one person or company. This is
actually a very exciting transitional time for the project, and all
existing member organizations are fully behind the project. We will let
people know details as they are available.

Meanwhile, the 2.5 "Sumo" release is on the way and should be released
soon, the 2.6 planning process has started in earnest (please
participate!), and we are excited to see what the future has in store for
the project.

-- 
Jeffrey “Jefro” Osier-Mixon, Intel Corporation
Open Source Community Ecosystem Strategist
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH] libselinux: python-importlib is now part of python*-core

[akuster808]

On 04/14/2018 07:08 PM, Armin Kuster wrote:
> Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 
> 'restorecond', 'libselinux', 'python-importlib']
>
> Signed-off-by: Armin Kuster 
ping
> ---
>  recipes-security/selinux/libselinux.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-security/selinux/libselinux.inc 
> b/recipes-security/selinux/libselinux.inc
> index bd5ce8d..51d0875 100644
> --- a/recipes-security/selinux/libselinux.inc
> +++ b/recipes-security/selinux/libselinux.inc
> @@ -8,7 +8,7 @@ LICENSE = "PD"
>  inherit lib_package pythonnative
>  
>  DEPENDS += "libsepol python libpcre swig-native"
> -RDEPENDS_${PN}-python += "python-importlib"
> +RDEPENDS_${PN}-python += "python-core"
>  
>  PACKAGES += "${PN}-python"
>  FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}/site-packages/*"

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH] policycoreutils: remove oe_filter_out

[akuster]

On 04/14/2018 03:33 PM, Armin Kuster wrote:
> bb.data_smart.ExpansionError: Failure expanding variable WARN_QA[:=], 
> expression was ${@oe_filter_out('unsafe-references-in-scripts', 'ldflags 
> useless-rpaths rpaths staticdev libdir xorg-driver-abi textrel 
> already-stripped incompatible-license files-invalid 
> installed-vs-shipped compile-host-path install-host-path 
> pn-overrides infodir build-deps unknown-configure-option 
> symlink-to-sysroot multilib invalid-packageconfig 
> host-user-contaminated uppercase-pn ', d)} which triggered 
> exception NameError: name 'oe_filter_out' is not defined
>
> Signed-off-by: Armin Kuster 

ping
> ---
>  recipes-security/selinux/policycoreutils.inc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes-security/selinux/policycoreutils.inc 
> b/recipes-security/selinux/policycoreutils.inc
> index 442b086..1842fd8 100644
> --- a/recipes-security/selinux/policycoreutils.inc
> +++ b/recipes-security/selinux/policycoreutils.inc
> @@ -64,8 +64,8 @@ RDEPENDS_${BPN}-setsebool += "\
>  "
>  RDEPENDS_${BPN} += "selinux-python"
>  
> -WARN_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${WARN_QA}', 
> d)}"
> -ERROR_QA := "${@oe_filter_out('unsafe-references-in-scripts', '${ERROR_QA}', 
> d)}"
> +WARN_QA_remove = " unsafe-references-in-scripts"
> +ERROR_QA_remove = " unsafe-references-in-scripts"
>  
>  
>  PACKAGES =+ "\

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW19’18

[Jolley, Stephen K]

Current Dev Position: YP 2.5 is in QA.

Next Deadline: YP 2.5 M4 release is 4/27/18


SWAT Team Rotation:

· SWAT lead is currently: Stephano

· SWAT team rotation: Stephano -> Maxin  on May 11, 2018

· SWAT team rotation: Maxin-> Armin on May 18, 2018

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


Key Status/Updates:

· 2.5 rc1 should be due from QA early this week. It is 96% complete. 
See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status

· The need for any rc2 is still to be determined when the report is 
complete.

· The technical call on 1st May started discussions on 2.6 planning. 
Some threads were started on the openembedded-architecture mailing list for 
some of the topics which need discussion. The email linked to below details the 
planning process we will be following along with some of the possible ideas for 
2.6: 
http://lists.openembedded.org/pipermail/openembedded-core/2018-April/150040.html

· A further 2.6 planning meeting will be scheduled at the same time as 
the original meeting on 15th May to continue the discussion (8am PST, 4pm GMT).

· We have started merging patches into master again to clear some of 
the backlog, particularly the recipe upgrades. This improved the overall patch 
count in metrics below.


Planned upcoming dot releases:

· YP 2.3.4 (Pyro) will be built after 2.5

· YP 2.2.4 (Morty) will be built after 2.5

· YP 2.4.3 (Rocko) is planned for post YP 2.5


Key YP 2.5 Dates are:

· YP 2.5 M4 release of 4/27/18


Tracking Metrics:

· WDD 2550 (last week 2508) 
(https://wiki.yoctoproject.org/charts/combo.html)

· Patches

oTotal patches found: 1590 (last week 1635)

oPercentage of patches in the Pending State: 47% (last week 46%)


Key Status Links for YP:

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

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

https://wiki.yoctoproject.org/wiki/Yocto_2.5_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
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•Cell:(208) 244-4460
• Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [layerindex-web][PATCH 2/2] Add CSV export for layer recipes

[Mark Hatle]

On 5/6/18 10:35 PM, Paul Eggleton wrote:
> Add the ability to export the recipe listing for a layer to a CSV file
> for importing into external tools. At the moment we include name,
> version and license, but there is a parameter that lets you specify the
> fields to include in the URL if desired.
> 
> Implements [YOCTO #12722].

With the bitbake layer library I'm working on, it should be possible to do this
directly out of bitbake.

This wouldn't limit it to just recipes either, but any data.  Loading (querying)
the json data from the layer index is easy, and the library would know how to
filter to the right branch/layer/etc.

Something to consider as we go forward with this and other work.

--Mark

> Signed-off-by: Paul Eggleton 
> ---
>  layerindex/urls_branch.py|  5 -
>  layerindex/views.py  | 22 ++
>  templates/layerindex/detail.html | 14 +++---
>  3 files changed, 33 insertions(+), 8 deletions(-)
> 
> diff --git a/layerindex/urls_branch.py b/layerindex/urls_branch.py
> index 0e41435e..2809147b 100644
> --- a/layerindex/urls_branch.py
> +++ b/layerindex/urls_branch.py
> @@ -7,7 +7,7 @@
>  from django.conf.urls import *
>  from django.views.defaults import page_not_found
>  from django.core.urlresolvers import reverse_lazy
> -from layerindex.views import LayerListView, RecipeSearchView, 
> MachineSearchView, DistroSearchView, ClassSearchView, LayerDetailView, 
> edit_layer_view, delete_layer_view, edit_layernote_view, 
> delete_layernote_view, RedirectParamsView, DuplicatesView, 
> LayerUpdateDetailView
> +from layerindex.views import LayerListView, RecipeSearchView, 
> MachineSearchView, DistroSearchView, ClassSearchView, LayerDetailView, 
> edit_layer_view, delete_layer_view, edit_layernote_view, 
> delete_layernote_view, RedirectParamsView, DuplicatesView, 
> LayerUpdateDetailView, layer_export_recipes_csv_view
>  
>  urlpatterns = [
>  url(r'^$', 
> @@ -20,6 +20,9 @@ urlpatterns = [
>  LayerDetailView.as_view(
>  template_name='layerindex/detail.html'),
>  name='layer_item'),
> +url(r'^layer/(?P[-\w]+)/recipes/csv/$',
> +layer_export_recipes_csv_view,
> +name='layer_export_recipes_csv'),
>  url(r'^recipes/$',
>  RecipeSearchView.as_view(
>  template_name='layerindex/recipes.html'),
> diff --git a/layerindex/views.py b/layerindex/views.py
> index dbf08497..06d35261 100644
> --- a/layerindex/views.py
> +++ b/layerindex/views.py
> @@ -1022,3 +1022,25 @@ class StatsView(TemplateView):
>  machine_count=Count('layerbranch__machine', distinct=True),
>  distro_count=Count('layerbranch__distro', distinct=True))
>  return context
> +
> +
> +def layer_export_recipes_csv_view(request, branch, slug):
> +import csv
> +layer = get_object_or_404(LayerItem, name=slug)
> +layerbranch = layer.get_layerbranch(branch)
> +
> +response = HttpResponse(content_type='text/csv')
> +response['Content-Disposition'] = 'attachment; 
> filename="recipes_%s_%s.csv"' % (layer.name, layerbranch.branch.name)
> +
> +fieldlist = request.GET.get('fields', 'pn,pv,license').split(',')
> +recipe_fields = [f.name for f in Recipe._meta.get_fields() if not 
> (f.auto_created and f.is_relation)]
> +for field in fieldlist:
> +if field not in recipe_fields:
> +return HttpResponse('Field %s is invalid' % field)
> +
> +writer = csv.writer(response)
> +for recipe in layerbranch.sorted_recipes():
> +values = [getattr(recipe, field) for field in fieldlist]
> +writer.writerow(values)
> +
> +return response
> diff --git a/templates/layerindex/detail.html 
> b/templates/layerindex/detail.html
> index 220d475b..67c21126 100644
> --- a/templates/layerindex/detail.html
> +++ b/templates/layerindex/detail.html
> @@ -199,13 +199,13 @@
>  
>  {{ layeritem.name }} 
> recipes ({{ layerbranch.sorted_recipes.count 
> }})
>  
> -
> -
> -
> - placeholder="Search recipes" class="search-query" id="filter">
> -
> -
> -
> +
> + class="icon-file"> Export CSV
> +
> +
> +
> +
> +
>  
>  
>  
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [dbus] [meta-raspberrypi] using dbus with system verilog

[Sherif Omran]

yes, see below, but my problem is with the systemVinit

DISTRO_FEATURES_append += " bluez5 bluez-utils bluetooth wifi alsa"
IMAGE_INSTALL_append += " linux-firmware-bcm43430 bluez5 bridge-utils
wpa-supplicant python-smbus i2c-tools"
DISTRO_FEATURES_append += " ext2 pulseaudio pam usbhost sbc alsa-plugins
${DISTRO_FEATURES_LIBC} "
PACKAGECONFIG_bluez += " --disable-systemd "
IMAGE_INSTALL_append += " bluez5-testtools bluez5-noinst-tools
libasound-module-bluez packagegroup-base-bluetooth "


IMAGE_INSTALL_append= " bluez5 pulseaudio-server libpulsecore sbc
pulseaudio-module-bluetooth-discover pulseaudio-module-bluez5-device
pulseaudio-module-bluez5-discover pulseaudio-$
DISTRO_FEATURES_remove = " x11 "
IMAGE_INSTALL_append= " screen "

On Mon, May 7, 2018 at 12:18 AM, Khem Raj  wrote:

>
> On Sun, May 6, 2018 at 2:02 AM Sherif Omran 
> wrote:
>
>> hi
>> i created an os for raspberry pi 0 w, it uses system v, but dbus does not
>> start automatically and when i started it using a startup script and
>> exported its parameters, i still get the following when i start pulseaudio
>> -.
>>
>> Unknown interface org.freedesktop.DBUS.Introspectable
>>
>> Unknown interface org.bluez.AgentManager1 found
>>
>> Unknown interface org.bluez.ProfileManager1
>>
>> Unknown interface org.freedesktop.DBUS.Properties found
>>
>> Unknown interace org.bluez.Media1 found
>>
>> Unknown interface org.bluez.NetworkServer1 found
>>
>>
> Have you included bluez in image ?
>
>
>>
>> What is the best way to start dbus? should i edit in kernel configuration?
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

[Alexander Kanavin]

On 05/07/2018 12:03 PM, Mirza Krak wrote:

I have also been bitten by rpm performance issues in docker and glad
that I found this. I am in the process of verifying above (on pyro
branch).

Is this patch on its way to pyro and rocko branches?


As far as I know, no. You are welcome to backport and submit.

Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

[Mirza Krak]

On 4 May 2018 at 14:41, Alexander Kanavin
 wrote:
> On 05/04/2018 03:42 PM, Paulo Neves wrote:
>>
>> I will propose a patch with a default bb.debug, and always have the
>> verbose on dnf. Let's see how it affects the performance. I cannot
>> test this in a docker container because of the problems described
>> below:
>>
>> In the mean time I found what was happening with my slow do_rootfs. I
>> was running bitbake with RPM packaging in a docker instance. It seems
>> there is a problem with RPM/dnf in bitbake where it is extremely slow
>> inside a docker container (1 file per second). After changing to IPK
>> packages everything went smoothly.
>>
>> Others have had the same problem[1]. I will later report this to
>> openembedded mailing list as this effectively makes RPM unusable in a
>> container. I will also provide a Dockerfile to reproduce this problem.
>>
>> [1] https://github.com/moby/moby/issues/23137#issuecomment-359097008
>
>
> No need to report. We have already fixed this and reported upstream:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/rpm/files/0001-Revert-Set-FD_CLOEXEC-on-opened-files-before-exec-fr.patch

I have also been bitten by rpm performance issues in docker and glad
that I found this. I am in the process of verifying above (on pyro
branch).

Is this patch on its way to pyro and rocko branches?

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Help with Bitbake: (bitbake-layers show-recipes)

[Zoran Stojsavljevic]

H... I called my best friend www.google.com to the help, since it seems
to me that you are trying to do Docker, and that you need to set your
kernel differently then it is done by default.

The link I found: definitely worth trying/reading. At least, I should say.

In the book: Embedded Linux Development Using Yocto Project Cookbook:
Practical recipes (Second Edition) By Alex González it says (pages 338 and
339):

Yocto Cookbook page 339


Please, go to the page 339 and read carefully both 338 and 339 pages.

Please, let us all know if this helps! ;-)

Zoran
___

On Mon, Apr 30, 2018 at 6:18 PM, Luis Martins 
wrote:

> Good afternoon,
>
> The path that lead me to bitbake's recipe building is going to be
> presented next, if the setup isn't important the warnings and errors are
> highlited in green and you can skip it to there.
>
> Similar to this thread
> ,
> i'm having some hard time building the openembedded filesystem.
> So far I have managed to follow this tutorial
>  until the
> "Booting the board" section. After running the board some errors appear
> during the execution:
>
> [image: Inline image OWAPstImg945310]
> [image: Inline image OWAPstImg953070]
>
> This lead me to follow the *"Addendum B: Building the OpenEmbedded
> filesysytem from source" *
> (I thought this part was optional since in this section "Initialising a
> workspace" it says "The script will guide you through the process of
> initialising your workspace, automatically downloading all relevant source
> files and required binaries.")
>
> I executed this commands with no problems:
>
> */* Create workspace */*
>
> */* WARNING: Do *not* create this as a subdirectory of the main Linaro Arm
> Platforms workspace created by `workspace_yy.mm '
> above */*
>
> *$ mkdir openembedded*
>
> *$ cd openembedded*
>
> *$ export OE_HOME=`pwd`*
>
> *$ git clone git://git.linaro.org/openembedded/jenkins-setup.git
> *
>
> *$ cd $OE_HOME/jenkins-setup*
>
> *$ git checkout release-YY.MM*
>
> *$ cd $OE_HOME*
>
> *$ sudo jenkins-setup/pre-build-root-install-dependencies.sh*
>
> *$ jenkins-setup/init-and-build.sh*
>
> *$ cd $OE_HOME/openembedded-core*
>
> *$ ./oe-init-build-env*
>
> */* Add bitbake to your $PATH */*
>
> *$ export PATH=$OE_HOME/openembedded-core/bi**tbake/bin:$PATH*
>
>
> But, after running this commands:
>
> *$ cd $OE_HOME/build*
>
> *$ bitbake-layers show-recip**es*
>
>
> I get the following Warnings and Errors (from the log file located in the
> directory /Desktop/openembedded/build/tmp-glibc/log/cooker)):
>
> *WARNING:
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc_2.26.bb
> : Exception during build_dependencies for do_install*
>
> *WARNING:
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc_2.26.bb
> : Error during finalise of
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc_2.26.bb
> *
>
> *WARNING:
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc-initial_2.26.bb
> : Exception during build_dependencies for
> do_install*
>
> *WARNING:
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc-initial_2.26.bb
> : Error during finalise of
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc-initial_2.26.bb
> *
>
> *ERROR: ExpansionError during parsing
> /home/lfpm1993/Desktop/openembedded/meta-linaro/meta-ilp32/recipes-overlayed/glibc/glibc_2.26.bb
> *
>
> *Traceback (most recent call last):*
>
> *bb.data_smart.ExpansionError: Failure expanding variable do_install,
> expression wasoe_runmake
> install_root=/home/lfpm1993/Desktop/openembedded/build/tmp-glibc/work/aarch64-oe-linux/glibc/2.26-r0/image
> install*
>
> *for r in bootparam_prot.x nlm_prot.x rstat.x
>  yppasswd.x klm_prot.x rex.x sm_inter.x mount.x   rusers.x spray.x
> nfs_prot.x rquota.x key_prot.x; do*
>
> *h=`echo $r|sed -e's,\.x$,.h,'`*
>
> *install -m 0644
> /home/lfpm1993/Desktop/openembedded/build/tmp-glibc/work/aarch64-oe-linux/glibc/2.26-r0/git/sunrpc/rpcsvc/$h
>