[OE-core] [PATCH 3/6] runqemu: use self.rootfs to replace self.nfs_dir

[Robert Yang]

We can use self.rootfs as self.nfs_dir when self.fstype is nfs, this can
reduce the code's complexity and we can re-use the code of checking
ROOTFS conflictions.

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 28 +---
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 71e3cdbe80..23a344da35 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -178,7 +178,6 @@ class BaseConfig(object):
 
 self.qemu_opt = ''
 self.qemu_opt_script = ''
-self.nfs_dir = ''
 self.clean_nfs_dir = False
 self.nfs_server = ''
 self.rootfs = ''
@@ -284,12 +283,11 @@ class BaseConfig(object):
 
 def check_arg_nfs(self, p):
 if os.path.isdir(p):
-self.nfs_dir = p
+self.rootfs = p
 else:
 m = re.match('(.*):(.*)', p)
 self.nfs_server = m.group(1)
-self.nfs_dir = m.group(2)
-self.rootfs = ""
+self.rootfs = m.group(2)
 self.check_arg_fstype('nfs')
 
 def check_arg_path(self, p):
@@ -759,7 +757,7 @@ class BaseConfig(object):
 print('MACHINE: [%s]' % self.get('MACHINE'))
 print('FSTYPE: [%s]' % self.fstype)
 if self.fstype  == 'nfs':
-print('NFS_DIR: [%s]' % self.nfs_dir)
+print('NFS_DIR: [%s]' % self.rootfs)
 else:
 print('ROOTFS: [%s]' % self.rootfs)
 if self.ovmf_bios:
@@ -804,13 +802,13 @@ class BaseConfig(object):
 
 
self.unfs_opts="nfsvers=3,port=%s,mountprog=%s,nfsprog=%s,udp,mountport=%s" % 
(nfsd_port, mountd_rpcport, nfsd_rpcport, mountd_port)
 
-# Extract .tar.bz2 or .tar.bz if no self.nfs_dir
-if not self.nfs_dir:
+# Extract .tar.bz2 or .tar.bz if no nfs dir
+if not (self.rootfs and os.path.isdir(self.rootfs)):
 src_prefix = '%s/%s' % (self.get('DEPLOY_DIR_IMAGE'), 
self.get('IMAGE_LINK_NAME'))
 dest = "%s-nfsroot" % src_prefix
 if os.path.exists('%s.pseudo_state' % dest):
 logger.info('Use %s as NFS_DIR' % dest)
-self.nfs_dir = dest
+self.rootfs = dest
 else:
 src = ""
 src1 = '%s.tar.bz2' % src_prefix
@@ -827,10 +825,10 @@ class BaseConfig(object):
 if subprocess.call(cmd, shell=True) != 0:
 raise Exception('Failed to run %s' % cmd)
 self.clean_nfs_dir = True
-self.nfs_dir = dest
+self.rootfs = dest
 
 # Start the userspace NFS server
-cmd = 'runqemu-export-rootfs start %s' % self.nfs_dir
+cmd = 'runqemu-export-rootfs start %s' % self.rootfs
 logger.info('Running %s...' % cmd)
 if subprocess.call(cmd, shell=True) != 0:
 raise Exception('Failed to run %s' % cmd)
@@ -1001,7 +999,7 @@ class BaseConfig(object):
 
 if self.fstype == 'nfs':
 self.rootfs_options = ''
-k_root = '/dev/nfs nfsroot=%s:%s,%s' % (self.nfs_server, 
self.nfs_dir, self.unfs_opts)
+k_root = '/dev/nfs nfsroot=%s:%s,%s' % (self.nfs_server, 
self.rootfs, self.unfs_opts)
 self.kernel_cmdline = 'root=%s rw highres=off' % k_root
 
 if self.fstype == 'none':
@@ -1147,7 +1145,7 @@ class BaseConfig(object):
 
 if self.nfs_running:
 logger.info("Shutting down the userspace NFS server...")
-cmd = "runqemu-export-rootfs stop %s" % self.nfs_dir
+cmd = "runqemu-export-rootfs stop %s" % self.rootfs
 logger.info('Running %s' % cmd)
 subprocess.call(cmd, shell=True)
 
@@ -1156,9 +1154,9 @@ class BaseConfig(object):
 subprocess.call(cmd, shell=True)
 
 if self.clean_nfs_dir:
-logger.info('Removing %s' % self.nfs_dir)
-shutil.rmtree(self.nfs_dir)
-shutil.rmtree('%s.pseudo_state' % self.nfs_dir)
+logger.info('Removing %s' % self.rootfs)
+shutil.rmtree(self.rootfs)
+shutil.rmtree('%s.pseudo_state' % self.rootfs)
 
 def load_bitbake_env(self, mach=None):
 if self.bitbake_e:
-- 
2.11.0.rc2.dirty

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

[OE-core] [PATCH 1/6] runqemu: fix 2 typos

[Robert Yang]

* "is it" -> "it is"
* Remove ".qemuboot.conf =" in the error message which looked strange.

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 23c9efbae2..251f5f7e94 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -421,7 +421,7 @@ class BaseConfig(object):
 elif arg.startswith('ovmf'):
 self.ovmf_bios.append(arg)
 else:
-# At last, assume is it the MACHINE
+# At last, assume it is the MACHINE
 if (not unknown_arg) or unknown_arg == arg:
 unknown_arg = arg
 else:
@@ -677,7 +677,7 @@ class BaseConfig(object):
 return
 
 if not os.path.exists(self.qemuboot):
-raise Exception("Failed to find .qemuboot.conf = %s (wrong 
image name or BSP does not support running under qemu?)." % self.qemuboot)
+raise Exception("Failed to find %s (wrong image name or BSP does 
not support running under qemu?)." % self.qemuboot)
 
 logger.info('CONFFILE: %s' % self.qemuboot)
 
-- 
2.11.0.rc2.dirty

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

[OE-core] [PATCH 6/6] runqemu: do not rely on grepping images

[Robert Yang]

Fixed when the image is large and not enough memory:
  grep: memory exhausted
  Aborted

[YOCTO #11073]

Signed-off-by: Robert Yang 
---
 meta/classes/qemuboot.bbclass |  3 +++
 scripts/runqemu   | 19 +++
 2 files changed, 14 insertions(+), 8 deletions(-)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index 3ca97cad4c..2870388dfb 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -64,6 +64,9 @@ QB_DEFAULT_FSTYPE ?= "ext4"
 QB_OPT_APPEND ?= "-show-cursor"
 QB_NETWORK_DEVICE ?= "-device virtio-net-pci,netdev=net0,mac=@MAC@"
 
+# This should be kept align with ROOT_VM
+QB_DRIVE_TYPE ?= "/dev/sd"
+
 # Create qemuboot.conf
 addtask do_write_qemuboot_conf after do_rootfs before do_image
 IMGDEPLOYDIR ?= "${WORKDIR}/deploy-${PN}-image-complete"
diff --git a/scripts/runqemu b/scripts/runqemu
index b9646223c4..b5fc22af18 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -978,23 +978,26 @@ class BaseConfig(object):
 self.kernel_cmdline = 'root=/dev/ram0 rw debugshell'
 self.rootfs_options = '-initrd %s' % self.rootfs
 else:
+vm_drive = ''
 if self.fstype in self.vmtypes:
 if self.fstype == 'iso':
 vm_drive = '-cdrom %s' % self.rootfs
-else:
-cmd1 = "grep -q 'root=/dev/sd' %s" % self.rootfs
-cmd2 = "grep -q 'root=/dev/hd' %s" % self.rootfs
-if subprocess.call(cmd1, shell=True) == 0:
+elif self.get('QB_DRIVE_TYPE'):
+drive_type = self.get('QB_DRIVE_TYPE')
+if drive_type.startswith("/dev/sd"):
 logger.info('Using scsi drive')
 vm_drive = '-drive if=none,id=hd,file=%s,format=%s 
-device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd' \
% (self.rootfs, rootfs_format)
-elif subprocess.call(cmd2, shell=True) == 0:
+elif drive_type.startswith("/dev/hd"):
 logger.info('Using ide drive')
 vm_drive = "%s,format=%s" % (self.rootfs, 
rootfs_format)
 else:
-logger.warn("Can't detect drive type %s" % self.rootfs)
-logger.warn('Trying to use virtio block drive')
-vm_drive = '-drive if=virtio,file=%s,format=%s' % 
(self.rootfs, rootfs_format)
+logger.warn("Unknown QB_DRIVE_TYPE: %s" % drive_type)
+
+if not vm_drive:
+logger.warn("Failed to figure out drive type, consider 
define or fix QB_DRIVE_TYPE")
+logger.warn('Trying to use virtio block drive')
+vm_drive = '-drive if=virtio,file=%s,format=%s' % 
(self.rootfs, rootfs_format)
 self.rootfs_options = '%s -no-reboot' % vm_drive
 self.kernel_cmdline = 'root=%s rw highres=off' % 
(self.get('QB_KERNEL_ROOT'))
 
-- 
2.11.0.rc2.dirty

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

[OE-core] [PATCH 4/6] runqemu: run without arguments

[Robert Yang]

Since we can get MACHINE and others from env vars and "bitbake -e",
"runqemu" can work without any arguments.

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 23a344da35..1b330b7cfd 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -83,6 +83,7 @@ of the following environment variables (in any order):
   help, -h, --help: print this text
 
 Examples:
+  runqemu
   runqemu qemuarm
   runqemu tmp/deploy/images/qemuarm
   runqemu tmp/deploy/images/qemux86/
@@ -1182,8 +1183,7 @@ class BaseConfig(object):
 logger.warn("Couldn't run 'bitbake -e' to gather environment 
information:\n%s" % err.output.decode('utf-8'))
 
 def main():
-if len(sys.argv) == 1 or "help" in sys.argv or \
-'-h' in sys.argv or '--help' in sys.argv:
+if "help" in sys.argv or '-h' in sys.argv or '--help' in sys.argv:
 print_usage()
 return 0
 config = BaseConfig()
-- 
2.11.0.rc2.dirty

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

[OE-core] [PATCH 2/6] runqemu: support env vars explicitly

[Robert Yang]

Use self.env_vars to support get vars from environment explicity. The
MACHINE, ROOTFS and KERNEL was supported by shell based runqemu, and
the help text says support them from env vars, so add them back.

[YOCTO #11141]

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 71 ++---
 1 file changed, 42 insertions(+), 29 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 251f5f7e94..71e3cdbe80 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -163,12 +163,18 @@ def check_free_port(host, port):
 
 class BaseConfig(object):
 def __init__(self):
-# Vars can be merged with .qemuboot.conf, use a dict to manage them.
-self.d = {
-'MACHINE': '',
-'DEPLOY_DIR_IMAGE': '',
-'QB_KERNEL_ROOT': '/dev/vda',
-}
+# The self.d saved vars from self.set(), part of them are from 
qemuboot.conf
+self.d = {'QB_KERNEL_ROOT': '/dev/vda'}
+
+# Supported env vars, add it here if a var can be got from env,
+# and don't use os.getenv in the code.
+self.env_vars = ('MACHINE',
+'ROOTFS',
+'KERNEL',
+'DEPLOY_DIR_IMAGE',
+'OE_TMPDIR',
+'OECORE_NATIVE_SYSROOT',
+)
 
 self.qemu_opt = ''
 self.qemu_opt_script = ''
@@ -238,6 +244,8 @@ class BaseConfig(object):
 def get(self, key):
 if key in self.d:
 return self.d.get(key)
+elif os.getenv(key):
+return os.getenv(key)
 else:
 return ''
 
@@ -338,10 +346,13 @@ class BaseConfig(object):
 
 def check_arg_machine(self, arg):
 """Check whether it is a machine"""
-if self.get('MACHINE') and self.get('MACHINE') != arg or 
re.search('/', arg):
-raise Exception("Unknown arg: %s" % arg)
-elif self.get('MACHINE') == arg:
+if self.get('MACHINE') == arg:
 return
+elif self.get('MACHINE') and self.get('MACHINE') != arg:
+raise Exception("Maybe conflicted MACHINE: %s vs %s" % 
(self.get('MACHINE'), arg))
+elif re.search('/', arg):
+raise Exception("Unknown arg: %s" % arg)
+
 logger.info('Assuming MACHINE = %s' % arg)
 
 # if we're running under testimage, or similarly as a child
@@ -350,14 +361,14 @@ class BaseConfig(object):
 # FIXME: testimage.bbclass exports these two variables into env,
 # are there other scenarios in which we need to support being
 # invoked by bitbake?
-deploy = os.environ.get('DEPLOY_DIR_IMAGE')
-bbchild = deploy and os.environ.get('OE_TMPDIR')
+deploy = self.get('DEPLOY_DIR_IMAGE')
+bbchild = deploy and self.get('OE_TMPDIR')
 if bbchild:
 self.set_machine_deploy_dir(arg, deploy)
 return
 # also check whether we're running under a sourced toolchain
 # environment file
-if os.environ.get('OECORE_NATIVE_SYSROOT'):
+if self.get('OECORE_NATIVE_SYSROOT'):
 self.set("MACHINE", arg)
 return
 
@@ -430,20 +441,15 @@ class BaseConfig(object):
 if unknown_arg:
 if self.get('MACHINE') == unknown_arg:
 return
-if not self.get('DEPLOY_DIR_IMAGE'):
-# Trying to get DEPLOY_DIR_IMAGE from env.
-p = os.getenv('DEPLOY_DIR_IMAGE')
-if p and self.is_deploy_dir_image(p):
-machine = os.path.basename(p)
-if unknown_arg == machine:
-self.set_machine_deploy_dir(machine, p)
-return
-else:
-logger.info('DEPLOY_DIR_IMAGE: %s' % p)
-self.set("DEPLOY_DIR_IMAGE", p)
+if self.get('DEPLOY_DIR_IMAGE'):
+machine = os.path.basename(self.get('DEPLOY_DIR_IMAGE'))
+if unknown_arg == machine:
+self.set_machine_deploy_dir(machine, p)
+return
+
 self.check_arg_machine(unknown_arg)
 
-if not (self.get('MACHINE') or self.get('DEPLOY_DIR_IMAGE')):
+if not self.get('DEPLOY_DIR_IMAGE'):
 self.load_bitbake_env()
 s = re.search('^DEPLOY_DIR_IMAGE="(.*)"', self.bitbake_e, re.M)
 if s:
@@ -505,7 +511,16 @@ class BaseConfig(object):
 def check_rootfs(self):
 """Check and set rootfs"""
 
-if self.fstype == 'nfs' or self.fstype == "none":
+if self.fstype == "none":
+return
+
+if self.get('ROOTFS'):
+if not self.rootfs:
+self.rootfs = self.get('ROOTFS')
+elif self.get('ROOTFS') != self.rootfs:
+raise Exception("Maybe conflicted ROOTFS: %s vs %s" % 
(self.get('ROOTFS'), self.rootfs))
+
+if self

[OE-core] [PATCH 5/6] runqemu: use realpath for imgdir

[Robert Yang]

The DEPLOY_DIR_IMAGE maybe relative or absolute path since it can be
read from env vars, so use realpath for both imgdir and
DEPLOY_DIR_IMAGE when compare.

Signed-off-by: Robert Yang 
---
 scripts/runqemu | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 1b330b7cfd..b9646223c4 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -705,8 +705,8 @@ class BaseConfig(object):
 # artefacts are relative to that file, rather than in whatever
 # directory DEPLOY_DIR_IMAGE in the conf file points to.
 if self.qbconfload:
-imgdir = os.path.dirname(self.qemuboot)
-if imgdir != self.get('DEPLOY_DIR_IMAGE'):
+imgdir = os.path.realpath(os.path.dirname(self.qemuboot))
+if imgdir != os.path.realpath(self.get('DEPLOY_DIR_IMAGE')):
 logger.info('Setting DEPLOY_DIR_IMAGE to folder containing %s 
(%s)' % (self.qemuboot, imgdir))
 self.set('DEPLOY_DIR_IMAGE', imgdir)
 
-- 
2.11.0.rc2.dirty

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

[OE-core] [PATCH 0/6] fixes for runqemu

[Robert Yang]

The following changes since commit 3a1cce659156ef2654a55a6e3c6922fa2dc780e4:

  glibc: fix nativesdk ldd RTLDLIST (2017-04-05 23:22:06 +0100)

are available in the git repository at:

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

Robert Yang (6):
  runqemu: fix 2 typos
  runqemu: support env vars explicitly
  runqemu: use self.rootfs to replace self.nfs_dir
  runqemu: run without arguments
  runqemu: use realpath for imgdir
  runqemu: do not rely on grepping images

 meta/classes/qemuboot.bbclass |   3 +
 scripts/runqemu   | 130 +++---
 2 files changed, 75 insertions(+), 58 deletions(-)

-- 
2.11.0.rc2.dirty

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

Re: [OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries (rev2)

[Dmitry Rozhkov]

On Thu, 2017-04-06 at 05:32 +, Patchwork wrote:
> == Series Details ==
> 
> Series: python3: fix run-time deps for core python3 libraries (rev2)
> Revision: 2
> URL   : https://patchwork.openembedded.org/series/6164/
> State : failure
> 
> == Summary ==
> 
> 
> Thank you for submitting this patch series to OpenEmbedded Core. This
> is
> an automated response. Several tests have been executed on the
> proposed
> series by patchtest resulting in the following failures:
> 
> 
> 
> * Issue Series does not apply on top of target branch
> [test_series_merge_on_head] 
>   Suggested fixRebase your series on top of targeted branch
>   Targeted branch  master (currently at 3a1cce6591)

So was my master at 3a1cce6591 when I submitted the patch (and still
is). And I believe the first version had no problems with applying it
too.

BR,
Dmitry

> 
> If you believe any of these test results are incorrect, please reply
> to the
> mailing list (openembedded-core@lists.openembedded.org) raising your
> concerns.
> Otherwise we would appreciate you correcting the issues and
> submitting a new
> version of the patchset if applicable. Please ensure you
> add/increment the
> version number when sending the new version (i.e. [PATCH] -> [PATCH
> v2] ->
> [PATCH v3] -> ...).
> 
> ---
> Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-o
> e
> 
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries (rev2)

[Patchwork]

== Series Details ==

Series: python3: fix run-time deps for core python3 libraries (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/6164/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at 3a1cce6591)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

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

[OE-core] [PATCH v2] python3: fix run-time deps for core python3 libraries

[Dmitry Rozhkov]

The http.server module from python3-netclient imports the html module
which is in python3-html. Also xmlrpc.server imports pydoc which is a
part of python3-pydoc. But those run-time dependencies are missing
from python3-netclient and python3-xmlrpc respectively.

Add the missing run-time dependencies.

Signed-off-by: Dmitry Rozhkov 
---

Changes in v2:
- rebased on top of 3a1cce659156ef2654a55a6e3c6922fa2dc780e4

 meta/recipes-devtools/python/python-3.5-manifest.inc | 4 ++--
 scripts/contrib/python/generate-manifest-3.5.py  | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-devtools/python/python-3.5-manifest.inc 
b/meta/recipes-devtools/python/python-3.5-manifest.inc
index 55bcc4b..ec30eb9 100644
--- a/meta/recipes-devtools/python/python-3.5-manifest.inc
+++ b/meta/recipes-devtools/python/python-3.5-manifest.inc
@@ -153,7 +153,7 @@ RDEPENDS_${PN}-multiprocessing="${PN}-core ${PN}-io 
${PN}-lang ${PN}-pickle ${PN
 
FILES_${PN}-multiprocessing="${libdir}/python3.5/lib-dynload/_multiprocessing.*.so
 ${libdir}/python3.5/lib-dynload/__pycache__/_multiprocessing.*.so 
${libdir}/python3.5/multiprocessing 
${libdir}/python3.5/multiprocessing/__pycache__ "
 
 SUMMARY_${PN}-netclient="Python Internet Protocol clients"
-RDEPENDS_${PN}-netclient="${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime 
${PN}-io ${PN}-lang ${PN}-logging ${PN}-mime"
+RDEPENDS_${PN}-netclient="${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime 
${PN}-io ${PN}-lang ${PN}-logging ${PN}-mime ${PN}-html"
 FILES_${PN}-netclient="${libdir}/python3.5/*Cookie*.* 
${libdir}/python3.5/__pycache__/*Cookie*.* ${libdir}/python3.5/base64.* 
${libdir}/python3.5/__pycache__/base64.* ${libdir}/python3.5/cookielib.* 
${libdir}/python3.5/__pycache__/cookielib.* ${libdir}/python3.5/ftplib.* 
${libdir}/python3.5/__pycache__/ftplib.* ${libdir}/python3.5/gopherlib.* 
${libdir}/python3.5/__pycache__/gopherlib.* ${libdir}/python3.5/hmac.* 
${libdir}/python3.5/__pycache__/hmac.* ${libdir}/python3.5/http* 
${libdir}/python3.5/http*/__pycache__ ${libdir}/python3.5/httplib.* 
${libdir}/python3.5/__pycache__/httplib.* ${libdir}/python3.5/mimetypes.* 
${libdir}/python3.5/__pycache__/mimetypes.* ${libdir}/python3.5/nntplib.* 
${libdir}/python3.5/__pycache__/nntplib.* ${libdir}/python3.5/poplib.* 
${libdir}/python3.5/__pycache__/poplib.* ${libdir}/python3.5/smtplib.* 
${libdir}/python3.5/__pycache__/smtplib.* ${libdir}/python3.5/telnetlib.* 
${libdir}/python3.5/__pycache__/telnetlib.* ${libdir}/python3.5/urllib ${lib
 dir}/python3.5/urllib/__pycache__ ${libdir}/python3.5/uuid.* 
${libdir}/python3.5/__pycache__/uuid.* ${libdir}/python3.5/rfc822.* 
${libdir}/python3.5/__pycache__/rfc822.* ${libdir}/python3.5/mimetools.* 
${libdir}/python3.5/__pycache__/mimetools.* "
 
 SUMMARY_${PN}-netserver="Python Internet Protocol servers"
@@ -273,7 +273,7 @@ RDEPENDS_${PN}-xml="${PN}-core ${PN}-re"
 FILES_${PN}-xml="${libdir}/python3.5/lib-dynload/_elementtree.*.so 
${libdir}/python3.5/lib-dynload/__pycache__/_elementtree.*.so 
${libdir}/python3.5/lib-dynload/pyexpat.*.so 
${libdir}/python3.5/lib-dynload/__pycache__/pyexpat.*.so 
${libdir}/python3.5/xml ${libdir}/python3.5/xml/__pycache__ 
${libdir}/python3.5/xmllib.* ${libdir}/python3.5/__pycache__/xmllib.* "
 
 SUMMARY_${PN}-xmlrpc="Python XML-RPC support"
-RDEPENDS_${PN}-xmlrpc="${PN}-core ${PN}-xml ${PN}-netserver ${PN}-lang"
+RDEPENDS_${PN}-xmlrpc="${PN}-core ${PN}-xml ${PN}-netserver ${PN}-lang 
${PN}-pydoc"
 FILES_${PN}-xmlrpc="${libdir}/python3.5/xmlrpclib.* 
${libdir}/python3.5/__pycache__/xmlrpclib.* 
${libdir}/python3.5/SimpleXMLRPCServer.* 
${libdir}/python3.5/__pycache__/SimpleXMLRPCServer.* 
${libdir}/python3.5/DocXMLRPCServer.* 
${libdir}/python3.5/__pycache__/DocXMLRPCServer.* ${libdir}/python3.5/xmlrpc 
${libdir}/python3.5/xmlrpc/__pycache__ "
 
 SUMMARY_${PN}-modules="All Python modules"
diff --git a/scripts/contrib/python/generate-manifest-3.5.py 
b/scripts/contrib/python/generate-manifest-3.5.py
index 386bdfc..5835de8 100755
--- a/scripts/contrib/python/generate-manifest-3.5.py
+++ b/scripts/contrib/python/generate-manifest-3.5.py
@@ -340,7 +340,7 @@ if __name__ == "__main__":
 m.addPackage( "${PN}-multiprocessing", "Python multiprocessing support", 
"${PN}-core ${PN}-io ${PN}-lang ${PN}-pickle ${PN}-threading ${PN}-ctypes 
${PN}-mmap",
 "lib-dynload/_multiprocessing.*.so multiprocessing" ) # package
 
-m.addPackage( "${PN}-netclient", "Python Internet Protocol clients", 
"${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime ${PN}-io ${PN}-lang 
${PN}-logging ${PN}-mime",
+m.addPackage( "${PN}-netclient", "Python Internet Protocol clients", 
"${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime ${PN}-io ${PN}-lang 
${PN}-logging ${PN}-mime ${PN}-html",
 "*Cookie*.* " +
 "base64.* cookielib.* ftplib.* gopherlib.* hmac.* http* httplib.* 
mimetypes.* nntplib.* poplib.* smtplib.* telnetlib.* urllib  uuid.* rfc822.* 
mimetools.*" )
 
@@ -422,7 +422,7 @@ if 

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

[Bruce Ashfield]

On Thu, Apr 6, 2017 at 12:41 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Thu, 2017-04-06 at 00:33 +0200, Bruce Ashfield wrote:
> > On Wed, Apr 5, 2017 at 3:21 PM, Richard Purdie
> >  wrote:
> > >
> > > > @@ -16,5 +16,4 @@ QB_MACHINE = "-machine versatilepb"
> > > >  QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty"
> > > >  # Add the 'virtio-rng-pci' device otherwise the guest may run
> > > out of entropy
> > > >  QB_OPT_APPEND = "-show-cursor -usb -usbdevice tablet -device
> > > virtio-rng-pci"
> > > > -PREFERRED_VERSION_linux-yocto ??= "4.8%"
> > > >  QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux
> > > -yocto', '4.7', '', 'zImage-versatile-pb.dtb', d)}"
> > >
> > > Note the line below the line you're removing here. This is why we
> > > need
> > > this one...
> > I had noticed that, but since the newest version is well above that,
> > I figured it would be ok.
>
> An unset variable returns "None", not sure
> what base_version_less_or_equal makes of that...
>
> > I can spin another patch that leaves it in place for ARM, but drops
> > it for x86.
>
> I took Martin's patch moving things to 4.10, quite happy to take a
> second one removing the x86 version. Removing the arm one too would be
> nice but I'm not sure we can yet.
>

Sounds good. I'll rebase onto those changes and follow up.

Bruce


>
> Cheers,
>
> Richard
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

[Richard Purdie]

On Thu, 2017-04-06 at 00:33 +0200, Bruce Ashfield wrote:
> On Wed, Apr 5, 2017 at 3:21 PM, Richard Purdie
>  wrote:
> > 
> > > @@ -16,5 +16,4 @@ QB_MACHINE = "-machine versatilepb"
> > >  QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty"
> > >  # Add the 'virtio-rng-pci' device otherwise the guest may run
> > out of entropy
> > >  QB_OPT_APPEND = "-show-cursor -usb -usbdevice tablet -device
> > virtio-rng-pci"
> > > -PREFERRED_VERSION_linux-yocto ??= "4.8%"
> > >  QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux
> > -yocto', '4.7', '', 'zImage-versatile-pb.dtb', d)}"
> > 
> > Note the line below the line you're removing here. This is why we  
> > need
> > this one...
> I had noticed that, but since the newest version is well above that,
> I figured it would be ok.

An unset variable returns "None", not sure
what base_version_less_or_equal makes of that...

> I can spin another patch that leaves it in place for ARM, but drops
> it for x86.

I took Martin's patch moving things to 4.10, quite happy to take a
second one removing the x86 version. Removing the arm one too would be
nice but I'm not sure we can yet.

Cheers,

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

[OE-core] [PATCH] selftest/wic: skip wic unit tests in case NLS is disable

[leonardo . sandoval . gonzalez]

From: Leonardo Sandoval 

WIC test case requires wic-tools which in turn depends on intltool-native and
gettext-native. However, if NLS is disable, the gettext-minimal-native is used 
instead
of gettext-native causing a failure on intltool-native as seen below:

  checking for msgfmt... no
  checking for gmsgfmt... no
  configure: error: GNU gettext tools not found; required for intltool
  ERROR: Function failed: do_configure (log file is located at 
/home/lsandov1/poky/build/tmp/work/i586-poky-linux-musl/systemd-boot/232-r0/temp/log.do_configure.7518)
  ERROR: Task 
(/home/lsandov1/poky/meta/recipes-bsp/systemd-boot/systemd-boot_232.bb:do_configure)
 failed with exit code '1'
  NOTE: Tasks Summary: Attempted 609 tasks of which 604 didn't need to be rerun 
and 1 failed.

[YOCTO #10902]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/selftest/wic.py | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/wic.py b/meta/lib/oeqa/selftest/wic.py
index df5e060..8030c35 100644
--- a/meta/lib/oeqa/selftest/wic.py
+++ b/meta/lib/oeqa/selftest/wic.py
@@ -77,7 +77,10 @@ class Wic(oeSelfTest):
 # clean up which can result in the native tools built earlier in
 # setUpClass being unavailable.
 if not Wic.image_is_ready:
-bitbake('wic-tools')
+if get_bb_var('USE_NLS') == 'yes':
+bitbake('wic-tools')
+else:
+self.skipTest('wic-tools cannot be built due its 
(intltool|gettext)-native dependency and NLS disable')
 
 bitbake('core-image-minimal')
 Wic.image_is_ready = True
-- 
2.10.2

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

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

[Bruce Ashfield]

On Wed, Apr 5, 2017 at 3:21 PM, Richard Purdie  wrote:

> On Wed, 2017-04-05 at 08:39 -0400, Bruce Ashfield wrote:
> > We don't make a linux-yocto version available unless it boots
> > on all qemu targets, hence there is no reason to specify a
> > specific version .. the latest is always fine.
> >
> > Also, the other qemu machines don't have this specification, so
> > this makes x86 and ARM consistent.
> >
> >
> > diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/
> qemuarm.conf
> > index f9d6dd7e364e..b9b640f974f3 100644
> > --- a/meta/conf/machine/qemuarm.conf
> > +++ b/meta/conf/machine/qemuarm.conf
> > @@ -16,5 +16,4 @@ QB_MACHINE = "-machine versatilepb"
> >  QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty"
> >  # Add the 'virtio-rng-pci' device otherwise the guest may run out of
> entropy
> >  QB_OPT_APPEND = "-show-cursor -usb -usbdevice tablet -device
> virtio-rng-pci"
> > -PREFERRED_VERSION_linux-yocto ??= "4.8%"
> >  QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux-yocto',
> '4.7', '', 'zImage-versatile-pb.dtb', d)}"
>
> Note the line below the line you're removing here. This is why we   need
> this one...
>

I had noticed that, but since the newest version is well above that, I
figured it
would be ok.

I can spin another patch that leaves it in place for ARM, but drops it for
x86.

Bruce


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



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] license.bbclass: improve reproducibility

[Juro Bystricky]

Two identical builds can end up having deploy/licenses folders
that differ. This is observed in cases where there are several
different license files of the same name in different folders,
i.e. "COPYING". In those case we have to differentiate the files
somehow and we do it via file expensions such as COPYING.0, COPYING.1.
However, which file will get which extension is presently random.
This means, for example, that COPYING.0 in one build is the same
as COPYING.1 in the other (and vice versa).
Although there is mothing wrong with this, for the sake of binary
reproducibility it is preferable to have a deterministic outcome.

Signed-off-by: Juro Bystricky 
---
 meta/classes/license.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/license.bbclass b/meta/classes/license.bbclass
index 81458e7..d4be478 100644
--- a/meta/classes/license.bbclass
+++ b/meta/classes/license.bbclass
@@ -505,7 +505,7 @@ def find_license_files(d):
 bb.warn("%s: Failed to parse it's LICENSE field." % (d.getVar('PF')))
 # Add files from LIC_FILES_CHKSUM to list of license files
 lic_chksum_paths = defaultdict(OrderedDict)
-for path, data in lic_chksums.items():
+for path, data in sorted(lic_chksums.items()):
 lic_chksum_paths[os.path.basename(path)][data] = (os.path.join(srcdir, 
path), data[1], data[2])
 for basename, files in lic_chksum_paths.items():
 if len(files) == 1:
-- 
2.7.4

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

[OE-core] [PATCH v2] create-pull-request: add "-t in-reply-to" option

[Jose Lamego]

The create-pull-request script creates patches as replies to a cover
letter, in the form of an email thread. If further revisions are sent to
the mailing list without referencing to the first revision, these new
revisions are not identified at the mailing list as part of the original
thread, but as a new thread instead.

This change adds the "[-t in_reply_to]" option, where "in_reply_to" is
the original cover letter's Message-Id, so this reference is added
to the new cover letter to ensure the thread continuity.

[YOCTO #11294]

Signed-off-by: Jose Lamego 
---
 scripts/create-pull-request | 17 +
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/scripts/create-pull-request b/scripts/create-pull-request
index e82858b..8f0be99 100755
--- a/scripts/create-pull-request
+++ b/scripts/create-pull-request
@@ -34,7 +34,7 @@ RFC=0
 usage() {
 CMD=$(basename $0)
 cat <"
 EOM
 }
 
 REMOTE="$CPR_CONTRIB_REMOTE"
 # Parse and validate arguments
-while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
+while getopts "b:acd:hi:m:o:p:r:s:u:l:t:" OPT; do
case $OPT in
b)
BRANCH="$OPTARG"
@@ -108,7 +110,10 @@ while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
a)
CPR_CONTRIB_AUTO_PUSH="1"
;;
-   esac
+t)
+IN_REPLY_TO="$OPTARG"
+;;
+esac
 done
 
 if [ -z "$REMOTE" ]; then
@@ -205,7 +210,11 @@ if [ -n "$RELDIR" ]; then
 fi
 
 # Generate the patches and cover letter
-git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
+if [ -n "$IN_REPLY_TO" ]; then
+git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --in-reply-to="$IN_REPLY_TO" --cover-letter 
$RELATIVE_TO..$COMMIT_ID > /dev/null
+else
+git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
+fi
 
 if [ -z "$(ls -A $ODIR 2> /dev/null)" ]; then
 echo "ERROR: $ODIR is empty, no cover letter and patches was generated!"
-- 
2.7.4

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

[OE-core] [yocto][patchwork][PATCH v2] create-pull-request: add "-t in-reply-to" option

[Jose Lamego]

The create-pull-request script creates patches as replies to a cover
letter, in the form of an email thread. If further revisions are sent to
the mailing list without referencing to the first revision, these new
revisions are not identified at the mailing list as part of the original
thread, but as a new thread instead.

This change adds the "[-t in_reply_to]" option, where "in_reply_to" is
the original cover letter's Message-Id, so this reference is added
to the new cover letter to ensure the thread continuity.

[YOCTO #11294]

Signed-off-by: Jose Lamego 
---
 scripts/create-pull-request | 17 +
 1 file changed, 13 insertions(+), 4 deletions(-)

diff --git a/scripts/create-pull-request b/scripts/create-pull-request
index e82858b..8f0be99 100755
--- a/scripts/create-pull-request
+++ b/scripts/create-pull-request
@@ -34,7 +34,7 @@ RFC=0
 usage() {
 CMD=$(basename $0)
 cat <"
 EOM
 }
 
 REMOTE="$CPR_CONTRIB_REMOTE"
 # Parse and validate arguments
-while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
+while getopts "b:acd:hi:m:o:p:r:s:u:l:t:" OPT; do
case $OPT in
b)
BRANCH="$OPTARG"
@@ -108,7 +110,10 @@ while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
a)
CPR_CONTRIB_AUTO_PUSH="1"
;;
-   esac
+t)
+IN_REPLY_TO="$OPTARG"
+;;
+esac
 done
 
 if [ -z "$REMOTE" ]; then
@@ -205,7 +210,11 @@ if [ -n "$RELDIR" ]; then
 fi
 
 # Generate the patches and cover letter
-git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
+if [ -n "$IN_REPLY_TO" ]; then
+git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --in-reply-to="$IN_REPLY_TO" --cover-letter 
$RELATIVE_TO..$COMMIT_ID > /dev/null
+else
+git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
--thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
+fi
 
 if [ -z "$(ls -A $ODIR 2> /dev/null)" ]; then
 echo "ERROR: $ODIR is empty, no cover letter and patches was generated!"
-- 
2.7.4

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

Re: [OE-core] [PATCH] create-pull-request: add "-t in-reply-to" option

[Jose Lamego]

On 04/05/2017 09:00 AM, Leonardo Sandoval wrote:
> On Tue, 2017-04-04 at 16:45 -0500, Jose Lamego wrote:
>> The create-patch-request script creates patches as replies to a cover
> 
> you mean create-pull-request, I believe
> 
>> letter, in the form of an email thread. If further revisions are sent to
>> the mailing list without referencing to the first revision, these new
>> revisions are not identified at the mailing list as part of the original
>> thread, but as a new thread instead.
>>
>> This change adds the "[-t in_reply_to]" option, where "in_reply_to" is
>> the original cover letter's Message-Id, so this reference is added
>> to the new cover letter to ensure the thread continuity.
>>
> 
> 
> BTW, is there an easy way to get the in-reply-to email besides using
> git-pw or looking at the message source?

That's a good question, I actually don't know of an easier way of
knowing the Message-Id. Will further investigate.

> 
> Some comments in patch:
> 
Thanks Leo!
> 
> 
> 
>> [YOCTO #11294]
>>
>> Signed-off-by: Jose Lamego 
>> ---
>>  scripts/create-pull-request | 14 +++---
>>  1 file changed, 11 insertions(+), 3 deletions(-)
>>
>> diff --git a/scripts/create-pull-request b/scripts/create-pull-request
>> index e82858b..46d6538 100755
>> --- a/scripts/create-pull-request
>> +++ b/scripts/create-pull-request
>> @@ -34,7 +34,7 @@ RFC=0
>>  usage() {
>>  CMD=$(basename $0)
>>  cat <> -Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s subject] [-r 
>> relative_to] [-i commit_id] [-d relative_dir] -u remote [-b branch]
>> +Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s subject] [-r 
>> relative_to] [-i commit_id] [-d relative_dir] -u remote [-b branch] [-t 
>> in_reply_to]
>>-b branch   Branch name in the specified remote (default: current 
>> branch)
>>-l local branch Local branch name (default: HEAD)
>>-c  Create an RFC (Request for Comment) patch series
>> @@ -49,6 +49,7 @@ Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s 
>> subject] [-r relative_to
>>-s subject  The subject to be inserted into the summary email
>>-u remote   The git remote where the branch is located, or set 
>> CPR_CONTRIB_REMOTE in env
>>-d relative_dir Generate patches relative to directory
>> +  -t in_reply_to  Make mails appear as replies to the given Message-Id, 
>> to continue patch/series threads
>>  
>>   Examples:
>> $CMD -u contrib -b nitin/basic
>> @@ -57,12 +58,13 @@ Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s 
>> subject] [-r relative_to
>> $CMD -u contrib -r master -i misc -b nitin/misc -o pull-misc
>> $CMD -u contrib -p "RFC PATCH" -b nitin/experimental
>> $CMD -u contrib -i misc -b nitin/misc -d ./bitbake
>> +   $CMD -u contrib -p "OE-core][PATCH v2" -t 
>> ""
>>  EOM
>>  }
>>  
>>  REMOTE="$CPR_CONTRIB_REMOTE"
>>  # Parse and validate arguments
>> -while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
>> +while getopts "b:acd:hi:m:o:p:r:s:u:l:t:" OPT; do
>>  case $OPT in
>>  b)
>>  BRANCH="$OPTARG"
>> @@ -108,6 +110,8 @@ while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
>>  a)
>>  CPR_CONTRIB_AUTO_PUSH="1"
>>  ;;
>> +t)
>> +IN_REPLY_TO="$OPTARG"
> 
> it would be nice to include also the double semi-colon, so future cases
> just start after it.
> 
done in v2 patch.
> 
>>  esac
>>  done
>>  
>> @@ -205,7 +209,11 @@ if [ -n "$RELDIR" ]; then
>>  fi
>>  
>>  # Generate the patches and cover letter
>> -git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
>> --thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
>> +if [ -z "$IN_REPLY_TO" ]; then
> 
> -n instead of -z?
> 
also done in v2 patch

>> +git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
>> --thread=shallow --in-reply-to="$IN_REPLY_TO" --cover-letter 
>> $RELATIVE_TO..$COMMIT_ID > /dev/null
>> +else
>> +git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
>> --thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
>> +fi
>>  
>>  if [ -z "$(ls -A $ODIR 2> /dev/null)" ]; then
>>  echo "ERROR: $ODIR is empty, no cover letter and patches was generated!"
>> -- 
>> 2.7.4
>>
> 
> 

-- 
Jose Lamego | OTC Embedded Platforms & Tools | GDC



signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/1] package_ipk.bbclass: Replace empty lines in DESCRIPTION with '.'

[mariano . lopez]

From: Mariano Lopez 

This will deal with empty lines in DESCRIPTION while creating ipk packages.

Changes in v2:

- Firts version of this patch would fail do_package_write_ipk task if found an
  empty line in DESCRIPTION, this version will replace an empty line with a '.'
  as suggested by Ross.

The following changes since commit eff56e4f0d59b1d965a68e4f009b7f07717b7edd:

  bitbake: bitbake-user-manual: Fixed special character in -D output 
(2017-04-03 22:32:02 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib mariano/bug10677v2
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mariano/bug10677v2

Mariano Lopez (1):
  package_ipk.bbclass: Replace empty lines in DESCRIPTION with '.'

 meta/classes/package_ipk.bbclass | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.10.2

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

[OE-core] [PATCH 1/1] package_ipk.bbclass: Replace empty lines in DESCRIPTION with '.'

[mariano . lopez]

From: Mariano Lopez 

opkg uses empty lines as separator for next package and if an ipk file was
packaged with empty lines in DESCRIPTION opkg won't be able to handle such ipk
file, this happens at execution time.

This commit will replace empty lines in DESCRIPTION with a '.' when generating
an ipk package to avoid this issue.

[YOCTO #10677]

Signed-off-by: Mariano Lopez 
---
 meta/classes/package_ipk.bbclass | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/classes/package_ipk.bbclass b/meta/classes/package_ipk.bbclass
index fa47385..c7cec9d 100644
--- a/meta/classes/package_ipk.bbclass
+++ b/meta/classes/package_ipk.bbclass
@@ -145,7 +145,11 @@ python do_package_ipk () {
 # We don't limit the width when manually indent, but 
we do
 # need the textwrap.fill() to set the initial_indent 
and
 # subsequent_indent, so set a large width
-ctrlfile.write('%s\n' % textwrap.fill(t.strip(), 
width=10, initial_indent=' ', subsequent_indent=' '))
+line = textwrap.fill(t.strip(),
+ width=10,
+ initial_indent=' ',
+ subsequent_indent=' ') or '.'
+ctrlfile.write('%s\n' % line)
 else:
 # Auto indent
 ctrlfile.write('%s\n' % textwrap.fill(description, 
width=74, initial_indent=' ', subsequent_indent=' '))
-- 
2.10.2

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

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Ravi chandra reddy]

Hi,
 is this what you are talking about

root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime#
ls -ltr *libxml*
-rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-ptest.packaged
-rwxrwxrwx 2 root root 463307 Nov 21 14:05 libxml2-ptest
-rwxrwxrwx 2 root root933 Nov 21 14:05 libxml2-staticdev
-rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-dbg.packaged
-rwxrwxrwx 2 root root  10526 Nov 21 14:05 libxml2-dbg
-rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-dev.packaged
-rwxrwxrwx 2 root root   3836 Nov 21 14:05 libxml2-dev
-rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-doc.packaged
-rwxrwxrwx 2 root root  17476 Nov 21 14:05 libxml2-doc
-rwxrwxrwx 2 root root638 Nov 21 14:05 libxml2-locale
-rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2.packaged
-rwxrwxrwx 2 root root   4164 Nov 21 14:05 libxml2
-rwxrwxrwx 2 root root628 Nov 21 14:05 libxml2-utils
-rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-python.packaged
-rwxrwxrwx 2 root root   2910 Nov 21 14:05 libxml2-python
root@polar
:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime#
root@polar
:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime#
root@polar
:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime#
root@polar
:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime#

if not, then sorry, i didnt get you when you say "static dev packages"

Thanks


On Wed, Apr 5, 2017 at 2:26 PM, Matthew McClintock 
wrote:

> Do you have the staticdev packages in your TMPDIR? E.g.
>
> tmp/work/cortexa15t2hf-neon-rdk-linux-gnueabi/libxml2/2.9.
> 4-r0/deploy-ipks/cortexa15t2hf-neon/libxml2-staticdev_2.9.4-r0_
> cortexa15t2hf-neon.ipk
>
> -M
>
> On Wed, Apr 5, 2017 at 1:09 PM, Ravi chandra reddy 
> wrote:
> > Hi,
> > Let me thank you guys for quick reply.
> > let me put my  email in correct steps
> >
> > 1. below local/local.conf changes makes bitbake fail.
> >
> > IMAGE_INSTALL_append = "lib32-glibc
> lib32-libgcc
> > lib32-libstdc++ libedit libxml2-staticdev"
> >
> > error:=
> > == i get the following
> > errors==
> > ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> > ERROR: Logfile of failure stored in:
> > /home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-
> poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
> > ERROR: Task 9
> > (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-
> image-minimal.bb,
> > do_rootfs) failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to be
> > rerun and 1 failed.
> > ===
> >
> > 2.  without staticdev changes [in local/local.conf], it
> > [bitbake-core-image-minimal] goes through and it builds [but there is
> only
> > .so [dynamic library] generated]
> >
> > IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
> > libxml2"
> >
> >
> > 3. i ran the search and found that all "no-static" lines are commented
> >
> > bitbake -e | grep static-libs
> >
> >
> > and all the "no-static-libs.inc" are commented [#]
> >
> > Thanks
> > RC
> >
> > On Wed, Apr 5, 2017 at 2:04 PM, Ravi chandra reddy 
> > wrote:
> >>
> >> Hi,
> >>in local/local.conf it [bitbake core-image-minimal] fails, if i
> use
> >> libxml2-staticdev
> >>
> >>   # Specify the 32-bit libraries to be added to all images
> >> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
> >> libxml2-staticdev"
> >>
> >> == i get the following
> >> errors==
> >> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> >> ERROR: Logfile of failure stored in:
> >> /home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-
> poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
> >> ERROR: Task 9
> >> (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-
> image-minimal.bb,
> >> do_rootfs) failed with exit code '1'
> >> NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to
> be
> >> rerun and 1 failed.
> >> ===
> >>
> >> if i use as below, there is no issue. however there is no .so
> >>
> >> # Specify the 32-bit libraries to be added to all images
> >> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
> >> libxml2"
> >>
> >> i ran
> >>
> >> bitbake -e | grep static-libs
> >>
> >> and all the "no-static-libs.inc" are commented [#]
> >>
> >> Thanks
> >> RC
> >>
> >>
> >>
> >> On Wed, Apr 5, 2017 at 11:48 AM, Richard Purdie
> >>  wrote:
> >>>
> >>> On Wed, 2017-04-05 at 10:33 -0500, Matthew McClintock wrote:
> >>> > On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy  >>> > com> wrote:
> >>> > >
> >>> > > Hi All,
> >>> > >   I am using meta-oe to generate libxml2 library using
> >>> > > AARCH64
> >>> > > compiler. However it generates shared object [.so]

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Matthew McClintock]

Do you have the staticdev packages in your TMPDIR? E.g.

tmp/work/cortexa15t2hf-neon-rdk-linux-gnueabi/libxml2/2.9.4-r0/deploy-ipks/cortexa15t2hf-neon/libxml2-staticdev_2.9.4-r0_cortexa15t2hf-neon.ipk

-M

On Wed, Apr 5, 2017 at 1:09 PM, Ravi chandra reddy  wrote:
> Hi,
> Let me thank you guys for quick reply.
> let me put my  email in correct steps
>
> 1. below local/local.conf changes makes bitbake fail.
>
> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc
> lib32-libstdc++ libedit libxml2-staticdev"
>
> error:=
> == i get the following
> errors==
> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
> ERROR: Task 9
> (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-image-minimal.bb,
> do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to be
> rerun and 1 failed.
> ===
>
> 2.  without staticdev changes [in local/local.conf], it
> [bitbake-core-image-minimal] goes through and it builds [but there is only
> .so [dynamic library] generated]
>
> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
> libxml2"
>
>
> 3. i ran the search and found that all "no-static" lines are commented
>
> bitbake -e | grep static-libs
>
>
> and all the "no-static-libs.inc" are commented [#]
>
> Thanks
> RC
>
> On Wed, Apr 5, 2017 at 2:04 PM, Ravi chandra reddy 
> wrote:
>>
>> Hi,
>>in local/local.conf it [bitbake core-image-minimal] fails, if i use
>> libxml2-staticdev
>>
>>   # Specify the 32-bit libraries to be added to all images
>> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
>> libxml2-staticdev"
>>
>> == i get the following
>> errors==
>> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
>> ERROR: Logfile of failure stored in:
>> /home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
>> ERROR: Task 9
>> (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-image-minimal.bb,
>> do_rootfs) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to be
>> rerun and 1 failed.
>> ===
>>
>> if i use as below, there is no issue. however there is no .so
>>
>> # Specify the 32-bit libraries to be added to all images
>> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
>> libxml2"
>>
>> i ran
>>
>> bitbake -e | grep static-libs
>>
>> and all the "no-static-libs.inc" are commented [#]
>>
>> Thanks
>> RC
>>
>>
>>
>> On Wed, Apr 5, 2017 at 11:48 AM, Richard Purdie
>>  wrote:
>>>
>>> On Wed, 2017-04-05 at 10:33 -0500, Matthew McClintock wrote:
>>> > On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy >> > com> wrote:
>>> > >
>>> > > Hi All,
>>> > >   I am using meta-oe to generate libxml2 library using
>>> > > AARCH64
>>> > > compiler. However it generates shared object [.so] library.
>>> > >
>>> > > is there any setting in recipe to modify this, to generate static
>>> > > library
>>> > > [instead of shared library]
>>> > >
>>> > > if so, please point me to the recipe/file to change.
>>> > >
>>> > > if not, i will try to add it as patch, plz point me to appropriate
>>> > > files to
>>> > > change
>>> > Is the ${PN}-staticdev package getting generated for you?
>>>
>>> Its possible you have conf/distro/include/no-static-libs.inc included
>>> in your build (bitbake -e would tell you).
>>>
>>> If so, you could remove that include or set:
>>>
>>> DISABLE_STATIC = ""
>>>
>>> as it would currently be set to this if that include file is included:
>>>
>>> DISABLE_STATIC = " --disable-static"
>>>
>>> We tend not to build static libraries as they're a waste of space/time
>>> on the most part.
>>>
>>> Cheers,
>>>
>>> Richard
>>
>>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 3/3] yocto-compat-layer: include bitbake-diffsigs output

[Patrick Ohly]

On Wed, 2017-04-05 at 10:26 -0500, Leonardo Sandoval wrote:
> > diff --git a/scripts/lib/compatlayer/cases/common.py 
> > b/scripts/lib/compatlayer/cases/common.py
> > index b91da9b..d909d5b 100644
> > --- a/scripts/lib/compatlayer/cases/common.py
> > +++ b/scripts/lib/compatlayer/cases/common.py
> > @@ -76,4 +76,14 @@ class CommonCompatLayer(OECompatLayerTestCase):
> > (self.tc.layer['name'], len(sig_diff)))
> >  for diff in sorted(sig_diff_filtered):
> >  msg.append('   %s: %s -> %s' % diff)
> > +try:
> > +recipe, taskname = diff[0].rsplit(':', 1)
> > +output = check_command('Determining signature 
> > difference failed.',
> > +   'bitbake-diffsigs --task %s %s 
> > --signature %s %s' %
> > +   (recipe, taskname, diff[1], 
> > diff[2])).decode('utf-8')
> > +except RuntimeError as error:
> > +output = str(error)
> 
> Patrick, just a minor comment:  there is no need for the 'if' check,
> because the try and the except bodies set the output variable.

I added that for the case that the command prints nothing (output ==
''). It's unlikely, but I prefer explicit, easy checking over making
assumptions.

-- 
Best Regards, Patrick Ohly

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



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

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Ravi chandra reddy]

Hi,
Let me thank you guys for quick reply.
let me put my  email in correct steps

1. below local/local.conf changes makes bitbake fail.

IMAGE_INSTALL_append = "lib32-glibc
lib32-libgcc lib32-libstdc++ libedit libxml2-*staticdev*"

error:=
== i get the following
errors==
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/polar/zcu_yocto/poky/
build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/
1.0-r0/temp/log.do_rootfs.17721
ERROR: Task 9 (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-
image-minimal.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to be
rerun and 1 failed.
===

2.  without staticdev changes [in local/local.conf], it
[bitbake-core-image-minimal] goes through and it builds [but there is only
.so [dynamic library] generated]

IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
libxml2"


3. i ran the search and found that all "no-static" lines are commented

bitbake -e | grep static-libs


and all the "no-static-libs.inc" are commented [#]

Thanks
RC

On Wed, Apr 5, 2017 at 2:04 PM, Ravi chandra reddy 
wrote:

> Hi,
>in local/local.conf it [bitbake core-image-minimal] fails, if i use
> libxml2-staticdev
>
>   # Specify the 32-bit libraries to be added to all images
> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
> libxml2-staticdev"
>
> == i get the following
> errors==
> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> ERROR: Logfile of failure stored in: /home/polar/zcu_yocto/poky/
> build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/
> 1.0-r0/temp/log.do_rootfs.17721
> ERROR: Task 9 (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-
> image-minimal.bb, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to be
> rerun and 1 failed.
> ===
>
> if i use as below, there is no issue. however there is no .so
>
> # Specify the 32-bit libraries to be added to all images
> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
> libxml2"
>
> i ran
>
> bitbake -e | grep static-libs
>
> and all the "no-static-libs.inc" are commented [#]
>
> Thanks
> RC
>
>
>
> On Wed, Apr 5, 2017 at 11:48 AM, Richard Purdie  linuxfoundation.org> wrote:
>
>> On Wed, 2017-04-05 at 10:33 -0500, Matthew McClintock wrote:
>> > On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy > > com> wrote:
>> > >
>> > > Hi All,
>> > >   I am using meta-oe to generate libxml2 library using
>> > > AARCH64
>> > > compiler. However it generates shared object [.so] library.
>> > >
>> > > is there any setting in recipe to modify this, to generate static
>> > > library
>> > > [instead of shared library]
>> > >
>> > > if so, please point me to the recipe/file to change.
>> > >
>> > > if not, i will try to add it as patch, plz point me to appropriate
>> > > files to
>> > > change
>> > Is the ${PN}-staticdev package getting generated for you?
>>
>> Its possible you have conf/distro/include/no-static-libs.inc included
>> in your build (bitbake -e would tell you).
>>
>> If so, you could remove that include or set:
>>
>> DISABLE_STATIC = ""
>>
>> as it would currently be set to this if that include file is included:
>>
>> DISABLE_STATIC = " --disable-static"
>>
>> We tend not to build static libraries as they're a waste of space/time
>> on the most part.
>>
>> Cheers,
>>
>> Richard
>>
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Ravi chandra reddy]

Hi,
   in local/local.conf it [bitbake core-image-minimal] fails, if i use
libxml2-staticdev

  # Specify the 32-bit libraries to be added to all images
IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
libxml2-staticdev"

== i get the following
errors==
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
ERROR: Task 9 (/home/polar/zcu_yocto/poky/meta/recipes-core/images/
core-image-minimal.bb, do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to be
rerun and 1 failed.
===

if i use as below, there is no issue. however there is no .so

# Specify the 32-bit libraries to be added to all images
IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
libxml2"

i ran

bitbake -e | grep static-libs

and all the "no-static-libs.inc" are commented [#]

Thanks
RC



On Wed, Apr 5, 2017 at 11:48 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Wed, 2017-04-05 at 10:33 -0500, Matthew McClintock wrote:
> > On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy  > com> wrote:
> > >
> > > Hi All,
> > >   I am using meta-oe to generate libxml2 library using
> > > AARCH64
> > > compiler. However it generates shared object [.so] library.
> > >
> > > is there any setting in recipe to modify this, to generate static
> > > library
> > > [instead of shared library]
> > >
> > > if so, please point me to the recipe/file to change.
> > >
> > > if not, i will try to add it as patch, plz point me to appropriate
> > > files to
> > > change
> > Is the ${PN}-staticdev package getting generated for you?
>
> Its possible you have conf/distro/include/no-static-libs.inc included
> in your build (bitbake -e would tell you).
>
> If so, you could remove that include or set:
>
> DISABLE_STATIC = ""
>
> as it would currently be set to this if that include file is included:
>
> DISABLE_STATIC = " --disable-static"
>
> We tend not to build static libraries as they're a waste of space/time
> on the most part.
>
> Cheers,
>
> Richard
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Richard Purdie]

On Wed, 2017-04-05 at 10:33 -0500, Matthew McClintock wrote:
> On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy  com> wrote:
> > 
> > Hi All,
> >   I am using meta-oe to generate libxml2 library using
> > AARCH64
> > compiler. However it generates shared object [.so] library.
> > 
> > is there any setting in recipe to modify this, to generate static
> > library
> > [instead of shared library]
> > 
> > if so, please point me to the recipe/file to change.
> > 
> > if not, i will try to add it as patch, plz point me to appropriate
> > files to
> > change
> Is the ${PN}-staticdev package getting generated for you?

Its possible you have conf/distro/include/no-static-libs.inc included
in your build (bitbake -e would tell you).

If so, you could remove that include or set:

DISABLE_STATIC = ""

as it would currently be set to this if that include file is included:

DISABLE_STATIC = " --disable-static"

We tend not to build static libraries as they're a waste of space/time
on the most part.

Cheers,

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

[OE-core] [PATCH] package.bbclass: add CONFFILES to pkgdata

[David Vincent]

Emit CONFFILES variable in pkgdata, or else the get_conffiles function
will return 'None' for some packages instead of the expected value. This
is especially true for optional module packages.

Signed-off-by: David Vincent 
---
 meta/classes/package.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 1bc4f6a4dc..cc466bd1b2 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1380,6 +1380,7 @@ python emit_pkgdata() {
 write_if_exists(sf, pkg, 'PKG')
 write_if_exists(sf, pkg, 'ALLOW_EMPTY')
 write_if_exists(sf, pkg, 'FILES')
+write_if_exists(sf, pkg, 'CONFFILES')
 write_if_exists(sf, pkg, 'pkg_postinst')
 write_if_exists(sf, pkg, 'pkg_postrm')
 write_if_exists(sf, pkg, 'pkg_preinst')
-- 
2.12.2

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

Re: [OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Matthew McClintock]

On Wed, Apr 5, 2017 at 10:18 AM, Ravi chandra reddy  wrote:
> Hi All,
>   I am using meta-oe to generate libxml2 library using AARCH64
> compiler. However it generates shared object [.so] library.
>
> is there any setting in recipe to modify this, to generate static library
> [instead of shared library]
>
> if so, please point me to the recipe/file to change.
>
> if not, i will try to add it as patch, plz point me to appropriate files to
> change

Is the ${PN}-staticdev package getting generated for you?

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

[OE-core] Fwd: Recipe [patch] modification to generate a static library instead of shared library

[Ravi chandra reddy]

Hi All,
  I am using meta-oe to generate libxml2 library using AARCH64
compiler. However it generates shared object [.so] library.

is there any setting in recipe to modify this, to generate static library
[instead of shared library]

if so, please point me to the recipe/file to change.

if not, i will try to add it as patch, plz point me to appropriate files to
change

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

Re: [OE-core] [PATCH 3/3] yocto-compat-layer: include bitbake-diffsigs output

[Leonardo Sandoval]

On Wed, 2017-04-05 at 15:36 +0200, Patrick Ohly wrote:
> After filtering out potential false positives, it becomes feasible to
> include the output of bitbake-diffsigs for those tasks which
> definitely have a change.
> 
> Depends on bitbake-diffsigs with the "--signature" parameter.
> 
> Enhanced output now is:
> 
>AssertionError: False is not true : Layer meta- changed 120 
> signatures, initial differences (first hash without, second with layer):
>   gstreamer1.0-plugins-base:do_fetch: 76973f19f2e30d282152bdd7e4efe5bb -> 
> e6e7c6fa9f2bd59d7d8d107f7c6ca1ac
>  Task dependencies changed from:
>  ['PV', 'SRCREV', 'SRC_URI', 'SRC_URI[md5sum]', 'SRC_URI[sha256sum]', 
> 'base_do_fetch']
>  to:
>  ['GST_IMX_PATCHES_TO_APPEND', 'PV', 'SRCREV', 'SRC_URI', 
> 'SRC_URI[md5sum]', 'SRC_URI[sha256sum]', 'base_do_fetch']
>  basehash changed from d679d30bd1ea41c56e57419b57587f3c to 
> 090a79b45f5fa26d10f9d34e2ed7a1e6
> List of dependencies for variable SRC_URI changed from '{'PV', 
> 'SRC_URI[md5sum]', 'SRC_URI[sha256sum]'}' to '{'GST_IMX_PATCHES_TO_APPEND', 
> 'PV', 'SRC_URI[md5sum]', 'SRC_URI[sha256sum]'}'
>  changed items: {'GST_IMX_PATCHES_TO_APPEND'}
>  Dependency on variable GST_IMX_PATCHES_TO_APPEND was added
>  Variable SRC_URI value changed:
>  " 
> http://gstreamer.freedesktop.org/src/gst-plugins-base/gst-plugins-base-${PV}.tar.xz
>  file://get-caps-from-src-pad-when-query-caps.patch 
> file://0003-ssaparse-enhance-SSA-text-lines-parsing.patch 
> file://0004-subparse-set-need_segment-after-sink-pad-received-GS.patch 
> file://encodebin-Need-more-buffers-in-output-queue-for-bett.patch 
> file://make-gio_unix_2_0-dependency-configurable.patch 
> file://0001-introspection.m4-prefix-pkgconfig-paths-with-PKG_CON.patch 
> file://0001-Makefile.am-don-t-hardcode-libtool-name-when-running.patch 
> file://0002-Makefile.am-prefix-calls-to-pkg-config-with-PKG_CONF.patch 
> file://0003-riff-add-missing-include-directories-when-calling-in.patch 
> file://0004-rtsp-drop-incorrect-reference-to-gstreamer-sdp-in-Ma.patch [--] 
> {+${GST_IMX_PATCHES_TO_APPEND}+}"
> 
>   pulseaudio:do_install: 6bb6fe23e11a6d5fef9c3a25e73e4f9c -> 
> 3f54ea75673a792e307197cfa6ef2694
>  basehash changed from ac4efcfa783bd04a5a98a2c38719aedd to 
> 37679d99623a37c8df955da3a01415a5
>  Variable do_install value changed:
>  @@ -1,3 +1,7 @@
>   autotools_do_install
>   install -d ${D}${sysconfdir}/default/volatiles
>   install -m 0644 ${WORKDIR}/volatiles.04_pulse  
> ${D}${sysconfdir}/default/volatiles/volatiles.04_pulse
>  +if [ -e "${WORKDIR}/daemon.conf" ] && [ -e 
> "${WORKDIR}/default.pa" ]; then
>  +install -m 0644 ${WORKDIR}/daemon.conf 
> ${D}${sysconfdir}/pulse/daemon.conf
>  +install -m 0644 ${WORKDIR}/default.pa 
> ${D}${sysconfdir}/pulse/default.pa
>  +fi
> 
> [YOCTO #11161]
> 
> Signed-off-by: Patrick Ohly 
> ---
>  scripts/lib/compatlayer/cases/common.py | 10 ++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/scripts/lib/compatlayer/cases/common.py 
> b/scripts/lib/compatlayer/cases/common.py
> index b91da9b..d909d5b 100644
> --- a/scripts/lib/compatlayer/cases/common.py
> +++ b/scripts/lib/compatlayer/cases/common.py
> @@ -76,4 +76,14 @@ class CommonCompatLayer(OECompatLayerTestCase):
> (self.tc.layer['name'], len(sig_diff)))
>  for diff in sorted(sig_diff_filtered):
>  msg.append('   %s: %s -> %s' % diff)
> +try:
> +recipe, taskname = diff[0].rsplit(':', 1)
> +output = check_command('Determining signature difference 
> failed.',
> +   'bitbake-diffsigs --task %s %s 
> --signature %s %s' %
> +   (recipe, taskname, diff[1], 
> diff[2])).decode('utf-8')
> +except RuntimeError as error:
> +output = str(error)

Patrick, just a minor comment:  there is no need for the 'if' check,
because the try and the except bodies set the output variable. 

Leo

> +if output:
> +msg.extend(['  ' + line for line in 
> output.splitlines()])
> +msg.append('')
>  self.assertTrue(False, '\n'.join(msg))
> -- 
> git-series 0.9.1


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

Re: [OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries

[Leonardo Sandoval]

On Wed, 2017-04-05 at 13:02 +, Patchwork wrote:
> == Series Details ==
> 
> Series: python3: fix run-time deps for core python3 libraries
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/6164/
> State : failure
> 
> == Summary ==
> 
> 
> Thank you for submitting this patch series to OpenEmbedded Core. This is
> an automated response. Several tests have been executed on the proposed
> series by patchtest resulting in the following failures:
> 
> 
> 
> * Issue Patch line too long (current length 184) 
> [test_max_line_length] 
>   Suggested fixShorten the corresponding patch line (max length supported 
> 180)
>   Patchscripts/contrib/python/generate-manifest-3.5.py
>   Line +m.addPackage( "${PN}-netclient", "Python Internet 
> Protocol clients", "${PN} ...


Ignore the above patchtest failure. It has been disabled until general
agreement.


> 
> * Issue Series does not apply on top of target branch 
> [test_series_merge_on_head] 
>   Suggested fixRebase your series on top of targeted branch
>   Targeted branch  master (currently at 3b7111b30d)
> 
> 
> 
> If you believe any of these test results are incorrect, please reply to the
> mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
> Otherwise we would appreciate you correcting the issues and submitting a new
> version of the patchset if applicable. Please ensure you add/increment the
> version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
> [PATCH v3] -> ...).
> 
> ---
> Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
> 


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

Re: [OE-core] [PATCHv2 3/3] base-files: profile: Simplify setting variables conditionally

[Richard Purdie]

On Wed, 2017-04-05 at 15:46 +0200, Peter Kjellerstedt wrote:
> It is preferred to use `[  ] || ...` instead of
> `[  ] && ...` as the latter leaves $? set to 1.

Your patch and the description above don't match. There are changes
here which aren't  and are stylistic changes instead
afaict. We're past feature freeze so whilst I'm interested in genuine
bugs, I do not really want code churn which just introduces risk.

Cheers,

Richard

> Signed-off-by: Peter Kjellerstedt 
> ---
>  meta/recipes-core/base-files/base-files/profile | 14 ++
>  1 file changed, 6 insertions(+), 8 deletions(-)
> 
> diff --git a/meta/recipes-core/base-files/base-files/profile
> b/meta/recipes-core/base-files/base-files/profile
> index ceaf15f799..a062028226 100644
> --- a/meta/recipes-core/base-files/base-files/profile
> +++ b/meta/recipes-core/base-files/base-files/profile
> @@ -3,15 +3,13 @@
>  
>  PATH="/usr/local/bin:/usr/bin:/bin"
>  EDITOR="vi"  # needed for packages like cron,
> git-commit
> -test -z "$TERM" && TERM="vt100"  # Basic terminal capab. For
> screen etc.
> +[ "$TERM" ] || TERM="vt100"  # Basic terminal capab. For
> screen etc.
>  
> -if [ "$HOME" = "ROOTHOME" ]; then
> - PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
> -fi
> -if [ "$PS1" ]; then
> - # works for bash and ash (no other shells known to be in use
> here)
> - PS1='\u@\h:\w\$ '
> -fi
> +# Add /sbin & co to $PATH for the root user
> +[ "$HOME" != "ROOTHOME" ] ||
> PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
> +
> +# Set the prompt for bash and ash (no other shells known to be in
> use here)
> +[ -z "$PS1" ] || PS1='\u@\h:\w\$ '
>  
>  if [ -d /etc/profile.d ]; then
>   for i in /etc/profile.d/*.sh; do
> -- 
> 2.12.0
> 
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/2] logrotate: Add systemd support

[Romain Perier]

Currently, this recipe only supports daily scheduling via a cron job.
This commit adds support for systemd in the recipe, as the feature is
already supported on upstream. When the corresponding distro feature
is enabled the systemd variant will be used. The timer granularity and
its accuracy are also configurable.

Signed-off-by: Romain Perier 
---
 .../recipes-extended/logrotate/logrotate_3.11.0.bb | 25 +++---
 1 file changed, 22 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-extended/logrotate/logrotate_3.11.0.bb 
b/meta/recipes-extended/logrotate/logrotate_3.11.0.bb
index d72c7f0..b75496d 100644
--- a/meta/recipes-extended/logrotate/logrotate_3.11.0.bb
+++ b/meta/recipes-extended/logrotate/logrotate_3.11.0.bb
@@ -46,14 +46,33 @@ EXTRA_OEMAKE = "\
 # INSTALL=install and BASEDIR=/usr.
 OS_NAME = "Linux"
 
-inherit autotools
+inherit autotools systemd
+
+SYSTEMD_AUTO_ENABLE = "disable"
+SYSTEMD_SERVICE_${PN} = "\
+${PN}.service \
+${PN}.timer \
+"
+
+LOGROTATE_SYSTEMD_TIMER_BASIS ?= "daily"
+LOGROTATE_SYSTEMD_TIMER_ACCURACY ?= "12h"
 
 do_install(){
 oe_runmake install DESTDIR=${D} PREFIX=${D} MANDIR=${mandir}
 mkdir -p ${D}${sysconfdir}/logrotate.d
-mkdir -p ${D}${sysconfdir}/cron.daily
 mkdir -p ${D}${localstatedir}/lib
 install -p -m 644 ${S}/examples/logrotate-default 
${D}${sysconfdir}/logrotate.conf
-install -p -m 755 ${S}/examples/logrotate.cron 
${D}${sysconfdir}/cron.daily/logrotate
 touch ${D}${localstatedir}/lib/logrotate.status
+
+# Install systemd unit files
+if [ "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd', '', 
d)}" = "systemd" ]; then
+install -d ${D}${systemd_system_unitdir}
+install -m 0644 ${S}/examples/logrotate.service 
${D}${systemd_system_unitdir}/logrotate.service
+install -m 0644 ${S}/examples/logrotate.timer 
${D}${systemd_system_unitdir}/logrotate.timer
+sed -i -e 
's,OnCalendar=.*$,OnCalendar=${LOGROTATE_SYSTEMD_TIMER_BASIS},g' 
${D}${systemd_system_unitdir}/logrotate.timer
+sed -i -e 
's,AccuracySec=.*$,AccuracySec=${LOGROTATE_SYSTEMD_TIMER_ACCURACY},g' 
${D}${systemd_system_unitdir}/logrotate.timer
+else
+mkdir -p ${D}${sysconfdir}/cron.daily
+install -p -m 0755 ${S}/examples/logrotate.cron 
${D}${sysconfdir}/cron.daily/logrotate
+fi
 }
-- 
2.9.3

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

Re: [OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

[Leonardo Sandoval]

wrong list, you may have better luck at the meta-fsl mailing list.

BTW, the kernel expects a filesystem on a partition and the latter must
be defined in the kernel command line, using the root parameter.






On Wed, 2017-04-05 at 09:25 +, Zheng, Ruoqin wrote:
> 32be_rootfs boot from sdcard (ls1046)
> 
>  
> 
> I used source code provided by nxp  QorIQ-Linux-SDK-v2.0-SOURCE.iso +
> SDK-V2.0-1701 to build the kernel and rootfs , then it can’t boot from
> sdcard.
> 
>  
> 
> I tried to put kernel(32be) and rootfs(32be) in SD card , and boot it
> follow the SDK2.0, it was fail to mount the rootfs(while 64be kernel
> is normal),and here is part of log:
> 
> mmcblk0: mmc0:0007 SL32G 29.0 GiB
> 
>  mcblk0: p1
> 
> VFS: Mounted root (ext2 filesystem) on device 1:0.
> 
> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error
> -6
> 
> Please append a correct "root=" boot option; here are the available
> partitions:
> 
> 0100  262144 ram0  (driver?)
> 
> 0101  262144 ram1  (driver?)
> 
> 0102  262144 ram2  (driver?)
> 
> 0103  262144 ram3  (driver?)
> 
> 0104  262144 ram4  (driver?)
> 
> 0105  262144 ram5  (driver?)
> 
> 0106  262144 ram6  (driver?)
> 
> 0107  262144 ram7  (driver?)
> 
> 1f00  524288 mtdblock0  (driver?)
> 
> b30030375936 mmcblk0  driver: mmcblk
> 
>   b30130371936 mmcblk0p1 -01
> 
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2
> 
> Hardware name: Freescale LAYERSCAPE
> 
>  
> 
> The entire log is in atachments, do anyone have any idea about this
> problem? 
> 
>  
> 
> By the way, I tried to boot the kernel with command “bootm
> a000:kernel@1 - a000:fdt@1”
> 
> And the log show as below, you can see that mmcblk0 device is missed,
> do anyone know the reason?
> 
>  
> 
> ALSA device list:
> 
>   No soundcards found.
> 
> VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error
> -6
> 
> Please append a correct "root=" boot option; here are the available
> partitions:
> 
> 0100  262144 ram0  (driver?)
> 
> 0101  262144 ram1  (driver?)
> 
> 0102  262144 ram2  (driver?)
> 
> 0103  262144 ram3  (driver?)
> 
> 0104  262144 ram4  (driver?)
> 
> 0105  262144 ram5  (driver?)
> 
> 0106  262144 ram6  (driver?)
> 
> 0107  262144 ram7  (driver?)
> 
> 1f00  524288 mtdblock0  (driver?)
> 
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> 
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2
> 
> Hardware name: Freescale LAYERSCAPE
> 
>  
> 
>  
> 
> Zheng Ruoqin
> 
> Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
> 
> ADDR.: No.6 Wenzhu Road, Software Avenue,
> 
>Nanjing, 210012, China
> 
> MAIL : zhengrq.f...@cn.fujistu.com
> 
>  
> 
> 
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

[OE-core] [PATCH 0/2] logrotate: systemd support

[Romain Perier]

SystemD is now supported by upstream logrotate. This set of patches first
bumps the recipe to the last upstream version, that is 3.11.0. Then it adds
support for systemd.

This series is the continuety of the following patch:

1. https://lists.yoctoproject.org/pipermail/yocto/2017-March/035277.html

Note:
The default SRC_URI to be used for tarball is still under discussion on the ML.
Do we use github or downloads.yoctoproject.org ? How do we upload the tarball ?

Romain Perier (2):
  logrotate: Bump to 3.11.0
  logrotate: Add systemd support

 .../recipes-extended/logrotate/logrotate_3.11.0.bb | 78 ++
 meta/recipes-extended/logrotate/logrotate_3.9.1.bb | 60 -
 2 files changed, 78 insertions(+), 60 deletions(-)
 create mode 100644 meta/recipes-extended/logrotate/logrotate_3.11.0.bb
 delete mode 100644 meta/recipes-extended/logrotate/logrotate_3.9.1.bb

-- 
2.9.3

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

[OE-core] [PATCH 1/2] logrotate: Bump to 3.11.0

[Romain Perier]

This commit updates the recipe to the last upstream tag. Then, as the
tarball no longer contains the pre-generated Makefile, inherit from
autotools

Signed-off-by: Romain Perier 
---
 .../{logrotate_3.9.1.bb => logrotate_3.11.0.bb}| 23 +++---
 1 file changed, 11 insertions(+), 12 deletions(-)
 rename meta/recipes-extended/logrotate/{logrotate_3.9.1.bb => 
logrotate_3.11.0.bb} (69%)

diff --git a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb 
b/meta/recipes-extended/logrotate/logrotate_3.11.0.bb
similarity index 69%
rename from meta/recipes-extended/logrotate/logrotate_3.9.1.bb
rename to meta/recipes-extended/logrotate/logrotate_3.11.0.bb
index 9c2dfe0..d72c7f0 100644
--- a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
+++ b/meta/recipes-extended/logrotate/logrotate_3.11.0.bb
@@ -3,23 +3,25 @@ SECTION = "console/utils"
 HOMEPAGE = "https://fedorahosted.org/logrotate/";
 LICENSE = "GPLv2"
 
-# TODO: logrotate 3.8.8 adds autotools/automake support, update recipe to use 
it.
 # TODO: Document coreutils dependency. Why not RDEPENDS? Why not busybox?
 
 DEPENDS="coreutils popt"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=18810669f13b87348459e611d31ab760"
 
-SRC_URI = 
"https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.gz \
+# TODO: We need to decide if we github or downloads.yoctoproject.org
+SRC_URI = 
"https://github.com/logrotate/logrotate/releases/download/${PV}/logrotate-${PV}.tar.gz
 \
file://act-as-mv-when-rotate.patch \
file://update-the-manual.patch \
file://disable-check-different-filesystems.patch \
 "
+SRC_URI[md5sum] = "15db4027b07b3e239297e4c87c6da2e9"
+SRC_URI[sha256sum] = 
"7dcb440ed2f1937459e1e06f841c6af1e564b77b2df8009147b56c8649197910"
 
-SRC_URI[md5sum] = "4492b145b6d542e4a2f41e77fa199ab0"
-SRC_URI[sha256sum] = 
"022769e3288c80981559a8421703c88e8438b447235e36dd3c8e97cd94c52545"
-
-PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl selinux', d)}"
+PACKAGECONFIG ?= "\
+${@bb.utils.contains('DISTRO_FEATURES', 'acl', 'acl', '', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux', '', d)} \
+"
 
 PACKAGECONFIG[acl] = ",,acl"
 PACKAGECONFIG[selinux] = ",,libselinux"
@@ -44,17 +46,14 @@ EXTRA_OEMAKE = "\
 # INSTALL=install and BASEDIR=/usr.
 OS_NAME = "Linux"
 
-do_compile_prepend() {
-# Make sure the recompile is OK
-rm -f ${B}/.depend
-}
+inherit autotools
 
 do_install(){
 oe_runmake install DESTDIR=${D} PREFIX=${D} MANDIR=${mandir}
 mkdir -p ${D}${sysconfdir}/logrotate.d
 mkdir -p ${D}${sysconfdir}/cron.daily
 mkdir -p ${D}${localstatedir}/lib
-install -p -m 644 examples/logrotate-default 
${D}${sysconfdir}/logrotate.conf
-install -p -m 755 examples/logrotate.cron 
${D}${sysconfdir}/cron.daily/logrotate
+install -p -m 644 ${S}/examples/logrotate-default 
${D}${sysconfdir}/logrotate.conf
+install -p -m 755 ${S}/examples/logrotate.cron 
${D}${sysconfdir}/cron.daily/logrotate
 touch ${D}${localstatedir}/lib/logrotate.status
 }
-- 
2.9.3

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

[OE-core] ✗ patchtest: failure for busybox: Security Fix CVE-2016-6301

[Patchwork]

== Series Details ==

Series: busybox: Security Fix CVE-2016-6301
Revision: 1
URL   : https://patchwork.openembedded.org/series/6173/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Patchbusybox: Security Fix CVE-2016-6301
 Issue Missing or incorrectly formatted CVE tag in commit message 
[test_cve_presence_in_commit_message] 
  Suggested fixInclude a "CVE--" tag in the commit message



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

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

[OE-core] [PATCH] busybox: Security Fix CVE-2016-6301

[Andrej Valek]

Signed-off-by: Andrej Valek 
Signed-off-by: Pascal Bach 
---
 .../busybox/busybox/CVE-2016-6301.patch| 37 ++
 meta/recipes-core/busybox/busybox_1.24.1.bb|  1 +
 2 files changed, 38 insertions(+)
 create mode 100644 meta/recipes-core/busybox/busybox/CVE-2016-6301.patch

diff --git a/meta/recipes-core/busybox/busybox/CVE-2016-6301.patch 
b/meta/recipes-core/busybox/busybox/CVE-2016-6301.patch
new file mode 100644
index 000..851bc20
--- /dev/null
+++ b/meta/recipes-core/busybox/busybox/CVE-2016-6301.patch
@@ -0,0 +1,37 @@
+busybox1.24.1: Fix CVE-2016-6301
+
+[No upstream tracking] -- https://bugzilla.redhat.com/show_bug.cgi?id=1363710
+
+ntpd: NTP server denial of service flaw
+
+The busybox NTP implementation doesn't check the NTP mode of packets
+received on the server port and responds to any packet with the right
+size. This includes responses from another NTP server. An attacker can
+send a packet with a spoofed source address in order to create an
+infinite loop of responses between two busybox NTP servers. Adding
+more packets to the loop increases the traffic between the servers
+until one of them has a fully loaded CPU and/or network.
+
+Upstream-Status: Backport 
[https://git.busybox.net/busybox/commit/?id=150dc7a2b483b8338a3e185c478b4b23ee884e71]
+CVE: CVE-2016-6301
+Signed-off-by: Andrej Valek 
+Signed-off-by: Pascal Bach 
+
+diff --git a/networking/ntpd.c b/networking/ntpd.c
+index 9732c9b..0f6a55f 100644
+--- a/networking/ntpd.c
 b/networking/ntpd.c
+@@ -1985,6 +1985,13 @@ recv_and_process_client_pkt(void /*int fd*/)
+   goto bail;
+   }
+ 
++  /* Respond only to client and symmetric active packets */
++  if ((msg.m_status & MODE_MASK) != MODE_CLIENT
++   && (msg.m_status & MODE_MASK) != MODE_SYM_ACT
++  ) {
++  goto bail;
++  }
++
+   query_status = msg.m_status;
+   query_xmttime = msg.m_xmttime;
+ 
diff --git a/meta/recipes-core/busybox/busybox_1.24.1.bb 
b/meta/recipes-core/busybox/busybox_1.24.1.bb
index 41fc641..6013ec9 100644
--- a/meta/recipes-core/busybox/busybox_1.24.1.bb
+++ b/meta/recipes-core/busybox/busybox_1.24.1.bb
@@ -47,6 +47,7 @@ SRC_URI = 
"http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \
file://CVE-2016-2148.patch \
file://CVE-2016-2147.patch \
file://CVE-2016-2147_2.patch \
+   file://CVE-2016-6301.patch \
file://ip_fix_problem_on_mips64_n64_big_endian_musl_systems.patch \
file://makefile-fix-backport.patch \

file://0001-sed-fix-sed-n-flushes-pattern-space-terminates-early.patch \
-- 
2.1.4

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

Re: [OE-core] [PATCH] create-pull-request: add "-t in-reply-to" option

[Leonardo Sandoval]

On Tue, 2017-04-04 at 16:45 -0500, Jose Lamego wrote:
> The create-patch-request script creates patches as replies to a cover

you mean create-pull-request, I believe

> letter, in the form of an email thread. If further revisions are sent to
> the mailing list without referencing to the first revision, these new
> revisions are not identified at the mailing list as part of the original
> thread, but as a new thread instead.
> 
> This change adds the "[-t in_reply_to]" option, where "in_reply_to" is
> the original cover letter's Message-Id, so this reference is added
> to the new cover letter to ensure the thread continuity.
> 


BTW, is there an easy way to get the in-reply-to email besides using
git-pw or looking at the message source?

Some comments in patch:




> [YOCTO #11294]
> 
> Signed-off-by: Jose Lamego 
> ---
>  scripts/create-pull-request | 14 +++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/scripts/create-pull-request b/scripts/create-pull-request
> index e82858b..46d6538 100755
> --- a/scripts/create-pull-request
> +++ b/scripts/create-pull-request
> @@ -34,7 +34,7 @@ RFC=0
>  usage() {
>  CMD=$(basename $0)
>  cat < -Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s subject] [-r 
> relative_to] [-i commit_id] [-d relative_dir] -u remote [-b branch]
> +Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s subject] [-r 
> relative_to] [-i commit_id] [-d relative_dir] -u remote [-b branch] [-t 
> in_reply_to]
>-b branch   Branch name in the specified remote (default: current 
> branch)
>-l local branch Local branch name (default: HEAD)
>-c  Create an RFC (Request for Comment) patch series
> @@ -49,6 +49,7 @@ Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s 
> subject] [-r relative_to
>-s subject  The subject to be inserted into the summary email
>-u remote   The git remote where the branch is located, or set 
> CPR_CONTRIB_REMOTE in env
>-d relative_dir Generate patches relative to directory
> +  -t in_reply_to  Make mails appear as replies to the given Message-Id, 
> to continue patch/series threads
>  
>   Examples:
> $CMD -u contrib -b nitin/basic
> @@ -57,12 +58,13 @@ Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s 
> subject] [-r relative_to
> $CMD -u contrib -r master -i misc -b nitin/misc -o pull-misc
> $CMD -u contrib -p "RFC PATCH" -b nitin/experimental
> $CMD -u contrib -i misc -b nitin/misc -d ./bitbake
> +   $CMD -u contrib -p "OE-core][PATCH v2" -t 
> ""
>  EOM
>  }
>  
>  REMOTE="$CPR_CONTRIB_REMOTE"
>  # Parse and validate arguments
> -while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
> +while getopts "b:acd:hi:m:o:p:r:s:u:l:t:" OPT; do
>   case $OPT in
>   b)
>   BRANCH="$OPTARG"
> @@ -108,6 +110,8 @@ while getopts "b:acd:hi:m:o:p:r:s:u:l:" OPT; do
>   a)
>   CPR_CONTRIB_AUTO_PUSH="1"
>   ;;
> +t)
> +IN_REPLY_TO="$OPTARG"

it would be nice to include also the double semi-colon, so future cases
just start after it.


>   esac
>  done
>  
> @@ -205,7 +209,11 @@ if [ -n "$RELDIR" ]; then
>  fi
>  
>  # Generate the patches and cover letter
> -git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
> --thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
> +if [ -z "$IN_REPLY_TO" ]; then

-n instead of -z?

> +git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
> --thread=shallow --in-reply-to="$IN_REPLY_TO" --cover-letter 
> $RELATIVE_TO..$COMMIT_ID > /dev/null
> +else
> +git format-patch $extraopts -M40 --subject-prefix="$PREFIX" -n -o $ODIR 
> --thread=shallow --cover-letter $RELATIVE_TO..$COMMIT_ID > /dev/null
> +fi
>  
>  if [ -z "$(ls -A $ODIR 2> /dev/null)" ]; then
>  echo "ERROR: $ODIR is empty, no cover letter and patches was generated!"
> -- 
> 2.7.4
> 


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

[OE-core] [PATCHv2 3/3] base-files: profile: Simplify setting variables conditionally

[Peter Kjellerstedt]

It is preferred to use `[  ] || ...` instead of
`[  ] && ...` as the latter leaves $? set to 1.

Signed-off-by: Peter Kjellerstedt 
---
 meta/recipes-core/base-files/base-files/profile | 14 ++
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/meta/recipes-core/base-files/base-files/profile 
b/meta/recipes-core/base-files/base-files/profile
index ceaf15f799..a062028226 100644
--- a/meta/recipes-core/base-files/base-files/profile
+++ b/meta/recipes-core/base-files/base-files/profile
@@ -3,15 +3,13 @@
 
 PATH="/usr/local/bin:/usr/bin:/bin"
 EDITOR="vi"# needed for packages like cron, git-commit
-test -z "$TERM" && TERM="vt100"# Basic terminal capab. For screen etc.
+[ "$TERM" ] || TERM="vt100"# Basic terminal capab. For screen etc.
 
-if [ "$HOME" = "ROOTHOME" ]; then
-   PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
-fi
-if [ "$PS1" ]; then
-   # works for bash and ash (no other shells known to be in use here)
-   PS1='\u@\h:\w\$ '
-fi
+# Add /sbin & co to $PATH for the root user
+[ "$HOME" != "ROOTHOME" ] || PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
+
+# Set the prompt for bash and ash (no other shells known to be in use here)
+[ -z "$PS1" ] || PS1='\u@\h:\w\$ '
 
 if [ -d /etc/profile.d ]; then
for i in /etc/profile.d/*.sh; do
-- 
2.12.0

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

[OE-core] [PATCHv2 2/3] base-files: profile: Do not assume that the tty command exists

[Peter Kjellerstedt]

This avoids the following error when logging in to a host that does
not have the tty command:

-sh: tty: not found

Reported-by: Cristian Ionescu-Idbohrn 
Signed-off-by: Peter Kjellerstedt 
---
 meta/recipes-core/base-files/base-files/profile   | 6 +++---
 meta/recipes-core/base-files/base-files_3.0.14.bb | 4 
 2 files changed, 3 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-core/base-files/base-files/profile 
b/meta/recipes-core/base-files/base-files/profile
index 22dfb4f219..ceaf15f799 100644
--- a/meta/recipes-core/base-files/base-files/profile
+++ b/meta/recipes-core/base-files/base-files/profile
@@ -22,12 +22,12 @@ if [ -d /etc/profile.d ]; then
unset i
 fi
 
-if [ -x /usr/bin/resize ] && termpath="`tty`"; then
+if command -v resize >/dev/null && command -v tty >/dev/null; then
# Make sure we are on a serial console (i.e. the device used starts with
# /dev/tty[A-z]), otherwise we confuse e.g. the eclipse launcher which
# tries do use ssh
-   case "$termpath" in
-   /dev/tty[A-z]*) resize >/dev/null
+   case $(tty) in
+   /dev/tty[A-z]*) resize >/dev/null;;
esac
 fi
 
diff --git a/meta/recipes-core/base-files/base-files_3.0.14.bb 
b/meta/recipes-core/base-files/base-files_3.0.14.bb
index f56969c52e..ca7bf06353 100644
--- a/meta/recipes-core/base-files/base-files_3.0.14.bb
+++ b/meta/recipes-core/base-files/base-files_3.0.14.bb
@@ -128,10 +128,6 @@ do_install () {
install -m 0644 ${WORKDIR}/host.conf ${D}${sysconfdir}/host.conf
install -m 0644 ${WORKDIR}/motd ${D}${sysconfdir}/motd
 
-   if [ "/usr/bin" != "${bindir}" ]; then
-   sed -i "s,/usr/bin/resize,${bindir}/resize," 
${D}${sysconfdir}/profile
-   fi
-
ln -sf /proc/mounts ${D}${sysconfdir}/mtab
 }
 
-- 
2.12.0

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

[OE-core] [PATCHv2 1/3] base-files: profile: Whitespace clean up

[Peter Kjellerstedt]

Signed-off-by: Peter Kjellerstedt 
---
 meta/recipes-core/base-files/base-files/profile | 29 +
 1 file changed, 15 insertions(+), 14 deletions(-)

diff --git a/meta/recipes-core/base-files/base-files/profile 
b/meta/recipes-core/base-files/base-files/profile
index c616616cee..22dfb4f219 100644
--- a/meta/recipes-core/base-files/base-files/profile
+++ b/meta/recipes-core/base-files/base-files/profile
@@ -6,28 +6,29 @@ EDITOR="vi"   # needed for packages like 
cron, git-commit
 test -z "$TERM" && TERM="vt100"# Basic terminal capab. For screen etc.
 
 if [ "$HOME" = "ROOTHOME" ]; then
-   PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
+   PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin
 fi
 if [ "$PS1" ]; then
-# works for bash and ash (no other shells known to be in use here)
-   PS1='\u@\h:\w\$ '
+   # works for bash and ash (no other shells known to be in use here)
+   PS1='\u@\h:\w\$ '
 fi
 
 if [ -d /etc/profile.d ]; then
-  for i in /etc/profile.d/*.sh ; do
-if [ -f $i -a -r $i ]; then
-  . $i
-fi
-  done
-  unset i
+   for i in /etc/profile.d/*.sh; do
+   if [ -f $i -a -r $i ]; then
+   . $i
+   fi
+   done
+   unset i
 fi
 
 if [ -x /usr/bin/resize ] && termpath="`tty`"; then
-  # Make sure we are on a serial console (i.e. the device used starts with 
/dev/tty),
-  # otherwise we confuse e.g. the eclipse launcher which tries do use ssh
-  case "$termpath" in
-  /dev/tty[A-z]*) resize >/dev/null
-  esac
+   # Make sure we are on a serial console (i.e. the device used starts with
+   # /dev/tty[A-z]), otherwise we confuse e.g. the eclipse launcher which
+   # tries do use ssh
+   case "$termpath" in
+   /dev/tty[A-z]*) resize >/dev/null
+   esac
 fi
 
 export PATH PS1 OPIEDIR QPEDIR QTDIR EDITOR TERM
-- 
2.12.0

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

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

[Nathan Rossi]

On 5 April 2017 at 21:22, Richard Purdie
 wrote:
> On Wed, 2017-04-05 at 20:06 +1000, Nathan Rossi wrote:
>> On 30 March 2017 at 15:12, Chen Qi  wrote:
>> >
>> > The 'recipe-sysroot' and 'recipe-sysroot-native' directories need
>> > to
>> > be preserved for runqemu to work correctly. Otherwise, when
>> > 'rm_work'
>> > is enabled, these directories are removed, thus causing errors when
>> > using runqemu .
>> >
>> > [YOCTO #11266]
>> > [YOCTO #11193]
>> >
>> > Signed-off-by: Chen Qi 
>> > ---
>> >  meta/classes/image.bbclass | 1 +
>> >  meta/conf/machine/include/qemu.inc | 3 +++
>> >  2 files changed, 4 insertions(+)
>> >
>> > diff --git a/meta/classes/image.bbclass
>> > b/meta/classes/image.bbclass
>> > index 405fd73..cac3a5f 100644
>> > --- a/meta/classes/image.bbclass
>> > +++ b/meta/classes/image.bbclass
>> > @@ -8,6 +8,7 @@ inherit ${SDKEXTCLASS}
>> >  TOOLCHAIN_TARGET_TASK += "${PACKAGE_INSTALL}"
>> >  TOOLCHAIN_TARGET_TASK_ATTEMPTONLY +=
>> > "${PACKAGE_INSTALL_ATTEMPTONLY}"
>> >  POPULATE_SDK_POST_TARGET_COMMAND += "rootfs_sysroot_relativelinks;
>> > "
>> > +RM_WORK_EXCLUDE_ITEMS_append = " ${IMAGE_RM_WORK_EXCLUDE_ITEMS}"
>> >
>> >  LICENSE = "MIT"
>> >  PACKAGES = ""
>> > diff --git a/meta/conf/machine/include/qemu.inc
>> > b/meta/conf/machine/include/qemu.inc
>> > index 0e4103b..8345c08 100644
>> > --- a/meta/conf/machine/include/qemu.inc
>> > +++ b/meta/conf/machine/include/qemu.inc
>> > @@ -29,3 +29,6 @@ KERNEL_FEATURES_append_pn-linux-yocto = "
>> > features/nfsd/nfsd-enable.scc"
>> >  MACHINE_EXTRA_RRECOMMENDS += "rng-tools"
>> >
>> >  IMAGE_CLASSES += "qemuboot"
>> > +
>> > +# These two directories need to be preserved for runqemu to work
>> > well
>> > +IMAGE_RM_WORK_EXCLUDE_ITEMS = "recipe-sysroot recipe-sysroot-
>> > native"
>> Should this be setup by qemuboot.bbclass instead, so that it applies
>> to any image/machine (even those that do not use qemu.inc) that is
>> intended to be used by runqemu?
>
> I'm trying to decide what the best approach here is. I'm thinking it
> might be better to:
>
> a) make qemu builds depend on qemu-helper-native
> b) make that preserve its native sysroot (not the target one).
> c) have runqemu look at qemu-helper-native
>
> I think that should solve problems and work better than the above?

That sounds like a good solution.

This would however change how meta-xilinx would need to handle
providing an additional version of QEMU (for which it currently sets
EXTRA_IMAGEDEPENDS, and subdirs the native binaries). But this change
means that the custom QEMU version would be built for all QEMU targets
(when the layer is used), although this is something that should be
sorted out with runqemu now that it can be given a different sysroot
(and a different sysroot can be built alongside). This would remove
the need for the workarounds that were used to get runqemu to use the
alternative QEMU in the first place. So your proposed solution works
better in that regard as well (as meta-xilinx could provide an
alternate qemu-helper-native for those qemu machines that use it).

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

[OE-core] [PATCH 3/3] yocto-compat-layer: include bitbake-diffsigs output

[Patrick Ohly]

After filtering out potential false positives, it becomes feasible to
include the output of bitbake-diffsigs for those tasks which
definitely have a change.

Depends on bitbake-diffsigs with the "--signature" parameter.

Enhanced output now is:

   AssertionError: False is not true : Layer meta- changed 120 signatures, 
initial differences (first hash without, second with layer):
  gstreamer1.0-plugins-base:do_fetch: 76973f19f2e30d282152bdd7e4efe5bb -> 
e6e7c6fa9f2bd59d7d8d107f7c6ca1ac
 Task dependencies changed from:
 ['PV', 'SRCREV', 'SRC_URI', 'SRC_URI[md5sum]', 'SRC_URI[sha256sum]', 
'base_do_fetch']
 to:
 ['GST_IMX_PATCHES_TO_APPEND', 'PV', 'SRCREV', 'SRC_URI', 
'SRC_URI[md5sum]', 'SRC_URI[sha256sum]', 'base_do_fetch']
 basehash changed from d679d30bd1ea41c56e57419b57587f3c to 
090a79b45f5fa26d10f9d34e2ed7a1e6
List of dependencies for variable SRC_URI changed from '{'PV', 
'SRC_URI[md5sum]', 'SRC_URI[sha256sum]'}' to '{'GST_IMX_PATCHES_TO_APPEND', 
'PV', 'SRC_URI[md5sum]', 'SRC_URI[sha256sum]'}'
 changed items: {'GST_IMX_PATCHES_TO_APPEND'}
 Dependency on variable GST_IMX_PATCHES_TO_APPEND was added
 Variable SRC_URI value changed:
 " 
http://gstreamer.freedesktop.org/src/gst-plugins-base/gst-plugins-base-${PV}.tar.xz
 file://get-caps-from-src-pad-when-query-caps.patch 
file://0003-ssaparse-enhance-SSA-text-lines-parsing.patch 
file://0004-subparse-set-need_segment-after-sink-pad-received-GS.patch 
file://encodebin-Need-more-buffers-in-output-queue-for-bett.patch 
file://make-gio_unix_2_0-dependency-configurable.patch 
file://0001-introspection.m4-prefix-pkgconfig-paths-with-PKG_CON.patch 
file://0001-Makefile.am-don-t-hardcode-libtool-name-when-running.patch 
file://0002-Makefile.am-prefix-calls-to-pkg-config-with-PKG_CONF.patch 
file://0003-riff-add-missing-include-directories-when-calling-in.patch 
file://0004-rtsp-drop-incorrect-reference-to-gstreamer-sdp-in-Ma.patch [--] 
{+${GST_IMX_PATCHES_TO_APPEND}+}"

  pulseaudio:do_install: 6bb6fe23e11a6d5fef9c3a25e73e4f9c -> 
3f54ea75673a792e307197cfa6ef2694
 basehash changed from ac4efcfa783bd04a5a98a2c38719aedd to 
37679d99623a37c8df955da3a01415a5
 Variable do_install value changed:
 @@ -1,3 +1,7 @@
  autotools_do_install
install -d ${D}${sysconfdir}/default/volatiles
install -m 0644 ${WORKDIR}/volatiles.04_pulse  
${D}${sysconfdir}/default/volatiles/volatiles.04_pulse
 +if [ -e "${WORKDIR}/daemon.conf" ] && [ -e 
"${WORKDIR}/default.pa" ]; then
 +install -m 0644 ${WORKDIR}/daemon.conf 
${D}${sysconfdir}/pulse/daemon.conf
 +install -m 0644 ${WORKDIR}/default.pa 
${D}${sysconfdir}/pulse/default.pa
 +fi

[YOCTO #11161]

Signed-off-by: Patrick Ohly 
---
 scripts/lib/compatlayer/cases/common.py | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/scripts/lib/compatlayer/cases/common.py 
b/scripts/lib/compatlayer/cases/common.py
index b91da9b..d909d5b 100644
--- a/scripts/lib/compatlayer/cases/common.py
+++ b/scripts/lib/compatlayer/cases/common.py
@@ -76,4 +76,14 @@ class CommonCompatLayer(OECompatLayerTestCase):
(self.tc.layer['name'], len(sig_diff)))
 for diff in sorted(sig_diff_filtered):
 msg.append('   %s: %s -> %s' % diff)
+try:
+recipe, taskname = diff[0].rsplit(':', 1)
+output = check_command('Determining signature difference 
failed.',
+   'bitbake-diffsigs --task %s %s 
--signature %s %s' %
+   (recipe, taskname, diff[1], 
diff[2])).decode('utf-8')
+except RuntimeError as error:
+output = str(error)
+if output:
+msg.extend(['  ' + line for line in 
output.splitlines()])
+msg.append('')
 self.assertTrue(False, '\n'.join(msg))
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/3] yocto-compat-layer: limit report of signature changes

[Patrick Ohly]

Typically a single change cascades through the entire task dependency
chain. Developers had to figure that out themselves, based on hard to
read and interpret output (not sorted, no indention, no explanations):

   $ yocto-compat-layer.py -n meta-
   ...
   AssertionError: True is not false : Layer meta- changed signatures.
   webkitgtk:do_install changed fe2edc9082bc0da98f9cb1391c52f565 -> 
b3a44684c5cd9aacd3f7c6ed88eefab5
   gstreamer1.0-plugins-good:do_configure changed 
3b2f8211be3fe08422bf6087f3af16d1 -> 7d80e42fa1f4f01ff4dfe2ea4477d382
   pulseaudio:do_package_qa changed 5d0a58ada66ff17f5576555302ac319a -> 
0e13bcb96143d1ae54c451bc3de0aa30
   epiphany:do_prepare_recipe_sysroot changed 29e1b277dbcb005bd54950594c50d91b 
-> d3c45527b37677a0668ce483c6db3052
   ...
   gst-player:do_packagedata changed 9ce6efdd357dd74919bc4957458b1e95 -> 
d0c083ce629f37adfc9c4ba9eff81f83
   gstreamer1.0-plugins-base:do_install changed 
1161cd867d15bea63e5dd5d9abf0519c -> 5bf2b652a2d77fee3eedb35af2f201a0
   gstreamer1.0-rtsp-server:do_packagedata changed 
6781dc3070f80b843ed1970d74dd323e -> 454620c2e3b9fea87e525d14b6ed0344
   alsa-plugins:do_packagedata changed 1808c3f737cb805b169d004e948ea19c -> 
480124b7fa5eab1f73bf96440d725231

Now the tool automates the problem analysis: it retrieves the depgraph
using the tinfoil API and only reports those tasks with modified
signatures whose dependencies have not changed, i.e. those tasks which
definitely introduce a change.

>From the previous example, that just leaves two tasks that need to be
checked:

   AssertionError: False is not true : Layer meta- changed 120 signatures, 
initial differences (first hash without, second with layer):
  gstreamer1.0-plugins-base:do_fetch: 76973f19f2e30d282152bdd7e4efe5bb -> 
e6e7c6fa9f2bd59d7d8d107f7c6ca1ac
  pulseaudio:do_install: 668eb1e30af129df9806b0aa0d7c10cd -> 
1196bdb88eef564613bb06b9387e

This pruning might be a bit too aggressive in the sense that tasks
which inherit a change and then add more changes themselves won't be
reported initially. They will be found when fixing the reported tasks
and re-running the check.

For a developer it seems better to have something listed which
definitely is a problem and needs fixing instead of everything,
including the tasks which don't need fixes.

Signed-off-by: Patrick Ohly 
---
 scripts/lib/compatlayer/__init__.py | 32 +++-
 scripts/lib/compatlayer/cases/common.py | 54 +++---
 2 files changed, 73 insertions(+), 13 deletions(-)

diff --git a/scripts/lib/compatlayer/__init__.py 
b/scripts/lib/compatlayer/__init__.py
index 9eb862d..b46527a 100644
--- a/scripts/lib/compatlayer/__init__.py
+++ b/scripts/lib/compatlayer/__init__.py
@@ -7,6 +7,8 @@ import os
 import subprocess
 from enum import Enum
 
+import bb.tinfoil
+
 class LayerType(Enum):
 BSP = 0
 DISTRO = 1
@@ -252,3 +254,33 @@ def get_signatures(builddir, failsafe=False):
 raise RuntimeError('Can\'t load signatures from %s' % sigs_file)
 
 return sigs
+
+def get_depgraph(targets=['world']):
+'''
+Returns the dependency graph for the given target(s).
+The dependency graph is taken directly from DepTreeEvent.
+'''
+depgraph = None
+with bb.tinfoil.Tinfoil() as tinfoil:
+tinfoil.prepare(config_only=False)
+tinfoil.set_event_mask(['bb.event.NoProvider', 
'bb.event.DepTreeGenerated', 'bb.command.CommandCompleted'])
+if not tinfoil.run_command('generateDepTreeEvent', targets, 
'do_build'):
+raise RuntimeError('starting generateDepTreeEvent failed')
+while True:
+event = tinfoil.wait_event(timeout=1000)
+if event:
+if isinstance(event, bb.command.CommandFailed):
+raise RuntimeError('Generating dependency information 
failed: %s' % event.error)
+elif isinstance(event, bb.command.CommandCompleted):
+break
+elif isinstance(event, bb.event.NoProvider):
+if event._reasons:
+raise RuntimeError('Nothing provides %s: %s' % 
(event._item, event._reasons))
+else:
+raise RuntimeError('Nothing provides %s.' % 
(event._item))
+elif isinstance(event, bb.event.DepTreeGenerated):
+depgraph = event._depgraph
+
+if depgraph is None:
+raise RuntimeError('Could not retrieve the depgraph.')
+return depgraph
diff --git a/scripts/lib/compatlayer/cases/common.py 
b/scripts/lib/compatlayer/cases/common.py
index 9cc682e..b91da9b 100644
--- a/scripts/lib/compatlayer/cases/common.py
+++ b/scripts/lib/compatlayer/cases/common.py
@@ -3,7 +3,7 @@
 
 import os
 import unittest
-from compatlayer import get_signatures, LayerType, check_command
+from compatlayer import get_signatures, LayerType, check_command, get_depgraph
 from compatlayer.case import OECompatLayerTestCase
 
 class CommonComp

[OE-core] [PATCH 1/3] yocto-compat-layer: fix also other command invocations

[Patrick Ohly]

In commit 5b9ac62ab535d, one place was fixed where a command was
invoked such that failures caused double stack traces and stderr was
lost. The same problem also occurs elsewhere, triggered for example by
a layer with parsing problems.

Now a new utility method is used instead of repeating the code.

Signed-off-by: Patrick Ohly 
---
 scripts/lib/compatlayer/__init__.py | 23 ---
 scripts/lib/compatlayer/cases/common.py | 25 +
 2 files changed, 21 insertions(+), 27 deletions(-)

diff --git a/scripts/lib/compatlayer/__init__.py 
b/scripts/lib/compatlayer/__init__.py
index 86f86eb..9eb862d 100644
--- a/scripts/lib/compatlayer/__init__.py
+++ b/scripts/lib/compatlayer/__init__.py
@@ -4,6 +4,7 @@
 # Released under the MIT license (see COPYING.MIT)
 
 import os
+import subprocess
 from enum import Enum
 
 class LayerType(Enum):
@@ -199,8 +200,20 @@ def add_layer(bblayersconf, layer, layers, logger):
 
 return True
 
+def check_command(error_msg, cmd):
+'''
+Run a command under a shell, capture stdout and stderr in a single stream,
+throw an error when command returns non-zero exit code. Returns the output.
+'''
+
+p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, 
stderr=subprocess.STDOUT)
+output, _ = p.communicate()
+if p.returncode:
+msg = "%s\nCommand: %s\nOutput:\n%s" % (error_msg, cmd, 
output.decode('utf-8'))
+raise RuntimeError(msg)
+return output
+
 def get_signatures(builddir, failsafe=False):
-import subprocess
 import re
 
 # some recipes needs to be excluded like meta-world-pkgdata
@@ -214,12 +227,8 @@ def get_signatures(builddir, failsafe=False):
 if failsafe:
 cmd += '-k '
 cmd += '-S none world'
-p = subprocess.Popen(cmd, shell=True,
- stdout=subprocess.PIPE, stderr=subprocess.STDOUT)
-output, _ = p.communicate()
-if p.returncode:
-msg = "Generating signatures failed. This might be due to some parse 
error and/or general layer incompatibilities.\nCommand: %s\nOutput:\n%s" % 
(cmd, output.decode('utf-8'))
-raise RuntimeError(msg)
+check_command('Generating signatures failed. This might be due to some 
parse error and/or general layer incompatibilities.',
+  cmd)
 sigs_file = os.path.join(builddir, 'locked-sigs.inc')
 
 sig_regex = re.compile("^(?P.*:.*):(?P.*) .$")
diff --git a/scripts/lib/compatlayer/cases/common.py 
b/scripts/lib/compatlayer/cases/common.py
index 4d328ec..9cc682e 100644
--- a/scripts/lib/compatlayer/cases/common.py
+++ b/scripts/lib/compatlayer/cases/common.py
@@ -2,9 +2,8 @@
 # Released under the MIT license (see COPYING.MIT)
 
 import os
-import subprocess
 import unittest
-from compatlayer import get_signatures, LayerType
+from compatlayer import get_signatures, LayerType, check_command
 from compatlayer.case import OECompatLayerTestCase
 
 class CommonCompatLayer(OECompatLayerTestCase):
@@ -20,26 +19,12 @@ class CommonCompatLayer(OECompatLayerTestCase):
 msg="Layer contains README file but is empty.")
 
 def test_parse(self):
-try:
-output = subprocess.check_output('bitbake -p', shell=True,
-stderr=subprocess.PIPE)
-except subprocess.CalledProcessError as e:
-import traceback
-exc = traceback.format_exc()
-msg = 'Layer %s failed to parse.\n%s\n%s\n' % 
(self.tc.layer['name'],
-exc, e.output.decode('utf-8'))
-raise RuntimeError(msg)
+check_command('Layer %s failed to parse.' % self.tc.layer['name'],
+  'bitbake -p')
 
 def test_show_environment(self):
-try:
-output = subprocess.check_output('bitbake -e', shell=True,
-stderr=subprocess.PIPE)
-except subprocess.CalledProcessError as e:
-import traceback
-exc = traceback.format_exc()
-msg = 'Layer %s failed to show environment.\n%s\n%s\n' % \
-(self.tc.layer['name'], exc, e.output.decode('utf-8'))
-raise RuntimeError(msg)
+check_command('Layer %s failed to show environment.' % 
self.tc.layer['name'],
+  'bitbake -e')
 
 def test_signatures(self):
 if self.tc.layer['type'] == LayerType.SOFTWARE:
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 0/3] yocto-compat-layer: various enhancements + bitbake-diffsigs support

[Patrick Ohly]

I started applying yocto-compat-layer to some real BSP layers and ran
into some usability issues with the tool.

I also didn't want to do the root cause analysis manually, so I
automated the dependency analysis and the running of
bitbake-diffsigs.

This patch series is based on Mark's "yocto-compat-layer.py updates"
series. The last commit depends on Paul's "bitbake-diffsigs: add an
option to find and compare specific signatures" patch from
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=paule/sigstuff&id=5bb69edfb4bbaa7373061daeb4f233a7e2f43a43

Regarding the BSP example that I ended up using: it actually was one
of the better BSP layers and only had one problem in a "bitbake world"
build instead of several as in other BSP layers. Nevertheless I
obscured the name to protect the (not so) guilty in the commit
messages ;-}

The two changes that show up in test_signatures look harmless at first
glance, but probably would need to be done differently to avoid a
false positive when doing the signature check.

Patrick Ohly (3):
  yocto-compat-layer: fix also other command invocations
  yocto-compat-layer: limit report of signature changes
  yocto-compat-layer: include bitbake-diffsigs output

 scripts/lib/compatlayer/__init__.py | 55 +---
 scripts/lib/compatlayer/cases/common.py | 87 --
 2 files changed, 103 insertions(+), 39 deletions(-)

base-commit: f6b68a87a11a84c7baf7784fc71e07c6595d598b
-- 
git-series 0.9.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

[Richard Purdie]

On Wed, 2017-04-05 at 08:39 -0400, Bruce Ashfield wrote:
> We don't make a linux-yocto version available unless it boots
> on all qemu targets, hence there is no reason to specify a
> specific version .. the latest is always fine.
> 
> Also, the other qemu machines don't have this specification, so
> this makes x86 and ARM consistent.
> 
> 
> diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
> index f9d6dd7e364e..b9b640f974f3 100644
> --- a/meta/conf/machine/qemuarm.conf
> +++ b/meta/conf/machine/qemuarm.conf
> @@ -16,5 +16,4 @@ QB_MACHINE = "-machine versatilepb"
>  QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty"
>  # Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
>  QB_OPT_APPEND = "-show-cursor -usb -usbdevice tablet -device virtio-rng-pci"
> -PREFERRED_VERSION_linux-yocto ??= "4.8%"
>  QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux-yocto', 
> '4.7', '', 'zImage-versatile-pb.dtb', d)}"

Note the line below the line you're removing here. This is why we need
this one...

Cheers,

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

[OE-core] Fwd: Adding Static Library Support to the SDK or Rootfs

[Life Life]

Hello,

I'm try to build static library for SDK.

Update the *build*/local.conf file with the following information

SDKIMAGE_FEATURES = "staticdev-pkgs dev-pkgs"

*INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "0"
 BUILDHISTORY_FEATURES = "sdk"*

*But cannot create static library for SDK. *


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

[OE-core] ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries

[Patchwork]

== Series Details ==

Series: python3: fix run-time deps for core python3 libraries
Revision: 1
URL   : https://patchwork.openembedded.org/series/6164/
State : failure

== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Patch line too long (current length 184) 
[test_max_line_length] 
  Suggested fixShorten the corresponding patch line (max length supported 
180)
  Patchscripts/contrib/python/generate-manifest-3.5.py
  Line +m.addPackage( "${PN}-netclient", "Python Internet 
Protocol clients", "${PN} ...

* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at 3b7111b30d)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

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

[OE-core] [PATCH morty] e2fsprogs: Fix wrong error code after optimization

[Daniel Schultz]

fsck.ext will return an error code of 1 if a file systems was checked
and successfully repaired. Even when an optimization was performed it
will return this error code.

This patch will change the error code to 0 if only optimizations had
changed the file systems.

The reason for this patch is a question I asked at the ext4 ML:
http://www.spinics.net/lists/linux-ext4/msg55700.html

Backport from git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
Based on commit bf9f3b6d5b10d19218b4ed904c12b22e36ec57dd

Signed-off-by: Daniel Schultz 
---
 ...-with-exit-status-0-if-no-errors-were-fix.patch | 285 +
 meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.bb  |   1 +
 2 files changed, 286 insertions(+)
 create mode 100644 
meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch

diff --git 
a/meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
new file mode 100644
index 000..44f3888
--- /dev/null
+++ 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
@@ -0,0 +1,285 @@
+From b9bb77a0dd712f06b262a12766972b99cd801269 Mon Sep 17 00:00:00 2001
+From: Theodore Ts'o 
+Date: Thu, 16 Feb 2017 22:02:35 -0500
+Subject: [PATCH] e2fsck: exit with exit status 0 if no errors were fixed
+
+Previously, e2fsck would exit with a status code of 1 even though the
+only changes that it made to the file system were various
+optimziations and not fixing file system corruption.  Since the man
+page states that an exit status of 1 means "file system errors
+corrupted", fix e2fsck to return an exit status of 0.
+
+Upstream-Status: Backport
+
+Signed-off-by: Theodore Ts'o 
+Signed-off-by: Daniel Schultz 
+
+Conflicts:
+   e2fsck/e2fsck.conf.5.in
+---
+ e2fsck/e2fsck.conf.5.in | 34 +
+ e2fsck/journal.c|  1 +
+ e2fsck/problem.c|  8 ---
+ e2fsck/problemP.h   |  1 +
+ e2fsck/unix.c   | 20 +
+ tests/f_collapse_extent_tree/expect.1   |  2 +-
+ tests/f_compress_extent_tree_level/expect.1 |  2 +-
+ tests/f_convert_bmap/expect.1   |  2 +-
+ tests/f_convert_bmap_and_extent/expect.1|  2 +-
+ tests/f_extent_htree/expect.1   |  2 +-
+ tests/f_jnl_errno/expect.1  |  2 +-
+ tests/f_journal/expect.1|  2 +-
+ tests/f_orphan/expect.1 |  2 +-
+ tests/f_orphan_extents_inode/expect.1   |  2 +-
+ tests/f_rehash_dir/expect.1 |  2 +-
+ tests/f_unsorted_EAs/expect.1   |  2 +-
+ 16 files changed, 68 insertions(+), 18 deletions(-)
+
+diff --git a/e2fsck/e2fsck.conf.5.in b/e2fsck/e2fsck.conf.5.in
+index 1f80a04..6a205ce 100644
+--- a/e2fsck/e2fsck.conf.5.in
 b/e2fsck/e2fsck.conf.5.in
+@@ -326,6 +326,40 @@ defaults to true.
+ This relation controls whether or not the scratch file directory is used
+ instead of an in-memory data structure when tracking inode counts.  It
+ defaults to true.
++.TP
++.I not_a_fix
++This boolean option, it set to true, marks the problem as
++one where if the user gives permission to make the requested change,
++it does not mean that the file system had a problem which has since
++been fixed.  This is used for requests to optimize the file system's
++data structure, such as pruning an extent tree.
++@TDB_MAN_COMMENT@.SH THE [scratch_files] STANZA
++@TDB_MAN_COMMENT@The following relations are defined in the
++@TDB_MAN_COMMENT@.I [scratch_files]
++@TDB_MAN_COMMENT@stanza.
++@TDB_MAN_COMMENT@.TP
++@TDB_MAN_COMMENT@.I directory
++@TDB_MAN_COMMENT@If the directory named by this relation exists and is
++@TDB_MAN_COMMENT@writeable, then e2fsck will attempt to use this
++@TDB_MAN_COMMENT@directory to store scratch files instead of using
++@TDB_MAN_COMMENT@in-memory data structures.
++@TDB_MAN_COMMENT@.TP
++@TDB_MAN_COMMENT@.I numdirs_threshold
++@TDB_MAN_COMMENT@If this relation is set, then in-memory data structures
++@TDB_MAN_COMMENT@be used if the number of directories in the filesystem
++@TDB_MAN_COMMENT@are fewer than amount specified.
++@TDB_MAN_COMMENT@.TP
++@TDB_MAN_COMMENT@.I dirinfo
++@TDB_MAN_COMMENT@This relation controls whether or not the scratch file
++@TDB_MAN_COMMENT@directory is used instead of an in-memory data
++@TDB_MAN_COMMENT@structure for directory information.  It defaults to
++@TDB_MAN_COMMENT@true.
++@TDB_MAN_COMMENT@.TP
++@TDB_MAN_COMMENT@.I icount
++@TDB_MAN_COMMENT@This relation controls whether or not the scratch file
++@TDB_MAN_COMMENT@directory is used instead of an in-memory data
++@TDB_MAN_COMMENT@structure when tracking inode counts.  It defaults to
++@TDB_MAN_COMMENT@true.
+ .SH LOGGING
+ E2fsck has the facility to save the i

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

[Romain Perier]

I have just realized, systemd service and timer is already present and
supported on upstream (like cron, in examples/). At least in 3.11.0 and
master.

I will propose an update of this recipe to 3.11.0 (the last release) and
then add support for systemd.


Regards,

Romain


Le 05/04/2017 à 11:41, Romain Perier a écrit :
> Add yocto and Alexander to Cc: (sorry)
>
> Romain
>
>
> Le 05/04/2017 à 11:30, Romain Perier a écrit :
>> Hello,
>>
>>
>> Le 05/04/2017 à 10:25, Alexander Kanavin a écrit :
>>> On 04/05/2017 10:58 AM, Romain Perier wrote:
 ping

>>> Is this available in newer upstream versions of logrotate? Should you
>>> send it there first?
>>>
>>> Alex
>>>
>> No, not yet.
>> Mhhh, we have variables specific to the recipe in the .service and
>> .timer, but I think that I can still send a generic version of these
>> files on upstream and use sed anyway from the recipe...
>>
>> Romain

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

[OE-core] [PATCH] qemu arm/x86: drop linux-yocto preferred version

[Bruce Ashfield]

We don't make a linux-yocto version available unless it boots
on all qemu targets, hence there is no reason to specify a
specific version .. the latest is always fine.

Also, the other qemu machines don't have this specification, so
this makes x86 and ARM consistent.

Signed-off-by: Bruce Ashfield 
---
 meta/conf/machine/include/x86-base.inc | 1 -
 meta/conf/machine/qemuarm.conf | 1 -
 2 files changed, 2 deletions(-)

diff --git a/meta/conf/machine/include/x86-base.inc 
b/meta/conf/machine/include/x86-base.inc
index 40d59577fdb5..82e0cf6a5f36 100644
--- a/meta/conf/machine/include/x86-base.inc
+++ b/meta/conf/machine/include/x86-base.inc
@@ -20,7 +20,6 @@ SERIAL_CONSOLE ?= "115200 ttyS0"
 # kernel-related variables
 #
 PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto"
-PREFERRED_VERSION_linux-yocto ??= "4.8%"
 
 #
 # XSERVER subcomponents, used to build the XSERVER variable
diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
index f9d6dd7e364e..b9b640f974f3 100644
--- a/meta/conf/machine/qemuarm.conf
+++ b/meta/conf/machine/qemuarm.conf
@@ -16,5 +16,4 @@ QB_MACHINE = "-machine versatilepb"
 QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0,115200 console=tty"
 # Add the 'virtio-rng-pci' device otherwise the guest may run out of entropy
 QB_OPT_APPEND = "-show-cursor -usb -usbdevice tablet -device virtio-rng-pci"
-PREFERRED_VERSION_linux-yocto ??= "4.8%"
 QB_DTB = "${@base_version_less_or_equal('PREFERRED_VERSION_linux-yocto', 
'4.7', '', 'zImage-versatile-pb.dtb', d)}"
-- 
2.5.0

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

[OE-core] [PATCH] python3: fix run-time deps for core python3 libraries

[Dmitry Rozhkov]

The http.server module from python3-netclient imports the html module
which is in python3-html. Also xmlrpc.server imports pydoc which is a
part of python3-pydoc. But those run-time dependencies are missing
from python3-netclient and python3-xmlrpc respectively.

Add the missing run-time dependencies.

Signed-off-by: Dmitry Rozhkov 
---
 meta/recipes-devtools/python/python-3.5-manifest.inc | 4 ++--
 scripts/contrib/python/generate-manifest-3.5.py  | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-devtools/python/python-3.5-manifest.inc 
b/meta/recipes-devtools/python/python-3.5-manifest.inc
index 55bcc4b..ec30eb9 100644
--- a/meta/recipes-devtools/python/python-3.5-manifest.inc
+++ b/meta/recipes-devtools/python/python-3.5-manifest.inc
@@ -153,7 +153,7 @@ RDEPENDS_${PN}-multiprocessing="${PN}-core ${PN}-io 
${PN}-lang ${PN}-pickle ${PN
 
FILES_${PN}-multiprocessing="${libdir}/python3.5/lib-dynload/_multiprocessing.*.so
 ${libdir}/python3.5/lib-dynload/__pycache__/_multiprocessing.*.so 
${libdir}/python3.5/multiprocessing 
${libdir}/python3.5/multiprocessing/__pycache__ "
 
 SUMMARY_${PN}-netclient="Python Internet Protocol clients"
-RDEPENDS_${PN}-netclient="${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime 
${PN}-io ${PN}-lang ${PN}-logging ${PN}-mime"
+RDEPENDS_${PN}-netclient="${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime 
${PN}-io ${PN}-lang ${PN}-logging ${PN}-mime ${PN}-html"
 FILES_${PN}-netclient="${libdir}/python3.5/*Cookie*.* 
${libdir}/python3.5/__pycache__/*Cookie*.* ${libdir}/python3.5/base64.* 
${libdir}/python3.5/__pycache__/base64.* ${libdir}/python3.5/cookielib.* 
${libdir}/python3.5/__pycache__/cookielib.* ${libdir}/python3.5/ftplib.* 
${libdir}/python3.5/__pycache__/ftplib.* ${libdir}/python3.5/gopherlib.* 
${libdir}/python3.5/__pycache__/gopherlib.* ${libdir}/python3.5/hmac.* 
${libdir}/python3.5/__pycache__/hmac.* ${libdir}/python3.5/http* 
${libdir}/python3.5/http*/__pycache__ ${libdir}/python3.5/httplib.* 
${libdir}/python3.5/__pycache__/httplib.* ${libdir}/python3.5/mimetypes.* 
${libdir}/python3.5/__pycache__/mimetypes.* ${libdir}/python3.5/nntplib.* 
${libdir}/python3.5/__pycache__/nntplib.* ${libdir}/python3.5/poplib.* 
${libdir}/python3.5/__pycache__/poplib.* ${libdir}/python3.5/smtplib.* 
${libdir}/python3.5/__pycache__/smtplib.* ${libdir}/python3.5/telnetlib.* 
${libdir}/python3.5/__pycache__/telnetlib.* ${libdir}/python3.5/urllib ${lib
 dir}/python3.5/urllib/__pycache__ ${libdir}/python3.5/uuid.* 
${libdir}/python3.5/__pycache__/uuid.* ${libdir}/python3.5/rfc822.* 
${libdir}/python3.5/__pycache__/rfc822.* ${libdir}/python3.5/mimetools.* 
${libdir}/python3.5/__pycache__/mimetools.* "
 
 SUMMARY_${PN}-netserver="Python Internet Protocol servers"
@@ -273,7 +273,7 @@ RDEPENDS_${PN}-xml="${PN}-core ${PN}-re"
 FILES_${PN}-xml="${libdir}/python3.5/lib-dynload/_elementtree.*.so 
${libdir}/python3.5/lib-dynload/__pycache__/_elementtree.*.so 
${libdir}/python3.5/lib-dynload/pyexpat.*.so 
${libdir}/python3.5/lib-dynload/__pycache__/pyexpat.*.so 
${libdir}/python3.5/xml ${libdir}/python3.5/xml/__pycache__ 
${libdir}/python3.5/xmllib.* ${libdir}/python3.5/__pycache__/xmllib.* "
 
 SUMMARY_${PN}-xmlrpc="Python XML-RPC support"
-RDEPENDS_${PN}-xmlrpc="${PN}-core ${PN}-xml ${PN}-netserver ${PN}-lang"
+RDEPENDS_${PN}-xmlrpc="${PN}-core ${PN}-xml ${PN}-netserver ${PN}-lang 
${PN}-pydoc"
 FILES_${PN}-xmlrpc="${libdir}/python3.5/xmlrpclib.* 
${libdir}/python3.5/__pycache__/xmlrpclib.* 
${libdir}/python3.5/SimpleXMLRPCServer.* 
${libdir}/python3.5/__pycache__/SimpleXMLRPCServer.* 
${libdir}/python3.5/DocXMLRPCServer.* 
${libdir}/python3.5/__pycache__/DocXMLRPCServer.* ${libdir}/python3.5/xmlrpc 
${libdir}/python3.5/xmlrpc/__pycache__ "
 
 SUMMARY_${PN}-modules="All Python modules"
diff --git a/scripts/contrib/python/generate-manifest-3.5.py 
b/scripts/contrib/python/generate-manifest-3.5.py
index 386bdfc..5835de8 100755
--- a/scripts/contrib/python/generate-manifest-3.5.py
+++ b/scripts/contrib/python/generate-manifest-3.5.py
@@ -340,7 +340,7 @@ if __name__ == "__main__":
 m.addPackage( "${PN}-multiprocessing", "Python multiprocessing support", 
"${PN}-core ${PN}-io ${PN}-lang ${PN}-pickle ${PN}-threading ${PN}-ctypes 
${PN}-mmap",
 "lib-dynload/_multiprocessing.*.so multiprocessing" ) # package
 
-m.addPackage( "${PN}-netclient", "Python Internet Protocol clients", 
"${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime ${PN}-io ${PN}-lang 
${PN}-logging ${PN}-mime",
+m.addPackage( "${PN}-netclient", "Python Internet Protocol clients", 
"${PN}-argparse ${PN}-core ${PN}-crypt ${PN}-datetime ${PN}-io ${PN}-lang 
${PN}-logging ${PN}-mime ${PN}-html",
 "*Cookie*.* " +
 "base64.* cookielib.* ftplib.* gopherlib.* hmac.* http* httplib.* 
mimetypes.* nntplib.* poplib.* smtplib.* telnetlib.* urllib  uuid.* rfc822.* 
mimetools.*" )
 
@@ -422,7 +422,7 @@ if __name__ == "__main__":
 m.addPackage( "${PN}-xml", "Python basic XML supp

Re: [OE-core] [PATCH] x86-base.inc, qemuarm.conf: prefer 4.10 version of linux-yocto

[Bruce Ashfield]

On Tue, Apr 4, 2017 at 11:48 AM, Burton, Ross  wrote:

>
> On 4 April 2017 at 09:02, Martin Jansa  wrote:
>
>> -PREFERRED_VERSION_linux-yocto ??= "4.8%"
>> +PREFERRED_VERSION_linux-yocto ??= "4.10%"
>>
>
> The qemuppc and qemumips machines don't have a preferred version, so
> should we be setting it in all the machine configurations, or can we remove
> it from these recipes?
>


I can look into that. But I'm traveling at the moment and won't have time
to spin a patch
and test for a few days.

Bruce


>
> Ross
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/3] oeqa/utils/targetbuild: tmp dir improvements

[Joshua Lock]

Don't hard-code /tmp as the tmpdir, instead use WORKDIR as the tmpdir if the
instantiater doesn't specify a value.

Signed-off-by: Joshua Lock 
---
 meta/lib/oeqa/utils/targetbuild.py | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/utils/targetbuild.py 
b/meta/lib/oeqa/utils/targetbuild.py
index 6f237b5..9249fa2 100644
--- a/meta/lib/oeqa/utils/targetbuild.py
+++ b/meta/lib/oeqa/utils/targetbuild.py
@@ -8,14 +8,19 @@ import os
 import re
 import bb.utils
 import subprocess
+import tempfile
 from abc import ABCMeta, abstractmethod
 
 class BuildProject(metaclass=ABCMeta):
 
-def __init__(self, d, uri, foldername=None, tmpdir="/tmp/"):
+def __init__(self, d, uri, foldername=None, tmpdir=None):
 self.d = d
 self.uri = uri
 self.archive = os.path.basename(uri)
+if not tmpdir:
+tmpdir = self.d.getVar('WORKDIR')
+if not tmpdir:
+tmpdir = tempfile.mkdtemp(prefix='buildproject')
 self.localarchive = os.path.join(tmpdir,self.archive)
 if foldername:
 self.fname = foldername
@@ -24,7 +29,6 @@ class BuildProject(metaclass=ABCMeta):
 
 # Download self.archive to self.localarchive
 def _download_archive(self):
-
 dl_dir = self.d.getVar("DL_DIR")
 if dl_dir and os.path.exists(os.path.join(dl_dir, self.archive)):
 bb.utils.copyfile(os.path.join(dl_dir, self.archive), 
self.localarchive)
@@ -73,7 +77,7 @@ class TargetBuildProject(BuildProject):
 def __init__(self, target, d, uri, foldername=None):
 self.target = target
 self.targetdir = "~/"
-BuildProject.__init__(self, d, uri, foldername, tmpdir="/tmp")
+BuildProject.__init__(self, d, uri, foldername)
 
 def download_archive(self):
 
-- 
2.9.3

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

[OE-core] [PATCH 3/3] oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir

[Joshua Lock]

Rather than hard-coding the tmpdir for TargetBuildProject to /tmp allow the
parent's default handling to define an appropriate tmpdir.

Signed-off-by: Joshua Lock 
---
 meta/lib/oeqa/runtime/utils/targetbuildproject.py | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/runtime/utils/targetbuildproject.py 
b/meta/lib/oeqa/runtime/utils/targetbuildproject.py
index 551b0b6..5af55d7 100644
--- a/meta/lib/oeqa/runtime/utils/targetbuildproject.py
+++ b/meta/lib/oeqa/runtime/utils/targetbuildproject.py
@@ -8,8 +8,7 @@ class TargetBuildProject(BuildProject):
 def __init__(self, target, uri, foldername=None, dl_dir=None):
 self.target = target
 self.targetdir = "~/"
-BuildProject.__init__(self, uri, foldername, tmpdir="/tmp",
-dl_dir=dl_dir)
+BuildProject.__init__(self, uri, foldername, dl_dir=dl_dir)
 
 def download_archive(self):
 self._download_archive()
-- 
2.9.3

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

[OE-core] [PATCH 1/3] oeqa/utils/buildproject: create a more unique tmp dir

[Joshua Lock]

Rather than hardcoding /tmp as the default tmpdir make a more unique tmpdir
with tempfile.mkdtemp() when the caller doesn't specify a tmpdir value.

Signed-off-by: Joshua Lock 
---
 meta/lib/oeqa/utils/buildproject.py | 7 +--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/buildproject.py 
b/meta/lib/oeqa/utils/buildproject.py
index fc8879c..487f08b 100644
--- a/meta/lib/oeqa/utils/buildproject.py
+++ b/meta/lib/oeqa/utils/buildproject.py
@@ -8,14 +8,17 @@ import os
 import re
 import subprocess
 import shutil
+import tempfile
 
 from abc import ABCMeta, abstractmethod
 
 class BuildProject(metaclass=ABCMeta):
-def __init__(self, uri, foldername=None, tmpdir="/tmp/", dl_dir=None):
+def __init__(self, uri, foldername=None, tmpdir=None, dl_dir=None):
 self.uri = uri
 self.archive = os.path.basename(uri)
-self.localarchive = os.path.join(tmpdir,self.archive)
+if not tmpdir:
+tmpdir = tempfile.mkdtemp(prefix='buildproject')
+self.localarchive = os.path.join(tmpdir, self.archive)
 self.dl_dir = dl_dir
 if foldername:
 self.fname = foldername
-- 
2.9.3

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

[OE-core] [PATCH 2/2] openssh: Use systemd-tmpfiles to create volatiles files and dirs

[Fabio Berton]

Volatiles files are installed in different locations depending on
distro feature update-rc.d or systemd. For update-rc.d volatiles
configuration files are installed in /etc/default/volatiles and
for systemd in /etc/tmpfiles.d/. So, we need to install volatiles
files in correct location depending on what distro feature is used.

Signed-off-by: Fabio Berton 
---
 .../openssh/openssh/sshd.tmpfiles.d|  2 ++
 meta/recipes-connectivity/openssh/openssh_7.4p1.bb | 27 +-
 2 files changed, 18 insertions(+), 11 deletions(-)
 create mode 100644 meta/recipes-connectivity/openssh/openssh/sshd.tmpfiles.d

diff --git a/meta/recipes-connectivity/openssh/openssh/sshd.tmpfiles.d 
b/meta/recipes-connectivity/openssh/openssh/sshd.tmpfiles.d
new file mode 100644
index 00..a2ae06ad94
--- /dev/null
+++ b/meta/recipes-connectivity/openssh/openssh/sshd.tmpfiles.d
@@ -0,0 +1,2 @@
+d /var/run/sshd 0755rootroot-   -
+f /var/log/lastlog  0644rootroot-   -
diff --git a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb 
b/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
index c8093d4e2b..eff83de135 100644
--- a/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_7.4p1.bb
@@ -20,6 +20,7 @@ SRC_URI = 
"http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar
file://sshd@.service \
file://sshdgenkeys.service \
file://volatiles.99_sshd \
+   file://sshd.tmpfiles.d \
file://add-test-support-for-busybox.patch \
file://run-ptest \
file://openssh-7.1p1-conditional-compile-des-in-cipher.patch \
@@ -104,8 +105,7 @@ do_install_append () {
install -m 0755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/sshd
rm -f ${D}${bindir}/slogin ${D}${datadir}/Ssh.bin
rmdir ${D}${localstatedir}/run/sshd ${D}${localstatedir}/run 
${D}${localstatedir}
-   install -d ${D}/${sysconfdir}/default/volatiles
-   install -m 644 ${WORKDIR}/volatiles.99_sshd 
${D}/${sysconfdir}/default/volatiles/99_sshd
+
install -m 0755 ${S}/contrib/ssh-copy-id ${D}${bindir}
 
# Create config files for read-only rootfs
@@ -117,14 +117,19 @@ do_install_append () {
echo "HostKey /var/run/ssh/ssh_host_ecdsa_key" >> 
${D}${sysconfdir}/ssh/sshd_config_readonly
echo "HostKey /var/run/ssh/ssh_host_ed25519_key" >> 
${D}${sysconfdir}/ssh/sshd_config_readonly
 
-   install -d ${D}${systemd_unitdir}/system
-   install -c -m 0644 ${WORKDIR}/sshd.socket ${D}${systemd_unitdir}/system
-   install -c -m 0644 ${WORKDIR}/sshd@.service 
${D}${systemd_unitdir}/system
-   install -c -m 0644 ${WORKDIR}/sshdgenkeys.service 
${D}${systemd_unitdir}/system
-   sed -i -e 's,@BASE_BINDIR@,${base_bindir},g' \
-   -e 's,@SBINDIR@,${sbindir},g' \
-   -e 's,@BINDIR@,${bindir},g' \
-   ${D}${systemd_unitdir}/system/sshd.socket 
${D}${systemd_unitdir}/system/*.service
+   if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; 
then
+   install -d ${D}${systemd_unitdir}/system
+   install -c -m 0644 ${WORKDIR}/sshd.socket 
${D}${systemd_unitdir}/system
+   install -c -m 0644 ${WORKDIR}/sshd@.service 
${D}${systemd_unitdir}/system
+   install -c -m 0644 ${WORKDIR}/sshdgenkeys.service 
${D}${systemd_unitdir}/system
+   sed -i -e 's,@BASE_BINDIR@,${base_bindir},g' \
+   -e 's,@SBINDIR@,${sbindir},g' \
+   -e 's,@BINDIR@,${bindir},g' \
+   ${D}${systemd_unitdir}/system/sshd.socket 
${D}${systemd_unitdir}/system/*.service
+   install -Dm 0644 ${WORKDIR}/sshd.tmpfiles.d 
${D}${sysconfdir}/tmpfiles.d/sshd.conf
+   else
+   install -Dm 0644 ${WORKDIR}/volatiles.99_sshd 
${D}/${sysconfdir}/default/volatiles/99_sshd
+   fi
 }
 
 do_install_ptest () {
@@ -138,7 +143,7 @@ PACKAGES =+ "${PN}-keygen ${PN}-scp ${PN}-ssh ${PN}-sshd 
${PN}-sftp ${PN}-misc $
 FILES_${PN}-scp = "${bindir}/scp.${BPN}"
 FILES_${PN}-ssh = "${bindir}/ssh.${BPN} ${sysconfdir}/ssh/ssh_config"
 FILES_${PN}-sshd = "${sbindir}/sshd ${sysconfdir}/init.d/sshd 
${systemd_unitdir}/system"
-FILES_${PN}-sshd += "${sysconfdir}/ssh/moduli ${sysconfdir}/ssh/sshd_config 
${sysconfdir}/ssh/sshd_config_readonly ${sysconfdir}/default/volatiles/99_sshd 
${sysconfdir}/pam.d/sshd"
+FILES_${PN}-sshd += "${sysconfdir}/ssh/moduli ${sysconfdir}/ssh/sshd_config 
${sysconfdir}/ssh/sshd_config_readonly ${sysconfdir}/default/volatiles/99_sshd 
${sysconfdir}/pam.d/sshd ${sysconfdir}/tmpfiles.d/sshd.conf"
 FILES_${PN}-sftp = "${bindir}/sftp"
 FILES_${PN}-sftp-server = "${libexecdir}/sftp-server"
 FILES_${PN}-misc = "${bindir}/ssh* ${libexecdir}/ssh*"
-- 
2.11.0

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

[OE-core] [PATCH 1/2] wpa-supplicant: Use systemd-tmpfiles to create volatiles files and dirs

[Fabio Berton]

Volatiles files are installed in different locations depending on
distro feature update-rc.d or systemd. For update-rc.d volatiles
configuration files are installed in /etc/default/volatiles and
for systemd in /etc/tmpfiles.d/. So, we need to install volatiles
files in correct location depending on what distro feature is used.

Signed-off-by: Fabio Berton 
---
 .../wpa-supplicant/wpa-supplicant/wpa_supplicant.tmpfiles.d   | 1 +
 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.bb| 8 +---
 2 files changed, 6 insertions(+), 3 deletions(-)
 create mode 100644 
meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/wpa_supplicant.tmpfiles.d

diff --git 
a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/wpa_supplicant.tmpfiles.d
 
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/wpa_supplicant.tmpfiles.d
new file mode 100644
index 00..5b27498b8e
--- /dev/null
+++ 
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/wpa_supplicant.tmpfiles.d
@@ -0,0 +1 @@
+d /var/run/wpa_supplicant   0700rootroot-   -
diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.bb 
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.bb
index 146bccfaa7..ff4ad34d51 100644
--- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.bb
+++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.6.bb
@@ -24,6 +24,7 @@ SRC_URI = "http://w1.fi/releases/wpa_supplicant-${PV}.tar.gz  
\
file://wpa_supplicant.conf \
file://wpa_supplicant.conf-sane \
file://99_wpa_supplicant \
+   file://wpa_supplicant.tmpfiles.d \
   "
 SRC_URI[md5sum] = "091569eb4440b7d7f2b4276dbfc03c3c"
 SRC_URI[sha256sum] = 
"b4936d34c4e6cdd44954beba74296d964bc2c9668ecaa5255e499636fe2b1450"
@@ -93,10 +94,11 @@ do_install () {
if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)}; 
then
install -d ${D}/${systemd_unitdir}/system
install -m 644 ${S}/wpa_supplicant/systemd/*.service 
${D}/${systemd_unitdir}/system
+   install -Dm 0644 ${WORKDIR}/wpa_supplicant.tmpfiles.d 
${D}${sysconfdir}/tmpfiles.d/wpa_supplicant.conf
+   else
+   install -d ${D}/etc/default/volatiles
+   install -m 0644 ${WORKDIR}/99_wpa_supplicant 
${D}/etc/default/volatiles
fi
-
-   install -d ${D}/etc/default/volatiles
-   install -m 0644 ${WORKDIR}/99_wpa_supplicant ${D}/etc/default/volatiles
 }
 
 pkg_postinst_wpa-supplicant () {
-- 
2.11.0

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

[OE-core] [PATCH] ghostscript: CVE-2017-7207

[Catalin Enache]

The mem_get_bits_rectangle function in Artifex Software, Inc.
Ghostscript 9.20 allows remote attackers to cause a denial
of service (NULL pointer dereference) via a crafted PostScript
document.

Reference:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7207

Upstream patch:
http://git.ghostscript.com/?p=ghostpdl.git;h=309eca4e0a31ea70dcc844812691439312dad091

Signed-off-by: Catalin Enache 
---
 .../ghostscript/ghostscript/CVE-2017-7207.patch| 39 ++
 .../ghostscript/ghostscript_9.20.bb|  1 +
 2 files changed, 40 insertions(+)
 create mode 100644 
meta/recipes-extended/ghostscript/ghostscript/CVE-2017-7207.patch

diff --git a/meta/recipes-extended/ghostscript/ghostscript/CVE-2017-7207.patch 
b/meta/recipes-extended/ghostscript/ghostscript/CVE-2017-7207.patch
new file mode 100644
index 000..a05dc02
--- /dev/null
+++ b/meta/recipes-extended/ghostscript/ghostscript/CVE-2017-7207.patch
@@ -0,0 +1,39 @@
+From 0e88bee1304993668fede72498d656a2dd33a35e Mon Sep 17 00:00:00 2001
+From: Ken Sharp 
+Date: Mon, 20 Mar 2017 09:34:11 +
+Subject: [PATCH] Ensure a device has raster memory, before trying to read it.
+
+Bug #697676 "Null pointer dereference in mem_get_bits_rectangle()"
+
+This is only possible by abusing/mis-using Ghostscript-specific
+language extensions, so cannot happen in a general PostScript program.
+
+Nevertheless, Ghostscript should not crash. So this commit checks the
+memory device to see if raster memory has been allocated, before trying
+to read from it.
+
+Upstream-Status: Backport
+CVE: CVE-2017-7207
+
+Author: Ken Sharp 
+Signed-off-by: Catalin Enache 
+---
+ base/gdevmem.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/base/gdevmem.c b/base/gdevmem.c
+index 41108ba..183f96d 100644
+--- a/base/gdevmem.c
 b/base/gdevmem.c
+@@ -605,6 +605,8 @@ mem_get_bits_rectangle(gx_device * dev, const gs_int_rect 
* prect,
+ GB_PACKING_CHUNKY | GB_COLORS_NATIVE | GB_ALPHA_NONE;
+ return_error(gs_error_rangecheck);
+ }
++if (mdev->line_ptrs == 0x00)
++return_error(gs_error_rangecheck);
+ if ((w <= 0) | (h <= 0)) {
+ if ((w | h) < 0)
+ return_error(gs_error_rangecheck);
+-- 
+2.10.2
+
diff --git a/meta/recipes-extended/ghostscript/ghostscript_9.20.bb 
b/meta/recipes-extended/ghostscript/ghostscript_9.20.bb
index 210e9a7..e8fc5df 100644
--- a/meta/recipes-extended/ghostscript/ghostscript_9.20.bb
+++ b/meta/recipes-extended/ghostscript/ghostscript_9.20.bb
@@ -31,6 +31,7 @@ SRC_URI = "${SRC_URI_BASE} \
file://ghostscript-9.02-genarch.patch \
file://objarch.h \
file://cups-no-gcrypt.patch \
+   file://CVE-2017-7207.patch \
"
 
 SRC_URI_class-native = "${SRC_URI_BASE} \
-- 
2.10.2

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

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

[Richard Purdie]

On Wed, 2017-04-05 at 20:06 +1000, Nathan Rossi wrote:
> On 30 March 2017 at 15:12, Chen Qi  wrote:
> > 
> > The 'recipe-sysroot' and 'recipe-sysroot-native' directories need
> > to
> > be preserved for runqemu to work correctly. Otherwise, when
> > 'rm_work'
> > is enabled, these directories are removed, thus causing errors when
> > using runqemu .
> > 
> > [YOCTO #11266]
> > [YOCTO #11193]
> > 
> > Signed-off-by: Chen Qi 
> > ---
> >  meta/classes/image.bbclass | 1 +
> >  meta/conf/machine/include/qemu.inc | 3 +++
> >  2 files changed, 4 insertions(+)
> > 
> > diff --git a/meta/classes/image.bbclass
> > b/meta/classes/image.bbclass
> > index 405fd73..cac3a5f 100644
> > --- a/meta/classes/image.bbclass
> > +++ b/meta/classes/image.bbclass
> > @@ -8,6 +8,7 @@ inherit ${SDKEXTCLASS}
> >  TOOLCHAIN_TARGET_TASK += "${PACKAGE_INSTALL}"
> >  TOOLCHAIN_TARGET_TASK_ATTEMPTONLY +=
> > "${PACKAGE_INSTALL_ATTEMPTONLY}"
> >  POPULATE_SDK_POST_TARGET_COMMAND += "rootfs_sysroot_relativelinks;
> > "
> > +RM_WORK_EXCLUDE_ITEMS_append = " ${IMAGE_RM_WORK_EXCLUDE_ITEMS}"
> > 
> >  LICENSE = "MIT"
> >  PACKAGES = ""
> > diff --git a/meta/conf/machine/include/qemu.inc
> > b/meta/conf/machine/include/qemu.inc
> > index 0e4103b..8345c08 100644
> > --- a/meta/conf/machine/include/qemu.inc
> > +++ b/meta/conf/machine/include/qemu.inc
> > @@ -29,3 +29,6 @@ KERNEL_FEATURES_append_pn-linux-yocto = "
> > features/nfsd/nfsd-enable.scc"
> >  MACHINE_EXTRA_RRECOMMENDS += "rng-tools"
> > 
> >  IMAGE_CLASSES += "qemuboot"
> > +
> > +# These two directories need to be preserved for runqemu to work
> > well
> > +IMAGE_RM_WORK_EXCLUDE_ITEMS = "recipe-sysroot recipe-sysroot-
> > native"
> Should this be setup by qemuboot.bbclass instead, so that it applies
> to any image/machine (even those that do not use qemu.inc) that is
> intended to be used by runqemu?

I'm trying to decide what the best approach here is. I'm thinking it
might be better to:

a) make qemu builds depend on qemu-helper-native
b) make that preserve its native sysroot (not the target one).
c) have runqemu look at qemu-helper-native

I think that should solve problems and work better than the above?

Cheers,

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

[OE-core] [PATCH] busybox: Security fix BUG9071

[Martin Balik]

Signed-off-by: Martin Balik 
Signed-off-by: Pascal Bach 
---
 .../busybox/BUG9071_buffer_overflow_arp.patch  | 53 ++
 meta/recipes-core/busybox/busybox_1.24.1.bb|  1 +
 2 files changed, 54 insertions(+)
 create mode 100644 
meta/recipes-core/busybox/busybox/BUG9071_buffer_overflow_arp.patch

diff --git 
a/meta/recipes-core/busybox/busybox/BUG9071_buffer_overflow_arp.patch 
b/meta/recipes-core/busybox/busybox/BUG9071_buffer_overflow_arp.patch
new file mode 100644
index 000..828694c
--- /dev/null
+++ b/meta/recipes-core/busybox/busybox/BUG9071_buffer_overflow_arp.patch
@@ -0,0 +1,53 @@
+busybox1.24.1: Fix busybox - (local) cmdline stack buffer overwrite 
+
+[No upstream tracking] -- https://bugs.busybox.net/show_bug.cgi?id=9071
+
+busybox - (local) cmdline stack buffer overwrite 
+
+Busybox provides an `arp` applet which is missing an array bounds check for 
+command-line parameter `IFNAME`. It is therefore vulnerable to a command-line 
+based local stack buffer overwrite effectively allowing local users to write 
+past a 16 bytes fixed stack buffer. This leads to two scenarios, one (A) where 
+an IOCTL for GET_HW_ADDRESS (`SIOCGIFHWADDR`) fails and results in a corrupted 
+`va_list` being passed to `*printf()` and one (B) where an attacker might 
provide 
+valid params for the IOCTL and trick the program to proceed and result in a 
+`RET eip overwrite` eventually gaining code execution.
+
+Upstream-Status: Backport 
[https://git.busybox.net/busybox/commit/networking/arp.c?id=88e2b1cb626761b1924305b761a5dfc723613c4e]
+BUG: BUG9071
+Signed-off-by: Martin Balik 
+Signed-off-by: Pascal Bach 
+
+--
+
+diff --git a/networking/arp.c b/networking/arp.c
+index 0099aa5..87eb327 100644
+--- a/networking/arp.c
 b/networking/arp.c
+@@ -176,7 +176,7 @@ static int arp_del(char **args)
+   if (flags == 0)
+   flags = 3;
+ 
+-  strncpy(req.arp_dev, device, sizeof(req.arp_dev));
++  strncpy_IFNAMSIZ(req.arp_dev, device);
+ 
+   err = -1;
+ 
+@@ -217,7 +217,7 @@ static void arp_getdevhw(char *ifname, struct sockaddr *sa)
+   struct ifreq ifr;
+   const struct hwtype *xhw;
+ 
+-  strcpy(ifr.ifr_name, ifname);
++  strncpy_IFNAMSIZ(ifr.ifr_name, ifname);
+   ioctl_or_perror_and_die(sockfd, SIOCGIFHWADDR, &ifr,
+   "can't get HW-Address for '%s'", 
ifname);
+   if (hw_set && (ifr.ifr_hwaddr.sa_family != hw->type)) {
+@@ -330,7 +330,7 @@ static int arp_set(char **args)
+   /* Fill in the remainder of the request. */
+   req.arp_flags = flags;
+ 
+-  strncpy(req.arp_dev, device, sizeof(req.arp_dev));
++  strncpy_IFNAMSIZ(req.arp_dev, device);
+ 
+   /* Call the kernel. */
+   if (option_mask32 & ARP_OPT_v)
diff --git a/meta/recipes-core/busybox/busybox_1.24.1.bb 
b/meta/recipes-core/busybox/busybox_1.24.1.bb
index 41fc641..5dc1808 100644
--- a/meta/recipes-core/busybox/busybox_1.24.1.bb
+++ b/meta/recipes-core/busybox/busybox_1.24.1.bb
@@ -55,6 +55,7 @@ SRC_URI = 
"http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \
file://makefile-libbb-race.patch \
file://0001-libiproute-handle-table-ids-larger-than-255.patch \
file://ifupdown-pass-interface-device-name-for-ipv6-route-c.patch \
+   file://BUG9071_buffer_overflow_arp.patch \
 "
 SRC_URI_append_libc-musl = " file://musl.cfg "
 
-- 
2.1.4

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

Re: [OE-core] [PATCH 1/1] image.inc/qemu.inc: preserve directories to be used by runqemu

[Nathan Rossi]

On 30 March 2017 at 15:12, Chen Qi  wrote:
> The 'recipe-sysroot' and 'recipe-sysroot-native' directories need to
> be preserved for runqemu to work correctly. Otherwise, when 'rm_work'
> is enabled, these directories are removed, thus causing errors when
> using runqemu .
>
> [YOCTO #11266]
> [YOCTO #11193]
>
> Signed-off-by: Chen Qi 
> ---
>  meta/classes/image.bbclass | 1 +
>  meta/conf/machine/include/qemu.inc | 3 +++
>  2 files changed, 4 insertions(+)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 405fd73..cac3a5f 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -8,6 +8,7 @@ inherit ${SDKEXTCLASS}
>  TOOLCHAIN_TARGET_TASK += "${PACKAGE_INSTALL}"
>  TOOLCHAIN_TARGET_TASK_ATTEMPTONLY += "${PACKAGE_INSTALL_ATTEMPTONLY}"
>  POPULATE_SDK_POST_TARGET_COMMAND += "rootfs_sysroot_relativelinks; "
> +RM_WORK_EXCLUDE_ITEMS_append = " ${IMAGE_RM_WORK_EXCLUDE_ITEMS}"
>
>  LICENSE = "MIT"
>  PACKAGES = ""
> diff --git a/meta/conf/machine/include/qemu.inc 
> b/meta/conf/machine/include/qemu.inc
> index 0e4103b..8345c08 100644
> --- a/meta/conf/machine/include/qemu.inc
> +++ b/meta/conf/machine/include/qemu.inc
> @@ -29,3 +29,6 @@ KERNEL_FEATURES_append_pn-linux-yocto = " 
> features/nfsd/nfsd-enable.scc"
>  MACHINE_EXTRA_RRECOMMENDS += "rng-tools"
>
>  IMAGE_CLASSES += "qemuboot"
> +
> +# These two directories need to be preserved for runqemu to work well
> +IMAGE_RM_WORK_EXCLUDE_ITEMS = "recipe-sysroot recipe-sysroot-native"

Should this be setup by qemuboot.bbclass instead, so that it applies
to any image/machine (even those that do not use qemu.inc) that is
intended to be used by runqemu?

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

Re: [OE-core] tainting other recipe's specific task

[Mike Looijmans]

On 04-04-17 15:54, André Draszik wrote:

Hi,

Is it possible to invalidate one recipe's hash for a specific task from
another recipe?


I hope not...



More specifically, I have an initramfs image recipe and a main image recipe
where do_rootfs of the main image [depends] on do_deploy of initramfs.

If do_rootfs of the main image needs to be re-run, I need to make sure that
do_rootfs of the initramfs image is re-run (and of course do_deploy) before.
Basically I want to add a timestamp to both images, and the timestamp should
be the same.

Using my current dependencies, do_rootfs of the main image is re-run if the
initramfs is re-deployed:

--- snip main_image.bb: ---
do_rootfs[depends] += "initramfs:do_deploy"
--- snap ---

but I need this both ways. Just adding the equivalent to the initramfs
recipe results in bitbake complaining about a recursive dependency loop.


Can this be achieved? Even some pointers would be helpful...


Or some other approach where I can add the same timestamp to both images if
either of the images needed to be rebuilt due to some change?


What I did was have two image recipes, let's say "big-image" and 
"small-image". The big-image included a package called "big-project". To the 
"big-project.bb" recipe I added:


DEPENDS += "small-image"
do_install[depends] += "small-image:do_image_complete"

And in the do_install I copy the stuff from small-image into whereever I 
wanted it to be insided the small image.


Maybe this covers your use case?


Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail





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

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

[Romain Perier]

Add yocto and Alexander to Cc: (sorry)

Romain


Le 05/04/2017 à 11:30, Romain Perier a écrit :
> Hello,
>
>
> Le 05/04/2017 à 10:25, Alexander Kanavin a écrit :
>> On 04/05/2017 10:58 AM, Romain Perier wrote:
>>> ping
>>>
>> Is this available in newer upstream versions of logrotate? Should you
>> send it there first?
>>
>> Alex
>>
> No, not yet.
> Mhhh, we have variables specific to the recipe in the .service and
> .timer, but I think that I can still send a generic version of these
> files on upstream and use sed anyway from the recipe...
>
> Romain

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

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

[Romain Perier]

Hello,


Le 05/04/2017 à 10:25, Alexander Kanavin a écrit :
> On 04/05/2017 10:58 AM, Romain Perier wrote:
>> ping
>>
>
> Is this available in newer upstream versions of logrotate? Should you
> send it there first?
>
> Alex
>
No, not yet.
Mhhh, we have variables specific to the recipe in the .service and
.timer, but I think that I can still send a generic version of these
files on upstream and use sed anyway from the recipe...

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

Re: [OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

[Zheng, Ruoqin]

32be_rootfs boot from sdcard (ls1046)

I used source code provided by nxp  QorIQ-Linux-SDK-v2.0-SOURCE.iso + 
SDK-V2.0-1701 to build the kernel and rootfs , then it can’t boot from sdcard.



I tried to put kernel(32be) and rootfs(32be) in SD card , and boot it follow 
the SDK2.0, it was fail to mount the rootfs(while 64be kernel is normal),and 
here is part of log:

mmcblk0: mmc0:0007 SL32G 29.0 GiB

 mcblk0: p1

VFS: Mounted root (ext2 filesystem) on device 1:0.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

b30030375936 mmcblk0  driver: mmcblk

  b30130371936 mmcblk0p1 -01

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE



The entire log is in atachments, do anyone have any idea about this problem?



By the way, I tried to boot the kernel with command “bootm a000:kernel@1 - 
a000:fdt@1”

And the log show as below, you can see that mmcblk0 device is missed, do anyone 
know the reason?



ALSA device list:

  No soundcards found.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE


Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
   Nanjing, 210012, China
MAIL : zhengrq.f...@cn.fujistu.com



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

[OE-core] [PATCH] recipe_sanity: Drop now unused FILESDIR

[Richard Purdie]

FILESDIR is long dead and unreferenced pretty much anywhere now, drop these
sanity references too.

Signed-off-by: Richard Purdie 
---
 meta/classes/recipe_sanity.bbclass | 17 -
 1 file changed, 17 deletions(-)

diff --git a/meta/classes/recipe_sanity.bbclass 
b/meta/classes/recipe_sanity.bbclass
index 3b00b0e..7fa4a84 100644
--- a/meta/classes/recipe_sanity.bbclass
+++ b/meta/classes/recipe_sanity.bbclass
@@ -70,22 +70,6 @@ def can_delete_FILESPATH(cfgdata, d):
 return False
 return expected != unexpanded
 
-def can_delete_FILESDIR(cfgdata, d):
-expected = cfgdata.get("FILESDIR")
-#expected = "${@bb.utils.which(d.getVar('FILESPATH'), '.')}"
-unexpanded = d.getVar("FILESDIR", False)
-if unexpanded is None:
-return False
-
-expanded = os.path.normpath(d.getVar("FILESDIR"))
-filespath = d.getVar("FILESPATH").split(":")
-filespath = [os.path.normpath(f) for f in filespath if os.path.exists(f)]
-
-return unexpanded != expected and \
-   os.path.exists(expanded) and \
-   (expanded in filespath or
-expanded == d.expand(expected))
-
 def can_delete_others(p, cfgdata, d):
 for k in ["S", "PV", "PN", "DESCRIPTION", "DEPENDS",
   "SECTION", "PACKAGES", "EXTRA_OECONF", "EXTRA_OEMAKE"]:
@@ -112,7 +96,6 @@ python do_recipe_sanity () {
 p = "%s %s %s" % (d.getVar("PN"), d.getVar("PV"), d.getVar("PR"))
 
 sanitychecks = [
-(can_delete_FILESDIR, "candidate for removal of FILESDIR"),
 (can_delete_FILESPATH, "candidate for removal of FILESPATH"),
 #(can_use_autotools_base, "candidate for use of autotools_base"),
 (incorrect_nonempty_PACKAGES, "native or cross recipe with non-empty 
PACKAGES"),
-- 
2.7.4

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

Re: [OE-core] time to get rid of FILESDIR?

[Richard Purdie]

On Tue, 2017-04-04 at 18:11 -0400, Robert P. J. Day wrote:
>   the only references i see to the deprecated FILESDIR are
> historical,
> none actually being used. what about just tossing it?

That has always been the intent, thanks for the reminder. Patches sent
to do just that.

Cheers,

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

[OE-core] [meta-freescale]: 32be_rootfs boot from sdcard

[Zheng, Ruoqin]

32be_rootfs boot from sdcard (ls1046)



I tried to put kernel and rootfs in SD card , and boot it follow the SDK 
note(ls1046), it was fail to mount the rootfs(while 64be kernel is good),and 
here is part of log:

mmcblk0: mmc0:0007 SL32G 29.0 GiB

 mcblk0: p1

VFS: Mounted root (ext2 filesystem) on device 1:0.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

b30030375936 mmcblk0  driver: mmcblk

  b30130371936 mmcblk0p1 -01

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE



The entire log is in atachments, do anyone have any idea about this problem?



By the way, I tried to boot the kernel with command “bootm a000:kernel@1 - 
a000:fdt@1”

And the log show as below, you can see that mmcblk0 device is missed, do anyone 
know the reason?



ALSA device list:

  No soundcards found.

VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6

Please append a correct "root=" boot option; here are the available partitions:

0100  262144 ram0  (driver?)

0101  262144 ram1  (driver?)

0102  262144 ram2  (driver?)

0103  262144 ram3  (driver?)

0104  262144 ram4  (driver?)

0105  262144 ram5  (driver?)

0106  262144 ram6  (driver?)

0107  262144 ram7  (driver?)

1f00  524288 mtdblock0  (driver?)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.30-rt34+ #2

Hardware name: Freescale LAYERSCAPE


Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
   Nanjing, 210012, China
MAIL : zhengrq.f...@cn.fujistu.com



=> setenv bootcmd "ext2load mmc 0 a000 kernel.itb && bootm a000"
=> setenv bootargs "root=/dev/mmcblk0p1 rw earlycon=uart8250,0x21c0500 
console=ttyS0,115200"
=> boot  
67991979 bytes read in 5829 ms (11.1 MiB/s)
## Loading kernel from FIT Image at a000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
 Description:  ARM32 Linux kernel
 Type: Kernel Image
 Compression:  uncompressed
 Data Start:   0xa0e0
 Data Size:4468048 Bytes = 4.3 MiB
 Architecture: ARM
 OS:   Linux
 Load Address: 0x80008000
 Entry Point:  0x80008000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at a000 ...
   Using 'config@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
 Description:  LS1046 Ramdisk
 Type: RAMDisk Image
 Compression:  uncompressed
 Data Start:   0xa0448e1c
 Data Size:63498311 Bytes = 60.6 MiB
 Architecture: ARM
 OS:   Linux
 Load Address: unavailable
 Entry Point:  unavailable
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at a000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
 Description:  Flattened Device Tree blob
 Type: Flat Device Tree
 Compression:  uncompressed
 Data Start:   0xa0442ee0
 Data Size:24245 Bytes = 23.7 KiB
 Architecture: ARM
   Verifying Hash Integrity ... OK
   Loading fdt from 0xa0442ee0 to 0x9000
   Booting using the fdt blob at 0x9000
   Loading Kernel Image ... OK
   Using Device Tree in place at 9000, end 90018eb4

Starting kernel ...

Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Linux version 4.1.30-rt34+ (zhengrq@okura) (gcc version 5.2.0 (GCC) ) #2 SMP 
Fri Mar 31 11:04:46 JST 2017
CPU: ARMv7 Processor [410fd082] revision 2 (ARMv7), cr=32c5383d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine model: LS1046A RDB Board
earlycon: Early serial console at MMIO 0x21c0500 (options '')
earlycon: earlycon_map: Couldn't map 0x21c0500
Malformed early option 'earlycon'
Reserved memory: initialized node bman-fbpr, compatible id fsl,bman-fbpr
Reserved memory: initialized node qman-fqd, compatible id fsl,qman-fqd
Reserved memory: initialized node qman-pfdr, compatible id fsl,qman-pfdr
cma: Reserved 16 MiB at 0x0009fb00
Forcing write-allocate cache policy for SMP
Memory policy: Data cache writealloc
PERCPU: Embedded 12 pages/cpu @dc7a s18688 r8192 d22272 u49152
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2093072
Kernel command line: root=/dev/mmcblk0p1 rw earlycon=uart8250,0x21c0500 
console=ttyS0,115200
PID

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

[Alexander Kanavin]

On 04/05/2017 10:58 AM, Romain Perier wrote:

ping



Is this available in newer upstream versions of logrotate? Should you 
send it there first?


Alex

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

Re: [OE-core] [PATCH v2] logrotate: Add systemd support

[Romain Perier]

ping


Le 24/03/2017 à 09:46, Romain Perier a écrit :
> Currently, this recipe only supports daily scheduling via a cron job.
> This commit adds support for systemd, including systemd service and
> systemd timer. When the corresponding distro feature is enabled the
> systemd variant will be used. The timer granularity and its accuracy
> are also configurable.
>
> Signed-off-by: Romain Perier 
> ---
>
> Changes in v2:
> - Make the systemd timer configurable (as this is distribution or target 
> specific)
>
>  .../logrotate/logrotate/logrotate.service  |  9 
>  .../logrotate/logrotate/logrotate.timer|  7 ++
>  meta/recipes-extended/logrotate/logrotate_3.9.1.bb | 27 
> --
>  3 files changed, 41 insertions(+), 2 deletions(-)
>  create mode 100644 
> meta/recipes-extended/logrotate/logrotate/logrotate.service
>  create mode 100644 meta/recipes-extended/logrotate/logrotate/logrotate.timer
>
> diff --git a/meta/recipes-extended/logrotate/logrotate/logrotate.service 
> b/meta/recipes-extended/logrotate/logrotate/logrotate.service
> new file mode 100644
> index 000..3edb8ef
> --- /dev/null
> +++ b/meta/recipes-extended/logrotate/logrotate/logrotate.service
> @@ -0,0 +1,9 @@
> +[Unit]
> +Description=Rotate log files
> +
> +[Service]
> +Type=oneshot
> +ExecStart=/usr/sbin/logrotate /etc/logrotate.conf
> +Nice=19
> +IOSchedulingClass=best-effort
> +IOSchedulingPriority=7
> diff --git a/meta/recipes-extended/logrotate/logrotate/logrotate.timer 
> b/meta/recipes-extended/logrotate/logrotate/logrotate.timer
> new file mode 100644
> index 000..c616b43
> --- /dev/null
> +++ b/meta/recipes-extended/logrotate/logrotate/logrotate.timer
> @@ -0,0 +1,7 @@
> +[Unit]
> +Description=Daily rotation of log files
> +
> +[Timer]
> +OnCalendar=@TIMER_BASIS@
> +AccuracySec=@TIMER_ACCURACY@
> +Persistent=true
> diff --git a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb 
> b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
> index 5f1a601..6953996 100644
> --- a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
> +++ b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
> @@ -14,6 +14,8 @@ SRC_URI = 
> "https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.g
> file://act-as-mv-when-rotate.patch \
> file://update-the-manual.patch \
> file://disable-check-different-filesystems.patch \
> +   ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 
> 'file://logrotate.service', '', d)} \
> +   ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 
> 'file://logrotate.timer', '', d)} \
>  "
>  
>  SRC_URI[md5sum] = "4492b145b6d542e4a2f41e77fa199ab0"
> @@ -47,6 +49,17 @@ EXTRA_OEMAKE = "\
>  # INSTALL=install and BASEDIR=/usr.
>  OS_NAME = "Linux"
>  
> +inherit systemd
> +
> +SYSTEMD_AUTO_ENABLE = "disable"
> +SYSTEMD_SERVICE_${PN} = "\
> +${PN}.service \
> +${PN}.timer \
> +"
> +
> +LOGROTATE_SYSTEMD_TIMER_BASIS ?= "daily"
> +LOGROTATE_SYSTEMD_TIMER_ACCURACY ?= "12h"
> +
>  do_compile_prepend() {
>  # Make sure the recompile is OK
>  rm -f ${B}/.depend
> @@ -55,9 +68,19 @@ do_compile_prepend() {
>  do_install(){
>  oe_runmake install DESTDIR=${D} PREFIX=${D} MANDIR=${mandir}
>  mkdir -p ${D}${sysconfdir}/logrotate.d
> -mkdir -p ${D}${sysconfdir}/cron.daily
>  mkdir -p ${D}${localstatedir}/lib
>  install -p -m 644 examples/logrotate-default 
> ${D}${sysconfdir}/logrotate.conf
> -install -p -m 755 examples/logrotate.cron 
> ${D}${sysconfdir}/cron.daily/logrotate
>  touch ${D}${localstatedir}/lib/logrotate.status
> +
> +# Install systemd unit files
> +if [ "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd', '', 
> d)}" = "systemd" ]; then
> +install -d ${D}/${systemd_system_unitdir}
> +install -m 0644 ${WORKDIR}/logrotate.service 
> ${D}/${systemd_system_unitdir}/logrotate.service
> +install -m 0644 ${WORKDIR}/logrotate.timer 
> ${D}/${systemd_system_unitdir}/logrotate.timer
> +sed -i -e 's,@TIMER_BASIS@,${LOGROTATE_SYSTEMD_TIMER_BASIS},g' 
> ${D}${systemd_system_unitdir}/logrotate.timer
> +sed -i -e 's,@TIMER_ACCURACY@,${LOGROTATE_SYSTEMD_TIMER_ACCURACY},g' 
> ${D}${systemd_system_unitdir}/logrotate.timer
> +else
> +mkdir -p ${D}${sysconfdir}/cron.daily
> +install -p -m 0755 examples/logrotate.cron 
> ${D}${sysconfdir}/cron.daily/logrotate
> +fi
>  }

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

Re: [OE-core] [PATCH v2 4/8] logrotate: replace fedorahosted.org SRC_URI with github.com source

[Choong, Yin Thong]

Thanks for the review. We will upstream the V3 patch once amended.

Thanks and Regards
Choong YinThong

-Original Message-
From: Alexander Kanavin [mailto:alexander.kana...@linux.intel.com] 
Sent: Tuesday, April 4, 2017 6:40 PM
To: openembedded-core@lists.openembedded.org; Choong, Yin Thong 

Subject: Re: [OE-core] [PATCH v2 4/8] logrotate: replace fedorahosted.org 
SRC_URI with github.com source

On 04/04/2017 12:29 PM, yin.thong.cho...@intel.com wrote:
> -SRC_URI = 
> "https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.g
> z \
> +S = "${WORKDIR}/${PN}-r3-9-1"
> +
> +UPSTREAM_CHECK_URI = "https://github.com/${PN}/${PN}/releases";
> +
> +SRC_URI = "https://github.com/${PN}/${PN}/archive/r3-9-1.tar.gz \

Why are we taking a github snapshot tarball (which is not standard parctice in 
oe-core)? Put a comment here that when updating logrotate to latest upstream, 
SRC_URI should point to a proper release tarball from 
https://github.com/logrotate/logrotate/releases and we have to take the 
snapshot for now because there is no such tarball available for 3.9.1.

Generally, don't be afraid to put comments next to your changes, the more the 
better! And especially when you are doing something unusual that is not 
self-explanatory like above.

Otherwise, I am happy with the patchset!

Alex

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

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

[Jussi Kukkonen]

On 23 January 2017 at 15:59, David Vincent  wrote:

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

This apparently breaks key generation with openssl-native because the file
doesn't exist.

I can fix it by adding one more complication to the recipe (will send a
patch) but I don't think the current solution is all that great: I've been
looking at this patch for a while now and still don't really understand why
it is needed and how these different packages interact. I'm sure it makes
sense when you look at the other recipe but ... isn't it a bad sign that
that context seems to be needed?

Jussi


> Signed-off-by: David Vincent 
> ---
>  meta/recipes-connectivity/openssl/openssl.inc | 13 -
>  1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-connectivity/openssl/openssl.inc
> b/meta/recipes-connectivity/openssl/openssl.inc
> index 5cca019e1d..696b564cdd 100644
> --- a/meta/recipes-connectivity/openssl/openssl.inc
> +++ b/meta/recipes-connectivity/openssl/openssl.inc
> @@ -201,7 +201,6 @@ do_install () {
>${D}${sysconfdir}/ssl/
> ln -sf ${sysconfdir}/ssl/certs ${D}${libdir}/ssl/certs
> ln -sf ${sysconfdir}/ssl/private ${D}${libdir}/ssl/private
> -   ln -sf ${sysconfdir}/ssl/openssl.cnf ${D}${libdir}/ssl/openssl.cnf
>  }
>
>  do_install_ptest () {
> @@ -245,4 +244,16 @@ do_install_append_class-native() {
> OPENSSL_ENGINES=${libdir}/ssl/engines
>  }
>
> +pkg_postinst_openssl-conf () {
> +#!/bin/sh
> +if [ -e $D${libdir}/ssl/openssl.cnf ]; then
> +   rm -f $D${libdir}/ssl/openssl.cnf
> +fi
> +
> +# If openssl-conf is installed before openssl, we must ensure that the
> symlink
> +# destination exists
> +mkdir -p $D${libdir}/ssl/
> +ln -s ${sysconfdir}/ssl/openssl.cnf $D${libdir}/ssl/openssl.cnf
> +}
> +
>  BBCLASSEXTEND = "native nativesdk"
> --
> 2.11.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] python-pycurl: create python3-pycurl recipe

[Dmitry Rozhkov]

The python-pycurl recipe can be used with python2 only even
though python3 is officially supported by upstream.

Create python3-pycurl recipe enabling the pycurl module for
python3.

Signed-off-by: Dmitry Rozhkov 
---
 meta/recipes-devtools/python/python-pycurl.inc | 31 +
 .../python/python-pycurl_7.21.5.bb | 32 +-
 .../python/python3-pycurl_7.21.5.bb|  5 
 3 files changed, 37 insertions(+), 31 deletions(-)
 create mode 100644 meta/recipes-devtools/python/python-pycurl.inc
 create mode 100644 meta/recipes-devtools/python/python3-pycurl_7.21.5.bb

diff --git a/meta/recipes-devtools/python/python-pycurl.inc 
b/meta/recipes-devtools/python/python-pycurl.inc
new file mode 100644
index 000..d26318b
--- /dev/null
+++ b/meta/recipes-devtools/python/python-pycurl.inc
@@ -0,0 +1,31 @@
+SUMMARY = "Python bindings for libcurl"
+HOMEPAGE = "http://pycurl.sourceforge.net/";
+SECTION = "devel/python"
+LICENSE = "LGPLv2.1+ | MIT"
+LIC_FILES_CHKSUM = 
"file://README.rst;beginline=166;endline=182;md5=a84a1caa65b89d4584b693d3680062fb
 \
+file://COPYING-LGPL;md5=3579a9fd0221d49a237aaa33492f988c \
+file://COPYING-MIT;md5=b7e434aeb228ed731c00bcf177e79b19"
+
+DEPENDS = "curl ${PYTHON_PN}"
+RDEPENDS_${PN} = "${PYTHON_PN}-core curl"
+SRCNAME = "pycurl"
+
+SRC_URI = "\
+  
http://${SRCNAME}.sourceforge.net/download/${SRCNAME}-${PV}.tar.gz;name=archive 
\
+  file://no-static-link.patch \
+"
+
+SRC_URI[archive.md5sum] = "bca7bf47320082588db544ced2ba8717"
+SRC_URI[archive.sha256sum] = 
"8a1e0eb55573388275a1d6c2534ca4cfca5d7fa772b99b505c08fa149b27aed0"
+S = "${WORKDIR}/${SRCNAME}-${PV}"
+
+BBCLASSEXTEND = "native"
+
+# Ensure the docstrings are generated as make clean will remove them
+do_compile_prepend() {
+   ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py 
docstrings
+}
+
+do_install_append() {
+   rm -rf ${D}${datadir}/share
+}
diff --git a/meta/recipes-devtools/python/python-pycurl_7.21.5.bb 
b/meta/recipes-devtools/python/python-pycurl_7.21.5.bb
index 7b41f6d..eb70cea 100644
--- a/meta/recipes-devtools/python/python-pycurl_7.21.5.bb
+++ b/meta/recipes-devtools/python/python-pycurl_7.21.5.bb
@@ -1,33 +1,3 @@
-SUMMARY = "Python bindings for libcurl"
-HOMEPAGE = "http://pycurl.sourceforge.net/";
-SECTION = "devel/python"
-LICENSE = "LGPLv2.1+ | MIT"
-LIC_FILES_CHKSUM = 
"file://README.rst;beginline=166;endline=182;md5=a84a1caa65b89d4584b693d3680062fb
 \
-file://COPYING-LGPL;md5=3579a9fd0221d49a237aaa33492f988c \
-file://COPYING-MIT;md5=b7e434aeb228ed731c00bcf177e79b19"
-
-DEPENDS = "curl python"
-RDEPENDS_${PN} = "python-core curl"
-SRCNAME = "pycurl"
-
-SRC_URI = "\
-  
http://${SRCNAME}.sourceforge.net/download/${SRCNAME}-${PV}.tar.gz;name=archive 
\
-  file://no-static-link.patch \
-"
-
-SRC_URI[archive.md5sum] = "bca7bf47320082588db544ced2ba8717"
-SRC_URI[archive.sha256sum] = 
"8a1e0eb55573388275a1d6c2534ca4cfca5d7fa772b99b505c08fa149b27aed0"
-S = "${WORKDIR}/${SRCNAME}-${PV}"
+require python-pycurl.inc
 
 inherit distutils
-
-BBCLASSEXTEND = "native"
-
-# Ensure the docstrings are generated as make clean will remove them
-do_compile_prepend() {
-   ${STAGING_BINDIR_NATIVE}/${PYTHON_PN}-native/${PYTHON_PN} setup.py 
docstrings
-}
-
-do_install_append() {
-   rm -rf ${D}${datadir}/share
-}
diff --git a/meta/recipes-devtools/python/python3-pycurl_7.21.5.bb 
b/meta/recipes-devtools/python/python3-pycurl_7.21.5.bb
new file mode 100644
index 000..5d11192
--- /dev/null
+++ b/meta/recipes-devtools/python/python3-pycurl_7.21.5.bb
@@ -0,0 +1,5 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycurl:"
+
+require python-pycurl.inc
+
+inherit distutils3
-- 
2.9.3

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