[yocto] QA cycle report for 2.6.1 RC1

2019-01-21 Thread Jain, Sangeeta


Hello All,



This is the full report for 2.6.1 RC1:



https://wiki.yoctoproject.org/wiki/WW02_-_2019-01-09_-_Full_Test_Cycle_2.6.1_RC1





=== Summary 



All planned tests were executed.

Total Test Executed - 3650

Passed Test - 3422

Failed Test - 210

Blocked Test - 12





There were zero high milestone defect.  Team had found 1 new defects coming 
from missing package 'gpg' [1].



For ptest, team had confirmed that there were no tests which passed in 2.6 M4 
while failed in current 2.6.1 rc1. Issues in qa-tools/ptest-parser script used 
to generate comparison table is fixed and script is now working fine.





=== QA-Hints



No high milestone defect.
One of the SDK test cases "/poky/meta/lib/oeqa/sdk/cases/python.py", while 
executed, is giving a result "unknown". We are not sure about the reason of 
this behavior and investigating more into it. This test case is a part of seven 
ADT test plans.



=== Bugs 



New Bugs

[1] Bug 13143 - [Bug] [2.6.1 rc1] bitbake core-image-minimal failed because no 
module named 'gpg' on CentOS 7 and OpenSuse 42.3

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13143



Previous Bugs observed in this release:



[2] Bug 13102 - [Bug][QA 2.7 M1 rc1][Toaster] All layers are not getting 
populated after clicking "View compatible layers" on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13102



[3] Bug 13103 - [Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" 
table are not getting populated after clicking on imported layer as well as 
after clicking Machines Tab on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13103



[4] Bug 13104 - [Bug][QA 2.7 M1 rc1][Toaster] All "Image Recipes" are not 
getting populated after clicking  "Image Recipes"  on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13104



[5] Bug 12991 - [Bug] 
[2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed 
during building image due to webkitgtk package.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



[6] Bug 12499 - [Bug] 
[2.5 M1 RC3] qemuarm: failed to shutdown.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499




Thanks & Regards,
Sangeeta Jain

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


Re: [yocto] [meta-mingw][PATCH V2] testsdk: enhance extract sdk part

2019-01-21 Thread Changqing Li

On 1/21/19 10:47 PM, Joshua Watt wrote:

Just FYI, I haven't forgot about this patch. I want to wait until the
dependent OE-core patch is at least in the master-next branch before I
apply this to the MinGW master-next branch. If you want to give me a
ping when the OE-core patch shows up in master-next, it would be very
helpful.

Thanks


Yes, I will do it.



On Thu, 2019-01-17 at 17:49 +0800, changqing...@windriver.com wrote:

From: Changqing Li 

Current sdk type is tar.xz, but for mingw sdk, since we
have symlink under the sdk folder, 7zip which used to
extract tar.xz cannot handle it, refer 7zip upstream bug:
https://sourceforge.net/p/sevenzip/discussion/45797/thread/c71d6b96/
so oe-core have add support of change SDK type to .zip, so correct
the extract function.

Signed-off-by: Changqing Li 
---
  lib/oeqa/sdkmingw/testsdk.py | 11 +--
  1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/lib/oeqa/sdkmingw/testsdk.py
b/lib/oeqa/sdkmingw/testsdk.py
index 85fe3c6..173cfd9 100644
--- a/lib/oeqa/sdkmingw/testsdk.py
+++ b/lib/oeqa/sdkmingw/testsdk.py
@@ -12,7 +12,7 @@ class TestSDKMinGW(TestSDK):
  """
  Get the name of the SDK file
  """
-return
d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.tar.xz")
+return
d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.${SDK_ARCHIVE_TYPE}")
  
  def extract_sdk(self, tcname, sdk_dir, d):

  """
@@ -23,7 +23,14 @@ class TestSDKMinGW(TestSDK):
  try:
  # TODO: It would be nice to try and extract the SDK in
Wine to make
  # sure it is well formed
-subprocess.check_output(['tar', '-xf', tcname, '-C',
sdk_dir])
+
+# TODO: Extract SDK according to SDK_ARCHIVE_TYPE, need
to change if
+# oe-core support other types.
+if d.getVar("SDK_ARCHIVE_TYPE") == "zip":
+subprocess.check_output(['unzip', '-d', sdk_dir,
tcname])
+else:
+subprocess.check_output(['tar', '-xf', tcname, '-C',
sdk_dir])
+
  except subprocess.CalledProcessError as e:
  bb.fatal("Couldn't install the SDK:\n%s" %
e.output.decode("utf-8"))
  
--

2.7.4


--
BRs

Sandy(Li Changqing)

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


[yocto] nativesdk questions

2019-01-21 Thread Steve Scott
Hi all:

I am using the jethro (2.0.1) version of yocto.

I added a shared library (foo.so) to our native sdk build by putting
BBCLASSEXTEND = "nativesdk"
in the foo.bb recipe, then 
TOOLCHAIN_HOST_TASK_append += " nativesdk-foo  nativesdk-foo-dev "
in our rootfs image recipe.

This had the effect of not only including my library and its header files,
but also a huge number of other
header files in my native sdk's
.../sysroots/x86_64-pokysdk-linux/usr/include
that weren't there previously. It looks like they are the header files for
the components of the GNU C library.

Questions:
1. What is causing all these additional header files to show up in my native
sdk usr/include directory?
2. Is there some way to turn this off?
3. Is the native toolchain  included in the native sdk (the cross compiler
tools
 are there, but I didn't see the native ones).
4. If the native toolchain isn't in the native sdk, how do I find the native
tool chain inside the Yocto tree?

Thanks.

-steve


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


Re: [yocto] [ptest-runner] ptest-runner: make DEFAULT_DIRECTORY be able to be defined when compiling

2019-01-21 Thread Anibal Limon
Pushed, thx!,

http://git.yoctoproject.org/cgit/cgit.cgi/ptest-runner2/commit/?id=e1062f776eea60c50435c6b8ddf9714a31141aee

Feel free to update the recipe.

Cheers,
Anibal

On Sun, 20 Jan 2019 at 20:29, Li Zhou  wrote:

> In yocto project ptest data are installed to
> PTEST_PATH ?= "${libdir}/${BPN}/ptest". Here make DEFAULT_DIRECTORY
> be able to be defined outside of c code (e.g. passed in by CFLAGS),
> in case libdir isn't "/usr/lib", which will cause "No ptests found"
> error when running "ptest-runner" command. We will pass libdir to
> DEFAULT_DIRECTORY when compiling to avoid that error.
>
> Signed-off-by: Li Zhou 
> ---
>  main.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/main.c b/main.c
> index 83600b7..e963efe 100644
> --- a/main.c
> +++ b/main.c
> @@ -37,7 +37,9 @@
>
>  #include "utils.h"
>
> +#ifndef DEFAULT_DIRECTORY
>  #define DEFAULT_DIRECTORY "/usr/lib"
> +#endif
>  #define DEFAULT_TIMEOUT 300
>
>  static inline void
> --
> 1.9.1
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Unassigned Bugs - Help Needed

2019-01-21 Thread Jolley, Stephen K
All,



The triage team meets weekly and does its best to handle the bugs reported into 
the Bugzilla. The number of people attending that meeting has fallen, as have 
the number of people available to help fix bugs. One of the things we hear 
users report is they don't know how to help. We (the triage team) are therefore 
going to start reporting out the currently 295 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out 
with these.



Bugs are split into two types, "true bugs" where things don't work as they 
should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", 
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and 
then "2.8".



Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me 
(stephen.k.jol...@intel.com) an e-mail with 
the bug number you would like and I will assign it to you (please make sure you 
have a Bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program 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] Community support for any Yocto release

2019-01-21 Thread Lukasz Zemla
> Hi All,
> For how many years yocto community officially support any Yocto 
> release? (This includes like bug fixes, CVE fixes, enhancements, etc etc) For 
> example, the latest release happened on 11/15/2018 (Yocto 2.6), so how long 
> this will be supported by community?
> Sorry, if this information is already present on some wiki page, but I am not 
> able to find it. So pointer to that wiki page will really help.
> Regards,
> Gaurang Shastri

https://wiki.yoctoproject.org/wiki/Frequently_Asked_Release_Engineering_Questions#How_long_are_point_releases_supported
 

Best regards,
Lukasz Zemla

***
The information in this email is confidential and intended solely for the 
individual or entity to whom it is addressed.  If you have received this email 
in error please notify the sender by return e-mail, delete this email, and 
refrain from any disclosure or action based on the information.
***
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Build error after changing PACKAGE_CLASSES to package_deb

2019-01-21 Thread Khem Raj
this is the problem

dpkg-deb: error: package name has characters that aren't lowercase
alphanums or '-+.'

its possible that linux-imx is adding some string to PR which is not
honoring this convention usually introduced by setting EXTRAVERSION in
kernel toplevel makefile

On Mon, Jan 21, 2019 at 8:15 AM srinivasan  wrote:
>
> Dear Yocto Experts Team,
>
> I am seeing the below error after changing the package_classes from "rpm" to 
> "deb" as below, when I am trying to add freescale meta layers to my custom 
> yocto distribution
>
> Could you please do the needful by providing some inputs in resolving the 
> below issue?
>
> Logs:
> WARNING: Host distribution "ubuntu-18.04" has not been validated with this 
> version of the build system; you may possibly experience unexpected failures. 
> It is recommended that you use a tested distribution.
> Parsing recipes: 100% 
> |#|
>  Time: 0:00:15
> Parsing of 2304 .bb files complete (0 cached, 2304 parsed). 3210 targets, 385 
> skipped, 6 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION   = "1.38.0"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBSTRING  = "ubuntu-18.04"
> TARGET_SYS   = "aarch64-poky-linux"
> MACHINE  = "imx8mmevk"
> DISTRO   = "NativeOS-TRK"
> DISTRO_VERSION   = "1.0.8"
> TUNE_FEATURES= "aarch64"
> TARGET_FPU   = ""
> meta-traktor-imx8= "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
> meta-traktor = "sumo:b91788da6bd52485faa85bb19bc7a9a1ddf2ee5d"
> meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
> meta-nativeos= "sumo:8a14b16e4049051e29009e67afa63bfac5ddb26e"
> meta-freescale   = "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
> meta
> meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
> meta-oe
> meta-python
> meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
> meta-bsp
> meta-sdk = "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
>
> Initialising tasks: 100% 
> |##|
>  Time: 0:00:05
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: linux-imx-4.14.62-r0 do_package_write_deb: Error executing a python 
> function in exec_python_func() autogenerated:
>
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'exec_python_func() autogenerated', lineno: 2, function: 
>  0001:
>  *** 0002:do_package_deb(d)
>  0003:
> File: 
> '/home/srinishanmugam/nibuild_test/nativeos/sources/poky/meta/classes/package_deb.bbclass',
>  lineno: 102, function: do_package_deb
>  0098:
>  0099:os.chdir(oldcwd)
>  0100:
>  0101:if error:
>  *** 0102:raise error
>  0103:}
>  0104:do_package_deb[vardeps] += "deb_write_pkg"
>  0105:do_package_deb[vardepsexclude] = "BB_NUMBER_THREADS"
>  0106:
> Exception: subprocess.CalledProcessError: Command 
> 'PATH="/home/srinishanmugam/nibuild_test/nativeos/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/srinishanmugam/nibuild_test/nativeos/sources/poky/scripts:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot/usr/bin/crossscripts:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/sbin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/bin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/sbin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/r
 
ecipe-sysroot-native/bin:/home/srinishanmugam/nibuild_test/nativeos/sources/poky/bitbake/bin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/hosttools"
 dpkg-deb -b 
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/packages-split/kernel-module-snd-usbmidi-lib-4.14.62-imx_4.14.62_1.0.0_beta+g1907fe4c3287
 
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/deploy-debs/imx8mmevk'
 returned non-zero exit status 2.
>
> Subprocess output:
> dpkg-deb: error: package name has characters that aren't lowercase 

Re: [yocto] Using old version of Recipe with new Yocto Release

2019-01-21 Thread Burton, Ross
That's because we now prune what tools the recipes can see on the
host, and cc isn't on the list.  Override cc to be ${BUILD_CC} and
this will work.

Ross

On Mon, 21 Jan 2019 at 16:14, Johannes Humpert
 wrote:
>
> Hallo Yocto,
>
> Is it possible to use old versions of the recipe with newer yocto releases? 
> For example, I am currently trying to compile a 2015.01 version of the U-boot 
> recipe with the Yocto Sumo release, but unfortunately it throws a compilation 
> error that oe-runmake failed. Could anyone please guide me with this issue.
>
> The build config is as follows:
>
> Build Configuration:
> BB_VERSION   = "1.37.0"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBSTRING  = "universal-4.8"
> TARGET_SYS   = "arm-poky-linux-gnueabi"
> MACHINE  = "arm-cortex-a8"
> DISTRO   = "poky"
> DISTRO_VERSION   = "2.5"
> TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"
> TARGET_FPU   = "hard"
> meta
> meta-poky
> meta-yocto-bsp
> meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"
>
> The error log message is as follows:
>
> DEBUG: Executing shell function do_compile
> NOTE: make -j 2 CROSS_COMPILE=arm-poky-linux-gnueabi- 
> CC=arm-poky-linux-gnueabi-gcc  
> --sysroot=/source/yocto/build/tmp/work/arm_cortex_a8-poky-linux-gnueabi/u-boot/v2015.01+gitAUTOINC+92fa7f53f1-r0/recipe-sysroot
>  V=1 KCFLAGS=-fgnu89-inline am335x_evm_config
> make -f ./scripts/Makefile.build obj=scripts/basic
>   cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2 
> -fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c
> /bin/sh: cc: command not found
> make[1]: *** [scripts/Makefile.host:91: scripts/basic/fixdep] Error 127
> make: *** [Makefile:390: scripts_basic] Error 2
> ERROR: oe_runmake failed
> WARNING: 
> /source/yocto/build/tmp/work/arm_cortex_a8-poky-linux-gnueabi/u-boot/v2015.01+gitAUTOINC+92fa7f53f1-r0/temp/run.do_compile.20414:1
>  exit 1 from 'exit 1'
> ERROR: Function failed: do_compile (log file is located at 
> /source/yocto/build/tmp/work/arm_cortex_a8-poky-linux-gnueabi/u-boot/v2015.01+gitAUTOINC+92fa7f53f1-r0/temp/log.do_compile.20414)
>
> Thanks,
> -Johannes
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Build error after changing PACKAGE_CLASSES to package_deb

2019-01-21 Thread srinivasan
Dear Yocto Experts Team,

I am seeing the below error after changing the package_classes from "rpm"
to "deb" as below, when I am trying to add freescale meta layers to my
custom yocto distribution

Could you please do the needful by providing some inputs in resolving the
below issue?

Logs:
WARNING: Host distribution "ubuntu-18.04" has not been validated with this
version of the build system; you may possibly experience unexpected
failures. It is recommended that you use a tested distribution.
Parsing recipes: 100%
|#|
Time: 0:00:15
Parsing of 2304 .bb files complete (0 cached, 2304 parsed). 3210 targets,
385 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "ubuntu-18.04"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "NativeOS-TRK"
DISTRO_VERSION   = "1.0.8"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
meta-traktor = "sumo:b91788da6bd52485faa85bb19bc7a9a1ddf2ee5d"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-nativeos= "sumo:8a14b16e4049051e29009e67afa63bfac5ddb26e"
meta-freescale   = "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "master:525bab5e576c2f0f1242cd1e6b546859c856441a"

Initialising tasks: 100%
|##|
Time: 0:00:05
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: linux-imx-4.14.62-r0 do_package_write_deb: Error executing a python
function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_package_deb(d)
 0003:
File:
'/home/srinishanmugam/nibuild_test/nativeos/sources/poky/meta/classes/package_deb.bbclass',
lineno: 102, function: do_package_deb
 0098:
 0099:os.chdir(oldcwd)
 0100:
 0101:if error:
 *** 0102:raise error
 0103:}
 0104:do_package_deb[vardeps] += "deb_write_pkg"
 0105:do_package_deb[vardepsexclude] = "BB_NUMBER_THREADS"
 0106:
Exception: subprocess.CalledProcessError: Command
'PATH="/home/srinishanmugam/nibuild_test/nativeos/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/srinishanmugam/nibuild_test/nativeos/sources/poky/scripts:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot/usr/bin/crossscripts:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/sbin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/bin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/sbin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/bin:/home/srinishanmugam/nibuild_test/nativeos/sources/poky/bitbake/bin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/hosttools"
dpkg-deb -b
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/packages-split/kernel-module-snd-usbmidi-lib-4.14.62-imx_4.14.62_1.0.0_beta+g1907fe4c3287
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/deploy-debs/imx8mmevk'
returned non-zero exit status 2.

Subprocess output:
dpkg-deb: error: package name has characters that aren't lowercase
alphanums or '-+.'

ERROR: linux-imx-4.14.62-r0 do_package_write_deb: Function failed:
do_package_deb
ERROR: Logfile of failure stored in:
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/temp/log.do_package_write_deb.31568
ERROR: Task
(/home/srinishanmugam/nibuild_test/nativeos/sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-kernel/linux/linux-imx_4.14.62.bb:do_package_write_deb)
failed with exit code '1'
NOTE: Tasks Summary: 

[yocto] Using old version of Recipe with new Yocto Release

2019-01-21 Thread Johannes Humpert
Hallo Yocto,

Is it possible to use old versions of the recipe with newer yocto releases?
For example, I am currently trying to compile a 2015.01 version of the
U-boot recipe with the Yocto Sumo release, but unfortunately it throws a
compilation error that oe-runmake failed. Could anyone please guide me with
this issue.

The build config is as follows:

*Build Configuration:*
*BB_VERSION   = "1.37.0"*
*BUILD_SYS= "x86_64-linux"*
*NATIVELSBSTRING  = "universal-4.8"*
*TARGET_SYS   = "arm-poky-linux-gnueabi"*
*MACHINE  = "arm-cortex-a8"*
*DISTRO   = "poky"*
*DISTRO_VERSION   = "2.5"*
*TUNE_FEATURES= "arm armv7a vfp neon callconvention-hard cortexa8"*
*TARGET_FPU   = "hard"   *
*meta *
*meta-poky*
*meta-yocto-bsp   *
*meta-oe  = "master:45ee3c0e98bd3ed81419aaeae1e7324e486161a2"*

The error log message is as follows:

*DEBUG: Executing shell function do_compile*
*NOTE: make -j 2 CROSS_COMPILE=arm-poky-linux-gnueabi-
CC=arm-poky-linux-gnueabi-gcc
--sysroot=/source/yocto/build/tmp/work/arm_cortex_a8-poky-linux-gnueabi/u-boot/v2015.01+gitAUTOINC+92fa7f53f1-r0/recipe-sysroot
V=1 KCFLAGS=-fgnu89-inline am335x_evm_config*
*make -f ./scripts/Makefile.build obj=scripts/basic*
*  cc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -o scripts/basic/fixdep scripts/basic/fixdep.c  *
*/bin/sh: cc: command not found*
*make[1]: *** [scripts/Makefile.host:91: scripts/basic/fixdep] Error 127*
*make: *** [Makefile:390: scripts_basic] Error 2*
*ERROR: oe_runmake failed*
*WARNING:
/source/yocto/build/tmp/work/arm_cortex_a8-poky-linux-gnueabi/u-boot/v2015.01+gitAUTOINC+92fa7f53f1-r0/temp/run.do_compile.20414:1
exit 1 from 'exit 1'*
*ERROR: Function failed: do_compile (log file is located at
/source/yocto/build/tmp/work/arm_cortex_a8-poky-linux-gnueabi/u-boot/v2015.01+gitAUTOINC+92fa7f53f1-r0/temp/log.do_compile.20414)*

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


[yocto] [ptest-runner] ptest-runner: make DEFAULT_DIRECTORY be able to be defined when compiling

2019-01-21 Thread Li Zhou
In yocto project ptest data are installed to
PTEST_PATH ?= "${libdir}/${BPN}/ptest". Here make DEFAULT_DIRECTORY
be able to be defined outside of c code (e.g. passed in by CFLAGS),
in case libdir isn't "/usr/lib", which will cause "No ptests found"
error when running "ptest-runner" command. We will pass libdir to
DEFAULT_DIRECTORY when compiling to avoid that error.

Signed-off-by: Li Zhou 
---
 main.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/main.c b/main.c
index 83600b7..e963efe 100644
--- a/main.c
+++ b/main.c
@@ -37,7 +37,9 @@
 
 #include "utils.h"
 
+#ifndef DEFAULT_DIRECTORY
 #define DEFAULT_DIRECTORY "/usr/lib"
+#endif
 #define DEFAULT_TIMEOUT 300
 
 static inline void
-- 
1.9.1

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


Re: [yocto] [meta-freescale] ERROR: Nothing PROVIDES 'virtual/libgles2'

2019-01-21 Thread srinivasan
imx8mmevk

On Fri, Jan 18, 2019 at 12:20 PM Daiane Angolini  wrote:
>
> On Fri, Jan 18, 2019 at 6:46 AM srinivasan  wrote:
> >
> > Dear Yocto Experts,
> >
> > I am seeing the below error when i am trying to integrate freescale
> > layers into my custom os?
>
> Which imx8 MACHINE are you trying?
>
> Daiane
> >
> > srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
> > bitbake -f -c clean custom-image-debug-imx8
> > WARNING: Host distribution "ubuntu-18.04" has not been validated with
> > this version of the build system; you may possibly experience
> > unexpected failures. It is recommended that you use a tested
> > distribution.
> > WARNING: 
> > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
> > Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
> > file could not be found
> >   | ETA:  0:00:05
> > Parsing recipes: 100%
> > |#|
> > Time: 0:00:09
> > Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
> > targets, 382 skipped, 1 masked, 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> > ERROR: Nothing PROVIDES 'virtual/libgles2' (but
> > /home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
> > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
> > DEPENDS on or otherwise requires it)
> > imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
> > with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> > NOTE: Runtime target 'qtbase' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['qtbase', 'virtual/libgles2']
> > ERROR: Required build target 'custom-image-debug-imx8' has no
> > buildable providers.
> > Missing or unbuildable dependency chain was:
> > ['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']
> >
> > Summary: There were 2 WARNING messages shown.
> > Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> >
> >
> > Could you anyone please provide me some inputs for resolving the above 
> > issue?
> >
> > Many Thanks in advance
> > --
> > ___
> > meta-freescale mailing list
> > meta-freesc...@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-freescale
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] ERROR: Nothing PROVIDES 'virtual/libgles2'

2019-01-21 Thread srinivasan
Dear Yocto Experts,

I am seeing the below error when i am trying to integrate freescale
layers into my custom os?

srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
bitbake -f -c clean custom-image-debug-imx8
WARNING: Host distribution "ubuntu-18.04" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
WARNING: 
/home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
file could not be found
  | ETA:  0:00:05
Parsing recipes: 100%
|#|
Time: 0:00:09
Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
targets, 382 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'virtual/libgles2' (but
/home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
/home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
DEPENDS on or otherwise requires it)
imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
with machine imx8mmevk (not in COMPATIBLE_MACHINE)
NOTE: Runtime target 'qtbase' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['qtbase', 'virtual/libgles2']
ERROR: Required build target 'custom-image-debug-imx8' has no
buildable providers.
Missing or unbuildable dependency chain was:
['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']

Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


Could you anyone please provide me some inputs for resolving the above issue?

Many Thanks in advance
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-intel] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

2019-01-21 Thread srinivasan
Thanks a ton Ross, your inputs really worked :)

On Tue, Jan 15, 2019 at 11:34 AM Burton, Ross  wrote:
>
> You'll have to not install either connman or network manager.
>
> Ross
>
> On Tue, 15 Jan 2019 at 05:18, srinivasan  wrote:
> >
> > Dear Yocto experts,
> >
> > I am seeing the below error when I am trying to integrate the
> > "fsl-image-validation-imx.bb" into my custom yocto build and trigger
> > the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel
> > networkmanager is conflicting with conman, could you please let me
> > know how this issue can be resolved?
> >
> > I have attached the recipe files for your information
> >
> > Error:
> >
> > ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf.
> > Command 
> > '/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf
> > -y -c 
> > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf
> > --setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d
> > --repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
> > --installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs
> > --setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp
> > --nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo
> > bash basicquick bc binutils binutils-symlinks bmap-tools-git
> > build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf
> > dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git
> > glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw
> > kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts
> > libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c
> > libsensors4 lmsensors-sensors lsof lttng-modules make memtester
> > merge-files nano networkmanager ni-isolcpus ninja openssl
> > packagegroup-base-extended packagegroup-core-boot
> > packagegroup-core-full-cmdline packagegroup-core-sdk
> > packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target
> > packagegroup-core-tools-debug packagegroup-core-tools-profile
> > packagegroup-core-tools-testapps packagegroup-fsl-optee-imx
> > packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external
> > packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps
> > psplash python python-dbus python-modules python-pandas python-pip
> > python3 python3-dbus python3-misc python3-modules python3-pip
> > python3-psutil python3-robotframework python3-six qt3d qt3d-dev
> > qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins
> > qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs
> > qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative
> > qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects
> > qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev
> > qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev
> > qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs
> > rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress
> > sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount
> > unzip usbreset usbutils util-linux valgrind wget wireless-tools
> > wpa-supplicant zip libz1 locale-base-en-us' returned 1:
> > Added oe-repo repo from
> > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
> > Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM 
> > UTC.
> > Error:
> >  Problem: package connman-tools-1.35-r0.aarch64 requires connman, but
> > none of the providers can be installed
> >   - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires
> > connman-tools, but none of the providers can be installed
> >   - package networkmanager-1.10.6-r0.aarch64 conflicts with connman
> > provided by connman-1.35-r0.aarch64
> >   - conflicting requests
> > (try to add '--allowerasing' to command line to replace conflicting
> > packages or '--skip-broken' to skip uninstallable packages)
> >
> > ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs
> > ERROR: Logfile of failure stored in:
> > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp/log.do_rootfs.56617
> > ERROR: Task 
> > (/home/user/test/os/sources/meta-custom-imx8/recipes-core/images/custom-image-debug-imx8.bb:do_rootfs)
> > failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 8016 tasks of which 7974 didn't need to
> > be rerun and 1 failed.
> >
> > Many Thanks in advance,

[yocto] Error: base-files/3.0.14-r89/temp/run.do_install.80432: Syntax error: Unterminated quoted string

2019-01-21 Thread srinivasan
Dear Yocto Experts,

I am trying to customize my vendor specific Yocto BSP's to my custom
OS.  I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue

Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution "ubuntu-18.04" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Loading cache: 100%
|###|
Time: 0:00:00
Loaded 3196 entries from dependency cache.
Parsing recipes: 100%
|#|
Time: 0:00:02
Parsing of 2298 .bb files complete (2284 cached, 14 parsed). 3202
targets, 398 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "custom-TRK"
DISTRO_VERSION   = "${custom_DISTRO_VERSION}"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "sumo:4b25c1ee6896b5447f8502f13c28570341505360"
meta-traktor = "sumo:818be7ec4f768ba485e437dc26beb7bdc4b8120a"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-custom= "sumo:d98452914e201d46a6b1360ca957d9b3e396b31f"
meta-freescale   = "HEAD:1deea6b4a2f83521ff247ea4743d09cc705ecd8e"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "HEAD:1de93d3d5128b8422c23a87cb8b54149e2bfb942"

Initialising tasks: 100%
|##|
Time: 0:00:02
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: base-files-3.0.14-r89 do_install: Function failed: do_install
(log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Logfile of failure stored in:
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
'virtual:native:/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
176: 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
Syntax error: Unterminated quoted string
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Task 
(/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1256 tasks of which 1204 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8$


Kindly do the needful,
Many Thanks in advance
-- 
___
yocto mailing list
yocto@yoctoproject.org

[yocto] (rocko) python3-pycario : Waf cannot unpacked

2019-01-21 Thread Geonho Kim
Hi,

I have some build error problem.
Now, I have working on rocko release.
When I have built, I met this error message

build_src/tmp/work/aarch64-poky-linux/python3-pycairo/1.10.0-r2/temp/log.do_configure.81617
Log data follows:
| DEBUG:Executing shell function do_configure
| sh :1: bunzip2: not found
| Error: Waf cannot be unpacked, check that bzip2 support is preset.
..

It seems that uninstalled bzip2 to host and sysroot-native area, but bzip2
is installed to
host pc and sysroot-native location.

Do you know how to fix this?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Community support for any Yocto release

2019-01-21 Thread Gaurang Shastri
Hi All,

For how many years yocto community officially support any Yocto release?
(This includes like bug fixes, CVE fixes, enhancements, etc etc)

For example, the latest release happened on 11/15/2018 (Yocto 2.6), so how
long this will be supported by community?

Sorry, if this information is already present on some wiki page, but I am
not able to find it. So pointer to that wiki page will really help.

Regards,
Gaurang Shastri
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [linux-yocto] [kernel-cache][PATCH 0/2] qemuarm: config changes needed for rename

2019-01-21 Thread Bruce Ashfield

On 1/18/19 4:45 PM, Jon Mason wrote:

Last 2 config patches needed for the upcoming rename.  The first one
allows for the current qemuarm to be renamed qemuarmv5, while keeping
the existing name for those who still want to access it that way for
legacy reasons.  The second one adds defconfigs for tiny and RT, as well
as adding the kmachine name to allow for qemuarma15 to be renamed to
qemuarm.



I had meant to follow up on this on Friday but got bogged down.

I was able to do some test builds and things looked sane here.

I do have one question, once this series is applied both the
arm-versatile-926ejs-standard and the new qemuarma15-standard will
match for "qemuarm". So there may be a bit of filesystem ordering
issue and non deterministic build happening.

I know that you want to do the rename, but what from what I can see,
I could drop the qemuarm from the versatile fragments now without
too much problem .. thoughts ?

Bruce



Jon Mason (2):
   qemuarm: Add qemuarmv5 kmachine name
   qemuarma15: Add Real-Time and Tiny configs

  .../arm-versatile-926ejs-preempt-rt.scc |  1 +
  .../arm-versatile-926ejs-standard.scc   |  1 +
  .../arm-versatile-926ejs-tiny.scc   |  1 +
  bsp/qemuarma15/qemuarma15-preempt-rt.scc| 13 +
  bsp/qemuarma15/qemuarma15-standard.scc  |  1 +
  bsp/qemuarma15/qemuarma15-tiny.scc  | 13 +
  6 files changed, 30 insertions(+)
  create mode 100644 bsp/qemuarma15/qemuarma15-preempt-rt.scc
  create mode 100644 bsp/qemuarma15/qemuarma15-tiny.scc



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


Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.25

2019-01-21 Thread Bruce Ashfield

On 1/18/19 9:20 AM, Paul Gortmaker wrote:

Bruce, Yocto kernel folks:

Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.24 release.

There are about 125 commits here, based on commits chosen from what
was used in the existing 4.19.15 stable release.

I've put this 4.18.x queue through the usual testing; build testing
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
and finally some sanity runtime tests on x86-64.

I did the signed tag just as per the previously released versions.
Please find a signed v4.18.25 tag using this key:



Thanks Paul, this is now merged.

Bruce


http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6

in the repo in the kernel.org directory here:

https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/
git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git

for merge to standard/base in linux-yocto-4.18 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 4.18.x release.

Paul.



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


Re: [linux-yocto] [PATCH] Revert "igb: reduce CPU0 latency when updating statistics"

2019-01-21 Thread Bruce Ashfield

On 1/21/19 8:55 AM, He Zhe wrote:



On 1/21/19 9:47 PM, Bruce Ashfield wrote:

Which kernel/bsp branch is this one for ? I'm about to push an
update to linux-yocto-dev today, so from the comment below, it
looks like we are already covered ?


This is for standard/base. It's from v5.0-rc3.


ok. so we are covered, I just updated linux-yocto-dev:

[/home/bruc...to-dev.git]> git push --tags origin
Counting objects: 2, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 1.10 KiB | 0 bytes/s, done.
Total 2 (delta 0), reused 2 (delta 0)
To ssh://g...@git.yoctoproject.org/linux-yocto-dev.git
 * [new tag]   v5.0-rc2 -> v5.0-rc2
 * [new tag]   v5.0-rc3 -> v5.0-rc3

Bruce



Zhe



Bruce

On 1/21/19 5:09 AM, zhe...@windriver.com wrote:

From: Jeff Kirsher 

This reverts commit 59361316afcb08569af21e1af83e89c7051c055a.

Due to problems found in additional testing, this causes an illegal
context switch in the RCU read-side critical section.

CC: Dave Jones 
CC: Cong Wang 
CC: Jan Jablonsky 
Signed-off-by: Jeff Kirsher 
Signed-off-by: David S. Miller 

commit 5642e27bf6a935c1d0d9149e83d625dfba286463 upstream

Before syncing up with 5.0-rc3, it's worth backporting this patch which fixes
the following serious crash.
yow-bashfiel-d4 [/home/bruc...to-dev.git]> git push --tags origin

DISPLAY "(null)" invalid; disabling X11 forwarding
Counting objects: 2, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (2/2), 1.10 KiB | 0 bytes/s, done.
Total 2 (delta 0), reused 2 (delta 0)
To ssh://g...@git.yoctoproject.org/linux-yocto-dev.git
 * [new tag]   v5.0-rc2 -> v5.0-rc2
 * [new tag]   v5.0-rc3 -> v5.0-rc3


BUG: sleeping function called from invalid context at kernel/locking/mutex.c:254
in_atomic(): 0, irqs_disabled(): 0, pid: 7867, name: ifconfig
Preemption disabled at:
[] memcg_kmem_put_cache+0x2e/0x70
 snip 
Call Trace:
   dump_stack+0x4f/0x6a
   ? memcg_kmem_put_cache+0x2e/0x70
   ___might_sleep.cold.17+0xd9/0xea
   __might_sleep+0x4a/0x80
   mutex_lock+0x20/0x40
   igb_get_stats64+0x2c/0x60
   dev_get_stats+0x3f/0xa0
   dev_seq_printf_stats+0x37/0xe0
   dev_seq_show+0x14/0x30
   seq_read+0x2d3/0x3e0
   proc_reg_read+0x3e/0x60
   __vfs_read+0x3a/0x180
   ? security_file_permission+0x9c/0xf0
   vfs_read+0xa1/0x160
   ksys_read+0x55/0xc0
   __x64_sys_read+0x1a/0x20
   do_syscall_64+0x4d/0xf0
   entry_SYSCALL_64_after_hwframe+0x44/0xa9

Signed-off-by: He Zhe 
---
   drivers/net/ethernet/intel/igb/igb.h |  2 +-
   drivers/net/ethernet/intel/igb/igb_ethtool.c |  4 ++--
   drivers/net/ethernet/intel/igb/igb_main.c    | 14 +++---
   3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/drivers/net/ethernet/intel/igb/igb.h 
b/drivers/net/ethernet/intel/igb/igb.h
index fe1592a..ca54e26 100644
--- a/drivers/net/ethernet/intel/igb/igb.h
+++ b/drivers/net/ethernet/intel/igb/igb.h
@@ -515,7 +515,7 @@ struct igb_adapter {
   /* OS defined structs */
   struct pci_dev *pdev;
   -    struct mutex stats64_lock;
+    spinlock_t stats64_lock;
   struct rtnl_link_stats64 stats64;
     /* structs defined in e1000_hw.h */
diff --git a/drivers/net/ethernet/intel/igb/igb_ethtool.c 
b/drivers/net/ethernet/intel/igb/igb_ethtool.c
index 7426060..c576710 100644
--- a/drivers/net/ethernet/intel/igb/igb_ethtool.c
+++ b/drivers/net/ethernet/intel/igb/igb_ethtool.c
@@ -2295,7 +2295,7 @@ static void igb_get_ethtool_stats(struct net_device 
*netdev,
   int i, j;
   char *p;
   -    mutex_lock(>stats64_lock);
+    spin_lock(>stats64_lock);
   igb_update_stats(adapter);
     for (i = 0; i < IGB_GLOBAL_STATS_LEN; i++) {
@@ -2338,7 +2338,7 @@ static void igb_get_ethtool_stats(struct net_device 
*netdev,
   } while (u64_stats_fetch_retry_irq(>rx_syncp, start));
   i += IGB_RX_QUEUE_STATS_LEN;
   }
-    mutex_unlock(>stats64_lock);
+    spin_unlock(>stats64_lock);
   }
     static void igb_get_strings(struct net_device *netdev, u32 stringset, u8 
*data)
diff --git a/drivers/net/ethernet/intel/igb/igb_main.c 
b/drivers/net/ethernet/intel/igb/igb_main.c
index 87bdf16..7137e7f 100644
--- a/drivers/net/ethernet/intel/igb/igb_main.c
+++ b/drivers/net/ethernet/intel/igb/igb_main.c
@@ -2203,9 +2203,9 @@ void igb_down(struct igb_adapter *adapter)
   del_timer_sync(>phy_info_timer);
     /* record the stats before reset*/
-    mutex_lock(>stats64_lock);
+    spin_lock(>stats64_lock);
   igb_update_stats(adapter);
-    mutex_unlock(>stats64_lock);
+    spin_unlock(>stats64_lock);
     adapter->link_speed = 0;
   adapter->link_duplex = 0;
@@ -3840,7 +3840,7 @@ static int igb_sw_init(struct igb_adapter *adapter)
   adapter->min_frame_size = ETH_ZLEN + ETH_FCS_LEN;
     spin_lock_init(>nfc_lock);
-    mutex_init(>stats64_lock);
+    spin_lock_init(>stats64_lock);
   #ifdef 

Re: [yocto] [meta-mingw][PATCH V2] testsdk: enhance extract sdk part

2019-01-21 Thread Joshua Watt
Just FYI, I haven't forgot about this patch. I want to wait until the
dependent OE-core patch is at least in the master-next branch before I
apply this to the MinGW master-next branch. If you want to give me a
ping when the OE-core patch shows up in master-next, it would be very
helpful.

Thanks

On Thu, 2019-01-17 at 17:49 +0800, changqing...@windriver.com wrote:
> From: Changqing Li 
> 
> Current sdk type is tar.xz, but for mingw sdk, since we
> have symlink under the sdk folder, 7zip which used to
> extract tar.xz cannot handle it, refer 7zip upstream bug:
> https://sourceforge.net/p/sevenzip/discussion/45797/thread/c71d6b96/
> so oe-core have add support of change SDK type to .zip, so correct
> the extract function.
> 
> Signed-off-by: Changqing Li 
> ---
>  lib/oeqa/sdkmingw/testsdk.py | 11 +--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/oeqa/sdkmingw/testsdk.py
> b/lib/oeqa/sdkmingw/testsdk.py
> index 85fe3c6..173cfd9 100644
> --- a/lib/oeqa/sdkmingw/testsdk.py
> +++ b/lib/oeqa/sdkmingw/testsdk.py
> @@ -12,7 +12,7 @@ class TestSDKMinGW(TestSDK):
>  """
>  Get the name of the SDK file
>  """
> -return
> d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.tar.xz")
> +return
> d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.${SDK_ARCHIVE_TYPE}")
>  
>  def extract_sdk(self, tcname, sdk_dir, d):
>  """
> @@ -23,7 +23,14 @@ class TestSDKMinGW(TestSDK):
>  try:
>  # TODO: It would be nice to try and extract the SDK in
> Wine to make
>  # sure it is well formed
> -subprocess.check_output(['tar', '-xf', tcname, '-C',
> sdk_dir])
> +
> +# TODO: Extract SDK according to SDK_ARCHIVE_TYPE, need
> to change if
> +# oe-core support other types.
> +if d.getVar("SDK_ARCHIVE_TYPE") == "zip":
> +subprocess.check_output(['unzip', '-d', sdk_dir,
> tcname])
> +else:
> +subprocess.check_output(['tar', '-xf', tcname, '-C', 
> sdk_dir])
> +
>  except subprocess.CalledProcessError as e:
>  bb.fatal("Couldn't install the SDK:\n%s" %
> e.output.decode("utf-8"))
>  
> -- 
> 2.7.4
> 
-- 
Joshua Watt 

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


Re: [linux-yocto] [PATCH] Revert "igb: reduce CPU0 latency when updating statistics"

2019-01-21 Thread He Zhe


On 1/21/19 9:47 PM, Bruce Ashfield wrote:
> Which kernel/bsp branch is this one for ? I'm about to push an
> update to linux-yocto-dev today, so from the comment below, it
> looks like we are already covered ?

This is for standard/base. It's from v5.0-rc3.

Zhe

>
> Bruce
>
> On 1/21/19 5:09 AM, zhe...@windriver.com wrote:
>> From: Jeff Kirsher 
>>
>> This reverts commit 59361316afcb08569af21e1af83e89c7051c055a.
>>
>> Due to problems found in additional testing, this causes an illegal
>> context switch in the RCU read-side critical section.
>>
>> CC: Dave Jones 
>> CC: Cong Wang 
>> CC: Jan Jablonsky 
>> Signed-off-by: Jeff Kirsher 
>> Signed-off-by: David S. Miller 
>>
>> commit 5642e27bf6a935c1d0d9149e83d625dfba286463 upstream
>>
>> Before syncing up with 5.0-rc3, it's worth backporting this patch which fixes
>> the following serious crash.
>>
>> BUG: sleeping function called from invalid context at 
>> kernel/locking/mutex.c:254
>> in_atomic(): 0, irqs_disabled(): 0, pid: 7867, name: ifconfig
>> Preemption disabled at:
>> [] memcg_kmem_put_cache+0x2e/0x70
>>  snip 
>> Call Trace:
>>   dump_stack+0x4f/0x6a
>>   ? memcg_kmem_put_cache+0x2e/0x70
>>   ___might_sleep.cold.17+0xd9/0xea
>>   __might_sleep+0x4a/0x80
>>   mutex_lock+0x20/0x40
>>   igb_get_stats64+0x2c/0x60
>>   dev_get_stats+0x3f/0xa0
>>   dev_seq_printf_stats+0x37/0xe0
>>   dev_seq_show+0x14/0x30
>>   seq_read+0x2d3/0x3e0
>>   proc_reg_read+0x3e/0x60
>>   __vfs_read+0x3a/0x180
>>   ? security_file_permission+0x9c/0xf0
>>   vfs_read+0xa1/0x160
>>   ksys_read+0x55/0xc0
>>   __x64_sys_read+0x1a/0x20
>>   do_syscall_64+0x4d/0xf0
>>   entry_SYSCALL_64_after_hwframe+0x44/0xa9
>>
>> Signed-off-by: He Zhe 
>> ---
>>   drivers/net/ethernet/intel/igb/igb.h |  2 +-
>>   drivers/net/ethernet/intel/igb/igb_ethtool.c |  4 ++--
>>   drivers/net/ethernet/intel/igb/igb_main.c    | 14 +++---
>>   3 files changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/igb/igb.h 
>> b/drivers/net/ethernet/intel/igb/igb.h
>> index fe1592a..ca54e26 100644
>> --- a/drivers/net/ethernet/intel/igb/igb.h
>> +++ b/drivers/net/ethernet/intel/igb/igb.h
>> @@ -515,7 +515,7 @@ struct igb_adapter {
>>   /* OS defined structs */
>>   struct pci_dev *pdev;
>>   -    struct mutex stats64_lock;
>> +    spinlock_t stats64_lock;
>>   struct rtnl_link_stats64 stats64;
>>     /* structs defined in e1000_hw.h */
>> diff --git a/drivers/net/ethernet/intel/igb/igb_ethtool.c 
>> b/drivers/net/ethernet/intel/igb/igb_ethtool.c
>> index 7426060..c576710 100644
>> --- a/drivers/net/ethernet/intel/igb/igb_ethtool.c
>> +++ b/drivers/net/ethernet/intel/igb/igb_ethtool.c
>> @@ -2295,7 +2295,7 @@ static void igb_get_ethtool_stats(struct net_device 
>> *netdev,
>>   int i, j;
>>   char *p;
>>   -    mutex_lock(>stats64_lock);
>> +    spin_lock(>stats64_lock);
>>   igb_update_stats(adapter);
>>     for (i = 0; i < IGB_GLOBAL_STATS_LEN; i++) {
>> @@ -2338,7 +2338,7 @@ static void igb_get_ethtool_stats(struct net_device 
>> *netdev,
>>   } while (u64_stats_fetch_retry_irq(>rx_syncp, start));
>>   i += IGB_RX_QUEUE_STATS_LEN;
>>   }
>> -    mutex_unlock(>stats64_lock);
>> +    spin_unlock(>stats64_lock);
>>   }
>>     static void igb_get_strings(struct net_device *netdev, u32 stringset, u8 
>> *data)
>> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c 
>> b/drivers/net/ethernet/intel/igb/igb_main.c
>> index 87bdf16..7137e7f 100644
>> --- a/drivers/net/ethernet/intel/igb/igb_main.c
>> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
>> @@ -2203,9 +2203,9 @@ void igb_down(struct igb_adapter *adapter)
>>   del_timer_sync(>phy_info_timer);
>>     /* record the stats before reset*/
>> -    mutex_lock(>stats64_lock);
>> +    spin_lock(>stats64_lock);
>>   igb_update_stats(adapter);
>> -    mutex_unlock(>stats64_lock);
>> +    spin_unlock(>stats64_lock);
>>     adapter->link_speed = 0;
>>   adapter->link_duplex = 0;
>> @@ -3840,7 +3840,7 @@ static int igb_sw_init(struct igb_adapter *adapter)
>>   adapter->min_frame_size = ETH_ZLEN + ETH_FCS_LEN;
>>     spin_lock_init(>nfc_lock);
>> -    mutex_init(>stats64_lock);
>> +    spin_lock_init(>stats64_lock);
>>   #ifdef CONFIG_PCI_IOV
>>   switch (hw->mac.type) {
>>   case e1000_82576:
>> @@ -5406,9 +5406,9 @@ static void igb_watchdog_task(struct work_struct *work)
>>   }
>>   }
>>   -    mutex_lock(>stats64_lock);
>> +    spin_lock(>stats64_lock);
>>   igb_update_stats(adapter);
>> -    mutex_unlock(>stats64_lock);
>> +    spin_unlock(>stats64_lock);
>>     for (i = 0; i < adapter->num_tx_queues; i++) {
>>   struct igb_ring *tx_ring = adapter->tx_ring[i];
>> @@ -6235,10 +6235,10 @@ static void igb_get_stats64(struct net_device 
>> *netdev,
>>   {
>>   struct igb_adapter *adapter = netdev_priv(netdev);
>>   -    mutex_lock(>stats64_lock);
>> +    spin_lock(>stats64_lock);
>>   

Re: [linux-yocto] [PATCH] Revert "igb: reduce CPU0 latency when updating statistics"

2019-01-21 Thread Bruce Ashfield

Which kernel/bsp branch is this one for ? I'm about to push an
update to linux-yocto-dev today, so from the comment below, it
looks like we are already covered ?

Bruce

On 1/21/19 5:09 AM, zhe...@windriver.com wrote:

From: Jeff Kirsher 

This reverts commit 59361316afcb08569af21e1af83e89c7051c055a.

Due to problems found in additional testing, this causes an illegal
context switch in the RCU read-side critical section.

CC: Dave Jones 
CC: Cong Wang 
CC: Jan Jablonsky 
Signed-off-by: Jeff Kirsher 
Signed-off-by: David S. Miller 

commit 5642e27bf6a935c1d0d9149e83d625dfba286463 upstream

Before syncing up with 5.0-rc3, it's worth backporting this patch which fixes
the following serious crash.

BUG: sleeping function called from invalid context at kernel/locking/mutex.c:254
in_atomic(): 0, irqs_disabled(): 0, pid: 7867, name: ifconfig
Preemption disabled at:
[] memcg_kmem_put_cache+0x2e/0x70
 snip 
Call Trace:
  dump_stack+0x4f/0x6a
  ? memcg_kmem_put_cache+0x2e/0x70
  ___might_sleep.cold.17+0xd9/0xea
  __might_sleep+0x4a/0x80
  mutex_lock+0x20/0x40
  igb_get_stats64+0x2c/0x60
  dev_get_stats+0x3f/0xa0
  dev_seq_printf_stats+0x37/0xe0
  dev_seq_show+0x14/0x30
  seq_read+0x2d3/0x3e0
  proc_reg_read+0x3e/0x60
  __vfs_read+0x3a/0x180
  ? security_file_permission+0x9c/0xf0
  vfs_read+0xa1/0x160
  ksys_read+0x55/0xc0
  __x64_sys_read+0x1a/0x20
  do_syscall_64+0x4d/0xf0
  entry_SYSCALL_64_after_hwframe+0x44/0xa9

Signed-off-by: He Zhe 
---
  drivers/net/ethernet/intel/igb/igb.h |  2 +-
  drivers/net/ethernet/intel/igb/igb_ethtool.c |  4 ++--
  drivers/net/ethernet/intel/igb/igb_main.c| 14 +++---
  3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/drivers/net/ethernet/intel/igb/igb.h 
b/drivers/net/ethernet/intel/igb/igb.h
index fe1592a..ca54e26 100644
--- a/drivers/net/ethernet/intel/igb/igb.h
+++ b/drivers/net/ethernet/intel/igb/igb.h
@@ -515,7 +515,7 @@ struct igb_adapter {
/* OS defined structs */
struct pci_dev *pdev;
  
-	struct mutex stats64_lock;

+   spinlock_t stats64_lock;
struct rtnl_link_stats64 stats64;
  
  	/* structs defined in e1000_hw.h */

diff --git a/drivers/net/ethernet/intel/igb/igb_ethtool.c 
b/drivers/net/ethernet/intel/igb/igb_ethtool.c
index 7426060..c576710 100644
--- a/drivers/net/ethernet/intel/igb/igb_ethtool.c
+++ b/drivers/net/ethernet/intel/igb/igb_ethtool.c
@@ -2295,7 +2295,7 @@ static void igb_get_ethtool_stats(struct net_device 
*netdev,
int i, j;
char *p;
  
-	mutex_lock(>stats64_lock);

+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
  
  	for (i = 0; i < IGB_GLOBAL_STATS_LEN; i++) {

@@ -2338,7 +2338,7 @@ static void igb_get_ethtool_stats(struct net_device 
*netdev,
} while (u64_stats_fetch_retry_irq(>rx_syncp, start));
i += IGB_RX_QUEUE_STATS_LEN;
}
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
  }
  
  static void igb_get_strings(struct net_device *netdev, u32 stringset, u8 *data)

diff --git a/drivers/net/ethernet/intel/igb/igb_main.c 
b/drivers/net/ethernet/intel/igb/igb_main.c
index 87bdf16..7137e7f 100644
--- a/drivers/net/ethernet/intel/igb/igb_main.c
+++ b/drivers/net/ethernet/intel/igb/igb_main.c
@@ -2203,9 +2203,9 @@ void igb_down(struct igb_adapter *adapter)
del_timer_sync(>phy_info_timer);
  
  	/* record the stats before reset*/

-   mutex_lock(>stats64_lock);
+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
  
  	adapter->link_speed = 0;

adapter->link_duplex = 0;
@@ -3840,7 +3840,7 @@ static int igb_sw_init(struct igb_adapter *adapter)
adapter->min_frame_size = ETH_ZLEN + ETH_FCS_LEN;
  
  	spin_lock_init(>nfc_lock);

-   mutex_init(>stats64_lock);
+   spin_lock_init(>stats64_lock);
  #ifdef CONFIG_PCI_IOV
switch (hw->mac.type) {
case e1000_82576:
@@ -5406,9 +5406,9 @@ static void igb_watchdog_task(struct work_struct *work)
}
}
  
-	mutex_lock(>stats64_lock);

+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
  
  	for (i = 0; i < adapter->num_tx_queues; i++) {

struct igb_ring *tx_ring = adapter->tx_ring[i];
@@ -6235,10 +6235,10 @@ static void igb_get_stats64(struct net_device *netdev,
  {
struct igb_adapter *adapter = netdev_priv(netdev);
  
-	mutex_lock(>stats64_lock);

+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
memcpy(stats, >stats64, sizeof(*stats));
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
  }
  
  /**




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


Re: [yocto] [Recipe reporting system] Upgradable recipe name list

2019-01-21 Thread Alexander Kanavin
Hello,

just to remind you that RRS continues to send these badly outdated,
misleading reports once a week to yocto@. Please switch them off
and/or take the new RRS into use (if the new RRS addresses the
problem).

Alex


On Mon, 21 Jan 2019 at 06:01,  wrote:
>
> This mail was sent out by Recipe reporting system.
>
> This message list those recipes which need to be upgraded. If maintainers
> believe some of them needn't to upgrade at this time, they can fill
> RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
> until newer upstream version was detected.
>
> Example:
> RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable"
>
> You can check the detail information at:
>
> http://recipes.yoctoproject.org/
>
> Package   Version  Upstream version  Maintainer   
> NoUpgradeReason
>   ---    
> ---  --
> libgloss  3.0.03.0.0.20180831Alejandro 
> Hernandez
> newlib3.0.03.0.0.20180831Alejandro 
> Hernandez
> libmodulemd   1.7.02.0.0 Alexander Kanavin
> pcmanfm   1.3.01.3.1 Alexander Kanavin
> webkitgtk 2.22.4   2.22.5Alexander Kanavin
> boost 1.68.0   1.69.0Alexander Kanavin
> libfm-extra   1.3.0.2  1.3.1 Alexander Kanavin
> libfm 1.3.0.2  1.3.1 Alexander Kanavin
> nativesdk-meson   0.47.2   0.49.0Alexander Kanavin
> ffmpeg4.0.24.1   Alexander Kanavin
> libcomps  0.1.8+gitX   0.1.9 Alexander Kanavin
> librepo   1.9.21.9.3 Alexander Kanavin
> meson 0.47.2   0.49.0Alexander Kanavin
> dnf   4.0.94.0.10Alexander Kanavin
> libdnf0.22.3   0.24.1Alexander Kanavin
> lighttpd  1.4.51   1.4.52Alexander Kanavin
> gobject-introspec...  1.58.1   1.58.2Alexander Kanavin
> btrfs-tools   4.19 4.19.1Alexander Kanavin
> bjam-native   1.68.0   1.69.0Alexander Kanavin
> createrepo-c  0.11.1+gitX  0.12.0Alexander Kanavin
> busybox   1.29.2   1.29.3Andrej Valek
> apt   1.2.24   1.4.8 Aníbal Limón
> apt-native1.2.24   1.4.8 Aníbal Limón
> dpkg  1.18.24  1.19.2Aníbal Limón
> puzzles   0.0+gitX 0.0-new-commits-a...  Anuj Mittal
> libpcap   1.8.11.9.0 Anuj Mittal
> base-passwd   3.5.29   3.5.45Anuj Mittal  
> Version 3.5.38 requires cde...
> ifupdown  0.8.16   0.8.33Anuj Mittal
> glib-2.0  2.58.0   2.58.1Anuj Mittal
> glib-networking   2.54.1   2.58.0Anuj Mittal
> pixman0.34.0   0.36.0Anuj Mittal
> harfbuzz  2.1.32.2.0 Anuj Mittal
> gst-examples  0.0.1+gitX   0.0.1-new-commits...  Anuj Mittal
> sqlite3   3.25.3   3.26.0Anuj Mittal
> vte   0.52.2   0.54.3Anuj Mittal
> gsettings-desktop...  3.28.0   3.28.1Anuj Mittal
> libsolv   0.7.10.7.2 Anuj Mittal
> eudev 3.2.53.2.7 Anuj Mittal
> atk   2.28.1   2.30.0Anuj Mittal
> librsvg   2.40.20  2.44.10   Anuj Mittal  
> Versions from 2.41.0 requir...
> cairo 1.14.12  1.16.2Anuj Mittal
> i2c-tools 4.0  4.1   Anuj Mittal
> libatomic-ops 7.6.6+gitX   7.6.8 Anuj Mittal
> libpng1.6.35   1.6.36Anuj Mittal
> at-spi2-atk   2.26.2   2.30.0Anuj Mittal
> mmc-utils 0.1  0.1-new-commits-a...  Anuj Mittal
> libjpeg-turbo 2.0.02.0.1 Anuj Mittal
> mtools4.0.19   4.0.23Anuj Mittal
> libassuan 2.5.12.5.2 Armin Kuster
> netbase   5.4  5.5   Armin Kuster
> openssh   7.9p1+git7.9.  Armin 

[linux-yocto] [PATCH] Revert "igb: reduce CPU0 latency when updating statistics"

2019-01-21 Thread zhe.he
From: Jeff Kirsher 

This reverts commit 59361316afcb08569af21e1af83e89c7051c055a.

Due to problems found in additional testing, this causes an illegal
context switch in the RCU read-side critical section.

CC: Dave Jones 
CC: Cong Wang 
CC: Jan Jablonsky 
Signed-off-by: Jeff Kirsher 
Signed-off-by: David S. Miller 

commit 5642e27bf6a935c1d0d9149e83d625dfba286463 upstream

Before syncing up with 5.0-rc3, it's worth backporting this patch which fixes
the following serious crash.

BUG: sleeping function called from invalid context at kernel/locking/mutex.c:254
in_atomic(): 0, irqs_disabled(): 0, pid: 7867, name: ifconfig
Preemption disabled at:
[] memcg_kmem_put_cache+0x2e/0x70
 snip 
Call Trace:
 dump_stack+0x4f/0x6a
 ? memcg_kmem_put_cache+0x2e/0x70
 ___might_sleep.cold.17+0xd9/0xea
 __might_sleep+0x4a/0x80
 mutex_lock+0x20/0x40
 igb_get_stats64+0x2c/0x60
 dev_get_stats+0x3f/0xa0
 dev_seq_printf_stats+0x37/0xe0
 dev_seq_show+0x14/0x30
 seq_read+0x2d3/0x3e0
 proc_reg_read+0x3e/0x60
 __vfs_read+0x3a/0x180
 ? security_file_permission+0x9c/0xf0
 vfs_read+0xa1/0x160
 ksys_read+0x55/0xc0
 __x64_sys_read+0x1a/0x20
 do_syscall_64+0x4d/0xf0
 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Signed-off-by: He Zhe 
---
 drivers/net/ethernet/intel/igb/igb.h |  2 +-
 drivers/net/ethernet/intel/igb/igb_ethtool.c |  4 ++--
 drivers/net/ethernet/intel/igb/igb_main.c| 14 +++---
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/drivers/net/ethernet/intel/igb/igb.h 
b/drivers/net/ethernet/intel/igb/igb.h
index fe1592a..ca54e26 100644
--- a/drivers/net/ethernet/intel/igb/igb.h
+++ b/drivers/net/ethernet/intel/igb/igb.h
@@ -515,7 +515,7 @@ struct igb_adapter {
/* OS defined structs */
struct pci_dev *pdev;
 
-   struct mutex stats64_lock;
+   spinlock_t stats64_lock;
struct rtnl_link_stats64 stats64;
 
/* structs defined in e1000_hw.h */
diff --git a/drivers/net/ethernet/intel/igb/igb_ethtool.c 
b/drivers/net/ethernet/intel/igb/igb_ethtool.c
index 7426060..c576710 100644
--- a/drivers/net/ethernet/intel/igb/igb_ethtool.c
+++ b/drivers/net/ethernet/intel/igb/igb_ethtool.c
@@ -2295,7 +2295,7 @@ static void igb_get_ethtool_stats(struct net_device 
*netdev,
int i, j;
char *p;
 
-   mutex_lock(>stats64_lock);
+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
 
for (i = 0; i < IGB_GLOBAL_STATS_LEN; i++) {
@@ -2338,7 +2338,7 @@ static void igb_get_ethtool_stats(struct net_device 
*netdev,
} while (u64_stats_fetch_retry_irq(>rx_syncp, start));
i += IGB_RX_QUEUE_STATS_LEN;
}
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
 }
 
 static void igb_get_strings(struct net_device *netdev, u32 stringset, u8 *data)
diff --git a/drivers/net/ethernet/intel/igb/igb_main.c 
b/drivers/net/ethernet/intel/igb/igb_main.c
index 87bdf16..7137e7f 100644
--- a/drivers/net/ethernet/intel/igb/igb_main.c
+++ b/drivers/net/ethernet/intel/igb/igb_main.c
@@ -2203,9 +2203,9 @@ void igb_down(struct igb_adapter *adapter)
del_timer_sync(>phy_info_timer);
 
/* record the stats before reset*/
-   mutex_lock(>stats64_lock);
+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
 
adapter->link_speed = 0;
adapter->link_duplex = 0;
@@ -3840,7 +3840,7 @@ static int igb_sw_init(struct igb_adapter *adapter)
adapter->min_frame_size = ETH_ZLEN + ETH_FCS_LEN;
 
spin_lock_init(>nfc_lock);
-   mutex_init(>stats64_lock);
+   spin_lock_init(>stats64_lock);
 #ifdef CONFIG_PCI_IOV
switch (hw->mac.type) {
case e1000_82576:
@@ -5406,9 +5406,9 @@ static void igb_watchdog_task(struct work_struct *work)
}
}
 
-   mutex_lock(>stats64_lock);
+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
 
for (i = 0; i < adapter->num_tx_queues; i++) {
struct igb_ring *tx_ring = adapter->tx_ring[i];
@@ -6235,10 +6235,10 @@ static void igb_get_stats64(struct net_device *netdev,
 {
struct igb_adapter *adapter = netdev_priv(netdev);
 
-   mutex_lock(>stats64_lock);
+   spin_lock(>stats64_lock);
igb_update_stats(adapter);
memcpy(stats, >stats64, sizeof(*stats));
-   mutex_unlock(>stats64_lock);
+   spin_unlock(>stats64_lock);
 }
 
 /**
-- 
2.7.4

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


[yocto] [PATCH V2 2/2] ref-variables.xml: update manual page for update-rc.d

2019-01-21 Thread changqing.li
From: Changqing Li 

Currently, yocto doc refer link http://www.tin.org/bin/man.cgi?
section=8=update-rc.d. as man page of update-rc.d, but lastest
debian udpate-rc.d have big difference with yocto, they need insserv
and all the initscripts support LSB comment header.

change to new link which is more similar to yocto

[Yocto #12955]

Signed-off-by: Changqing Li 
---
 documentation/ref-manual/ref-variables.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/ref-manual/ref-variables.xml 
b/documentation/ref-manual/ref-variables.xml
index 9e51b75..dc5fc6d 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -7198,7 +7198,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = 
"${INC_PR}.3"
 to the update-rc.d command.
 For more information on valid parameters, please see the
 update-rc.d manual page at
-.
+.
 
 
 
-- 
2.7.4

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


[yocto] [update-rc.d][PATCH V2] update-rc.d: support enable/disable function

2019-01-21 Thread changqing.li
From: Changqing Li 

Add support of enable/disable function, so that user can keep
previous config like disable one service even after upgrade package.

this patch need to work with oe-core patch
[update-rc.d.bbclass: remove preinst and remove -f for postinst]

[Yocto 12955]

Signed-off-by: Changqing Li 
---
 update-rc.d | 81 +
 1 file changed, 81 insertions(+)

diff --git a/update-rc.d b/update-rc.d
index e07cf85..a7fb7bc 100644
--- a/update-rc.d
+++ b/update-rc.d
@@ -27,6 +27,7 @@ usage()
 usage: update-rc.d [-n] [-f] [-r ]  remove
update-rc.d [-n] [-r ] [-s]  defaults [NN | sNN kNN]
update-rc.d [-n] [-r ] [-s]  start|stop NN runlvl 
[runlvl] [...] .
+   update-rc.d [-n] [-r ] [-s]  enable|disable [S|2|3|4|5]
-n: not really
-f: force
-v: verbose
@@ -101,6 +102,53 @@ makelinks()
done
 }
 
+# function to disable/enable init script link of one run level
+# $1 should be K/S, means to disable/enable
+# $2 means which run level to disable/enable 
+renamelink()
+{
+   local oldstartstop newstartstop lev oldnn newnn
+   if [ "x$1" = "xS" ]; then
+   oldstartstop="K"
+   newstartstop="S"
+   else
+   oldstartstop="S"
+   newstartstop="K"
+   fi
+
+   lev=$2
+   # modifies existing runlevel links for the script /etc/init.d/name by 
renaming start links to stop link
+# or stop link to start link with a sequence number equal to the 
difference of 100 minus the original sequence number.
+   if ls ${etcd}${lev}.d/${oldstartstop}*${bn} >/dev/null 2>&1; then
+   oldnn=`basename ${etcd}${lev}.d/${oldstartstop}*${bn}|cut -c2-3`
+   newnn=$[100-$oldnn]
+   [ $verbose -eq 1 ] && echo "rename 
${etcd}${lev}.d/${oldstartstop}${oldnn}${bn} -> 
${etcd}${lev}.d/${newstartstop}${newnn}${bn}"
+   if [ $notreally -eq 0 ];then
+   mv ${etcd}${lev}.d/${oldstartstop}${oldnn}${bn} 
${etcd}${lev}.d/${newstartstop}${newnn}${bn}
+   fi
+   if [ $dostart -eq 1 ] && [ $newstartstop = "S" ] && [ $lev = 
$RUNLEVEL ]; then
+   $fn start || true
+   fi
+   fi
+
+}
+
+# function to disable/enable init script link
+# $1 should be K/S, means to disable/enable
+# $2 run level [S|2|3|4|5], optional, If no start runlevel is 
+# specified after the disable or enable keywords 
+# the script will attempt to modify links in all start runlevels
+renamelinks()
+{
+   if [ $# -eq 2 ]; then
+   renamelink $1 $2
+   else
+   for i in 2 3 4 5 S; do
+   renamelink $1 $i
+   done
+   fi
+}
+
 while [ $# -gt 0 ]; do
case $1 in
-n) notreally=1
@@ -221,6 +269,13 @@ case $1 in
;;
 
start | stop)
+   if [ $# -lt 4 ]
+   then
+   echo "Not enough arguments"
+   usage
+   exit 1
+   fi
+
while [ $# -gt 0 ]; do
if [ $1 = "start" ]; then
letter=S
@@ -251,6 +306,32 @@ case $1 in
makelinks
;;
 
+   enable | disable)
+   if [ $1 = "enable" ]; then
+   letter=S
+   elif [ $1 = "disable" ]; then
+   letter=K
+   else
+   usage
+   exit 1
+   fi
+   shift
+   # 
+   if [ $# -gt 0 ]
+   then
+   case $1 in
+   S|2|3|4|5)
+   renamelinks $letter $1
+   ;;
+   *)
+   usage
+   exit 1
+   ;;
+   esac
+   else
+   renamelinks $letter
+   fi
+   ;;
*)
usage
exit 1
-- 
2.7.4

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


[yocto] [PATCH V2 0/2] update-rc.d: support enable/disable function

2019-01-21 Thread changqing.li
These three patches are for support disable/enable function for update-rc.d

change in V2:
add some comments and fix commit message

change in V1:
* change of script update-rc.d is for support disable/enable of init script link
* update-rc.d.bbclass remove preinst to make disable/enable can work after 
upgrade
* fix the doc manual 

Changqing Li (2):
  update-rc.d.bbclass: remove preinst and remove -f for postinst
  ref-variables.xml: update manual page for update-rc.d

 documentation/ref-manual/ref-variables.xml |  2 +-
 meta/classes/update-rc.d.bbclass   | 28 
 2 files changed, 5 insertions(+), 25 deletions(-)

-- 
2.7.4

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


[yocto] [PATCH V2 1/2] update-rc.d.bbclass: remove preinst and remove -f for postinst

2019-01-21 Thread changqing.li
From: Changqing Li 

*preinst use "-f remove" to remove any links in the /etc/rcrunlevel.d
  but this will make user cannot keep previous init script link
  after upgrade

  eg: user disable one service before upgrade, after upgrade, service
  could be started since during preinst, all link have been deleted, so
  postinst may create the link to start service.

  remove preinst to keep previous links, so that after upgrade, if any
  link existed for the package, postinst will not create new start/stop
  links.

  (note: patch of support enable/disable function of update-rc.d send
  to yocto mail list today)

*remove -f for postinst, previously, recipe keepalived use remove during
  postinst, so need this -f, but remove in postinst is not proper, recipe
  keepalived have fixed this problem, so remove -f.

[Yocto #12955]

Signed-off-by: Changqing Li 
---
 meta/classes/update-rc.d.bbclass | 28 
 1 file changed, 4 insertions(+), 24 deletions(-)

diff --git a/meta/classes/update-rc.d.bbclass b/meta/classes/update-rc.d.bbclass
index 265c4be..1366fee 100644
--- a/meta/classes/update-rc.d.bbclass
+++ b/meta/classes/update-rc.d.bbclass
@@ -20,28 +20,14 @@ def use_updatercd(d):
 return '[ -n "$D" -o ! -d /run/systemd/system ]'
 return 'true'
 
-updatercd_preinst() {
-if ${@use_updatercd(d)} && [ -z "$D" -a -f "${INIT_D_DIR}/${INITSCRIPT_NAME}" 
]; then
-   ${INIT_D_DIR}/${INITSCRIPT_NAME} stop || :
-fi
-if ${@use_updatercd(d)} && type update-rc.d >/dev/null 2>/dev/null; then
-   if [ -n "$D" ]; then
-   OPT="-f -r $D"
-   else
-   OPT="-f"
-   fi
-   update-rc.d $OPT ${INITSCRIPT_NAME} remove
-fi
-}
-
 PACKAGE_WRITE_DEPS += "update-rc.d-native"
 
 updatercd_postinst() {
 if ${@use_updatercd(d)} && type update-rc.d >/dev/null 2>/dev/null; then
if [ -n "$D" ]; then
-   OPT="-f -r $D"
+   OPT="-r $D"
else
-   OPT="-f -s"
+   OPT="-s"
fi
update-rc.d $OPT ${INITSCRIPT_NAME} ${INITSCRIPT_PARAMS}
 fi
@@ -79,7 +65,7 @@ python __anonymous() {
 PACKAGESPLITFUNCS_prepend = "${@bb.utils.contains('DISTRO_FEATURES', 
'sysvinit', 'populate_packages_updatercd ', '', d)}"
 PACKAGESPLITFUNCS_remove_class-nativesdk = "populate_packages_updatercd "
 
-populate_packages_updatercd[vardeps] += "updatercd_prerm updatercd_postrm 
updatercd_preinst updatercd_postinst"
+populate_packages_updatercd[vardeps] += "updatercd_prerm updatercd_postrm 
updatercd_postinst"
 populate_packages_updatercd[vardepsexclude] += "OVERRIDES"
 
 python populate_packages_updatercd () {
@@ -95,7 +81,7 @@ python populate_packages_updatercd () {
 d.appendVar('RDEPENDS_' + pkg, ' %sinitd-functions' % (mlprefix))
 
 def update_rcd_package(pkg):
-bb.debug(1, 'adding update-rc.d calls to preinst/postinst/prerm/postrm 
for %s' % pkg)
+bb.debug(1, 'adding update-rc.d calls to postinst/prerm/postrm for %s' 
% pkg)
 
 localdata = bb.data.createCopy(d)
 overrides = localdata.getVar("OVERRIDES")
@@ -103,12 +89,6 @@ python populate_packages_updatercd () {
 
 update_rcd_auto_depend(pkg)
 
-preinst = d.getVar('pkg_preinst_%s' % pkg)
-if not preinst:
-preinst = '#!/bin/sh\n'
-preinst += localdata.getVar('updatercd_preinst')
-d.setVar('pkg_preinst_%s' % pkg, preinst)
-
 postinst = d.getVar('pkg_postinst_%s' % pkg)
 if not postinst:
 postinst = '#!/bin/sh\n'
-- 
2.7.4

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


Re: [yocto] Systemd service recipe fails while booting from initramfs

2019-01-21 Thread Lukasz Zemla
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Zoran Stojsavljevic
Sent: Monday, January 21, 2019 7:56 AM

[...]

> While downloading initramfs on the target system, while bringing kernel up, 
> the following
> happened (actual log):
> [    0.00] Kernel command line: console=ttyO0,115200n8 root=/dev/ram0 
> ip=dhcp
> ... [snap]...
> [  114.064032] Sending DHCP requests .. timed out!
> [  190.652571] IP-Config: Auto-configuration of network failed
> [  190.663158] Freeing unused kernel memory: 1024K
> [  190.668661] Run /init as init process
> System time before build time, advancing clock.
> Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory
> Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory
> [!!] Failed to mount API filesystems, freezing.
> Freezing execution.
> [  192.984442] random: crng init done
> I have two questions (please, could you provide to me some help here):
> [1] How to fix this run-time bug (what I should do in the configuration)?
> I found some interesting explanation about possible solution 
>(PACKAGECONFIG):
> https://lists.yoctoproject.org/pipermail/yocto/2013-November/016965.html

Probably you are missing CONFIG_CGROUPS in your kernel configuration.
Please read README file in the systemd sources folder - it describes all options
required to be enabled in kernel configuration.

> [2] I would like also to include networkctl service (should I do something 
> specific to
> enable it, or this is done by default enabling systemd)?

Please add following to your conf/local.conf file:
PACKAGECONFIG_append_pn-systemd = " networkd"

Best regards,
Lukasz Zemla

***
The information in this email is confidential and intended solely for the 
individual or entity to whom it is addressed.  If you have received this email 
in error please notify the sender by return e-mail, delete this email, and 
refrain from any disclosure or action based on the information.
***
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Systemd service recipe fails while booting from initramfs

2019-01-21 Thread Peter Bergin

On 2019-01-21 07:56, Zoran Stojsavljevic wrote:

Hello to all,

I have added to my local.conf the following lines in order to port 
systemd service

in YOCTO (Thud release):

_/## Add systemd service
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_dev_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
DISTRO_FEATURES_append = " nfs systemd"/_

By executing bitbake -k core-image-minimal command, all went good 
(although it rebuilt

almost the whole build - circa 80% of it), which is understandable.

While downloading initramfs on the target system, while bringing 
kernel up, the following

happened (actual log):
[    0.00] Kernel command line: console=ttyO0,115200n8 
root=/dev/ram0 ip=dhcp

... [snap]...
[  114.064032] Sending DHCP requests .. timed out!
[  190.652571] IP-Config: Auto-configuration of network failed
[  190.663158] Freeing unused kernel memory: 1024K
[  190.668661] Run /init as init process
System time before build time, advancing clock.
/*Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory
Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or 
directory

[!!] */Failed to mount API filesystems, freezing.
/*Freezing execution.*/
[  192.984442] random: crng init done

I have two questions (please, could you provide to me some help here):
[1] How to fix this run-time bug (what I should do in the configuration)?
 I found some interesting explanation about possible solution 
/(PACKAGECONFIG)/:

https://lists.yoctoproject.org/pipermail/yocto/2013-November/016965.html


Could be that you miss some required kernel configurations. See 
systemd/README 
(https://github.com/systemd/systemd/blob/8464d9e0dc506538fd0f2d1d667966750cb9cf30/README#L38)
[2] I would like also to include networkctl service (should I do 
something specific to

 enable it, or this is done by default enabling systemd)?
PACKAGECONFIG will control which features you have enabled for systemd. 
To check which ones you have you can execute 'bitbake -e systemd | grep 
^PACKAGECONFIG='. If you want to change this config you can adjust 
PACKAGECONFIG in your own systemd_%.bbappend file.


I guess networkd is enabled default with the systemd recipe. But check 
it out. There are several way to see which files that are included in 
your image. I use buildhistory.bbclass in all my build which make it 
easy too look up what's included.


Regards,
/Peter

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