[OE-core] [PATCHv2 1/3] oeqa/utils/commands.py: Make a copy of variables in get_bb_vars

[mariano . lopez]

From: Mariano Lopez 

The function get_bb_vars will remove items for the list passed
as the function argument, this will leave the caller with an
empty list and the function never says it will consume the items.

This hasn't been found before because only get_bb_var uses this
function.

Signed-off-by: Mariano Lopez 
---
 meta/lib/oeqa/utils/commands.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/lib/oeqa/utils/commands.py b/meta/lib/oeqa/utils/commands.py
index 5cd0f74..e00c879 100644
--- a/meta/lib/oeqa/utils/commands.py
+++ b/meta/lib/oeqa/utils/commands.py
@@ -149,6 +149,7 @@ def get_bb_vars(variables=None, target=None, 
postconfig=None):
 """Get values of multiple bitbake variables"""
 bbenv = get_bb_env(target, postconfig=postconfig)
 
+variables = variables.copy()
 var_re = re.compile(r'^(export )?(?P\w+)="(?P.*)"$')
 unset_re = re.compile(r'^unset (?P\w+)$')
 lastline = None
-- 
2.7.3

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

[OE-core] [PATCHv2 3/3] oe-selftest: Add option to submit test result to a git repository.

[mariano . lopez]

From: Mariano Lopez 

This new option allows to commit the result to a git repository,
along with the results it will add a metadata file for information
of the current selftest run, such as: hostname, machine, distro,
distro version, host version, and layers.

This implementation will have a branch per different hostname,
testing branch, and machine.

To use this feature use:

oe-selftest  --repository 

[YOCTO #9954]

Signed-off-by: Mariano Lopez 
---
 scripts/oe-selftest | 102 
 1 file changed, 102 insertions(+)

diff --git a/scripts/oe-selftest b/scripts/oe-selftest
index deaa432..f4b861f 100755
--- a/scripts/oe-selftest
+++ b/scripts/oe-selftest
@@ -36,6 +36,7 @@ import re
 import fnmatch
 import collections
 import imp
+import git
 
 sys.path.insert(0, os.path.dirname(os.path.realpath(__file__)) + '/lib')
 import scriptpath
@@ -46,6 +47,7 @@ import argparse_oe
 import oeqa.selftest
 import oeqa.utils.ftools as ftools
 from oeqa.utils.commands import runCmd, get_bb_var, get_test_layer
+from oeqa.utils.metadata import metadata_from_bb, write_metadata_file
 from oeqa.selftest.base import oeSelfTest, get_available_machines
 
 try:
@@ -106,6 +108,8 @@ def get_args_parser():
help='List all tags that have been set to test cases.')
 parser.add_argument('--machine', required=False, dest='machine', 
choices=['random', 'all'], default=None,
 help='Run tests on different machines (random/all).')
+parser.add_argument('--repository', required=False, dest='repository', 
default='', action='store',
+help='Submit test results to a repository')
 return parser
 
 
@@ -572,6 +576,75 @@ def main():
 
 log.info("Finished")
 
+if args.repository:
+# Commit tests results to repository
+metadata = metadata_from_bb()
+git_dir = os.path.join(os.getcwd(), 'selftest')
+if not os.path.isdir(git_dir):
+os.mkdir(git_dir)
+
+log.debug('Checking for git repository in %s' % git_dir)
+try:
+repo = git.Repo(git_dir)
+except git.exc.InvalidGitRepositoryError:
+log.debug("Couldn't find git repository %s; "
+ "cloning from %s" % (git_dir, args.repository))
+repo = git.Repo.clone_from(args.repository, git_dir)
+
+r_branches = repo.git.branch(r=True)
+r_branches = set(r_branches.replace('origin/', '').split())
+l_branches = {str(branch) for branch in repo.branches}
+branch = '%s/%s/%s' % (metadata['hostname'],
+   metadata['layers']['meta']['branch'],
+   metadata['machine'])
+
+if branch in l_branches:
+log.debug('Found branch in local repository, checking out')
+repo.git.checkout(branch)
+elif branch in r_branches:
+log.debug('Found branch in remote repository, checking'
+  ' out and pulling')
+repo.git.checkout(branch)
+repo.git.pull()
+else:
+log.debug('New branch %s' % branch)
+repo.git.checkout('master')
+repo.git.checkout(b=branch)
+
+cleanResultsDir(repo)
+xml_dir = os.path.join(os.getcwd(), log_prefix)
+copyResultFiles(xml_dir, git_dir, repo)
+metadata_file = os.path.join(git_dir, 'metadata.xml')
+write_metadata_file(metadata_file, metadata)
+repo.index.add([metadata_file])
+repo.index.write()
+
+# Get information for commit message
+layer_info = ''
+for layer, values in metadata['layers'].items():
+layer_info = '%s%-17s = %s:%s\n' % (layer_info, layer,
+  values['branch'], values['revision'])
+msg = 'Selftest for build %s of %s %s for machine %s on %s\n\n%s' 
% (
+   log_prefix[12:], metadata['distro'], 
metadata['distro_version'],
+   metadata['machine'], metadata['hostname'], layer_info)
+
+log.debug('Commiting results to local repository')
+repo.index.commit(msg)
+if not repo.is_dirty():
+try:
+if branch in r_branches:
+log.debug('Pushing changes to remote repository')
+repo.git.push()
+else:
+log.debug('Pushing changes to remote repository '
+  'creating new branch')
+repo.git.push('-u', 'origin', branch)
+except GitCommandError:
+log.error('Falied to push to remote repository')
+

Re: [OE-core] [Master][PATCH] libtiff: Update to 4.0.7

[Alexander Kanavin]

On 11/23/2016 05:32 PM, akuster808 wrote:

The never made into patchwork. is there a bug there ? is there an issue
on how I submitted?

- armin


On 11/21/2016 09:28 PM, Armin Kuster wrote:


I haven't actually seen the email with the patch at all on the mailing 
list, just your response to it. Can you resend?


Alex

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

[OE-core] [PATCHv2 2/3] oeqa/utils/metadata.py: Add metadata library

[mariano . lopez]

From: Mariano Lopez 

Adds functions to get metadata from the host running the tests.

[YOCTO #9954]

Signed-off-by: Mariano Lopez 
---
 meta/lib/oeqa/utils/metadata.py | 83 +
 1 file changed, 83 insertions(+)
 create mode 100644 meta/lib/oeqa/utils/metadata.py

diff --git a/meta/lib/oeqa/utils/metadata.py b/meta/lib/oeqa/utils/metadata.py
new file mode 100644
index 000..ecbe763
--- /dev/null
+++ b/meta/lib/oeqa/utils/metadata.py
@@ -0,0 +1,83 @@
+# Copyright (C) 2016 Intel Corporation
+#
+# Released under the MIT license (see COPYING.MIT)
+#
+# Functions to get metadata from the testing host used
+# for analytics of test results.
+
+from git import Repo, InvalidGitRepositoryError, NoSuchPathError
+from collections import OrderedDict
+from collections.abc import MutableMapping
+from xml.dom.minidom import parseString
+from xml.etree.ElementTree import Element, tostring
+
+from oe.lsb import distro_identifier
+from oeqa.utils.commands import runCmd, get_bb_var, get_bb_vars
+
+metadata_vars = ['MACHINE', 'DISTRO', 'DISTRO_VERSION']
+
+def metadata_from_bb():
+""" Returns test's metadata as OrderedDict.
+
+Data will be gathered using bitbake -e thanks to get_bb_vars.
+"""
+
+info_dict = OrderedDict()
+hostname = runCmd('hostname')
+info_dict['hostname'] = hostname.output
+data_dict = get_bb_vars(metadata_vars)
+for var in metadata_vars:
+info_dict[var.lower()] = data_dict[var]
+host_distro= distro_identifier()
+host_distro, _, host_distro_release = host_distro.partition('-')
+info_dict['host_distro'] = host_distro
+info_dict['host_distro_release'] = host_distro_release
+info_dict['layers'] = get_layers(get_bb_var('BBLAYERS'))
+return info_dict
+
+def metadata_from_data_store(d):
+""" Returns test's metadata as OrderedDict.
+
+Data will be collected from the provided data store.
+"""
+# TODO: Getting metadata from the data store would
+# be useful when running within bitbake.
+pass
+
+def get_layers(layers):
+""" Returns layer name, branch, and revision as OrderedDict. """
+
+layer_dict = OrderedDict()
+for layer in layers.split():
+layer_name = os.path.basename(layer)
+layer_dict[layer_name] = OrderedDict()
+try:
+repo = Repo(layer, search_parent_directories=True)
+revision, branch = repo.head.object.name_rev.split()
+layer_dict[layer_name]['branch'] = branch
+layer_dict[layer_name]['revision'] = revision
+except (InvalidGitRepositoryError, NoSuchPathError):
+layer_dict[layer_name]['branch'] = 'unknown'
+layer_dict[layer_name]['revision'] = 'unknown'
+return layer_dict
+
+def write_metadata_file(file_path, metadata):
+""" Writes metadata to a XML file in directory. """
+
+xml = dict_to_XML('metadata', metadata)
+xml_doc = parseString(tostring(xml).decode('UTF-8'))
+with open(file_path, 'w') as f:
+f.write(xml_doc.toprettyxml())
+
+def dict_to_XML(tag, dictionary):
+""" Return XML element converting dicts recursively. """
+
+elem = Element(tag)
+for key, val in dictionary.items():
+if isinstance(val, MutableMapping):
+child = (dict_to_XML(key, val))
+else:
+child = Element(key)
+child.text = str(val)
+elem.append(child)
+return elem
-- 
2.7.3

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

[OE-core] [PATCHv2 0/3] Add communication mechanism for sending test results

[mariano . lopez]

From: Mariano Lopez 

These changes add a mechanism for sending test result to a remote
repository for later consumption of the data from other clients.

These patches were tested in our local autobuilders.

Changes in v2:

- Give more priority to local branches, because it would be difficult
  to match a branch name (because it includes the hostname).
- Instead of throwing an execption when a push fails, log the error
  and return 1 to the caller.
- Instead to call 3 times bitbake -e, just call it one time to get
  needed variables.

The following changes since commit 9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a:

  bitbake: ast: remove BBVERSIONS support (2016-11-30 15:48:10 +)

are available in the git repository at:

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

Mariano Lopez (3):
  oeqa/utils/commands.py: Make a copy of variables in get_bb_vars
  oeqa/utils/metadata.py: Add metadata library
  oe-selftest: Add option to submit test result to a git repository.

 meta/lib/oeqa/utils/commands.py |   1 +
 meta/lib/oeqa/utils/metadata.py |  83 
 scripts/oe-selftest | 102 
 3 files changed, 186 insertions(+)
 create mode 100644 meta/lib/oeqa/utils/metadata.py

-- 
2.7.3

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

Re: [OE-core] [PATCH] buildhistory-diff: report directory renames

[Ed Bartosh]

On Tue, Nov 29, 2016 at 03:51:21PM +0200, Alexander Kanavin wrote:
> On 11/28/2016 07:28 PM, Ed Bartosh wrote:
> >The script detects directory renaming if two different
> >directories with the same set of files are added and removed.
> 
> What happens if the sets of files are slightly different? (e.g. a
> couple of files are added or removed). Can we get some wiggle space
> here?
> 
In this case script will behave like it does currently. It will show all
added and removed files.

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

[OE-core] Fwd: [PATCH 00/27] Morty-next pull request cover letter only

[akuster808]

resending. looks like this did not hit the list. I think its do to my
corporate email not registered.

- armin

 Forwarded Message 
Subject: [PATCH 00/27] Morty-next pull request cover letter only
Date: Tue, 29 Nov 2016 09:08:18 -0800
From: Armin Kuster 
To: akuster...@gmail.com, openembedded-core@lists.openembedded.org

Please consider these changes for Morty. Built clean in AB.

The following changes since commit 73454473d7c286c41ee697f74052fed03c79f9f5:

  bitbake: toaster: settings set ALLOWED_HOSTS to * in debug mode
(2016-11-16 11:38:51 +)

are available in the git repository at:

  http://git.yoctoproject.org/git/poky-contrib akuster/morty-next

http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akuster/morty-next

André Draszik (2):
  cve-check.bbclass: CVE-2014-2524 / readline v5.2
  openssl: fix bashism in c_rehash shell script

Armin Kuster (2):
  tzcode: update to 2016i
  tzdata: update to 2016i

Daniel Díaz (1):
  weston: Add no-input-device patch to 1.11.0.

Ed Bartosh (1):
  systemd-bootdisk.wks: use PARTUUID

Kai Kang (3):
  openssh: fix CVE-2016-8858
  qemu: fix CVE-2016-7909
  qemu: update run-ptest script

Khem Raj (2):
  libbsd: Fix build with musl
  cmake.bbclass: Set CXXFLAGS and CFLAGS

Koen Kooi (1):
  libbsd 0.8.3: BBCLASSEXTEND to native and nativesdk

Li Zhou (1):
  db: disable the ARM assembler mutex code

Maciej Borzecki (3):
  wic: make sure that partition size is always an integer in internal
processing
  wic: check that filesystem is specified for a rootfs partition
  wic: fix function comment typos

Robert Yang (1):
  qemuarm64.conf: make runqemu's graphics work

Ross Burton (5):
  Revert "libwnck3: remove the recipe"
  Revert "epiphany: remove unnecessary libwnck3 dependency"
  lib/oe/qa: handle binaries with segments outside the first 4kb
  systemtap: remove explicit msgfmt check
  systemtap: fix native linking on recent Ubuntu

T.O. Radzy Radzykewycz (1):
  OpenSSL: CVE-2004-2761 replace MD5 hash algorithm

Yi Zhao (3):
  openssl: Security fix CVE-2016-7055
  nfs-utils: fix protocol minor version fall-back
  tiff: Security fix CVE-2016-3632

Zhixiong Chi (1):
  tiff: Security fix CVE-2016-3658

 meta/classes/cmake.bbclass |   2 +
 meta/classes/cve-check.bbclass |   2 +-
 meta/conf/machine/qemuarm64.conf   |   2 +-
 meta/lib/oe/qa.py  |  82 ++---
 .../fix-protocol-minor-version-fall-back.patch |  55 
 .../nfs-utils/nfs-utils_1.3.3.bb   |   1 +
 .../openssh/openssh/fix-CVE-2016-8858.patch|  39 +++
 meta/recipes-connectivity/openssh/openssh_7.3p1.bb |   1 +
 .../openssl/openssl/CVE-2016-7055.patch|  43 +++
 .../Use-SHA256-not-MD5-as-default-digest.patch |  69 
 .../openssl/openssl/openssl-c_rehash.sh|   2 +-
 .../recipes-connectivity/openssl/openssl_1.0.2j.bb |   1 +
 .../qemu/qemu/0004-fix-CVE-2016-7909.patch |  42 +++
 meta/recipes-devtools/qemu/qemu/run-ptest  |   8 +-
 meta/recipes-devtools/qemu/qemu_2.7.0.bb   |   1 +
 ...code-native_2016h.bb => tzcode-native_2016i.bb} |   8 +-
 .../tzdata/{tzdata_2016h.bb => tzdata_2016i.bb}|   4 +-
 meta/recipes-gnome/epiphany/epiphany_3.20.3.bb |   4 +-
 meta/recipes-gnome/libwnck/libwnck3_3.20.1.bb  |  19 ++
 ...on-1.11-config-option-for-no-input-device.patch | 123 +++
 meta/recipes-graphics/wayland/weston_1.11.0.bb |   1 +
 .../systemtap/systemtap/fix-monitor-linking.patch  |  41 +++
 .../systemtap/systemtap/no-msgfmt-check.patch  |  15 +
 meta/recipes-kernel/systemtap/systemtap_git.inc|   2 +
 .../libtiff/files/CVE-2016-3632.patch  |  34 ++
 .../libtiff/files/CVE-2016-3658.patch  | 111 +++
 meta/recipes-multimedia/libtiff/tiff_4.0.6.bb  |   2 +
 meta/recipes-support/db/db_6.0.35.bb   |   9 -
 ...001-Replace-__BEGIN_DECLS-and-__END_DECLS.patch | 363
+
 .../libbsd/libbsd/0002-Remove-funopen.patch|  55 
 ...3-Fix-build-breaks-due-to-missing-a.out.h.patch | 130 
 meta/recipes-support/libbsd/libbsd_0.8.3.bb|   7 +
 scripts/lib/wic/canned-wks/systemd-bootdisk.wks|   2 +-
 scripts/lib/wic/partition.py   |  16 +-
 scripts/lib/wic/plugins/source/bootimg-efi.py  |   2 +-
 scripts/lib/wic/plugins/source/rawcopy.py  |   4 +-
 scripts/lib/wic/utils/partitionedfs.py |   4 +-
 37 files changed, 1234 insertions(+), 72 deletions(-)
 create mode 100644
meta/recipes-connectivity/nfs-utils/nfs-utils/fix-protocol-minor-version-fall-back.patch
 create mode 100644
meta/recipes-connectivity/openssh/openssh/fix-CVE-2016-8858.patch
 create mode 100644
meta/recipes-connectivity/openssl/openssl/CVE-2016-7055.patch
 create mode 100644
meta/recipes-connectivity/openssl/openssl/Use-SHA256-not-MD5-as-default-digest.patch
 create mode 100644

Re: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232

[Khem Raj]

On Thu, Dec 1, 2016 at 1:28 AM, Peter Kjellerstedt
 wrote:
>> -Original Message-
>> From: openembedded-core-boun...@lists.openembedded.org
>> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
>> Khem Raj
>> Sent: den 28 november 2016 22:26
>> To: openembedded-core@lists.openembedded.org
>> Subject: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232
>>
>> * Drop support for rcS.d SysV init scripts.
>>   These are prone to cause dependency loops, and almost all packages
>> with
>>   rcS scripts now ship a native systemd service.
>>
>> * Drop mount propagation patch, it only happens with libseccomp, OE
>> doesnt
>>   enable it
>>
>> * kdbus option has disappeared from configure
>>
>> * Ignore dev-so for PN now since systemd introduced private .so see
>>   https://github.com/systemd/systemd/issues/3810
>
> Rather than adding:
>
> INSANE_SKIP_${PN} += "dev-so"
>
> would it not be more appropriate to add
> ${systemd_unitdir}/libsystemd-shared.so to FILES_${PN}-dev, i.e.:
>
> -FILES_${PN}-dev += "${base_libdir}/security/*.la 
> ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd"
> +FILES_${PN}-dev += "${base_libdir}/security/*.la 
> ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd 
> ${systemd_unitdir}/libsystemd-shared.so"
>
> The binaries are linked with libsystemd-shared-232.so which ends up in
> ${PN} as usual.

As mentioned this is not a typical .so which is a symlink and can be
shoved into -dev package
if we do that, then we have to include -dev package into every image
containing systemd.

>
>> * Add libnss* to PACKAGES_DYNAMIC for libnss-resolve to work correctly
>>
>> * Forward port systemd-boot patches to systemd-232
>>
>> Signed-off-by: Khem Raj 
>
> //Peter
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] libc-package.bbclass: split binary localedata even more if asked to

[Khem Raj]

On Thu, Dec 1, 2016 at 4:33 AM, Andreas Oberritter  
wrote:
> On 01.12.2016 05:02, Khem Raj wrote:
>>
>>> On Nov 30, 2016, at 3:50 PM, Andreas Oberritter  
>>> wrote:
>>>
>>> If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
>>> glibc-binary-localedata-XX-YY to be a meta package depending on
>>> glibc-binary-localedata-XX-YY-lc-address and so on. This enables
>>> saving quite some space if someone doesn't need LC_COLLATE for
>>> example.
>>>
>>> Some regex code was removed from output_locale_binary_rdepends,
>>> because legitimize_package_name already converts to lowercase.
>>>
>>
>> This looks ok. May be add some documentation around
>> GLIBC_SPLIT_LC_PACKAGES in extended local.conf sample.
>
> OK, will send a v2.
>
>> I am worried about dependency changes, may be comparing old and new
>> would help.
>
> The generated meta packages make sure that dependencies stay intact. I
> didn't observe any deviation in my test builds, with or without setting
> GLIBC_SPLIT_LC_PACKAGES to 1.

Thats comforting. did you also try a online package upgrade ?

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

[OE-core] [PATCH] AUH: status email indicates the URL of the log folder

[Edwin Plauchu]

Upgrade status email should indicate the URL of the log folder instead of the 
tar URL

[YOCTO #10670]

Signed-off-by: Edwin Plauchu 
---
 upgradehelper.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index 239fd88..3954e1f 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -616,7 +616,7 @@ class Updater(object):
 publish_work_url = ''
 
 statistics_summary = self.statistics.get_summary(
-publish_work_url, os.path.basename(work_tarball))
+publish_work_url, self.uh_work_dir)
 
 statistics_file = os.path.join(self.uh_work_dir,
 "statistics_summary")
-- 
2.9.3

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

[OE-core] [PATCH] perl-native: Remove usage of -fstack-protector=strong

[Aníbal Limón]

Some distributions (like opensuse421) supported by the project
comes with older gcc releases, -fstack-protector=strong is supported
by GCC>=4.9.

This causes a build failure when install perl-native from a sstate that
comes from a machine supporting -fstack-protector=strong [1].

So disable usage of this flag in perl-native builds, this patch could
be removed when all supported distros comes with GCC>=4.9.

[YOCTO #10338]

[1] http://errors.yoctoproject.org/Errors/Details/109589/

Signed-off-by: Aníbal Limón 
---
 meta/recipes-devtools/perl/perl-native_5.24.0.bb   |   1 +
 ...emove-fstack-protector-strong-for-native-.patch | 103 +
 2 files changed, 104 insertions(+)
 create mode 100644 
meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch

diff --git a/meta/recipes-devtools/perl/perl-native_5.24.0.bb 
b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
index af2ad7b..b1f0179 100644
--- a/meta/recipes-devtools/perl/perl-native_5.24.0.bb
+++ b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
@@ -11,6 +11,7 @@ SRC_URI += "\
file://debian/errno_ver.diff \
file://dynaloaderhack.patch \
file://perl-PathTools-don-t-filter-out-blib-from-INC.patch \
+   
file://0001-Configure-Remove-fstack-protector-strong-for-native-.patch \
   "
 
 SRC_URI[md5sum] = "59456ae4bd4b06cb6e57cb19a3b2d349"
diff --git 
a/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
 
b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
new file mode 100644
index 000..7391ac5
--- /dev/null
+++ 
b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
@@ -0,0 +1,103 @@
+Some distributions (like opensuse421) supported by the project
+comes with older gcc releases, -fstack-protector=strong is supported
+by GCC>=4.9.
+
+This causes a build failure when install perl-native from a sstate that
+comes from a machine supporting -fstack-protector=strong [1].
+
+So disable usage of this flag in perl-native builds, this patch could
+be removed when all supported distros comes with GCC>=4.9.
+
+[YOCTO #10338]
+
+Upstream-status: Inappropriate [configuration]
+
+[1] http://errors.yoctoproject.org/Errors/Details/109589/
+
+Signed-off-by: Aníbal Limón 
+---
+ Configure | 54 --
+ 1 file changed, 54 deletions(-)
+
+diff --git a/Configure b/Configure
+index efbdcfd..d5bd98c 100755
+--- a/Configure
 b/Configure
+@@ -5468,30 +5468,6 @@ default|recommended)
+   eval $checkccflag
+   ;;
+   esac
+-
+-  # on x86_64 (at least) we require an extra library (libssp) in the
+-  # link command line. This library is not named, so I infer that it is
+-  # an implementation detail that may change. Hence the safest approach
+-  # is to add the flag to the flags passed to the compiler at link time,
+-  # as that way the compiler can do the right implementation dependant
+-  # thing. (NWC)
+-  case "$osname" in
+-  amigaos) ;; # -fstack-protector builds but doesn't work
+-  *)  case "$gccversion" in
+-  ?*) set stack-protector-strong -fstack-protector-strong
+-  eval $checkccflag
+-  case "$dflt" in
+-  *-fstack-protector-strong*) ;; # It got added.
+-  *) # Try the plain/older -fstack-protector.
+- set stack-protector -fstack-protector
+- eval $checkccflag
+- ;;
+-  esac
+-  ;;
+-  esac
+-  ;;
+-  esac
+-  ;;
+ esac
+ 
+ case "$mips_type" in
+@@ -5634,21 +5610,6 @@ case "$ldflags" in
+   ;;
+ *) dflt="$ldflags";;
+ esac
+-# See note above about -fstack-protector
+-case "$ccflags" in
+-*-fstack-protector-strong*)
+-  case "$dflt" in
+-  *-fstack-protector-strong*) ;; # Don't add it again
+-  *) dflt="$dflt -fstack-protector-strong" ;;
+-  esac
+-  ;;
+-*-fstack-protector*)
+-  case "$dflt" in
+-  *-fstack-protector*) ;; # Don't add it again
+-  *) dflt="$dflt -fstack-protector" ;;
+-  esac
+-  ;;
+-esac
+ 
+ : Try to guess additional flags to pick up local libraries.
+ for thislibdir in $libpth; do
+@@ -8571,21 +8532,6 @@ EOM
+   ''|' ') dflt='none' ;;
+   esac
+ 
+-  case "$ldflags" in
+-  *-fstack-protector-strong*)
+-  case "$dflt" in
+-  *-fstack-protector-strong*) ;; # Don't add it again
+-  *) dflt="$dflt -fstack-protector-strong" ;;
+-  esac
+-  ;;
+-  *-fstack-protector*)
+-  case "$dflt" in
+-  *-fstack-protector*) ;; # Don't add it again
+- 

Re: [OE-core] [PATCH] AUH: status email indicates the URL of the log folder

[Leonardo Sandoval]

This is not the correct list. AUH goes to the Yocto list, I believe.


On 12/01/2016 10:14 AM, Edwin Plauchu wrote:

Upgrade status email should indicate the URL of the log folder instead of the 
tar URL

[YOCTO #10670]

Signed-off-by: Edwin Plauchu 
---
  upgradehelper.py | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index 239fd88..3954e1f 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -616,7 +616,7 @@ class Updater(object):
  publish_work_url = ''
  
  statistics_summary = self.statistics.get_summary(

-publish_work_url, os.path.basename(work_tarball))
+publish_work_url, self.uh_work_dir)
  
  statistics_file = os.path.join(self.uh_work_dir,

  "statistics_summary")


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

Re: [OE-core] [PATCH] AUH: status email indicates the URL of the log folder

[Plauchu Edwin]

Thanks for clarification


On 01/12/16 10:22, Leonardo Sandoval wrote:

This is not the correct list. AUH goes to the Yocto list, I believe.


On 12/01/2016 10:14 AM, Edwin Plauchu wrote:
Upgrade status email should indicate the URL of the log folder 
instead of the tar URL


[YOCTO #10670]

Signed-off-by: Edwin Plauchu 
---
  upgradehelper.py | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index 239fd88..3954e1f 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -616,7 +616,7 @@ class Updater(object):
  publish_work_url = ''
statistics_summary = self.statistics.get_summary(
-publish_work_url, os.path.basename(work_tarball))
+publish_work_url, self.uh_work_dir)
statistics_file = os.path.join(self.uh_work_dir,
  "statistics_summary")




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

[OE-core] [PATCH 1/3] python3-native: Add python3-modules to RPROVIDES list

[linus . svensson]

From: Linus Svensson 

Signed-off-by: Linus Svensson 
---
 meta/recipes-devtools/python/python3-native_3.5.2.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/python/python3-native_3.5.2.bb 
b/meta/recipes-devtools/python/python3-native_3.5.2.bb
index 08802cd..7ac3942 100644
--- a/meta/recipes-devtools/python/python3-native_3.5.2.bb
+++ b/meta/recipes-devtools/python/python3-native_3.5.2.bb
@@ -54,6 +54,7 @@ RPROVIDES += " \
 python3-json-native \
 python3-lang-native \
 python3-misc-native \
+python3-modules-native \
 python3-netclient-native \
 python3-netserver-native \
 python3-numbers-native \
-- 
2.1.4

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

[OE-core] [PATCH 2/3] meson: Add recipe for the meson build system

[linus . svensson]

From: Linus Svensson 

Meson is a build system designed to be fast and as user firendly as
possible. Find out more about meson at mesonbuild.com.

This patch is based on a prototype patch by
Ross Burton .

Signed-off-by: Linus Svensson 
---
 meta/recipes-devtools/meson/meson_0.36.0.bb | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 meta/recipes-devtools/meson/meson_0.36.0.bb

diff --git a/meta/recipes-devtools/meson/meson_0.36.0.bb 
b/meta/recipes-devtools/meson/meson_0.36.0.bb
new file mode 100644
index 000..1ec7e3e
--- /dev/null
+++ b/meta/recipes-devtools/meson/meson_0.36.0.bb
@@ -0,0 +1,15 @@
+HOMEPAGE = "http://mesonbuild.com;
+SUMMARY = "A high performance build system"
+
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://COPYING;md5=3b83ef96387f14655fc854ddc3c6bd57"
+
+SRC_URI = 
"https://github.com/mesonbuild/meson/releases/download/${PV}/${BP}.tar.gz;
+SRC_URI[md5sum] = "dfdd190c5f10a67bb40e6cf93944dd43"
+SRC_URI[sha256sum] = 
"dc087ec40dacb5e256e6ee6467f2d004faf4ef284d3c1ce5e89faa1e16540950"
+
+inherit setuptools3
+
+RDEPENDS_${PN} = "ninja python3-core python3-modules"
+
+BBCLASSEXTEND = "native"
-- 
2.1.4

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

[OE-core] [PATCH 3/3] meson.bbclass: Add meson.bbclass

[linus . svensson]

From: Linus Svensson 

Add a class for packages that uses the meson build system.

Meson uses a cross-file that contain needed tools and information about
the host and target system. Such a file will be created in {WORKDIR}.

Meson only allows installation directories to be specified as relative
to prefix, except for sysconfdir, which can be absolute.

This patch is based on a prototype patch by
Ross Burton .

Signed-off-by: Linus Svensson 
---
 meta/classes/meson.bbclass | 86 ++
 1 file changed, 86 insertions(+)
 create mode 100644 meta/classes/meson.bbclass

diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
new file mode 100644
index 000..5a04134
--- /dev/null
+++ b/meta/classes/meson.bbclass
@@ -0,0 +1,86 @@
+inherit python3native
+
+DEPENDS_append = " meson-native ninja-native"
+
+# As Meson enforces out-of-tree builds we can just use cleandirs
+B = "${WORKDIR}/build"
+do_configure[cleandirs] = "${B}"
+
+# Where the meson.build build configuration is
+MESON_SOURCEPATH = "${S}"
+
+# These variables in the environment override the *native* tools not the cross,
+# so they need to be unexported.
+CC[unexport] = "1"
+
+def noprefix(var, d):
+return d.getVar(var, True).replace(d.getVar('prefix', True) + '/', '', 1)
+
+MESONOPTS = " --prefix ${prefix} \
+  --bindir ${@noprefix('bindir', d)} \
+  --datadir ${@noprefix('datadir', d)} \
+  --libdir ${@noprefix('libdir', d)} \
+  --libexecdir ${@noprefix('libexecdir', d)} \
+  --includedir ${@noprefix('includedir', d)} \
+  --mandir ${@noprefix('mandir', d)} \
+  --localedir ${@noprefix('localedir', d)} \
+  --sysconfdir ${sysconfdir}"
+
+MESON_C_ARGS = "${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}"
+
+MESON_HOST_ENDIAN = "${@bb.utils.contains('SITEINFO_ENDIANNESS', 'be', 'big', 
'little', d)}"
+MESON_TARGET_ENDIAN = "${@bb.utils.contains('TUNE_FEATURES', 'bigendian', 
'big', 'little', d)}"
+
+EXTRA_OEMESON += "${PACKAGECONFIG_CONFARGS}"
+
+def meson_array(var, d):
+return "', '".join(d.getVar(var, True).split()).join(("'", "'"))
+
+addtask write_config before do_configure
+do_write_config[vardeps] += "MESON_C_ARGS TOOLCHAIN_OPTIONS"
+do_write_config() {
+# This needs to be Py to split the args into single-element lists
+cat >${WORKDIR}/meson.cross 

Re: [OE-core] [PATCHv2 3/3] oe-selftest: Add option to submit test result to a git repository.

[Mariano Lopez]

On Thursday, December 01, 2016 10:52:40 AM Benjamin Esquivel wrote:
> Hi Mariano
> 
> On Thu, 2016-12-01 at 09:37 -0600, mariano.lo...@linux.intel.com wrote:
> > From: Mariano Lopez 
> > 
> > This new option allows to commit the result to a git repository,
> > along with the results it will add a metadata file for information
> > of the current selftest run, such as: hostname, machine, distro,
> > distro version, host version, and layers.
> > 
> > This implementation will have a branch per different hostname,
> > testing branch, and machine.
> > 
> > To use this feature use:
> > 
> > oe-selftest  --repository 
> > 
> > [YOCTO #9954]

> I think this version is okay :) have you tested it in an Autobuilder
> task? 

Indeed, that is why it took me a bit longer to submit the patch. I
know this won't blow up current master.  But Ihaven't used the
option yet, we would need a remote repo and a new autobuilder
buildset.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/2] bash: use update-alternatives for the bash binary

[Burton, Ross]

On 30 November 2016 at 18:50, Andreas Oberritter 
wrote:

> Busybox may offer a bash applet. If enabled, the alternatives mechanism
>

Wait, what?  busybox can ship a /bin/bash that isn't bash?  That's
*hideous*!

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

Re: [OE-core] [oe] [meta-oe][PATCH] libva: Import from meta-intel and update to 1.7.3

[Khem Raj]

On Thu, Dec 1, 2016 at 9:19 AM, Burton, Ross  wrote:
> On 1 December 2016 at 03:42, Khem Raj  wrote:
>
>> >> If libva goes in, can we get libva-intel-driver in as well? Those go
>> >> hand-in-glove currently.
>> >>
>> >
>> > Khem, does the AMD BSP use that?  I'd have thought that bit was actually
>> > meta-intel specific.
>>
>> its intel BSPs specific
>
>
> So I'd endorse libva for oe-core, and the intel-driver remains in
> meta-intel.

I am fine with proposal. This is time for someone to raise objections.

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

Re: [OE-core] [PATCH] libc-package.bbclass: split binary localedata even more if asked to

[Andreas Oberritter]

On 01.12.2016 17:51, Khem Raj wrote:
> On Thu, Dec 1, 2016 at 4:33 AM, Andreas Oberritter  
> wrote:
>> On 01.12.2016 05:02, Khem Raj wrote:
>>>
 On Nov 30, 2016, at 3:50 PM, Andreas Oberritter  
 wrote:

 If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
 glibc-binary-localedata-XX-YY to be a meta package depending on
 glibc-binary-localedata-XX-YY-lc-address and so on. This enables
 saving quite some space if someone doesn't need LC_COLLATE for
 example.

 Some regex code was removed from output_locale_binary_rdepends,
 because legitimize_package_name already converts to lowercase.

>>>
>>> This looks ok. May be add some documentation around
>>> GLIBC_SPLIT_LC_PACKAGES in extended local.conf sample.
>>
>> OK, will send a v2.
>>
>>> I am worried about dependency changes, may be comparing old and new
>>> would help.
>>
>> The generated meta packages make sure that dependencies stay intact. I
>> didn't observe any deviation in my test builds, with or without setting
>> GLIBC_SPLIT_LC_PACKAGES to 1.
> 
> Thats comforting. did you also try a online package upgrade ?

Yes, but you can't switch existing package feeds from one setting to
another with deb, because of file conflicts (unless you run apt-get -f
install after upgrading). This would need additional RREPLACES,
RCONFLICTS (and RBREAKS?) statements, which IMHO are impossible to
automate. I'm not sure about other package managers. But it's a very
common problem when moving files from one package to another.

Regards,
Andreas

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

Re: [OE-core] [PATCH 1/2] bash: use update-alternatives for the bash binary

[Andreas Oberritter]

On 01.12.2016 18:41, Burton, Ross wrote:
> 
> On 30 November 2016 at 18:50, Andreas Oberritter  > wrote:
> 
> Busybox may offer a bash applet. If enabled, the alternatives mechanism
> 
> 
> Wait, what?  busybox can ship a /bin/bash that isn't bash?  That's
> *hideous*!

That's what busybox is all about, isn't it? Shipping things that aren't
the real thing with varying levels of compatibility (think sed, awk,
grep for other tools in busybox that use some kind of interpreted
language). Busybox' ash even supports some bash extensions.

FWIW, using /bin/bash as a login shell with busybox was the easiest way
to get bash-completions working with bash installed in a normal rootfs
(it doesn't work fully in POSIX mode) and get working logins in an
initramfs image at the same time, where bash isn't installed.
/etc/passwd is shared between both images.

Regards,
Andreas

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

Re: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232

[Burton, Ross]

On 28 November 2016 at 21:26, Khem Raj  wrote:

> -PV = "230+git${SRCPV}"
>

packages/corei7-64-intel-common-poky-linux/systemd-boot/systemd-boot-dev:
PKGV changed from 230+git0+3a74d4fc90 to 1.0 [default]

I'm starting to wonder if systemd and systemd-boot sharing a .inc is a good
idea!

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

Re: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232

[Khem Raj]

On Thu, Dec 1, 2016 at 12:22 PM, Burton, Ross  wrote:
>
> On 28 November 2016 at 21:26, Khem Raj  wrote:
>>
>> -PV = "230+git${SRCPV}"
>
>
> packages/corei7-64-intel-common-poky-linux/systemd-boot/systemd-boot-dev:
> PKGV changed from 230+git0+3a74d4fc90 to 1.0 [default]
>
> I'm starting to wonder if systemd and systemd-boot sharing a .inc is a good
> idea!

I think its fine. We should consolidate all systemd related recipes in
one place may
be under

recipes-systemd/
or recipes-core/systemd

currently we have

./recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
./recipes-bsp/systemd-boot/systemd-boot.bb
./recipes-core/systemd/systemd_232.bb
./recipes-core/systemd/systemd-serialgetty.bb
./recipes-core/systemd/systemd.inc
./recipes-core/systemd/systemd-compat-units.bb
./recipes-core/systemd/systemd-systemctl-native.bb



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

[OE-core] [PATCH V4 2/2] systemd: Upgrade to 232

[Khem Raj]

* Drop support for rcS.d SysV init scripts.
  These are prone to cause dependency loops, and almost all packages with
  rcS scripts now ship a native systemd service.

* Drop mount propagation patch, it only happens with libseccomp, OE doesnt
  enable it

* kdbus option has disappeared from configure

* Ignore dev-so for PN now since systemd introduced private .so see
  https://github.com/systemd/systemd/issues/3810

* Add libnss* to PACKAGES_DYNAMIC for libnss-resolve to work correctly

* Forward port systemd-boot patches to systemd-232

Signed-off-by: Khem Raj 
---
 ...pper-instead-of-looking-for-relative-opti.patch |  55 +++--
 .../{systemd-boot.bb => systemd-boot_232.bb}   |   0
 meta/recipes-core/systemd/systemd.inc  |   4 +-
 c-Change-the-default-device-timeout-to-2.patch |   8 +-
 ...r-getty-to-agetty-in-console-setup-system.patch |  10 +-
 .../systemd/0003-define-exp10-if-missing.patch |  12 +-
 ...nv-when-secure-versions-are-not-available.patch |  21 ++--
 ...t-install-dependency-links-at-install-tim.patch |  10 +-
 ...heck-for-additional-features-that-uclibc-.patch |  10 +-
 ...pper-instead-of-looking-for-relative-opti.patch |  38 ++
 ...wn-Use-execvpe-only-when-libc-supports-it.patch |  16 +--
 ...-unimplemented-_SC_PHYS_PAGES-system-conf.patch |  27 +++--
 ...0010-implment-systemd-sysv-install-for-OE.patch |   6 +-
 ...nes-Build-conditionally-when-HAVE_MYHOSTN.patch |  12 +-
 .../systemd/0012-rules-whitelist-hd-devices.patch  |  21 ++--
 ...-Make-root-s-home-directory-configurable.patch} |  90 +-
 ...tor-add-support-for-executing-scripts-und.patch | 133 -
 ...vert-rules-remove-firmware-loading-rules.patch} |   6 +-
 ...remove-userspace-firmware-loading-suppor.patch} |  58 +
 ...0015-systemd-user-avoid-using-system-auth.patch |  35 --
 ...patch => 0016-make-test-dir-configurable.patch} |  21 ++--
 ...=> 0017-remove-duplicate-include-uchar.h.patch} |  10 +-
 ...h => 0018-check-for-uchar.h-in-configure.patch} |  16 ++-
 ...l-don-t-fail-if-libc-doesn-t-support-IDN.patch} |  20 ++--
 ...sing.h-for-getting-secure_getenv-definiti.patch |  27 -
 .../systemd/systemd/CVE-2016-7795.patch|  69 ---
 ...dev-re-enable-mount-propagation-for-udevd.patch |  31 -
 .../systemd/{systemd_230.bb => systemd_232.bb} |  24 ++--
 28 files changed, 213 insertions(+), 577 deletions(-)
 rename meta/recipes-bsp/systemd-boot/{systemd-boot.bb => systemd-boot_232.bb} 
(100%)
 rename 
meta/recipes-core/systemd/systemd/{0014-Make-root-s-home-directory-configurable.patch
 => 0013-Make-root-s-home-directory-configurable.patch} (66%)
 delete mode 100644 
meta/recipes-core/systemd/systemd/0013-sysv-generator-add-support-for-executing-scripts-und.patch
 rename 
meta/recipes-core/systemd/systemd/{0016-Revert-rules-remove-firmware-loading-rules.patch
 => 0014-Revert-rules-remove-firmware-loading-rules.patch} (84%)
 rename 
meta/recipes-core/systemd/systemd/{0017-Revert-udev-remove-userspace-firmware-loading-suppor.patch
 => 0015-Revert-udev-remove-userspace-firmware-loading-suppor.patch} (89%)
 delete mode 100644 
meta/recipes-core/systemd/systemd/0015-systemd-user-avoid-using-system-auth.patch
 rename 
meta/recipes-core/systemd/systemd/{0018-make-test-dir-configurable.patch => 
0016-make-test-dir-configurable.patch} (77%)
 rename 
meta/recipes-core/systemd/systemd/{0019-remove-duplicate-include-uchar.h.patch 
=> 0017-remove-duplicate-include-uchar.h.patch} (81%)
 rename 
meta/recipes-core/systemd/systemd/{0020-check-for-uchar.h-in-configure.patch => 
0018-check-for-uchar.h-in-configure.patch} (76%)
 rename 
meta/recipes-core/systemd/systemd/{0022-socket-util-don-t-fail-if-libc-doesn-t-support-IDN.patch
 => 0019-socket-util-don-t-fail-if-libc-doesn-t-support-IDN.patch} (69%)
 delete mode 100644 
meta/recipes-core/systemd/systemd/0021-include-missing.h-for-getting-secure_getenv-definiti.patch
 delete mode 100644 meta/recipes-core/systemd/systemd/CVE-2016-7795.patch
 delete mode 100644 
meta/recipes-core/systemd/systemd/udev-re-enable-mount-propagation-for-udevd.patch
 rename meta/recipes-core/systemd/{systemd_230.bb => systemd_232.bb} (96%)

diff --git 
a/meta/recipes-bsp/systemd-boot/files/0001-use-lnr-wrapper-instead-of-looking-for-relative-opti.patch
 
b/meta/recipes-bsp/systemd-boot/files/0001-use-lnr-wrapper-instead-of-looking-for-relative-opti.patch
index 103d286..bc92db7 100644
--- 
a/meta/recipes-bsp/systemd-boot/files/0001-use-lnr-wrapper-instead-of-looking-for-relative-opti.patch
+++ 
b/meta/recipes-bsp/systemd-boot/files/0001-use-lnr-wrapper-instead-of-looking-for-relative-opti.patch
@@ -1,31 +1,22 @@
-From 9dcd2c80347493f73800d8c1cb539f1daef14394 Mon Sep 17 00:00:00 2001
-From: Jackie Huang 
-Date: Tue, 26 Jul 2016 03:54:42 -0400
-Subject: [PATCH] use lnr wrapper instead of looking for --relative option for 
ln
+From a3482c91642cf568b3ac27fa6c0cb3c6b30669b7 Mon Sep 17 

Re: [OE-core] [PATCH] perl-native: Remove usage of -fstack-protector=strong

[Khem Raj]

On Thu, Dec 1, 2016 at 2:46 PM, Aníbal Limón
 wrote:
>
>
> On 12/01/2016 04:39 PM, Khem Raj wrote:
>> On Thu, Dec 1, 2016 at 8:34 AM, Aníbal Limón
>>  wrote:
>>> Some distributions (like opensuse421) supported by the project
>>> comes with older gcc releases, -fstack-protector=strong is supported
>>> by GCC>=4.9.
>>>
>>> This causes a build failure when install perl-native from a sstate that
>>> comes from a machine supporting -fstack-protector=strong [1].
>>>
>>> So disable usage of this flag in perl-native builds, this patch could
>>> be removed when all supported distros comes with GCC>=4.9.
>>
>>
>> Instead of disabling it. Can it be made detectable during configure.
>
> The issue here is that comes from SSTATE mirror so the configure step
> isn't executed again when a other machine without
> -fstack-protector=strong download the sstate artifact was generate in
> other machine with -fstack-protector=strong support. This is only for
> native builds for target builds in enabled.
>
> We have similar patches for example in rpm,
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/rpm/rpm/popt-disable-auto-stack-protector.patch
>

yeah I see, thanks, I guess we need to bring it down to lowest common
denominator I guess.
maybe we should start thinking about gcc-native


> Cheers,
> alimon
>
>
>>
>>>
>>> [YOCTO #10338]
>>>
>>> [1] http://errors.yoctoproject.org/Errors/Details/109589/
>>>
>>> Signed-off-by: Aníbal Limón 
>>> ---
>>>  meta/recipes-devtools/perl/perl-native_5.24.0.bb   |   1 +
>>>  ...emove-fstack-protector-strong-for-native-.patch | 103 
>>> +
>>>  2 files changed, 104 insertions(+)
>>>  create mode 100644 
>>> meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>>>
>>> diff --git a/meta/recipes-devtools/perl/perl-native_5.24.0.bb 
>>> b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
>>> index af2ad7b..b1f0179 100644
>>> --- a/meta/recipes-devtools/perl/perl-native_5.24.0.bb
>>> +++ b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
>>> @@ -11,6 +11,7 @@ SRC_URI += "\
>>> file://debian/errno_ver.diff \
>>> file://dynaloaderhack.patch \
>>> file://perl-PathTools-don-t-filter-out-blib-from-INC.patch \
>>> +   
>>> file://0001-Configure-Remove-fstack-protector-strong-for-native-.patch \
>>>"
>>>
>>>  SRC_URI[md5sum] = "59456ae4bd4b06cb6e57cb19a3b2d349"
>>> diff --git 
>>> a/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>>>  
>>> b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>>> new file mode 100644
>>> index 000..7391ac5
>>> --- /dev/null
>>> +++ 
>>> b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>>> @@ -0,0 +1,103 @@
>>> +Some distributions (like opensuse421) supported by the project
>>> +comes with older gcc releases, -fstack-protector=strong is supported
>>> +by GCC>=4.9.
>>> +
>>> +This causes a build failure when install perl-native from a sstate that
>>> +comes from a machine supporting -fstack-protector=strong [1].
>>> +
>>> +So disable usage of this flag in perl-native builds, this patch could
>>> +be removed when all supported distros comes with GCC>=4.9.
>>> +
>>> +[YOCTO #10338]
>>> +
>>> +Upstream-status: Inappropriate [configuration]
>>> +
>>> +[1] http://errors.yoctoproject.org/Errors/Details/109589/
>>> +
>>> +Signed-off-by: Aníbal Limón 
>>> +---
>>> + Configure | 54 --
>>> + 1 file changed, 54 deletions(-)
>>> +
>>> +diff --git a/Configure b/Configure
>>> +index efbdcfd..d5bd98c 100755
>>> +--- a/Configure
>>>  b/Configure
>>> +@@ -5468,30 +5468,6 @@ default|recommended)
>>> +   eval $checkccflag
>>> +   ;;
>>> +   esac
>>> +-
>>> +-  # on x86_64 (at least) we require an extra library (libssp) in the
>>> +-  # link command line. This library is not named, so I infer that it 
>>> is
>>> +-  # an implementation detail that may change. Hence the safest 
>>> approach
>>> +-  # is to add the flag to the flags passed to the compiler at link 
>>> time,
>>> +-  # as that way the compiler can do the right implementation dependant
>>> +-  # thing. (NWC)
>>> +-  case "$osname" in
>>> +-  amigaos) ;; # -fstack-protector builds but doesn't work
>>> +-  *)  case "$gccversion" in
>>> +-  ?*) set stack-protector-strong -fstack-protector-strong
>>> +-  eval $checkccflag
>>> +-  case "$dflt" in
>>> +-  *-fstack-protector-strong*) ;; # It got added.
>>> +-  *) # Try the plain/older -fstack-protector.
>>> +- set stack-protector 

Re: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232

[Khem Raj]

sent a v4

On Thu, Dec 1, 2016 at 12:22 PM, Burton, Ross  wrote:
>
> On 28 November 2016 at 21:26, Khem Raj  wrote:
>>
>> -PV = "230+git${SRCPV}"
>
>
> packages/corei7-64-intel-common-poky-linux/systemd-boot/systemd-boot-dev:
> PKGV changed from 230+git0+3a74d4fc90 to 1.0 [default]
>
> I'm starting to wonder if systemd and systemd-boot sharing a .inc is a good
> idea!
>
> Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] perl-native: Remove usage of -fstack-protector=strong

[Khem Raj]

On Thu, Dec 1, 2016 at 8:34 AM, Aníbal Limón
 wrote:
> Some distributions (like opensuse421) supported by the project
> comes with older gcc releases, -fstack-protector=strong is supported
> by GCC>=4.9.
>
> This causes a build failure when install perl-native from a sstate that
> comes from a machine supporting -fstack-protector=strong [1].
>
> So disable usage of this flag in perl-native builds, this patch could
> be removed when all supported distros comes with GCC>=4.9.


Instead of disabling it. Can it be made detectable during configure.

>
> [YOCTO #10338]
>
> [1] http://errors.yoctoproject.org/Errors/Details/109589/
>
> Signed-off-by: Aníbal Limón 
> ---
>  meta/recipes-devtools/perl/perl-native_5.24.0.bb   |   1 +
>  ...emove-fstack-protector-strong-for-native-.patch | 103 
> +
>  2 files changed, 104 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>
> diff --git a/meta/recipes-devtools/perl/perl-native_5.24.0.bb 
> b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
> index af2ad7b..b1f0179 100644
> --- a/meta/recipes-devtools/perl/perl-native_5.24.0.bb
> +++ b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
> @@ -11,6 +11,7 @@ SRC_URI += "\
> file://debian/errno_ver.diff \
> file://dynaloaderhack.patch \
> file://perl-PathTools-don-t-filter-out-blib-from-INC.patch \
> +   
> file://0001-Configure-Remove-fstack-protector-strong-for-native-.patch \
>"
>
>  SRC_URI[md5sum] = "59456ae4bd4b06cb6e57cb19a3b2d349"
> diff --git 
> a/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>  
> b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
> new file mode 100644
> index 000..7391ac5
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
> @@ -0,0 +1,103 @@
> +Some distributions (like opensuse421) supported by the project
> +comes with older gcc releases, -fstack-protector=strong is supported
> +by GCC>=4.9.
> +
> +This causes a build failure when install perl-native from a sstate that
> +comes from a machine supporting -fstack-protector=strong [1].
> +
> +So disable usage of this flag in perl-native builds, this patch could
> +be removed when all supported distros comes with GCC>=4.9.
> +
> +[YOCTO #10338]
> +
> +Upstream-status: Inappropriate [configuration]
> +
> +[1] http://errors.yoctoproject.org/Errors/Details/109589/
> +
> +Signed-off-by: Aníbal Limón 
> +---
> + Configure | 54 --
> + 1 file changed, 54 deletions(-)
> +
> +diff --git a/Configure b/Configure
> +index efbdcfd..d5bd98c 100755
> +--- a/Configure
>  b/Configure
> +@@ -5468,30 +5468,6 @@ default|recommended)
> +   eval $checkccflag
> +   ;;
> +   esac
> +-
> +-  # on x86_64 (at least) we require an extra library (libssp) in the
> +-  # link command line. This library is not named, so I infer that it is
> +-  # an implementation detail that may change. Hence the safest approach
> +-  # is to add the flag to the flags passed to the compiler at link time,
> +-  # as that way the compiler can do the right implementation dependant
> +-  # thing. (NWC)
> +-  case "$osname" in
> +-  amigaos) ;; # -fstack-protector builds but doesn't work
> +-  *)  case "$gccversion" in
> +-  ?*) set stack-protector-strong -fstack-protector-strong
> +-  eval $checkccflag
> +-  case "$dflt" in
> +-  *-fstack-protector-strong*) ;; # It got added.
> +-  *) # Try the plain/older -fstack-protector.
> +- set stack-protector -fstack-protector
> +- eval $checkccflag
> +- ;;
> +-  esac
> +-  ;;
> +-  esac
> +-  ;;
> +-  esac
> +-  ;;
> + esac
> +
> + case "$mips_type" in
> +@@ -5634,21 +5610,6 @@ case "$ldflags" in
> +   ;;
> + *) dflt="$ldflags";;
> + esac
> +-# See note above about -fstack-protector
> +-case "$ccflags" in
> +-*-fstack-protector-strong*)
> +-  case "$dflt" in
> +-  *-fstack-protector-strong*) ;; # Don't add it again
> +-  *) dflt="$dflt -fstack-protector-strong" ;;
> +-  esac
> +-  ;;
> +-*-fstack-protector*)
> +-  case "$dflt" in
> +-  *-fstack-protector*) ;; # Don't add it again
> +-  *) dflt="$dflt -fstack-protector" ;;
> +-  esac
> +-  ;;
> +-esac
> +
> + : Try to guess additional flags to pick up local libraries.
> + for thislibdir in $libpth; do
> +@@ -8571,21 +8532,6 @@ EOM
> +   ''|' ') dflt='none' ;;
> +   esac
> +
> +- 

Re: [OE-core] [PATCH] perl-native: Remove usage of -fstack-protector=strong

[Aníbal Limón]

On 12/01/2016 04:39 PM, Khem Raj wrote:
> On Thu, Dec 1, 2016 at 8:34 AM, Aníbal Limón
>  wrote:
>> Some distributions (like opensuse421) supported by the project
>> comes with older gcc releases, -fstack-protector=strong is supported
>> by GCC>=4.9.
>>
>> This causes a build failure when install perl-native from a sstate that
>> comes from a machine supporting -fstack-protector=strong [1].
>>
>> So disable usage of this flag in perl-native builds, this patch could
>> be removed when all supported distros comes with GCC>=4.9.
> 
> 
> Instead of disabling it. Can it be made detectable during configure.

The issue here is that comes from SSTATE mirror so the configure step
isn't executed again when a other machine without
-fstack-protector=strong download the sstate artifact was generate in
other machine with -fstack-protector=strong support. This is only for
native builds for target builds in enabled.

We have similar patches for example in rpm,

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/rpm/rpm/popt-disable-auto-stack-protector.patch

Cheers,
alimon


> 
>>
>> [YOCTO #10338]
>>
>> [1] http://errors.yoctoproject.org/Errors/Details/109589/
>>
>> Signed-off-by: Aníbal Limón 
>> ---
>>  meta/recipes-devtools/perl/perl-native_5.24.0.bb   |   1 +
>>  ...emove-fstack-protector-strong-for-native-.patch | 103 
>> +
>>  2 files changed, 104 insertions(+)
>>  create mode 100644 
>> meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>>
>> diff --git a/meta/recipes-devtools/perl/perl-native_5.24.0.bb 
>> b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
>> index af2ad7b..b1f0179 100644
>> --- a/meta/recipes-devtools/perl/perl-native_5.24.0.bb
>> +++ b/meta/recipes-devtools/perl/perl-native_5.24.0.bb
>> @@ -11,6 +11,7 @@ SRC_URI += "\
>> file://debian/errno_ver.diff \
>> file://dynaloaderhack.patch \
>> file://perl-PathTools-don-t-filter-out-blib-from-INC.patch \
>> +   
>> file://0001-Configure-Remove-fstack-protector-strong-for-native-.patch \
>>"
>>
>>  SRC_URI[md5sum] = "59456ae4bd4b06cb6e57cb19a3b2d349"
>> diff --git 
>> a/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>>  
>> b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>> new file mode 100644
>> index 000..7391ac5
>> --- /dev/null
>> +++ 
>> b/meta/recipes-devtools/perl/perl/0001-Configure-Remove-fstack-protector-strong-for-native-.patch
>> @@ -0,0 +1,103 @@
>> +Some distributions (like opensuse421) supported by the project
>> +comes with older gcc releases, -fstack-protector=strong is supported
>> +by GCC>=4.9.
>> +
>> +This causes a build failure when install perl-native from a sstate that
>> +comes from a machine supporting -fstack-protector=strong [1].
>> +
>> +So disable usage of this flag in perl-native builds, this patch could
>> +be removed when all supported distros comes with GCC>=4.9.
>> +
>> +[YOCTO #10338]
>> +
>> +Upstream-status: Inappropriate [configuration]
>> +
>> +[1] http://errors.yoctoproject.org/Errors/Details/109589/
>> +
>> +Signed-off-by: Aníbal Limón 
>> +---
>> + Configure | 54 --
>> + 1 file changed, 54 deletions(-)
>> +
>> +diff --git a/Configure b/Configure
>> +index efbdcfd..d5bd98c 100755
>> +--- a/Configure
>>  b/Configure
>> +@@ -5468,30 +5468,6 @@ default|recommended)
>> +   eval $checkccflag
>> +   ;;
>> +   esac
>> +-
>> +-  # on x86_64 (at least) we require an extra library (libssp) in the
>> +-  # link command line. This library is not named, so I infer that it is
>> +-  # an implementation detail that may change. Hence the safest approach
>> +-  # is to add the flag to the flags passed to the compiler at link 
>> time,
>> +-  # as that way the compiler can do the right implementation dependant
>> +-  # thing. (NWC)
>> +-  case "$osname" in
>> +-  amigaos) ;; # -fstack-protector builds but doesn't work
>> +-  *)  case "$gccversion" in
>> +-  ?*) set stack-protector-strong -fstack-protector-strong
>> +-  eval $checkccflag
>> +-  case "$dflt" in
>> +-  *-fstack-protector-strong*) ;; # It got added.
>> +-  *) # Try the plain/older -fstack-protector.
>> +- set stack-protector -fstack-protector
>> +- eval $checkccflag
>> +- ;;
>> +-  esac
>> +-  ;;
>> +-  esac
>> +-  ;;
>> +-  esac
>> +-  ;;
>> + esac
>> +
>> + case "$mips_type" in
>> +@@ -5634,21 +5610,6 @@ case "$ldflags" in
>> +   ;;
>> + *) dflt="$ldflags";;
>> 

Re: [OE-core] [PATCHv2 3/3] oe-selftest: Add option to submit test result to a git repository.

[Benjamin Esquivel]

On Thu, 2016-12-01 at 11:00 -0600, Mariano Lopez wrote:
> > I think this version is okay :) have you tested it in an
> Autobuilder
> > task? 
> 
> Indeed, that is why it took me a bit longer to submit the patch. I
> know this won't blow up current master.  But Ihaven't used the
> option yet, we would need a remote repo and a new autobuilder
> buildset.
So, for enabling it you still need the repo, right? is that repo
already requested? it would help to understand the timing of this
feature coming online.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] non-standard library locations and rpath

[Jack Mitchell]

I'm having some troubles with shared library, shared library 
dependencies and rpaths. I have libfoo, which depends on libbar when I 
try to link libfoo with my app, it requires libbar to be found. libbar 
is in a non-standard location, /usr/local/bar when I compiled libfoo, I 
used -Wl,rpath-link ${STAGING_SYSROOT}/usr/local/bar and -Wl,rpath 
/usr/local/bar. Now when I come to try link my app with libfoo, it fails 
to link as it can't find libbar, which I assume means the rpath in 
libfoo isn't being properly prepending with sysroot what is the proper 
way to support this in OE? My library has the following rpath information:


0x000f (RPATH) Library rpath: [$ORIGIN/../lib:/usr/local/bar]

So why isn't the rpath being prepended with the sysroot when I compile 
my app and link libfoo? The apps build system is using cmake, but this 
should be a built in linker feature, correct?


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

Re: [OE-core] [PATCHv2 3/3] oe-selftest: Add option to submit test result to a git repository.

[Benjamin Esquivel]

Hi Mariano

On Thu, 2016-12-01 at 09:37 -0600, mariano.lo...@linux.intel.com wrote:
> From: Mariano Lopez 
> 
> This new option allows to commit the result to a git repository,
> along with the results it will add a metadata file for information
> of the current selftest run, such as: hostname, machine, distro,
> distro version, host version, and layers.
> 
> This implementation will have a branch per different hostname,
> testing branch, and machine.
> 
> To use this feature use:
> 
> oe-selftest  --repository 
> 
> [YOCTO #9954]
I think this version is okay :) have you tested it in an Autobuilder
task? 
> 
> Signed-off-by: Mariano Lopez 
> ---
>  scripts/oe-selftest | 102
> 
>  1 file changed, 102 insertions(+)
> 
> diff --git a/scripts/oe-selftest b/scripts/oe-selftest
> index deaa432..f4b861f 100755
> --- a/scripts/oe-selftest
> +++ b/scripts/oe-selftest
> @@ -36,6 +36,7 @@ import re
>  import fnmatch
>  import collections
>  import imp
> +import git
>  
>  sys.path.insert(0, os.path.dirname(os.path.realpath(__file__)) +
> '/lib')
>  import scriptpath
> @@ -46,6 +47,7 @@ import argparse_oe
>  import oeqa.selftest
>  import oeqa.utils.ftools as ftools
>  from oeqa.utils.commands import runCmd, get_bb_var, get_test_layer
> +from oeqa.utils.metadata import metadata_from_bb,
> write_metadata_file
>  from oeqa.selftest.base import oeSelfTest, get_available_machines
>  
>  try:
> @@ -106,6 +108,8 @@ def get_args_parser():
> help='List all tags that have been set to
> test cases.')
>  parser.add_argument('--machine', required=False, dest='machine',
> choices=['random', 'all'], default=None,
>  help='Run tests on different machines
> (random/all).')
> +parser.add_argument('--repository', required=False,
> dest='repository', default='', action='store',
> +help='Submit test results to a repository')
>  return parser
>  
>  
> @@ -572,6 +576,75 @@ def main():
>  
>  log.info("Finished")
>  
> +if args.repository:
> +# Commit tests results to repository
> +metadata = metadata_from_bb()
> +git_dir = os.path.join(os.getcwd(), 'selftest')
> +if not os.path.isdir(git_dir):
> +os.mkdir(git_dir)
> +
> +log.debug('Checking for git repository in %s' % git_dir)
> +try:
> +repo = git.Repo(git_dir)
> +except git.exc.InvalidGitRepositoryError:
> +log.debug("Couldn't find git repository %s; "
> + "cloning from %s" % (git_dir,
> args.repository))
> +repo = git.Repo.clone_from(args.repository, git_dir)
> +
> +r_branches = repo.git.branch(r=True)
> +r_branches = set(r_branches.replace('origin/',
> '').split())
> +l_branches = {str(branch) for branch in repo.branches}
> +branch = '%s/%s/%s' % (metadata['hostname'],
> +   metadata['layers']['meta']['branc
> h'],
> +   metadata['machine'])
> +
> +if branch in l_branches:
> +log.debug('Found branch in local repository,
> checking out')
> +repo.git.checkout(branch)
> +elif branch in r_branches:
> +log.debug('Found branch in remote repository,
> checking'
> +  ' out and pulling')
> +repo.git.checkout(branch)
> +repo.git.pull()
> +else:
> +log.debug('New branch %s' % branch)
> +repo.git.checkout('master')
> +repo.git.checkout(b=branch)
> +
> +cleanResultsDir(repo)
> +xml_dir = os.path.join(os.getcwd(), log_prefix)
> +copyResultFiles(xml_dir, git_dir, repo)
> +metadata_file = os.path.join(git_dir, 'metadata.xml')
> +write_metadata_file(metadata_file, metadata)
> +repo.index.add([metadata_file])
> +repo.index.write()
> +
> +# Get information for commit message
> +layer_info = ''
> +for layer, values in metadata['layers'].items():
> +layer_info = '%s%-17s = %s:%s\n' % (layer_info,
> layer,
> +  values['branch'], values['revision'])
> +msg = 'Selftest for build %s of %s %s for machine %s on
> %s\n\n%s' % (
> +   log_prefix[12:], metadata['distro'],
> metadata['distro_version'],
> +   metadata['machine'], metadata['hostname'],
> layer_info)
> +
> +log.debug('Commiting results to local repository')
> +repo.index.commit(msg)
> +if not repo.is_dirty():
> +try:
> +if branch in r_branches:
> +log.debug('Pushing changes to 

[OE-core] [PATCH] diffutils: 3.4 -> 3.5

[huangqy]

From: Huang Qiyu 

Upgrade diffutils from 3.4 to 3.5.

Signed-off-by: Huang Qiyu 
---
 .../0001-Unset-need_charset_alias-when-building-for-musl.patch| 0
 .../diffutils/{diffutils-3.4 => diffutils-3.5}/run-ptest  | 0
 .../recipes-extended/diffutils/{diffutils_3.4.bb => diffutils_3.5.bb} | 4 ++--
 3 files changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-extended/diffutils/{diffutils-3.4 => 
diffutils-3.5}/0001-Unset-need_charset_alias-when-building-for-musl.patch (100%)
 rename meta/recipes-extended/diffutils/{diffutils-3.4 => 
diffutils-3.5}/run-ptest (100%)
 rename meta/recipes-extended/diffutils/{diffutils_3.4.bb => diffutils_3.5.bb} 
(87%)

diff --git 
a/meta/recipes-extended/diffutils/diffutils-3.4/0001-Unset-need_charset_alias-when-building-for-musl.patch
 
b/meta/recipes-extended/diffutils/diffutils-3.5/0001-Unset-need_charset_alias-when-building-for-musl.patch
similarity index 100%
rename from 
meta/recipes-extended/diffutils/diffutils-3.4/0001-Unset-need_charset_alias-when-building-for-musl.patch
rename to 
meta/recipes-extended/diffutils/diffutils-3.5/0001-Unset-need_charset_alias-when-building-for-musl.patch
diff --git a/meta/recipes-extended/diffutils/diffutils-3.4/run-ptest 
b/meta/recipes-extended/diffutils/diffutils-3.5/run-ptest
similarity index 100%
rename from meta/recipes-extended/diffutils/diffutils-3.4/run-ptest
rename to meta/recipes-extended/diffutils/diffutils-3.5/run-ptest
diff --git a/meta/recipes-extended/diffutils/diffutils_3.4.bb 
b/meta/recipes-extended/diffutils/diffutils_3.5.bb
similarity index 87%
rename from meta/recipes-extended/diffutils/diffutils_3.4.bb
rename to meta/recipes-extended/diffutils/diffutils_3.5.bb
index cb7092b..673f5d4 100644
--- a/meta/recipes-extended/diffutils/diffutils_3.4.bb
+++ b/meta/recipes-extended/diffutils/diffutils_3.5.bb
@@ -17,8 +17,8 @@ do_configure_prepend () {
done
 }
 
-SRC_URI[md5sum] = "df9ca465f30307cffd03da176a43a5d4"
-SRC_URI[sha256sum] = 
"db53c025f2ac3d217bcf753dad6dee7b410b33d0948495ff015aaf8b91189ce2"
+SRC_URI[md5sum] = "569354697ff1cfc9a9de3781361015fa"
+SRC_URI[sha256sum] = 
"dad398ccd5b9faca6b0ab219a036453f62a602a56203ac659b43e889bec35533"
 
 inherit ptest
 
-- 
2.7.4



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

[OE-core] Debugfs + nfs-utils-client + ipkg

[Michael Gloff]

I've run into an issue recently when trying to build an image along with
the companion debugfs. This error only occurs if 'nfs-utils-client' is
added to IMAGE_INSTALL and ipkg packages are selected. I don't get the
error with RPM or with removing nfs-utils-client. Also, I can see the
missing files are present at some point during do_rootfs, but then must be
getting wiped out? I noticed this in Krogoth first, but can reproduce in
latest master. Any ideas?

developer@OEBuilder:~/oe/recipes/poky/build$ bitbake core-image-minimal
Loading cache: 100%
|##|
Time: 0:00:00
Loaded 1304 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "i586-poky-linux"
MACHINE   = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "2.2"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta
meta-poky
meta-yocto-bsp= "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a"

Initialising tasks: 100%
|#|
Time: 0:00:03
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed
packages list. Command
'/home/developer/oe/recipes/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg
-f
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/opkg.conf
-o
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs
--force_postinstall --prefer-arch-to-version   status' returned 0 and
stderr:
Collected errors:
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/etab:
No such file or directory.
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/rmtab:
No such file or directory.
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/xtab:
No such file or directory.
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/statd/state:
No such file or directory.

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.5361
ERROR: Task
(/home/developer/oe/recipes/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 2168 tasks of which 2167 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/home/developer/oe/recipes/poky/meta/recipes-core/images/core-image-minimal.bb:
do_rootfs
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Thanks,

Michael Gloff
mgl...@emacinc.com
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Debugfs + nfs-utils-client + ipkg

[Robert Yang]

Hi Michael,

On 12/02/2016 11:19 AM, Michael Gloff wrote:

I've run into an issue recently when trying to build an image along with the
companion debugfs. This error only occurs if 'nfs-utils-client' is added to
IMAGE_INSTALL and ipkg packages are selected. I don't get the error with RPM or
with removing nfs-utils-client. Also, I can see the missing files are present at
some point during do_rootfs, but then must be getting wiped out? I noticed this
in Krogoth first, but can reproduce in latest master. Any ideas?


Maybe something is wrong with opkg, it only happens when files are in 
/var/lib/foo, here is a *workaround*:


diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
index a348b97..ba072c0 100644
--- a/meta/lib/oe/rootfs.py
+++ b/meta/lib/oe/rootfs.py
@@ -951,7 +951,7 @@ class OpkgRootfs(DpkgOpkgRootfs):
 if self.progress_reporter:
 self.progress_reporter.next_stage()

-self._setup_dbg_rootfs(['/etc', '/var/lib/opkg', '/usr/lib/ssl'])
+self._setup_dbg_rootfs(['/etc', '/var/lib/opkg', '/usr/lib/ssl', 
'/var/lib/nfs'])


 execute_pre_post_process(self.d, opkg_post_process_cmds)


This is not a regular fix, you can file a bug here:
https://bugzilla.yoctoproject.org/

We may fix it later.

// Robert



developer@OEBuilder:~/oe/recipes/poky/build$ bitbake core-image-minimal
Loading cache: 100%
|##|
Time: 0:00:00
Loaded 1304 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "i586-poky-linux"
MACHINE   = "qemux86"
DISTRO= "poky"
DISTRO_VERSION= "2.2"
TUNE_FEATURES = "m32 i586"
TARGET_FPU= ""
meta
meta-poky
meta-yocto-bsp= "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a"

Initialising tasks: 100%
|#|
Time: 0:00:03
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed packages
list. Command
'/home/developer/oe/recipes/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg -f
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/opkg.conf
-o
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs
--force_postinstall --prefer-arch-to-version   status' returned 0 and stderr:
Collected errors:
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/etab:
No such file or directory.
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/rmtab:
No such file or directory.
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/xtab:
No such file or directory.
 * file_md5sum_alloc: Failed to open file
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/statd/state:
No such file or directory.

ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.5361
ERROR: Task
(/home/developer/oe/recipes/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 2168 tasks of which 2167 didn't need to be rerun
and 1 failed.

Summary: 1 task failed:

/home/developer/oe/recipes/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Thanks,

Michael Gloff
mgl...@emacinc.com 



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

Re: [OE-core] non-standard library locations and rpath

[Khem Raj]

On Thu, Dec 1, 2016 at 8:18 AM, Jack Mitchell  wrote:
> I'm having some troubles with shared library, shared library dependencies
> and rpaths. I have libfoo, which depends on libbar when I try to link libfoo
> with my app, it requires libbar to be found. libbar is in a non-standard
> location, /usr/local/bar when I compiled libfoo, I used -Wl,rpath-link
> ${STAGING_SYSROOT}/usr/local/bar and -Wl,rpath /usr/local/bar. Now when I
> come to try link my app with libfoo, it fails to link as it can't find
> libbar, which I assume means the rpath in libfoo isn't being properly
> prepending with sysroot what is the proper way to support this in OE? My
> library has the following rpath information:
>
> 0x000f (RPATH) Library rpath: [$ORIGIN/../lib:/usr/local/bar]
>
> So why isn't the rpath being prepended with the sysroot when I compile my
> app and link libfoo? The apps build system is using cmake, but this should
> be a built in linker feature, correct?

Only first path ( before :) is relative to location of binary at runtime

>
> Cheers,
> Jack.
> --
> ___
> 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/1] kernel.bbclass: let do_deploy depend on do_packagedata

[Robert Yang]

The following changes since commit 11063a01d4511b2688ea7ba2d7359e4e07328c66:

  ruby: upgrade to 2.3.1 (2016-11-30 15:47:17 +)

are available in the git repository at:

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

Robert Yang (1):
  kernel.bbclass: let do_deploy depend on do_packagedata

 meta/classes/kernel.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.9.0

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

[OE-core] [PATCH 1/1] kernel.bbclass: let do_deploy depend on do_packagedata

[Robert Yang]

The do_deploy runs depmodwrapper which requires
pkgdata/kernel-depmod/kernel-abiversion, which is generated by
PACKAGEFUNCS. So we need let do_deploy depend on do_packagedata.

This can fix the errors which happens sometimes when kernel upgrades:
DEBUG: Executing shell function do_deploy
Error: Kernel version 4.8.8-WR9.0.0.1_standard does not match kernel-abiversion 
(4.8.8-WR9.0.0.0_standard)

And we only see this error when kernel upgrades and rebuild, but doesn't
see it in a normal build, this is becuase depmodwrapper doesn't exit
error when kernel-depmod/kernel-abiversion doesn't exit, it just prints
an error which should go into log.do_deploy:
if [ ! -r /path/to/sysroots/qemux86-64/pkgdata/kernel-depmod/kernel-abiversion 
]; then
echo "Unable to read: 
/path/to/sysroots/qemux86-64/pkgdata/kernel-depmod/kernel-abiversion" >&2
else
[foo]
fi

We can see that there is no "exit 1", I guess it was designed to let it
can run without kernel-abiversion

Signed-off-by: Robert Yang 
---
 meta/classes/kernel.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 25a153c..17e85a4 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -630,6 +630,6 @@ do_deploy[cleandirs] = "${DEPLOYDIR}"
 do_deploy[dirs] = "${DEPLOYDIR} ${B}"
 do_deploy[prefuncs] += "package_get_auto_pr"
 
-addtask deploy after do_populate_sysroot
+addtask deploy after do_populate_sysroot do_packagedata
 
 EXPORT_FUNCTIONS do_deploy
-- 
2.9.0

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

[OE-core] [PATCH] gstreamer1.0-plugins-bad: Add PKG_CONFIG_SYSROOT_DIR to output of pkg-config

[Khem Raj]

When configure pokes for wayland-protocols isntallations it ended up
using the ones from host, which is because it did not account for sysroot
prefix

Signed-off-by: Khem Raj 
---
 .../gstreamer/gstreamer1.0-plugins-bad.inc |  2 +-
 ...G_CONFIG_SYSROOT_DIR-to-pkg-config-output.patch | 37 ++
 .../gstreamer/gstreamer1.0-plugins-bad_1.10.1.bb   |  1 +
 3 files changed, 39 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-Prepend-PKG_CONFIG_SYSROOT_DIR-to-pkg-config-output.patch

diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
index d26a6a9..d3c5326 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
@@ -64,7 +64,7 @@ PACKAGECONFIG[srtp]= 
"--enable-srtp,--disable-srtp,libsrtp"
 PACKAGECONFIG[uvch264] = "--enable-uvch264,--disable-uvch264,libusb1 
libgudev"
 PACKAGECONFIG[voaacenc]= 
"--enable-voaacenc,--disable-voaacenc,vo-aacenc"
 PACKAGECONFIG[voamrwbenc]  = 
"--enable-voamrwbenc,--disable-voamrwbenc,vo-amrwbenc"
-PACKAGECONFIG[wayland] = 
"--enable-wayland,--disable-wayland,wayland-native wayland"
+PACKAGECONFIG[wayland] = 
"--enable-wayland,--disable-wayland,wayland-native wayland wayland-protocols"
 PACKAGECONFIG[webp]= "--enable-webp,--disable-webp,libwebp"
 
 # these plugins have not been ported to 1.0 (yet):
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-Prepend-PKG_CONFIG_SYSROOT_DIR-to-pkg-config-output.patch
 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-Prepend-PKG_CONFIG_SYSROOT_DIR-to-pkg-config-output.patch
new file mode 100644
index 000..eb789df
--- /dev/null
+++ 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0001-Prepend-PKG_CONFIG_SYSROOT_DIR-to-pkg-config-output.patch
@@ -0,0 +1,37 @@
+From c271503d7e233428ac0323c51d6517113e26bef7 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Thu, 1 Dec 2016 00:27:13 -0800
+Subject: [PATCH] Prepend PKG_CONFIG_SYSROOT_DIR to pkg-config output
+
+In cross environment we have to prepend the sysroot to the path found by
+pkgconfig since the path returned from pkgconfig does not have sysroot prefixed
+it ends up using the files from host system. If build host has wayland 
installed
+the build will succeed but if you dont have wayland-protocols installed on 
build host then
+it wont find the files on build host
+
+This should work ok with non sysrooted builds too since in those cases 
PKG_CONFIG_SYSROOT_DIR
+will be empty
+
+Upstream-Status: Pending
+
+Signed-off-by: Khem Raj 
+---
+ configure.ac | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index f8ac96b..dc87b08 100644
+--- a/configure.ac
 b/configure.ac
+@@ -2233,7 +2233,7 @@ AG_GST_CHECK_FEATURE(WAYLAND, [wayland sink], wayland , [
+ PKG_CHECK_MODULES(WAYLAND_PROTOCOLS, wayland-protocols >= 1.4, [
+   if test "x$wayland_scanner" != "x"; then
+ HAVE_WAYLAND="yes"
+-AC_SUBST(WAYLAND_PROTOCOLS_DATADIR, `$PKG_CONFIG 
--variable=pkgdatadir wayland-protocols`)
++AC_SUBST(WAYLAND_PROTOCOLS_DATADIR, 
${PKG_CONFIG_SYSROOT_DIR}`$PKG_CONFIG --variable=pkgdatadir wayland-protocols`)
+   else
+ AC_MSG_RESULT([wayland-scanner is required to build the wayland 
plugin])
+ HAVE_WAYLAND="no"
+-- 
+2.10.2
+
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.10.1.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.10.1.bb
index 9cd892e..6c6f011 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.10.1.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.10.1.bb
@@ -14,6 +14,7 @@ SRC_URI = " \
 file://0001-gstreamer-gl.pc.in-don-t-append-GL_CFLAGS-to-CFLAGS.patch \
 file://0009-glimagesink-Downrank-to-marginal.patch \
 file://0001-introspection.m4-prefix-pkgconfig-paths-with-PKG_CON.patch \
+file://0001-Prepend-PKG_CONFIG_SYSROOT_DIR-to-pkg-config-output.patch \
 "
 SRC_URI[md5sum] = "491d2d5aab55ffc60c66e714d3d664ea"
 SRC_URI[sha256sum] = 
"133e0ed9fe21011b15d3898e3d3a9d17ab74eed31996da2e353353e688ca921d"
-- 
2.10.2

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

Re: [OE-core] [PATCH] libc-package.bbclass: split binary localedata even more if asked to

[Andreas Oberritter]

On 01.12.2016 05:02, Khem Raj wrote:
> 
>> On Nov 30, 2016, at 3:50 PM, Andreas Oberritter  
>> wrote:
>>
>> If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
>> glibc-binary-localedata-XX-YY to be a meta package depending on
>> glibc-binary-localedata-XX-YY-lc-address and so on. This enables
>> saving quite some space if someone doesn't need LC_COLLATE for
>> example.
>>
>> Some regex code was removed from output_locale_binary_rdepends,
>> because legitimize_package_name already converts to lowercase.
>>
> 
> This looks ok. May be add some documentation around 
> GLIBC_SPLIT_LC_PACKAGES in extended local.conf sample.

OK, will send a v2.

> I am worried about dependency changes, may be comparing old and new
> would help.

The generated meta packages make sure that dependencies stay intact. I
didn't observe any deviation in my test builds, with or without setting
GLIBC_SPLIT_LC_PACKAGES to 1.

Regards,
Andreas

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

[OE-core] [PATCH v2] libc-package.bbclass: split binary localedata even more if asked to

[Andreas Oberritter]

If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
glibc-binary-localedata-XX-YY to be a meta package depending on
glibc-binary-localedata-XX-YY-lc-address and so on. This enables
saving quite some space if someone doesn't need LC_COLLATE for
example.

Some regex code was removed from output_locale_binary_rdepends,
because legitimize_package_name already converts to lowercase.

Signed-off-by: Andreas Oberritter 
---
v2: Added description to local.conf.sample.extended.

 meta/classes/libc-package.bbclass| 39 +++-
 meta/conf/local.conf.sample.extended |  7 +++
 2 files changed, 32 insertions(+), 14 deletions(-)

diff --git a/meta/classes/libc-package.bbclass 
b/meta/classes/libc-package.bbclass
index 2dc90c4..071978b 100644
--- a/meta/classes/libc-package.bbclass
+++ b/meta/classes/libc-package.bbclass
@@ -9,6 +9,8 @@
 
 GLIBC_INTERNAL_USE_BINARY_LOCALE ?= "ondevice"
 
+GLIBC_SPLIT_LC_PACKAGES ?= "0"
+
 python __anonymous () {
 enabled = d.getVar("ENABLE_BINARY_LOCALE_GENERATION", True)
 
@@ -219,13 +221,12 @@ python package_do_split_gconvs () {
 (locale, encoding, locale))
 
 def output_locale_binary_rdepends(name, pkgname, locale, encoding):
-m = re.match("(.*)\.(.*)", name)
-if m:
-libc_name = "%s.%s" % (m.group(1), m.group(2).lower())
-else:
-libc_name = name
-d.setVar('RDEPENDS_%s' % pkgname, 
legitimize_package_name('%s-binary-localedata-%s' \
-% (mlprefix+bpn, libc_name)))
+dep = legitimize_package_name('%s-binary-localedata-%s' % (bpn, name))
+lcsplit = d.getVar('GLIBC_SPLIT_LC_PACKAGES', True)
+if lcsplit and int(lcsplit):
+d.appendVar('PACKAGES', ' ' + dep)
+d.setVar('ALLOW_EMPTY_%s' % dep, '1')
+d.setVar('RDEPENDS_%s' % pkgname, mlprefix + dep)
 
 commands = {}
 
@@ -337,6 +338,11 @@ python package_do_split_gconvs () {
 else:
 output_locale('%s.%s' % (base, charset), base, charset)
 
+def metapkg_hook(file, pkg, pattern, format, basename):
+name = basename.split('/', 1)[0]
+metapkg = legitimize_package_name('%s-binary-localedata-%s' % 
(mlprefix+bpn, name))
+d.appendVar('RDEPENDS_%s' % metapkg, ' ' + pkg)
+
 if use_bin == "compile":
 makefile = base_path_join(d.getVar("WORKDIR", True), "locale-tree", 
"Makefile")
 m = open(makefile, "w")
@@ -350,13 +356,18 @@ python package_do_split_gconvs () {
 bb.build.exec_func("oe_runmake", d)
 bb.note("collecting binary locales from locale tree")
 bb.build.exec_func("do_collect_bins_from_locale_tree", d)
-do_split_packages(d, binary_locales_dir, file_regex='(.*)', \
-output_pattern=bpn+'-binary-localedata-%s', \
-description='binary locale definition for %s', extra_depends='', 
allow_dirs=True)
-elif use_bin == "precompiled":
-do_split_packages(d, binary_locales_dir, file_regex='(.*)', \
-output_pattern=bpn+'-binary-localedata-%s', \
-description='binary locale definition for %s', extra_depends='', 
allow_dirs=True)
+
+if use_bin in ('compile', 'precompiled'):
+lcsplit = d.getVar('GLIBC_SPLIT_LC_PACKAGES', True)
+if lcsplit and int(lcsplit):
+do_split_packages(d, binary_locales_dir, 
file_regex='^(.*/LC_\w+)', \
+output_pattern=bpn+'-binary-localedata-%s', \
+description='binary locale definition for %s', recursive=True,
+hook=metapkg_hook, extra_depends='', allow_dirs=True, 
match_path=True)
+else:
+do_split_packages(d, binary_locales_dir, file_regex='(.*)', \
+output_pattern=bpn+'-binary-localedata-%s', \
+description='binary locale definition for %s', 
extra_depends='', allow_dirs=True)
 else:
 bb.note("generation of binary locales disabled. this may break i18n!")
 
diff --git a/meta/conf/local.conf.sample.extended 
b/meta/conf/local.conf.sample.extended
index 57f656a..f7cabf0 100644
--- a/meta/conf/local.conf.sample.extended
+++ b/meta/conf/local.conf.sample.extended
@@ -47,6 +47,13 @@
 # less than 128MB RAM.
 #ENABLE_BINARY_LOCALE_GENERATION = "1"
 
+# If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
+# glibc-binary-localedata-XX-YY to be a meta package depending on
+# glibc-binary-localedata-XX-YY-lc-address and so on. This enables
+# saving quite some space if someone doesn't need LC_COLLATE for
+# example.
+#GLIBC_SPLIT_LC_PACKAGES = "1"
+
 # Set GLIBC_GENERATE_LOCALES to the locales you wish to generate should you not
 # wish to perform the time-consuming step of generating all LIBC locales.
 # NOTE: If removing en_US.UTF-8 you will also need to uncomment, and set
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org

[OE-core] [PATCH] initscripts: populate-volatile: improve config file parsing

[Mans Rullgard]

This improves the config file parsing to permit blank lines and
comments following an entry or preceeded by whitespace.

Signed-off-by: Mans Rullgard 
---
 meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh | 6 +++---
 meta/recipes-core/initscripts/initscripts-1.0/volatiles| 6 --
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh 
b/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
index ce4622a5e555..91514bac86fa 100755
--- a/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
+++ b/meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
@@ -150,9 +150,9 @@ apply_cfgfile() {
return 1
}
 
-   cat ${CFGFILE} | grep -v "^#" | \
-   while read LINE; do
-   eval `echo "$LINE" | sed -n "s/\(.*\)\ \(.*\) \(.*\)\ \(.*\)\ 
\(.*\)\ \(.*\)/TTYPE=\1 ; TUSER=\2; TGROUP=\3; TMODE=\4; TNAME=\5 
TLTARGET=\6/p"`
+   cat ${CFGFILE} | sed 's/#.*//' | \
+   while read TTYPE TUSER TGROUP TMODE TNAME TLTARGET; do
+   test -z "${TLTARGET}" && continue
TNAME=${ROOT_DIR}${TNAME}
[ "${VERBOSE}" != "no" ] && echo "Checking for -${TNAME}-."
 
diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles 
b/meta/recipes-core/initscripts/initscripts-1.0/volatiles
index 297245d0e40e..bc17c4553da2 100644
--- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles
+++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles
@@ -1,11 +1,13 @@
 # This configuration file lists filesystem objects that should get verified
 # during startup and be created if missing.
 #
-# Every line must either be a comment starting with #
-# or a definition of format:
+# Entries have the following format:
 #  
 # where the items are separated by whitespace !
 #
+# The # character introduces a comment lasting until end of line.
+# Blank lines are ignored.
+#
 #  : d|f|l : (d)irectory|(f)ile|(l)ink
 #
 # A linking example:
-- 
2.10.2

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

[OE-core] [PATCH] gstreamer1.0-rtsp-server: Add libcheck to deps

[Khem Raj]

Signed-off-by: Khem Raj 
---
 meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc
index 13ba40d..7191f98 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-rtsp-server.inc
@@ -3,7 +3,7 @@ HOMEPAGE = 
"http://cgit.freedesktop.org/gstreamer/gst-rtsp-server/;
 SECTION = "multimedia"
 LICENSE = "LGPLv2"
 
-DEPENDS = "gstreamer1.0 libcgroup gstreamer1.0-plugins-base"
+DEPENDS = "gstreamer1.0 libcgroup gstreamer1.0-plugins-base libcheck"
 
 PNREAL = "gst-rtsp-server"
 
-- 
2.10.2

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

Re: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: den 28 november 2016 22:26
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 2/2 V5] systemd: Upgrade to 232
> 
> * Drop support for rcS.d SysV init scripts.
>   These are prone to cause dependency loops, and almost all packages
> with
>   rcS scripts now ship a native systemd service.
> 
> * Drop mount propagation patch, it only happens with libseccomp, OE
> doesnt
>   enable it
> 
> * kdbus option has disappeared from configure
> 
> * Ignore dev-so for PN now since systemd introduced private .so see
>   https://github.com/systemd/systemd/issues/3810

Rather than adding:

INSANE_SKIP_${PN} += "dev-so"

would it not be more appropriate to add 
${systemd_unitdir}/libsystemd-shared.so to FILES_${PN}-dev, i.e.:

-FILES_${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ 
${sysconfdir}/rpm/macros.systemd"
+FILES_${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ 
${sysconfdir}/rpm/macros.systemd ${systemd_unitdir}/libsystemd-shared.so"

The binaries are linked with libsystemd-shared-232.so which ends up in 
${PN} as usual.

> * Add libnss* to PACKAGES_DYNAMIC for libnss-resolve to work correctly
> 
> * Forward port systemd-boot patches to systemd-232
> 
> Signed-off-by: Khem Raj 

//Peter

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

[OE-core] [PATCH] libarchive: enable non-recursive extract/list

[Patrick Ohly]

Required for meta-swupd performance enhancements: in meta-swupd, the
so called "mega" image contains a rootfs with all files that can
potentially be installed on a device. Other virtual image recipes need
a subset of those files or directories, and a partial extraction from
a single tar archive is faster than letting all virtual image recipes
share access to a directory under a single pseudo instance.

It may be necessary to extract a directory with all of its attributes
without the content of the directory, hence this patch. Upstream
agreed to consider merging such a patch (see
https://groups.google.com/forum/#!topic/libarchive-discuss/JO3hqSaAVfs)
but has been slow in actually commenting on it, so for now it has
to be carried as distro patch.

Signed-off-by: Patrick Ohly 
---
 .../files/non-recursive-extract-and-list.patch | 153 +
 .../libarchive/libarchive_3.2.2.bb |   1 +
 2 files changed, 154 insertions(+)
 create mode 100644 
meta/recipes-extended/libarchive/files/non-recursive-extract-and-list.patch

diff --git 
a/meta/recipes-extended/libarchive/files/non-recursive-extract-and-list.patch 
b/meta/recipes-extended/libarchive/files/non-recursive-extract-and-list.patch
new file mode 100644
index 000..61f8f3e
--- /dev/null
+++ 
b/meta/recipes-extended/libarchive/files/non-recursive-extract-and-list.patch
@@ -0,0 +1,153 @@
+From d6271709d2deb980804f92e75f9b5cb600dc42ed Mon Sep 17 00:00:00 2001
+From: Patrick Ohly 
+Date: Mon, 24 Oct 2016 12:54:48 +0200
+Subject: [PATCH 1/2] non-recursive extract and list
+
+Sometimes it makes sense to extract or list a directory contained in
+an archive without also doing the same for the content of the
+directory, i.e. allowing -n (= --no-recursion) in combination with the
+x and t modes.
+
+bsdtar uses the match functionality in libarchive to track include
+matches. A new libarchive API call
+archive_match_include_directories_recursively() gets introduced to
+influence the matching behavior, with the default behavior as before.
+
+Non-recursive matching can be achieved by anchoring the path match at
+both start and end. Asking for a directory which itself isn't in the
+archive when in non-recursive mode is an error and handled by the
+existing mechanism for tracking unused inclusion entries.
+
+Upstream-Status: Submitted [https://github.com/libarchive/libarchive/pull/812]
+
+Signed-off-by: Patrick Ohly 
+
+---
+ libarchive/archive.h   |  2 ++
+ libarchive/archive_match.c | 30 +-
+ tar/bsdtar.1   |  3 +--
+ tar/bsdtar.c   | 12 ++--
+ 4 files changed, 42 insertions(+), 5 deletions(-)
+
+diff --git a/libarchive/archive.h b/libarchive/archive.h
+index ff401e9..38d8746 100644
+--- a/libarchive/archive.h
 b/libarchive/archive.h
+@@ -1085,6 +1085,8 @@ __LA_DECL intarchive_match_excluded(struct archive *,
+  */
+ __LA_DECL int archive_match_path_excluded(struct archive *,
+   struct archive_entry *);
++/* Control recursive inclusion of directory content when directory is 
included. Default on. */
++__LA_DECL int archive_match_include_directories_recursively(struct archive *, 
int _enabled);
+ /* Add exclusion pathname pattern. */
+ __LA_DECL int archive_match_exclude_pattern(struct archive *, const char *);
+ __LA_DECL int archive_match_exclude_pattern_w(struct archive *,
+diff --git a/libarchive/archive_match.c b/libarchive/archive_match.c
+index 0719cbd..6d03a65 100644
+--- a/libarchive/archive_match.c
 b/libarchive/archive_match.c
+@@ -93,6 +93,9 @@ struct archive_match {
+   /* exclusion/inclusion set flag. */
+   int  setflag;
+ 
++  /* Recursively include directory content? */
++  int  recursive_include;
++
+   /*
+* Matching filename patterns.
+*/
+@@ -223,6 +226,7 @@ archive_match_new(void)
+   return (NULL);
+   a->archive.magic = ARCHIVE_MATCH_MAGIC;
+   a->archive.state = ARCHIVE_STATE_NEW;
++  a->recursive_include = 1;
+   match_list_init(&(a->inclusions));
+   match_list_init(&(a->exclusions));
+   __archive_rb_tree_init(&(a->exclusion_tree), _ops_mbs);
+@@ -471,6 +475,28 @@ archive_match_path_excluded(struct archive *_a,
+ }
+ 
+ /*
++ * When recursive inclusion of directory content is enabled,
++ * an inclusion pattern that matches a directory will also
++ * include everything beneath that directory. Enabled by default.
++ *
++ * For compatibility with GNU tar, exclusion patterns always
++ * match if a subset of the full patch matches (i.e., they are
++ * are not rooted at the beginning of the path) and thus there
++ * is no corresponding non-recursive exclusion mode.
++ */
++int
++archive_match_include_directories_recursively(struct archive *_a, int 
_enabled)
++{
++  struct archive_match *a;
++
++  archive_check_magic(_a, 

Re: [OE-core] [PATCH] gstreamer1.0: Upgrade to 1.10.1

[Khem Raj]

> On Nov 30, 2016, at 7:17 AM, Burton, Ross  wrote:
> 
> Breaks if built from a empty sysroot with wayland enabled:
> 
> gst-plugins-bad:
> | make[3]: *** No rule to make target 'viewporter-protocol.c', needed by 
> 'all'.  Stop.

This one I was able to reproduce and fix. Sent the fix to ml.

> 
> Also rtsp-server gains various runtime dependencies on util-linux, can you 
> verify that these are expected and in the depends?
> 

Can you be more specific about this ? how to reproduce it ? what kind of 
diagnostics do you see ?

> Ross

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

[OE-core] [PATCH] arch-mips: sort new MACHINEOVERRIDES by priority

[André Draszik]

From: André Draszik 

While I couldn't find explicit documentation, it appears
that the list of MACHINEOVERRIDES should be sorted from
less specific to more specific left to right, so that
more specific overrides take precedence.

Signed-off-by: André Draszik 
---
 meta/conf/machine/include/mips/arch-mips.inc | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta/conf/machine/include/mips/arch-mips.inc 
b/meta/conf/machine/include/mips/arch-mips.inc
index d8b2bcb..ec3af0a 100644
--- a/meta/conf/machine/include/mips/arch-mips.inc
+++ b/meta/conf/machine/include/mips/arch-mips.inc
@@ -52,15 +52,15 @@ TUNE_ARCH = 
"mips${MIPSPKGSFX_32R6}${MIPSPKGSFX_64R6}${MIPSPKGSFX_BYTE}${MIPSPKG
 TUNE_PKGARCH = 
"${MIPSPKGSFX_VARIANT_tune-${DEFAULTTUNE}}${MIPSPKGSFX_FPU}${MIPSPKGSFX_ABI}"
 
 # Various Global Machine Overrides
-MACHINEOVERRIDES =. "mipsarch:"
-MACHINEOVERRIDES =. "mipsarch${MIPSPKGSFX_ENDIAN2}:"
-MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'r6', 
'mipsarchr6:', '' ,d)}"
-MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n32', 
'mipsarchn32:', '' ,d)}"
-MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'o32', 
'mipsarcho32:', '' ,d)}"
-MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n64', 
'mipsarchn64:', '' ,d)}"
-MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n32', 
'mipsarchn32${MIPSPKGSFX_ENDIAN2}:', '' ,d)}"
-MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'o32', 
'mipsarcho32${MIPSPKGSFX_ENDIAN2}:', '' ,d)}"
 MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n64', 
'mipsarchn64${MIPSPKGSFX_ENDIAN2}:', '' ,d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'o32', 
'mipsarcho32${MIPSPKGSFX_ENDIAN2}:', '' ,d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n32', 
'mipsarchn32${MIPSPKGSFX_ENDIAN2}:', '' ,d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n64', 
'mipsarchn64:', '' ,d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'o32', 
'mipsarcho32:', '' ,d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'n32', 
'mipsarchn32:', '' ,d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'r6', 
'mipsarchr6:', '' ,d)}"
+MACHINEOVERRIDES =. "mipsarch${MIPSPKGSFX_ENDIAN2}:"
+MACHINEOVERRIDES =. "mipsarch:"
 
 # Base tunes
 AVAILTUNES += "mips mips64-n32 mips64 mipsel mips64el-n32 mips64el mips-nf 
mips64-nf-n32 mips64-nf mipsel-nf mips64el-nf-n32 mips64el-nf"
-- 
2.10.2

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

Re: [OE-core] purpose of variables like "base_bindir_native"?

[Richard Purdie]

On Wed, 2016-11-30 at 06:34 -0500, Robert P. J. Day wrote:
>   i'm putting together a tutorial on the structure of the native
> sysroot and how it's built and variables involved, and was poking
> around in both bitbake.conf and native.bbclass, and i'm curious about
> one or two things.
> 
>   i could be totally wrong but it *seems* like there's native-related
> content in bitbake.conf that could be moved over to native.bbclass to
> reduce a little of the clutter. i'm perusing bitbake.conf and it's
> hard to keep track of some of the variables just because there's both
> native- and target- related settings in there. but i'll admit i
> haven't finished my inspection.
> 
>   on a more specific note, in the entire oe-core layer, there are two
> references to the variable "base_bindir_native" (formatted for
> aesthetics):
> 
> $ grep -rw base_bindir_native *
> meta/conf/bitbake.conf:base_bindir_native = "/bin"
> meta/conf/bitbake.conf:PATH_prepend =
>  "${COREBASE}/scripts:i
>  ${STAGING_BINDIR_TOOLCHAIN}:
>  ${STAGING_BINDIR_CROSS}:
>  ${STAGING_DIR_NATIVE}${sbindir_native}:
>  ${STAGING_BINDIR_NATIVE}:
>  ${STAGING_DIR_NATIVE}${base_sbindir_native}:
>  ${STAGING_DIR_NATIVE}${base_bindir_native}:"  <- there
> 
>   so, given that that variable is set in bitbake.conf, and is only
> referenced in that same file, what's the point of making it a
> variable? doesn't hurt, of course, but when i see a variable, i
> normally assume it's because it might be modified later somewhere,
> but
> i don't see that happening here. is there a reason for it? same thing
> could be said for "base_sbindir_native" as well.
> 
>   thoughts?

Its really for consistency. We don't hardcode the other path
relationships and whilst that one is a minority, we've clearly decided
not to hardcode it either. The fact its not widely used compared to
some of its relatives is not really the point.

If we did hardcode it, I can imagine the question about why it wasn't
parametrised ;-).

Cheers,

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

[OE-core] [PATCH v3] ltp: 20160126 -> 20160920

[huangqy]

From: Huang Qiyu 

1)Upgrade ltp from 20160126 to 20160920. 
2)Delete some patches, since they are integrated upstream. 
 0001-ltp-Don-t-link-against-libfl.patch 
 0006-sendfile-Use-off64_t-instead-of-__off64_t.patch 
 0007-replace-SIGCLD-with-SIGCHLD.patch 
 0009-Guard-error.h-with-__GLIBC__.patch 
 0012-fsstress.c-Replace-__int64_t-with-int64_t.patch 
 0013-include-fcntl.h-for-getting-O_-definitions.patch 
 0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch 
 0015-mincore01-Rename-PAGESIZE-to-pagesize.patch 
 0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch 
 0017-replace-sigval_t-with-union-sigval.patch 
 0019-tomoyo-Replace-canonicalize_file_name-with-realpath.patch 
 0022-include-sys-types.h.patch 
 0027-sysconf01-Use-_SC_2_C_VERSION-conditionally.patch 
 0029-trace_shed-Fix-build-with-musl.patch 
 0030-lib-Use-PTHREAD_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch 
 0031-vma03-fix-page-size-offset-as-per-page-size-alignmen.patch 
 0032-regen.sh-Include-asm-unistd.h-explicitly.patch 
3)Modify one patch, since the data has been changed.  
 0011-Rename-sigset-variable-to-sigset1.patch 
 0035-fix-test_proc_kill-hang.patch 
4)Add some new patches. 
 0001-Define-__SIGRTMIN-and-__SIGRTMAX-on-musl.patch 
 0002-initialize-recursive-mutex-in-a-portable-way.patch 
 0004-rt_sigaction-rt_sigprocmark-Replace-SA_NOMASK-with-S.patch 
 0006-Remove-unused-__BEGIN_DECLS-and-__END_DECLS.patch 
5)Modify security_flags.inc to fix error:
  /  
  |In file included from ../../../../include/old/test.h:47:0,
  |  from faccessat01.c:44:
  |faccessat01.c: In function 'setup':
  |../../../../include/old/old_safe_file_ops.h:55:27: error: format not a 
string literal and no format arguments [-Werror=format-security]
  |   (path), (fmt), ## __VA_ARGS__)
  \

Signed-off-by: Wang Xin 
Signed-off-by: Huang Qiyu 
---
 meta/conf/distro/include/security_flags.inc|   2 +
 ...-Define-__SIGRTMIN-and-__SIGRTMAX-on-musl.patch |  32 ++
 .../ltp/0001-ltp-Don-t-link-against-libfl.patch|  30 --
 ...tialize-recursive-mutex-in-a-portable-way.patch | 167 +
 ...n-rt_sigprocmark-Replace-SA_NOMASK-with-S.patch | 120 +++
 ...move-unused-__BEGIN_DECLS-and-__END_DECLS.patch |  48 +++
 ...sendfile-Use-off64_t-instead-of-__off64_t.patch |  31 --
 .../ltp/ltp/0007-replace-SIGCLD-with-SIGCHLD.patch | 394 -
 .../ltp/0009-Guard-error.h-with-__GLIBC__.patch| 270 --
 .../0011-Rename-sigset-variable-to-sigset1.patch   |  60 ++--
 ...fsstress.c-Replace-__int64_t-with-int64_t.patch | 351 --
 ...nclude-fcntl.h-for-getting-O_-definitions.patch |  67 
 ...ing-Include-sys-types.h-for-pid_t-definit.patch |  56 ---
 ...015-mincore01-Rename-PAGESIZE-to-pagesize.patch |  64 
 ...Change-header-from-ustat.h-to-sys-ustat.h.patch |  45 ---
 .../0017-replace-sigval_t-with-union-sigval.patch  |  88 -
 ...lace-canonicalize_file_name-with-realpath.patch |  32 --
 .../ltp/ltp/0022-include-sys-types.h.patch |  29 --
 ...sconf01-Use-_SC_2_C_VERSION-conditionally.patch |  29 --
 .../ltp/0029-trace_shed-Fix-build-with-musl.patch  |  32 --
 ...READ_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch |  33 --
 ...age-size-offset-as-per-page-size-alignmen.patch |  33 --
 ...-regen.sh-Include-asm-unistd.h-explicitly.patch |  30 --
 .../ltp/ltp/0035-fix-test_proc_kill-hang.patch |  25 +-
 .../ltp/{ltp_20160126.bb => ltp_20160920.bb}   |  23 +-
 25 files changed, 420 insertions(+), 1671 deletions(-)
 create mode 100644 
meta/recipes-extended/ltp/ltp/0001-Define-__SIGRTMIN-and-__SIGRTMAX-on-musl.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0001-ltp-Don-t-link-against-libfl.patch
 create mode 100644 
meta/recipes-extended/ltp/ltp/0002-initialize-recursive-mutex-in-a-portable-way.patch
 create mode 100644 
meta/recipes-extended/ltp/ltp/0004-rt_sigaction-rt_sigprocmark-Replace-SA_NOMASK-with-S.patch
 create mode 100644 
meta/recipes-extended/ltp/ltp/0006-Remove-unused-__BEGIN_DECLS-and-__END_DECLS.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0007-replace-SIGCLD-with-SIGCHLD.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0009-Guard-error.h-with-__GLIBC__.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0012-fsstress.c-Replace-__int64_t-with-int64_t.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0013-include-fcntl.h-for-getting-O_-definitions.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0015-mincore01-Rename-PAGESIZE-to-pagesize.patch
 delete mode 100644 
meta/recipes-extended/ltp/ltp/0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch
 delete mode 100644