date:20170821

== Series Details ==

Series: conf-notes.txt: add shell environment header
Revision: 1
URL   : https://patchwork.openembedded.org/series/8411/
State : failure

== Summary ==


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



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

* Issue Series sent to the wrong mailing list or some patches from 
the series correspond to different mailing lists [test_target_mailing_list] 
  Suggested fixSend the series again to the correct mailing list (ML)
  Suggested ML p...@yoctoproject.org 
[http://git.yoctoproject.org/cgit/cgit.cgi/poky/]
  Patch's path:meta-poky/conf/conf-notes.txt



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

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

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

[OE-core] [Poky] [PATCH] conf-notes.txt: add shell environment header

2017-08-21 Thread liu . ming50

From: Ming Liu 

The header text has been moved to meta/conf/conf-notes.txt by:
[ meta: move some text from oe-setup-builddir to conf-notes.txt ]

Need do the same to meta-poky/conf/conf-notes.txt.

Signed-off-by: Ming Liu 
---
 meta-poky/conf/conf-notes.txt | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta-poky/conf/conf-notes.txt b/meta-poky/conf/conf-notes.txt
index 2f2932b..f1a4f4d 100644
--- a/meta-poky/conf/conf-notes.txt
+++ b/meta-poky/conf/conf-notes.txt
@@ -1,3 +1,8 @@
+
+### Shell environment set up for builds. ###
+
+You can now run 'bitbake '
+
 Common targets are:
 core-image-minimal
 core-image-sato
-- 
2.7.4

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

[OE-core] [PATCH V2 9/9] buildhistory.bbclass: add ptest

The ptest log will be saved to buildhistory/ptest, we can easily get
the regression result between builds by:

$ git show HEAD ptest/pass.fail.skip.*

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/classes/buildhistory.bbclass | 30 ++
 1 file changed, 30 insertions(+)

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index a3e4c7a..dbfcc05 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -912,3 +912,33 @@ def write_latest_srcrev(d, pkghistdir):
 else:
 if os.path.exists(srcrevfile):
 os.remove(srcrevfile)
+
+do_testimage[postfuncs] += "write_ptest_result"
+do_testimage[vardepsexclude] += "write_ptest_result"
+
+python write_ptest_result() {
+write_latest_ptest_result(d, d.getVar('BUILDHISTORY_DIR'))
+}
+
+def write_latest_ptest_result(d, histdir):
+import glob
+import subprocess
+test_log_dir = d.getVar('TEST_LOG_DIR')
+input_ptest = os.path.join(test_log_dir, 'ptest_log')
+output_ptest = os.path.join(histdir, 'ptest')
+if os.path.exists(input_ptest):
+try:
+# Lock it avoid race issue
+lock = bb.utils.lockfile(output_ptest + "/ptest.lock")
+bb.utils.mkdirhier(output_ptest)
+oe.path.copytree(input_ptest, output_ptest)
+# Sort test result
+for result in glob.glob('%s/pass.fail.*' % output_ptest):
+bb.debug(1, 'Processing %s' % result)
+cmd = ['sort', result, '-o', result]
+bb.debug(1, 'Running %s' % cmd)
+ret = subprocess.call(cmd)
+if ret != 0:
+bb.error('Failed to run %s!' % cmd)
+finally:
+bb.utils.unlockfile(lock)
-- 
2.10.2

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

[OE-core] [PATCH V2 8/9] testimage.bbclass: update comments

It's very important to add IMAGE_CLASSES += "testimage" in local.conf firstly,
otherwise the var like TEST_LOG_DIR (defined in testimage.bbclass) will not be
in testdata.json.

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/classes/testimage.bbclass | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass
index 0c4a84e..6a43560 100644
--- a/meta/classes/testimage.bbclass
+++ b/meta/classes/testimage.bbclass
@@ -7,8 +7,8 @@
 # Most of the tests are commands run on target image over ssh.
 # To use it add testimage to global inherit and call your target image with -c 
testimage
 # You can try it out like this:
-# - first build a qemu core-image-sato
-# - add IMAGE_CLASSES += "testimage" in local.conf
+# - first add IMAGE_CLASSES += "testimage" in local.conf
+# - build a qemu core-image-sato
 # - then bitbake core-image-sato -c testimage. That will run a standard suite 
of tests.
 
 # You can set (or append to) TEST_SUITES in local.conf to select the tests
-- 
2.10.2

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

[OE-core] [PATCH V2 7/9] buildhistory.bbclass: print message when no commit

This makes the user easier to know how to make commit in buildhistory.

[YOCTO #11547]

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

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index 81784ee..a3e4c7a 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -824,6 +824,8 @@ python buildhistory_eventhandler() {
 interrupted = getattr(e, '_interrupted', 0)
 localdata.setVar('BUILDHISTORY_BUILD_INTERRUPTED', 
str(interrupted))
 bb.build.exec_func("buildhistory_commit", localdata)
+else:
+bb.note("No commit since BUILDHISTORY_COMMIT != '1'")
 }
 
 addhandler buildhistory_eventhandler
-- 
2.10.2

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

[OE-core] [PATCH V2 6/9] core/target/ssh.py: replace decode errors

There might be wild strings when read from target (especially when
reading ptest results), replace the errors to avoid breaking the test.

Fixed: (Not always happen)
$ bitbake core-image-sato -ctestimage
[snip]
status, output = self.target.run('ptest-runner', 0)
  File "/buildarea/lyang1/poky/meta/lib/oeqa/core/target/ssh.py", line 84, in 
run
status, output = self._run(sshCmd, processTimeout, True)
  File "/buildarea/lyang1/poky/meta/lib/oeqa/core/target/ssh.py", line 55, in 
_run
status, output = SSHCall(command, self.logger, timeout)
  File "/buildarea/lyang1/poky/meta/lib/oeqa/core/target/ssh.py", line 258, in 
SSHCall
run()
  File "/buildarea/lyang1/poky/meta/lib/oeqa/core/target/ssh.py", line 236, in 
run
output = process.communicate()[0].decode("utf-8")
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 4906: 
invalid continuation byte

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/core/target/ssh.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib/oeqa/core/target/ssh.py
index b80939c..a2eafcd 100644
--- a/meta/lib/oeqa/core/target/ssh.py
+++ b/meta/lib/oeqa/core/target/ssh.py
@@ -211,7 +211,7 @@ def SSHCall(command, logger, timeout=None, **opts):
 process.stdout.close()
 eof = True
 else:
-data = data.decode("utf-8")
+data = data.decode("utf-8", errors='replace')
 output += data
 logger.debug('Partial data from SSH call: %s' % 
data)
 endtime = time.time() + timeout
@@ -233,7 +233,7 @@ def SSHCall(command, logger, timeout=None, **opts):
 output += lastline
 
 else:
-output = process.communicate()[0].decode("utf-8")
+output = process.communicate()[0].decode("utf-8", errors='replace')
 logger.debug('Data from SSH call: %s' % output.rstrip())
 
 options = {
-- 
2.10.2

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

[OE-core] [PATCH V2 4/9] runtime/cases/_ptest.py: rename it to ptest.py

It works now.

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/runtime/cases/{_ptest.py => ptest.py} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename meta/lib/oeqa/runtime/cases/{_ptest.py => ptest.py} (100%)

diff --git a/meta/lib/oeqa/runtime/cases/_ptest.py 
b/meta/lib/oeqa/runtime/cases/ptest.py
similarity index 100%
rename from meta/lib/oeqa/runtime/cases/_ptest.py
rename to meta/lib/oeqa/runtime/cases/ptest.py
-- 
2.10.2

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

[OE-core] [PATCH V2 5/9] utils/logparser.py: fix section check

The section might be None or '', so use "if section" for it.

Fixed:
File "/buildarea/lyang1/poky/meta/lib/oeqa/utils/logparser.py", line 113, in 
log_as_files
prefix += section
TypeError: Can't convert 'NoneType' object to str implicitly

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/utils/logparser.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/utils/logparser.py b/meta/lib/oeqa/utils/logparser.py
index 4355ce0..0670627 100644
--- a/meta/lib/oeqa/utils/logparser.py
+++ b/meta/lib/oeqa/utils/logparser.py
@@ -109,7 +109,7 @@ class Result(object):
 prefix = ''
 for x in test_status:
 prefix +=x+'.'
-if (section != ''):
+if section:
 prefix += section
 section_file = os.path.join(target_dir, prefix)
 # purge the file contents if it exists
-- 
2.10.2

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

[OE-core] [PATCH V2 2/9] oeqa/utils/logparser.py: add skip status

Some test cases maybe skipped, let's parse it.

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/utils/logparser.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/utils/logparser.py b/meta/lib/oeqa/utils/logparser.py
index b377dcd..4355ce0 100644
--- a/meta/lib/oeqa/utils/logparser.py
+++ b/meta/lib/oeqa/utils/logparser.py
@@ -9,7 +9,7 @@ from . import ftools
 # A parser that can be used to identify weather a line is a test result or a 
section statement.
 class Lparser(object):
 
-def __init__(self, test_0_pass_regex, test_0_fail_regex, 
section_0_begin_regex=None, section_0_end_regex=None, **kwargs):
+def __init__(self, test_0_pass_regex, test_0_fail_regex, 
test_0_skip_regex, section_0_begin_regex=None, section_0_end_regex=None, 
**kwargs):
 # Initialize the arguments dictionary
 if kwargs:
 self.args = kwargs
@@ -19,12 +19,13 @@ class Lparser(object):
 # Add the default args to the dictionary
 self.args['test_0_pass_regex'] = test_0_pass_regex
 self.args['test_0_fail_regex'] = test_0_fail_regex
+self.args['test_0_skip_regex'] = test_0_skip_regex
 if section_0_begin_regex:
 self.args['section_0_begin_regex'] = section_0_begin_regex
 if section_0_end_regex:
 self.args['section_0_end_regex'] = section_0_end_regex
 
-self.test_possible_status = ['pass', 'fail', 'error']
+self.test_possible_status = ['pass', 'fail', 'error', 'skip']
 self.section_possible_status = ['begin', 'end']
 
 self.initialized = False
-- 
2.10.2

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

[OE-core] [PATCH V2 3/9] runtime/cases/_ptest.py: add skip status

The packages' test cases maybe skipped, check and save them.

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/runtime/cases/_ptest.py | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/runtime/cases/_ptest.py 
b/meta/lib/oeqa/runtime/cases/_ptest.py
index 6d23949..ec8c038 100644
--- a/meta/lib/oeqa/runtime/cases/_ptest.py
+++ b/meta/lib/oeqa/runtime/cases/_ptest.py
@@ -10,6 +10,7 @@ class PtestRunnerTest(OERuntimeTestCase):
 def parse_ptest(self, logfile):
 parser = Lparser(test_0_pass_regex="^PASS:(.+)",
  test_0_fail_regex="^FAIL:(.+)",
+ test_0_skip_regex="^SKIP:(.+)",
  section_0_begin_regex="^BEGIN: .*/(.+)/ptest",
  section_0_end_regex="^END: .*/(.+)/ptest")
 parser.init()
@@ -38,6 +39,10 @@ class PtestRunnerTest(OERuntimeTestCase):
 result.store(current_section, name, status)
 continue
 
+if line_type == 'test' and status == 'skip':
+result.store(current_section, name, status)
+continue
+
 result.sort_tests()
 return result
 
@@ -70,7 +75,7 @@ class PtestRunnerTest(OERuntimeTestCase):
 
 # Parse and save results
 parse_result = self.parse_ptest(ptest_runner_log)
-parse_result.log_as_files(ptest_log_dir, test_status = ['pass','fail'])
+parse_result.log_as_files(ptest_log_dir, test_status = ['pass','fail', 
'skip'])
 if os.path.exists(ptest_log_dir_link):
 # Remove the old link to create a new one
 os.remove(ptest_log_dir_link)
-- 
2.10.2

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

[OE-core] [PATCH V2 0/9] Revive ptest and add result to buildhistory

* V2:
  - Fix Paul's comments
  - Fix RP's comments

* V1:
  - Initial version

// Robert

The following changes since commit 5c9ef0734d23909b5694ed43cdbb205c2ba9ca95:

  devtool/copy_buildsystem: adds meta-skeleton layer in the eSDK installation. 
(2017-08-19 22:15:25 +0100)

are available in the git repository at:

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

Robert Yang (9):
  runtime/cases/_ptest.py: revive it
  oeqa/utils/logparser.py: add skip status
  runtime/cases/_ptest.py: add skip status
  runtime/cases/_ptest.py: rename it to ptest.py
  utils/logparser.py: fix section check
  core/target/ssh.py: replace decode errors
  buildhistory.bbclass: print message when no commit
  testimage.bbclass: update comments
  buildhistory.bbclass: add ptest

 meta/classes/buildhistory.bbclass |  32 +++
 meta/classes/testimage.bbclass|   4 +-
 meta/lib/oeqa/core/target/ssh.py  |   4 +-
 meta/lib/oeqa/runtime/cases/_ptest.py | 103 --
 meta/lib/oeqa/runtime/cases/ptest.py  |  82 +++
 meta/lib/oeqa/utils/logparser.py  |   7 ++-
 6 files changed, 122 insertions(+), 110 deletions(-)
 delete mode 100644 meta/lib/oeqa/runtime/cases/_ptest.py
 create mode 100644 meta/lib/oeqa/runtime/cases/ptest.py

-- 
2.10.2

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

[OE-core] [PATCH V2 1/9] runtime/cases/_ptest.py: revive it

* Make it work with current oeqa
* Skip the test if ptest is not in DISTRO_FEATURES
* Skip the test if ptest-pkgs is not in IMAGE_FEATURES
* The logs are saved to:
  testimage/ptest_log -> testimage/ptest_log.
* This provides data that could be used to detect regressions in ptest results

[YOCTO #11547]

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/runtime/cases/_ptest.py | 96 +--
 1 file changed, 35 insertions(+), 61 deletions(-)

diff --git a/meta/lib/oeqa/runtime/cases/_ptest.py 
b/meta/lib/oeqa/runtime/cases/_ptest.py
index aaed9a5..6d23949 100644
--- a/meta/lib/oeqa/runtime/cases/_ptest.py
+++ b/meta/lib/oeqa/runtime/cases/_ptest.py
@@ -1,28 +1,10 @@
-import os
-import shutil
-import subprocess
-
 from oeqa.runtime.case import OERuntimeTestCase
 from oeqa.core.decorator.depends import OETestDepends
 from oeqa.core.decorator.oeid import OETestID
-from oeqa.core.decorator.data import skipIfNotDataVar, skipIfNotFeature
-from oeqa.runtime.decorator.package import OEHasPackage
-
-from oeqa.runtime.cases.dnf import DnfTest
-from oeqa.utils.logparser import *
-from oeqa.utils.httpserver import HTTPService
-
-class PtestRunnerTest(DnfTest):
+from oeqa.core.decorator.data import skipIfNotFeature
+from oeqa.utils.logparser import Lparser, Result
 
-@classmethod
-def setUpClass(cls):
-rpm_deploy = os.path.join(cls.tc.td['DEPLOY_DIR'], 'rpm')
-cls.repo_server = HTTPService(rpm_deploy, cls.tc.target.server_ip)
-cls.repo_server.start()
-
-@classmethod
-def tearDownClass(cls):
-cls.repo_server.stop()
+class PtestRunnerTest(OERuntimeTestCase):
 
 # a ptest log parser
 def parse_ptest(self, logfile):
@@ -59,45 +41,37 @@ class PtestRunnerTest(DnfTest):
 result.sort_tests()
 return result
 
-def _install_ptest_packages(self):
-# Get ptest packages that can be installed in the image.
-packages_dir = os.path.join(self.tc.td['DEPLOY_DIR'], 'rpm')
-ptest_pkgs = [pkg[:pkg.find('-ptest')+6]
-  for _, _, filenames in os.walk(packages_dir)
-  for pkg in filenames
-  if 'ptest' in pkg
-  and pkg[:pkg.find('-ptest')] in 
self.tc.image_packages]
-
-repo_url = 'http://%s:%s' % (self.target.server_ip,
- self.repo_server.port)
-dnf_options = ('--repofrompath=oe-ptest-repo,%s '
-   '--nogpgcheck '
-   'install -y' % repo_url)
-self.dnf('%s %s ptest-runner' % (dnf_options, ' '.join(ptest_pkgs)))
-
-@skipIfNotFeature('package-management',
-  'Test requires package-management to be in 
DISTRO_FEATURES')
-@skipIfNotFeature('ptest',
-  'Test requires package-management to be in 
DISTRO_FEATURES')
-@skipIfNotDataVar('IMAGE_PKGTYPE', 'rpm',
-  'RPM is not the primary package manager')
-@OEHasPackage(['dnf'])
+@OETestID(1600)
+@skipIfNotFeature('ptest', 'Test requires ptest to be in DISTRO_FEATURES')
+@skipIfNotFeature('ptest-pkgs', 'Test requires ptest-pkgs to be in 
IMAGE_FEATURES')
 @OETestDepends(['ssh.SSHTest.test_ssh'])
 def test_ptestrunner(self):
-self.ptest_log = os.path.join(self.tc.td['TEST_LOG_DIR'],
-  'ptest-%s.log' % self.tc.td['DATETIME'])
-self._install_ptest_packages()
-
-(runnerstatus, result) = self.target.run('/usr/bin/ptest-runner > 
/tmp/ptest.log 2>&1', 0)
-#exit code is !=0 even if ptest-runner executes because some ptest 
tests fail.
-self.assertTrue(runnerstatus != 127, msg="Cannot execute 
ptest-runner!")
-self.target.copyFrom('/tmp/ptest.log', self.ptest_log)
-shutil.copyfile(self.ptest_log, "ptest.log")
-
-result = self.parse_ptest("ptest.log")
-log_results_to_location = "./results"
-if os.path.exists(log_results_to_location):
-shutil.rmtree(log_results_to_location)
-os.makedirs(log_results_to_location)
-
-result.log_as_files(log_results_to_location, test_status = 
['pass','fail'])
+import datetime
+
+test_log_dir = self.td.get('TEST_LOG_DIR', '')
+# The TEST_LOG_DIR maybe NULL when testimage is added after
+# testdata.json is generated.
+if not test_log_dir:
+test_log_dir = os.path.join(self.td.get('WORKDIR', ''), 
'testimage')
+# Don't use self.td.get('DATETIME'), it's from testdata.json, not
+# up-to-date, and may cause "File exists" when re-reun.
+datetime = datetime.datetime.now().strftime('%Y%m%d%H%M%S')
+ptest_log_dir_link = os.path.join(test_log_dir, 'ptest_log')
+ptest_log_dir = '%s.%s' % (ptest_log_dir_link, datetime)
+ptest_runner_log = os.path.join(ptest_log_dir, 'ptest-runner.log')
+
+status, output =

Re: [OE-core] [PATCH 01/10] oeqa/targetcontrol.py: simplify checking for qemu_use_kvm




On 08/22/2017 04:35 AM, Richard Purdie wrote:

On Mon, 2017-08-21 at 16:02 +0800, Robert Yang wrote:

Ping.


Can you repost this series please? I suspect you've changed the patches


Thanks, I will repost them. And Yes, I had fixed Paul's comments.

// Robert


as per the feedback from Paul but I'd like to see another round of
review before we consider this.

Just repushing is fine for minor changes but more significant things
should be resubmitted.

Cheers,

Richard


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

[OE-core] [PATCH] tiff: Security fixes

2017-08-21 Thread Yi Zhao

Fix CVE-2017-9147, CVE-2017-9936, CVE-2017-10668, CVE-2017-11335

References:
https://nvd.nist.gov/vuln/detail/CVE-2017-9147
https://nvd.nist.gov/vuln/detail/CVE-2017-9936
https://nvd.nist.gov/vuln/detail/CVE-2017-10668
https://nvd.nist.gov/vuln/detail/CVE-2017-11335

Patches from:
CVE-2017-9147:
https://github.com/vadz/libtiff/commit/4d4fa0b68ae9ae038959ee4f69ebe288ec892f06
CVE-2017-9936:
https://github.com/vadz/libtiff/commit/fe8d7165956b88df4837034a9161dc5fd20cf67a
CVE-2017-10688:
https://github.com/vadz/libtiff/commit/6173a57d39e04d68b139f8c1aa499a24dbe74ba1
CVE-2017-11355:
https://github.com/vadz/libtiff/commit/69bfeec247899776b1b396651adb47436e5f1556

Signed-off-by: Yi Zhao 
---
 .../libtiff/files/CVE-2017-10688.patch |  91 +
 .../libtiff/files/CVE-2017-11335.patch |  54 ++
 .../libtiff/files/CVE-2017-9147.patch  | 206 +
 .../libtiff/files/CVE-2017-9936.patch  |  49 +
 meta/recipes-multimedia/libtiff/tiff_4.0.8.bb  |   4 +
 5 files changed, 404 insertions(+)
 create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-10688.patch
 create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-11335.patch
 create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-9147.patch
 create mode 100644 meta/recipes-multimedia/libtiff/files/CVE-2017-9936.patch

diff --git a/meta/recipes-multimedia/libtiff/files/CVE-2017-10688.patch 
b/meta/recipes-multimedia/libtiff/files/CVE-2017-10688.patch
new file mode 100644
index 000..b0db969
--- /dev/null
+++ b/meta/recipes-multimedia/libtiff/files/CVE-2017-10688.patch
@@ -0,0 +1,91 @@
+From 333ba5599e87bd7747516d7863d61764e4ca2d92 Mon Sep 17 00:00:00 2001
+From: Even Rouault 
+Date: Fri, 30 Jun 2017 17:29:44 +
+Subject: [PATCH] * libtiff/tif_dirwrite.c: in
+ TIFFWriteDirectoryTagChecked() functions associated with LONG8/SLONG8
+ data type, replace assertion that the file is BigTIFF, by a non-fatal error.
+ Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2712 Reported by team
+ OWL337
+
+Upstream-Status: Backport
+[https://github.com/vadz/libtiff/commit/6173a57d39e04d68b139f8c1aa499a24dbe74ba1]
+
+CVE: CVE-2017-10688
+
+Signed-off-by: Yi Zhao 
+---
+ ChangeLog  |  8 
+ libtiff/tif_dirwrite.c | 20 
+ 2 files changed, 24 insertions(+), 4 deletions(-)
+
+diff --git a/ChangeLog b/ChangeLog
+index 0240f0b..42eaeb7 100644
+--- a/ChangeLog
 b/ChangeLog
+@@ -1,3 +1,11 @@
++2017-06-30  Even Rouault 
++
++  * libtiff/tif_dirwrite.c: in TIFFWriteDirectoryTagChecked()
++  functions associated with LONG8/SLONG8 data type, replace assertion that
++  the file is BigTIFF, by a non-fatal error.
++  Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2712
++  Reported by team OWL337
++
+ 2017-06-26  Even Rouault 
+ 
+   * libtiff/tif_jbig.c: fix memory leak in error code path of JBIGDecode()
+diff --git a/libtiff/tif_dirwrite.c b/libtiff/tif_dirwrite.c
+index 2967da5..8d6686b 100644
+--- a/libtiff/tif_dirwrite.c
 b/libtiff/tif_dirwrite.c
+@@ -2111,7 +2111,10 @@ TIFFWriteDirectoryTagCheckedLong8(TIFF* tif, uint32* 
ndir, TIFFDirEntry* dir, ui
+ {
+   uint64 m;
+   assert(sizeof(uint64)==8);
+-  assert(tif->tif_flags_BIGTIFF);
++  if( !(tif->tif_flags_BIGTIFF) ) {
++  
TIFFErrorExt(tif->tif_clientdata,"TIFFWriteDirectoryTagCheckedLong8","LONG8 not 
allowed for ClassicTIFF");
++  return(0);
++  }
+   m=value;
+   if (tif->tif_flags_SWAB)
+   TIFFSwabLong8();
+@@ -2124,7 +2127,10 @@ TIFFWriteDirectoryTagCheckedLong8Array(TIFF* tif, 
uint32* ndir, TIFFDirEntry* di
+ {
+   assert(count<0x2000);
+   assert(sizeof(uint64)==8);
+-  assert(tif->tif_flags_BIGTIFF);
++  if( !(tif->tif_flags_BIGTIFF) ) {
++  
TIFFErrorExt(tif->tif_clientdata,"TIFFWriteDirectoryTagCheckedLong8","LONG8 not 
allowed for ClassicTIFF");
++  return(0);
++  }
+   if (tif->tif_flags_SWAB)
+   TIFFSwabArrayOfLong8(value,count);
+   
return(TIFFWriteDirectoryTagData(tif,ndir,dir,tag,TIFF_LONG8,count,count*8,value));
+@@ -2136,7 +2142,10 @@ TIFFWriteDirectoryTagCheckedSlong8(TIFF* tif, uint32* 
ndir, TIFFDirEntry* dir, u
+ {
+   int64 m;
+   assert(sizeof(int64)==8);
+-  assert(tif->tif_flags_BIGTIFF);
++  if( !(tif->tif_flags_BIGTIFF) ) {
++  
TIFFErrorExt(tif->tif_clientdata,"TIFFWriteDirectoryTagCheckedLong8","SLONG8 
not allowed for ClassicTIFF");
++  return(0);
++  }
+   m=value;
+   if (tif->tif_flags_SWAB)
+   TIFFSwabLong8((uint64*)());
+@@ -2149,7 +2158,10 @@ TIFFWriteDirectoryTagCheckedSlong8Array(TIFF* tif, 
uint32* ndir, TIFFDirEntry* d
+ {
+   assert(count<0x2000);
+   assert(sizeof(int64)==8);
+-  assert(tif->tif_flags_BIGTIFF);
++  if(

Re: [OE-core] [PATCH] systemd: don't symlink /etc/resolv.conf if resolved is disabled

2017-08-21 Thread Carlos Alberto Lopez Perez

On 21/08/17 21:05, Carlos Alberto Lopez Perez wrote:
>  * symlinking /etc/resolv.conf to /run/systemd/resolve/resolv.conf
>when resolved is not enabled is wrong, as this prevents network
>manager from handling the resolv.conf file itself and breaking
>DNS resolution.
> 
>See: NetworkManager.conf manpage or https://git.io/v5UJQ
> 
> Signed-off-by: Carlos Alberto Lopez Perez 
> ---
>  meta/recipes-core/systemd/systemd_234.bb | 7 +--
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/meta/recipes-core/systemd/systemd_234.bb 
> b/meta/recipes-core/systemd/systemd_234.bb
> index 4560cf4175..dddad62941 100644
> --- a/meta/recipes-core/systemd/systemd_234.bb
> +++ b/meta/recipes-core/systemd/systemd_234.bb
> @@ -235,12 +235,7 @@ do_install() {
>   if [ -s ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf ]; then
>   ${@bb.utils.contains('PACKAGECONFIG', 'networkd', ':', 'sed -i 
> -e "\$ad /run/systemd/netif/links 0755 root root -" 
> ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf', d)}
>   fi
> - if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true', 'false', 
> d)}; then
> - echo 'L! ${sysconfdir}/resolv.conf - - - - 
> ../run/systemd/resolve/resolv.conf' 
> >>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
> - echo 'd /run/systemd/resolve 0755 root root -' 
> >>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
> - echo 'f /run/systemd/resolve/resolv.conf 0644 root root' 
> >>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
> - ln -s ../run/systemd/resolve/resolv.conf 
> ${D}${sysconfdir}/resolv-conf.systemd
> - else
> + if ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true', 'false', 
> d)}; then
>   sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf - - - 
> - ../run/systemd/resolve/resolv.conf%g" 
> ${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
>   ln -s ../run/systemd/resolve/resolv.conf 
> ${D}${sysconfdir}/resolv-conf.systemd
>   fi
> 

Looking at the previous history it seems symlinking /etc/resolv.conf
when not enabling resolved was done originally to allow updating
resolv.conf on read-only-rootfs filesystems ( commit 7f087f161e ).

So the above patch is not right, as it will break that.

An idea is to symlink /etc/resolv.conf to a different filename in /run
when resolved is not enabled.



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

[OE-core] [PATCH] devtool/standard: set a preferred provider when adding a new recipe with devtool

2017-08-21 Thread juan . m . cruz . alcaraz

From: Juan M Cruz Alcaraz 

A recipe added with "devtool add" requires to be able to take precedence on 
recipes
previously defined with PREFERRED_PROVIDER.

By adding the parameter "--provides" to "devtool add" it is possible to specify
an element to be provided by the recipe. A devtool recipe can override a 
previous
PREFERRED_PROVIDER using the layer configuration file in the workspace.

E.g.
devtool add my-mesa git@git://my-mesa-repository --provides virtual/mesa

[YOCTO #10415]

Signed-off-by: Juan M Cruz Alcaraz 
---
 scripts/lib/devtool/standard.py  | 20 
 scripts/lib/recipetool/create.py |  3 +++
 2 files changed, 23 insertions(+)

diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index ec192238ed..02b4ff4d3b 100644
--- a/scripts/lib/devtool/standard.py
+++ b/scripts/lib/devtool/standard.py
@@ -151,6 +151,8 @@ def add(args, config, basepath, workspace):
 extracmdopts += ' --fetch-dev'
 if args.mirrors:
 extracmdopts += ' --mirrors'
+if args.provides:
+extracmdopts += ' --provides %s' % args.provides
 
 tempdir = tempfile.mkdtemp(prefix='devtool')
 try:
@@ -266,6 +268,23 @@ def add(args, config, basepath, workspace):
 f.write('done\n')
 f.write('}\n')
 
+# Check if the new layer provides recipes whose priorities have been
+# overriden by PREFERRED_PROVIDER.
+recipe_name = rd.getVar('PN')
+provides = rd.getVar('PROVIDES')
+# Search every item defined in PROVIDES
+for recipe_provided in provides.split():
+preferred_provider = 'PREFERRED_PROVIDER_' + recipe_provided
+if rd.getVar(preferred_provider):
+if args.fixed_setup:
+#if we are inside the eSDK add the new PREFERRED_PROVIDER 
in the workspace layer.conf
+layerconf_file = os.path.join(config.workspace_path, 
"conf", "layer.conf")
+with open(layerconf_file, 'a') as f:
+f.write('%s="%s"\n' % (preferred_provider, 
recipe_name))
+else:
+logger.warn('Set \'%s\' in order to use the recipe' % 
preferred_provider)
+break
+
 _add_md5(config, recipename, appendfile)
 
 logger.info('Recipe %s has been automatically created; further editing 
may be required to make it fully functional' % recipefile)
@@ -1810,6 +1829,7 @@ def register_commands(subparsers, context):
 parser_add.add_argument('--also-native', help='Also add native variant 
(i.e. support building recipe for the build host as well as the target 
machine)', action='store_true')
 parser_add.add_argument('--src-subdir', help='Specify subdirectory within 
source tree to use', metavar='SUBDIR')
 parser_add.add_argument('--mirrors', help='Enable PREMIRRORS and MIRRORS 
for source tree fetching (disable by default).', action="store_true")
+parser_add.add_argument('--provides', '-p', help='Specify an alias for the 
item provided by the recipe. E.g. virtual/mesa')
 parser_add.set_defaults(func=add, fixed_setup=context.fixed_setup)
 
 parser_modify = subparsers.add_parser('modify', help='Modify the source 
for an existing recipe',
diff --git a/scripts/lib/recipetool/create.py b/scripts/lib/recipetool/create.py
index e21e2bf298..83c8e4f7b7 100644
--- a/scripts/lib/recipetool/create.py
+++ b/scripts/lib/recipetool/create.py
@@ -607,6 +607,8 @@ def create_recipe(args):
 (stdout, _) = bb.process.run('git rev-parse HEAD', cwd=srctree)
 srcrev = stdout.rstrip()
 lines_before.append('SRCREV = "%s"' % srcrev)
+if args.provides:
+lines_before.append('PROVIDES = "%s"' % args.provides)
 lines_before.append('')
 
 if srcsubdir and not args.binary:
@@ -1158,6 +1160,7 @@ def register_commands(subparsers):
   description='Creates a new recipe 
from a source tree')
 parser_create.add_argument('source', help='Path or URL to source')
 parser_create.add_argument('-o', '--outfile', help='Specify filename for 
recipe to create')
+parser_create.add_argument('-p', '--provides', help='Specify an alias for 
the item provided by the recipe')
 parser_create.add_argument('-m', '--machine', help='Make recipe 
machine-specific as opposed to architecture-specific', action='store_true')
 parser_create.add_argument('-x', '--extract-to', metavar='EXTRACTPATH', 
help='Assuming source is a URL, fetch it and extract it to the directory 
specified as %(metavar)s')
 parser_create.add_argument('-N', '--name', help='Name to use within recipe 
(PN)')
-- 
2.13.2

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

Re: [OE-core] [PATCH 2/2] grub2: fix build with gcc-7

2017-08-21 Thread Khem Raj

On Mon, Aug 21, 2017 at 1:57 PM, Martin Jansa  wrote:
> * build with gcc-7 fails with:
>   | ./config-util.h:1504:48: error: this use of "defined" may not be   
> portable [-Werror=expansion-to-defined]
>   |  || (defined _FORTIFY_SOURCE && 0 < _FORTIFY_SOURCE \
>   |
^~~
>   and we're not building on Apple or BSD, so we should be able
>   to just ignoreit until it's resolved properly in some newer gnulib
>   and imported from gnulib to grub-2
>
> Signed-off-by: Martin Jansa 
> ---
>  meta/recipes-bsp/grub/grub-efi_2.02.bb | 6 ++
>  1 file changed, 6 insertions(+)
>
> diff --git a/meta/recipes-bsp/grub/grub-efi_2.02.bb 
> b/meta/recipes-bsp/grub/grub-efi_2.02.bb
> index b949bebced..45f4c1ed34 100644
> --- a/meta/recipes-bsp/grub/grub-efi_2.02.bb
> +++ b/meta/recipes-bsp/grub/grub-efi_2.02.bb
> @@ -36,6 +36,12 @@ EXTRA_OECONF += "--enable-efiemu=no"
>  # and many other places in the grub code when compiled with some native gcc 
> compilers (specifically, gentoo)
>  CFLAGS_append_class-native = " -Wno-error=trampolines"
>
> +# this comes from gnulib and it's used only for Apple and BSD, so we can 
> ignore it
> +# ./config-util.h:1504:48: error: this use of "defined" may not be portable 
> [-Werror=expansion-to-defined]
> +# || (defined _FORTIFY_SOURCE && 0 < _FORTIFY_SOURCE \
> +#^~~
> +CFLAGS_append_class-native = " -Wno-error=expansion-to-defined"
> +

This workaround seems reasonable but I wonder why it fails on build host
for you. how is your build hosts toolchain configured to generate this
warning. Since you mentioned gcc7 then why doesnt it fail for OE
targets
in same way.

An upstreamable fix would be to break this define into another #if ..
#else macros and define the new macro to 1 or 0 depending upon the
conditions
being tested.

>  do_install_class-native() {
> install -d ${D}${bindir}
> install -m 755 grub-mkimage ${D}${bindir}
> --
> 2.14.1
>
> --
> ___
> 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] ✗ patchtest: failure for hwlatdetect: fix RDEPENDS to avoid QA failures

== Series Details ==

Series: hwlatdetect: fix RDEPENDS to avoid QA failures
Revision: 1
URL   : https://patchwork.openembedded.org/series/8407/
State : failure

== Summary ==


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



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



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

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

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

[OE-core] [PATCH] hwlatdetect: fix RDEPENDS to avoid QA failures

2017-08-21 Thread Alejandro Hernandez

When listing python3 as an RDEPENDS, the image will in fact
contain python3-modules, but the QA check fails to get
RPROVIDERS correctly (since the python3 package does not
actually exist), /usr/bin/python3 is provided by the
python3-core package, so by fixing the RDEPENDS and listing
python3-creo instead of python3, the QA check works correctly
and we avoid failures

Signed-off-by: Alejandro Hernandez 
---
 meta/recipes-rt/rt-tests/hwlatdetect_1.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-rt/rt-tests/hwlatdetect_1.1.bb 
b/meta/recipes-rt/rt-tests/hwlatdetect_1.1.bb
index 60b44a4d258..5f61c4ecddc 100644
--- a/meta/recipes-rt/rt-tests/hwlatdetect_1.1.bb
+++ b/meta/recipes-rt/rt-tests/hwlatdetect_1.1.bb
@@ -22,5 +22,5 @@ do_install() {
 }
 
 FILES_${PN} += 
"${libdir}/python${PYTHON_BASEVERSION}/dist-packages/hwlatdetect.py"
-RDEPENDS_${PN} = "python3 "
+RDEPENDS_${PN} = "python3-core "
 RRECOMMENDS_${PN} = "kernel-module-hwlat-detector"
-- 
2.12.3

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

Re: [OE-core] [PATCH 1/2] apt: Upgrade to 1.2.24

2017-08-21 Thread Aníbal Limón

Here is the diff of the GPL license,

Cheers,
Anibal

On 08/21/2017 04:31 PM, Aníbal Limón wrote:
> The LIC_FILES_CHKSUM changed because the license file now has
> style changes in the text remains GPLv2+.
> 
> The patch Revert-always-run-dpkg-configure-a-at-the-end-of-our
> was updated because now the precision fields use floating
> point numbers.
> 
> Signed-off-by: Aníbal Limón 
> ---
>  .../{apt-native_1.2.12.bb => apt-native_1.2.24.bb} |  0
>  meta/recipes-devtools/apt/apt.inc  |  8 
>  ...ys-run-dpkg-configure-a-at-the-end-of-our.patch | 24 
> +++---
>  .../apt/{apt_1.2.12.bb => apt_1.2.24.bb}   |  0
>  4 files changed, 16 insertions(+), 16 deletions(-)
>  rename meta/recipes-devtools/apt/{apt-native_1.2.12.bb => 
> apt-native_1.2.24.bb} (100%)
>  rename meta/recipes-devtools/apt/{apt_1.2.12.bb => apt_1.2.24.bb} (100%)
> 
> diff --git a/meta/recipes-devtools/apt/apt-native_1.2.12.bb 
> b/meta/recipes-devtools/apt/apt-native_1.2.24.bb
> similarity index 100%
> rename from meta/recipes-devtools/apt/apt-native_1.2.12.bb
> rename to meta/recipes-devtools/apt/apt-native_1.2.24.bb
> diff --git a/meta/recipes-devtools/apt/apt.inc 
> b/meta/recipes-devtools/apt/apt.inc
> index 30263708444..f1cde3068da 100644
> --- a/meta/recipes-devtools/apt/apt.inc
> +++ b/meta/recipes-devtools/apt/apt.inc
> @@ -2,7 +2,7 @@ SUMMARY = "Advanced front-end for dpkg"
>  LICENSE = "GPLv2.0+"
>  SECTION = "base"
>  
> -SRC_URI = 
> "http://snapshot.debian.org/archive/debian/20160526T162943Z/pool/main/a/${BPN}/${BPN}_${PV}.tar.xz
>  \
> +SRC_URI = 
> "http://archive.ubuntu.com/ubuntu/pool/main/a/${BPN}/${BPN}_${PV}.tar.xz \
> file://use-host.patch \
> file://makerace.patch \
> file://no-nls-dpkg.patch \
> @@ -14,9 +14,9 @@ SRC_URI = 
> "http://snapshot.debian.org/archive/debian/20160526T162943Z/pool/main/
> 
> file://0001-environment.mak-musl-based-systems-can-generate-shar.patch \
> file://0001-apt-1.2.12-Fix-musl-build.patch \
> "
> -SRC_URI[md5sum] = "80f6f0ef110a45a7e5af8a9d233fb0e7"
> -SRC_URI[sha256sum] = 
> "e820d27cba73476df4abcff27dadd1b5847474bfe85f7e9202a9a07526973ea6"
> -LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=0636e73ff0215e8d672dc4c32c317bb3"
> +SRC_URI[md5sum] = "ce8f9ab11f4fd0a08ec73eaffd75c8f0"
> +SRC_URI[sha256sum] = 
> "fa1311a9ce00e72379a0a3bc6d240ba30c0968cfbbb3472859e50b99e24e9598"
> +LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
>  # the package is taken from snapshots.debian.org; that source is static and 
> goes stale
>  # so we check the latest upstream from a directory that does get updated
> diff --git 
> a/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
>  
> b/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
> index b3a883bae88..734ba00d4f2 100644
> --- 
> a/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
> +++ 
> b/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
> @@ -22,10 +22,10 @@ Signed-off-by: Roy Li 
>   3 files changed, 11 insertions(+), 18 deletions(-)
>  
>  diff --git a/apt-pkg/deb/dpkgpm.cc b/apt-pkg/deb/dpkgpm.cc
> -index 834cb0e..84ded3a 100644
> +index 533d9b367..6ce81bbd9 100644
>  --- a/apt-pkg/deb/dpkgpm.cc
>  +++ b/apt-pkg/deb/dpkgpm.cc
> -@@ -1037,12 +1037,6 @@ void pkgDPkgPM::BuildPackagesProgressMap()
> +@@ -1041,12 +1041,6 @@ void pkgDPkgPM::BuildPackagesProgressMap()
>PackagesTotal++;
> }
>  }
> @@ -38,7 +38,7 @@ index 834cb0e..84ded3a 100644
>   }
>   
> /*}}}*/
>   bool pkgDPkgPM::Go(int StatusFd)
> -@@ -1250,8 +1244,9 @@ bool pkgDPkgPM::Go(APT::Progress::PackageManager 
> *progress)
> +@@ -1268,8 +1262,9 @@ bool pkgDPkgPM::Go(APT::Progress::PackageManager 
> *progress)
>   
>  // support subpressing of triggers processing for special
>  // cases like d-i that runs the triggers handling manually
> @@ -50,7 +50,7 @@ index 834cb0e..84ded3a 100644
>   
>  // for the progress
>  diff --git a/test/integration/test-apt-progress-fd-deb822 
> b/test/integration/test-apt-progress-fd-deb822
> -index 58fd732..3359762 100755
> +index a8d59608d..0c6a9bbbf 100755
>  --- a/test/integration/test-apt-progress-fd-deb822
>  +++ b/test/integration/test-apt-progress-fd-deb822
>  @@ -27,36 +27,36 @@ Message: Installing testing (amd64)
> @@ -69,19 +69,19 @@ index 58fd732..3359762 100755
>   
>   Status: progress
>   Package: testing:amd64
> --Percent: 50
> -+Percent: 60
> +-Percent: 50.
> ++Percent: 60.
>   Message: Preparing to configure testing (amd64)
>   
>   Status: progress
> --Percent: 50
> -+Percent: 60
> +-Percent: 50.
> ++Percent: 60.
>   Message: Running dpkg
>   
>   Status:

[OE-core] [PATCH 1/2] apt: Upgrade to 1.2.24

2017-08-21 Thread Aníbal Limón

The LIC_FILES_CHKSUM changed because the license file now has
style changes in the text remains GPLv2+.

The patch Revert-always-run-dpkg-configure-a-at-the-end-of-our
was updated because now the precision fields use floating
point numbers.

Signed-off-by: Aníbal Limón 
---
 .../{apt-native_1.2.12.bb => apt-native_1.2.24.bb} |  0
 meta/recipes-devtools/apt/apt.inc  |  8 
 ...ys-run-dpkg-configure-a-at-the-end-of-our.patch | 24 +++---
 .../apt/{apt_1.2.12.bb => apt_1.2.24.bb}   |  0
 4 files changed, 16 insertions(+), 16 deletions(-)
 rename meta/recipes-devtools/apt/{apt-native_1.2.12.bb => 
apt-native_1.2.24.bb} (100%)
 rename meta/recipes-devtools/apt/{apt_1.2.12.bb => apt_1.2.24.bb} (100%)

diff --git a/meta/recipes-devtools/apt/apt-native_1.2.12.bb 
b/meta/recipes-devtools/apt/apt-native_1.2.24.bb
similarity index 100%
rename from meta/recipes-devtools/apt/apt-native_1.2.12.bb
rename to meta/recipes-devtools/apt/apt-native_1.2.24.bb
diff --git a/meta/recipes-devtools/apt/apt.inc 
b/meta/recipes-devtools/apt/apt.inc
index 30263708444..f1cde3068da 100644
--- a/meta/recipes-devtools/apt/apt.inc
+++ b/meta/recipes-devtools/apt/apt.inc
@@ -2,7 +2,7 @@ SUMMARY = "Advanced front-end for dpkg"
 LICENSE = "GPLv2.0+"
 SECTION = "base"
 
-SRC_URI = 
"http://snapshot.debian.org/archive/debian/20160526T162943Z/pool/main/a/${BPN}/${BPN}_${PV}.tar.xz
 \
+SRC_URI = 
"http://archive.ubuntu.com/ubuntu/pool/main/a/${BPN}/${BPN}_${PV}.tar.xz \
file://use-host.patch \
file://makerace.patch \
file://no-nls-dpkg.patch \
@@ -14,9 +14,9 @@ SRC_URI = 
"http://snapshot.debian.org/archive/debian/20160526T162943Z/pool/main/

file://0001-environment.mak-musl-based-systems-can-generate-shar.patch \
file://0001-apt-1.2.12-Fix-musl-build.patch \
"
-SRC_URI[md5sum] = "80f6f0ef110a45a7e5af8a9d233fb0e7"
-SRC_URI[sha256sum] = 
"e820d27cba73476df4abcff27dadd1b5847474bfe85f7e9202a9a07526973ea6"
-LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=0636e73ff0215e8d672dc4c32c317bb3"
+SRC_URI[md5sum] = "ce8f9ab11f4fd0a08ec73eaffd75c8f0"
+SRC_URI[sha256sum] = 
"fa1311a9ce00e72379a0a3bc6d240ba30c0968cfbbb3472859e50b99e24e9598"
+LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263"
 
 # the package is taken from snapshots.debian.org; that source is static and 
goes stale
 # so we check the latest upstream from a directory that does get updated
diff --git 
a/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
 
b/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
index b3a883bae88..734ba00d4f2 100644
--- 
a/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
+++ 
b/meta/recipes-devtools/apt/apt/0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch
@@ -22,10 +22,10 @@ Signed-off-by: Roy Li 
  3 files changed, 11 insertions(+), 18 deletions(-)
 
 diff --git a/apt-pkg/deb/dpkgpm.cc b/apt-pkg/deb/dpkgpm.cc
-index 834cb0e..84ded3a 100644
+index 533d9b367..6ce81bbd9 100644
 --- a/apt-pkg/deb/dpkgpm.cc
 +++ b/apt-pkg/deb/dpkgpm.cc
-@@ -1037,12 +1037,6 @@ void pkgDPkgPM::BuildPackagesProgressMap()
+@@ -1041,12 +1041,6 @@ void pkgDPkgPM::BuildPackagesProgressMap()
 PackagesTotal++;
}
 }
@@ -38,7 +38,7 @@ index 834cb0e..84ded3a 100644
  }
  
/*}}}*/
  bool pkgDPkgPM::Go(int StatusFd)
-@@ -1250,8 +1244,9 @@ bool pkgDPkgPM::Go(APT::Progress::PackageManager 
*progress)
+@@ -1268,8 +1262,9 @@ bool pkgDPkgPM::Go(APT::Progress::PackageManager 
*progress)
  
 // support subpressing of triggers processing for special
 // cases like d-i that runs the triggers handling manually
@@ -50,7 +50,7 @@ index 834cb0e..84ded3a 100644
  
 // for the progress
 diff --git a/test/integration/test-apt-progress-fd-deb822 
b/test/integration/test-apt-progress-fd-deb822
-index 58fd732..3359762 100755
+index a8d59608d..0c6a9bbbf 100755
 --- a/test/integration/test-apt-progress-fd-deb822
 +++ b/test/integration/test-apt-progress-fd-deb822
 @@ -27,36 +27,36 @@ Message: Installing testing (amd64)
@@ -69,19 +69,19 @@ index 58fd732..3359762 100755
  
  Status: progress
  Package: testing:amd64
--Percent: 50
-+Percent: 60
+-Percent: 50.
++Percent: 60.
  Message: Preparing to configure testing (amd64)
  
  Status: progress
--Percent: 50
-+Percent: 60
+-Percent: 50.
++Percent: 60.
  Message: Running dpkg
  
  Status: progress
  Package: testing:amd64
--Percent: 50
-+Percent: 60
+-Percent: 50.
++Percent: 60.
  Message: Configuring testing (amd64)
  
  Status: progress
@@ -98,7 +98,7 @@ index 58fd732..3359762 100755
  
  Status: progress
 diff --git a/test/integration/test-no-fds-leaked-to-maintainer-scripts

[OE-core] [PATCH 2/2] dpkg: Upgrade to 1.18.24

2017-08-21 Thread Aníbal Limón

Patches rebased due to don't apply, no major changes,

- 0002-Adapt-to-linux-wrs-kernel-version-which-has-characte.patch
- arch_pm.patch
- noman.patch

Patches related to move ostable/triplettable insida data/ostable and
data/tupletable instead also needs to comply the new format of the
tables for arch detection.

- 0006-add-musleabi-to-known-target-tripets.patch
- add_armeb_triplet_entry.patch

And finally a patch to avoid usage --clamp-mtime in tar needs to be
modified because the dpkg-deb internal API changed.

- 0007-dpkg-deb-build.c-Remove-usage-of-clamp-mtime-in-tar.patch

Signed-off-by: Aníbal Limón 
---
 ...nux-wrs-kernel-version-which-has-characte.patch | 12 ++---
 ...0006-add-musleabi-to-known-target-tripets.patch | 57 +++---
 ...uild.c-Remove-usage-of-clamp-mtime-in-tar.patch | 21 
 .../dpkg/dpkg/add_armeb_triplet_entry.patch| 30 ++--
 meta/recipes-devtools/dpkg/dpkg/arch_pm.patch  | 19 +---
 meta/recipes-devtools/dpkg/dpkg/noman.patch| 18 +--
 .../dpkg/{dpkg_1.18.10.bb => dpkg_1.18.24.bb}  |  6 +--
 7 files changed, 89 insertions(+), 74 deletions(-)
 rename meta/recipes-devtools/dpkg/{dpkg_1.18.10.bb => dpkg_1.18.24.bb} (77%)

diff --git 
a/meta/recipes-devtools/dpkg/dpkg/0002-Adapt-to-linux-wrs-kernel-version-which-has-characte.patch
 
b/meta/recipes-devtools/dpkg/dpkg/0002-Adapt-to-linux-wrs-kernel-version-which-has-characte.patch
index 231a6a2909d..9fe0ca76002 100644
--- 
a/meta/recipes-devtools/dpkg/dpkg/0002-Adapt-to-linux-wrs-kernel-version-which-has-characte.patch
+++ 
b/meta/recipes-devtools/dpkg/dpkg/0002-Adapt-to-linux-wrs-kernel-version-which-has-characte.patch
@@ -13,13 +13,13 @@ Upstream-Status: Inappropriate [embedded specific]
  1 file changed, 2 insertions(+), 4 deletions(-)
 
 diff --git a/lib/dpkg/parsehelp.c b/lib/dpkg/parsehelp.c
-index 79b2908..7758aa5 100644
+index 453077fd9..f42ea2882 100644
 --- a/lib/dpkg/parsehelp.c
 +++ b/lib/dpkg/parsehelp.c
-@@ -235,14 +235,12 @@ parseversion(struct dpkg_version *rversion, const char 
*string,
- 
-   /* XXX: Would be faster to use something like cisversion and cisrevision. */
+@@ -243,14 +243,12 @@ parseversion(struct dpkg_version *rversion, const char 
*string,
ptr = rversion->version;
+   if (!*ptr)
+ return dpkg_put_error(err, _("version number is empty"));
 -  if (*ptr && !c_isdigit(*ptr++))
 -return dpkg_put_warn(err, _("version number does not start with digit"));
for (; *ptr; ptr++) {
@@ -33,6 +33,6 @@ index 79b2908..7758aa5 100644
return dpkg_put_warn(err, _("invalid character in revision number"));
}
  
--- 
-2.1.4
 
+-- 
+2.11.0
diff --git 
a/meta/recipes-devtools/dpkg/dpkg/0006-add-musleabi-to-known-target-tripets.patch
 
b/meta/recipes-devtools/dpkg/dpkg/0006-add-musleabi-to-known-target-tripets.patch
index a6b00880ced..d929466b702 100644
--- 
a/meta/recipes-devtools/dpkg/dpkg/0006-add-musleabi-to-known-target-tripets.patch
+++ 
b/meta/recipes-devtools/dpkg/dpkg/0006-add-musleabi-to-known-target-tripets.patch
@@ -6,37 +6,36 @@ Subject: [PATCH] add musleabi to known target tripets
 helps compiling dpkg for musl/arm-softfloat
 
 Signed-off-by: Khem Raj 
+Signed-off-by: Aníbal Limón 
 ---
-Upstream-Status: Pending
-
- ostable  | 1 +
- triplettable | 1 +
+ data/ostable| 1 +
+ data/tupletable | 1 +
  2 files changed, 2 insertions(+)
 
-diff --git a/ostable b/ostable
-index 3bb6819..d0ffdc7 100644
 a/ostable
-+++ b/ostable
-@@ -15,6 +15,7 @@
- uclibceabi-linux  linux-uclibceabilinux[^-]*-uclibceabi
- uclibc-linux  linux-uclibclinux[^-]*-uclibc
- musleabihf-linux  linux-musleabihflinux[^-]*-musleabihf
-+musleabi-linuxlinux-musleabi  linux[^-]*-musleabi
- musl-linuxlinux-musl  linux[^-]*-musl
- gnueabihf-linux   linux-gnueabihf linux[^-]*-gnueabihf
- gnueabi-linux linux-gnueabi   linux[^-]*-gnueabi
-diff --git a/triplettable b/triplettable
-index 1213584..70d24c1 100644
 a/triplettable
-+++ b/triplettable
-@@ -6,6 +6,7 @@
- uclibceabi-linux-arm  uclibc-linux-armel
- uclibc-linux-uclibc-linux-
- musleabihf-linux-arm  musl-linux-armhf
-+musleabi-linux-armmusl-linux-armel
- musl-linux-  musl-linux-
- gnueabihf-linux-arm   armhf
- gnueabi-linux-arm armel
+diff --git a/data/ostable b/data/ostable
+index 99c1f889d..be6434271 100644
+--- a/data/ostable
 b/data/ostable
+@@ -17,6 +17,7 @@
+ eabi-uclibc-linux linux-uclibceabilinux[^-]*-uclibceabi
+ base-uclibc-linux linux-uclibclinux[^-]*-uclibc
+ eabihf-musl-linux linux-musleabihflinux[^-]*-musleabihf
++eabi-musl-linux   linux-musleabi  linux[^-]*-musleabi
+ base-musl-linux   linux-musl  linux[^-]*-musl
+ eabihf-gnu-linux  linux-gnueabihf linux[^-]*-gnueabihf
+

Re: [OE-core] [PATCHv2] insane.bbclass: write QA issues to log file only when they are in ERROR_QA or WARN_QA

> You could do "grep -v version-going-backwards qa.log" I guess?

In theory yes, in practice the same jenkins jobs are building different
DISTROs or different Yocto releases with different QA flags enabled, so I
would end up with using bitbke -e to find
WARN_QA and ERROR_QA for given build and then filter only those from qa.log.

I can still do it outside OE, I just didn't realize that there are reasons
for not wanting the levels in the log file (and I still don't know why it's
a good thing not to have them).

Regards,

On Mon, Aug 21, 2017 at 11:23 PM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Mon, 2017-08-21 at 23:13 +0200, Martin Jansa wrote:
> > > all messages are put into the log but at differing log levels.
> >
> > But there aren't the "log levels" in the file (as NOTE, WARN, ERROR)
> > now, it writes only P, error message and type of QA check (not the
> > selected severity of it, like bb.error, bb.warn, bb.note used in the
> > function for normal output).
> >
> > See the function above package_qa_handle_error:
> >
> > def package_qa_write_error(type, error, d):
> > logfile = d.getVar('QA_LOGFILE')
> > if logfile:
> > p = d.getVar('P')
> > with open(logfile, "a+") as f:
> > f.write("%s: %s [%s]\n" % (p, error, type))
> >
>
> Sorry, I misread your earlier message and assumed it was logging the
> level already. I've spent too long staring at bitbake server bugs :/.
>
> I'm still torn on this, I can see why qa.log makes sense to contain all
> the qa issues found and then the WARN/ERROR levels filter the console
> output (and ultimately the bitbake exit code). I can also see why in
> general we'd not want "levels" in the logfile, its more of a console
> issue.
>
> You could do "grep -v version-going-backwards qa.log" I guess?
>
> Cheers,
>
> Richard
>
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCHv2] insane.bbclass: write QA issues to log file only when they are in ERROR_QA or WARN_QA

On Mon, 2017-08-21 at 23:13 +0200, Martin Jansa wrote:
> > all messages are put into the log but at differing log levels.
> 
> But there aren't the "log levels" in the file (as NOTE, WARN, ERROR)
> now, it writes only P, error message and type of QA check (not the
> selected severity of it, like bb.error, bb.warn, bb.note used in the
> function for normal output).
> 
> See the function above package_qa_handle_error:
> 
> def package_qa_write_error(type, error, d):
>     logfile = d.getVar('QA_LOGFILE')
>     if logfile:
>         p = d.getVar('P')
>         with open(logfile, "a+") as f:
>             f.write("%s: %s [%s]\n" % (p, error, type))
> 

Sorry, I misread your earlier message and assumed it was logging the
level already. I've spent too long staring at bitbake server bugs :/.

I'm still torn on this, I can see why qa.log makes sense to contain all
the qa issues found and then the WARN/ERROR levels filter the console
output (and ultimately the bitbake exit code). I can also see why in
general we'd not want "levels" in the logfile, its more of a console
issue.

You could do "grep -v version-going-backwards qa.log" I guess?

Cheers,

Richard

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

Re: [OE-core] [PATCHv2] insane.bbclass: write QA issues to log file only when they are in ERROR_QA or WARN_QA

> all messages are put into the log but at differing log levels.

But there aren't the "log levels" in the file (as NOTE, WARN, ERROR) now,
it writes only P, error message and type of QA check (not the selected
severity of it, like bb.error, bb.warn, bb.note used in the function for
normal output).

See the function above package_qa_handle_error:

def package_qa_write_error(type, error, d):
logfile = d.getVar('QA_LOGFILE')
if logfile:
p = d.getVar('P')
with open(logfile, "a+") as f:
f.write("%s: %s [%s]\n" % (p, error, type))


On Mon, Aug 21, 2017 at 11:07 PM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Mon, 2017-08-21 at 22:56 +0200, Martin Jansa wrote:
> > * QA check which aren't included in WARN_QA and ERROR_QA are shown
> >   during the build only as NOTE message (not shown at all with
> > default
> >   knotty setting), so it might be surprising to see them later in
> > qa.log
> >   file
> >
> > Signed-off-by: Martin Jansa 
> > ---
> >  meta/classes/insane.bbclass | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
>
> I've just been having a look at this and I think its by design, all
> messages are put into the log but at differing log levels. I think the
> correct thing to do may be to filter it as you proposed in your CI
> system.
>
> Any other opinions?
>
> Cheers,
>
> Richard
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [oe-commits] [openembedded-core] 01/02: package.bbclass: Restore functionality to detect RPM dependencies

On Mon, 2017-08-21 at 11:00 +0200, Martin Jansa wrote:
> This seems to find a many more missed dependencies which is good
> thing.
> 
> There is +- 20 failures found in meta-oe recipes and there is still
> at least one in oe-core:
> 
> ERROR: nativesdk-libcheck-0.10.0-r0 do_package_qa: QA Issue:
> /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/checkmk
> contained in package nativesdk-libcheck requires /usr/local/oecore-
> x86_64/sysroots/x86_64-oesdk-linux/usr/bin/gawk, but no providers
> found in RDEPENDS_nativesdk-libcheck? [file-rdeps]
> 
> I wonder why this one wasn't catched by oe-core autobuilder.

At a guess, nativesdk are excluded from world so nothing in OE-Core
likely depends on nativesdk-libcheck. Thanks for the patch, you beat me
to it!

Cheers,

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

Re: [OE-core] [PATCHv2] insane.bbclass: write QA issues to log file only when they are in ERROR_QA or WARN_QA

On Mon, 2017-08-21 at 22:56 +0200, Martin Jansa wrote:
> * QA check which aren't included in WARN_QA and ERROR_QA are shown
>   during the build only as NOTE message (not shown at all with
> default
>   knotty setting), so it might be surprising to see them later in
> qa.log
>   file
> 
> Signed-off-by: Martin Jansa 
> ---
>  meta/classes/insane.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

I've just been having a look at this and I think its by design, all
messages are put into the log but at differing log levels. I think the
correct thing to do may be to filter it as you proposed in your CI
system.

Any other opinions?

Cheers,

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

[OE-core] [PATCH 2/2] grub2: fix build with gcc-7

* build with gcc-7 fails with:
  | ./config-util.h:1504:48: error: this use of "defined" may not be   portable 
[-Werror=expansion-to-defined]
  |  || (defined _FORTIFY_SOURCE && 0 < _FORTIFY_SOURCE \
  | ^~~
  and we're not building on Apple or BSD, so we should be able
  to just ignoreit until it's resolved properly in some newer gnulib
  and imported from gnulib to grub-2

Signed-off-by: Martin Jansa 
---
 meta/recipes-bsp/grub/grub-efi_2.02.bb | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/meta/recipes-bsp/grub/grub-efi_2.02.bb 
b/meta/recipes-bsp/grub/grub-efi_2.02.bb
index b949bebced..45f4c1ed34 100644
--- a/meta/recipes-bsp/grub/grub-efi_2.02.bb
+++ b/meta/recipes-bsp/grub/grub-efi_2.02.bb
@@ -36,6 +36,12 @@ EXTRA_OECONF += "--enable-efiemu=no"
 # and many other places in the grub code when compiled with some native gcc 
compilers (specifically, gentoo)
 CFLAGS_append_class-native = " -Wno-error=trampolines"
 
+# this comes from gnulib and it's used only for Apple and BSD, so we can 
ignore it
+# ./config-util.h:1504:48: error: this use of "defined" may not be portable 
[-Werror=expansion-to-defined]
+# || (defined _FORTIFY_SOURCE && 0 < _FORTIFY_SOURCE \
+#^~~
+CFLAGS_append_class-native = " -Wno-error=expansion-to-defined"
+
 do_install_class-native() {
install -d ${D}${bindir}
install -m 755 grub-mkimage ${D}${bindir}
-- 
2.14.1

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

[OE-core] [PATCH 1/2] squashfs: fix build with glibc-2.26

Signed-off-by: Martin Jansa 
---
 .../squashfs-tools-4.3-sysmacros.patch | 32 ++
 .../squashfs-tools/squashfs-tools_git.bb   |  1 +
 2 files changed, 33 insertions(+)
 create mode 100644 
meta/recipes-devtools/squashfs-tools/squashfs-tools/squashfs-tools-4.3-sysmacros.patch

diff --git 
a/meta/recipes-devtools/squashfs-tools/squashfs-tools/squashfs-tools-4.3-sysmacros.patch
 
b/meta/recipes-devtools/squashfs-tools/squashfs-tools/squashfs-tools-4.3-sysmacros.patch
new file mode 100644
index 00..39521a7d8b
--- /dev/null
+++ 
b/meta/recipes-devtools/squashfs-tools/squashfs-tools/squashfs-tools-4.3-sysmacros.patch
@@ -0,0 +1,32 @@
+From 
https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-fs/squashfs-tools/files/squashfs-tools-4.3-sysmacros.patch
+
+Signed-off-by: Martin Jansa 
+
+Upstream-Status: Pending
+
+
+sys/types.h might not always include sys/sysmacros.h for major/minor/makedev
+
+--- a/squashfs-tools/mksquashfs.c
 b/squashfs-tools/mksquashfs.c
+@@ -59,6 +59,7 @@
+ #else
+ #include 
+ #include 
++#include 
+ #endif
+ 
+ #include "squashfs_fs.h"
+--- a/squashfs-tools/unsquashfs.c
 b/squashfs-tools/unsquashfs.c
+@@ -38,6 +38,10 @@
+ #include 
+ #include 
+ 
++#ifdef linux
++#include 
++#endif
++
+ struct cache *fragment_cache, *data_cache;
+ struct queue *to_reader, *to_inflate, *to_writer, *from_writer;
+ pthread_t *thread, *inflator_thread;
diff --git a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb 
b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
index 4f68d01131..0f991706c1 100644
--- a/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
+++ b/meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb
@@ -13,6 +13,7 @@ SRCREV = "9c1db6d13a51a2e009f0027ef336ce03624eac0d"
 SRC_URI = "git://github.com/plougher/squashfs-tools.git;protocol=https \
http://downloads.sourceforge.net/sevenzip/lzma465.tar.bz2;name=lzma 
\

file://0001-mksquashfs.c-get-inline-functions-work-with-C99.patch;striplevel=2 \
+   file://squashfs-tools-4.3-sysmacros.patch;striplevel=2 \
file://fix-compat.patch \
 "
 UPSTREAM_VERSION_UNKNOWN = "1"
-- 
2.14.1

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

[OE-core] [PATCH] libcheck: fix file-rdeps QA issue

* Fixes:
  ERROR: nativesdk-libcheck-0.10.0-r0 do_package_qa: QA Issue: 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/checkmk contained 
in package nativesdk-libcheck requires 
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/gawk, but no 
providers found in RDEPENDS_nativesdk-libcheck? [file-rdeps]

Signed-off-by: Martin Jansa 
---
 meta/recipes-support/libcheck/libcheck_0.10.0.bb | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/recipes-support/libcheck/libcheck_0.10.0.bb 
b/meta/recipes-support/libcheck/libcheck_0.10.0.bb
index 4db2d7528c..9d34198a96 100644
--- a/meta/recipes-support/libcheck/libcheck_0.10.0.bb
+++ b/meta/recipes-support/libcheck/libcheck_0.10.0.bb
@@ -20,6 +20,5 @@ CACHED_CONFIGUREVARS += "ac_cv_path_AWK_PATH=${bindir}/gawk"
 RREPLACES_${PN} = "check (<= 0.9.5)"
 RDEPENDS_${PN} += "gawk"
 RDEPENDS_${PN}_class-native = ""
-RDEPENDS_${PN}_class-nativesdk = ""
 
 BBCLASSEXTEND = "native nativesdk"
-- 
2.14.1

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

[OE-core] [PATCHv2] insane.bbclass: write QA issues to log file only when they are in ERROR_QA or WARN_QA

* QA check which aren't included in WARN_QA and ERROR_QA are shown
  during the build only as NOTE message (not shown at all with default
  knotty setting), so it might be surprising to see them later in qa.log
  file

Signed-off-by: Martin Jansa 
---
 meta/classes/insane.bbclass | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index b7177c9b32..44e4a01c92 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -184,12 +184,13 @@ def package_qa_write_error(type, error, d):
 f.write("%s: %s [%s]\n" % (p, error, type))
 
 def package_qa_handle_error(error_class, error_msg, d):
-package_qa_write_error(error_class, error_msg, d)
 if error_class in (d.getVar("ERROR_QA") or "").split():
+package_qa_write_error(error_class, error_msg, d)
 bb.error("QA Issue: %s [%s]" % (error_msg, error_class))
 d.setVar("QA_SANE", False)
 return False
 elif error_class in (d.getVar("WARN_QA") or "").split():
+package_qa_write_error(error_class, error_msg, d)
 bb.warn("QA Issue: %s [%s]" % (error_msg, error_class))
 else:
 bb.note("QA Issue: %s [%s]" % (error_msg, error_class))
-- 
2.14.1

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

Re: [OE-core] [PATCH 01/10] oeqa/targetcontrol.py: simplify checking for qemu_use_kvm

On Mon, 2017-08-21 at 16:02 +0800, Robert Yang wrote:
> Ping.

Can you repost this series please? I suspect you've changed the patches
as per the feedback from Paul but I'd like to see another round of
review before we consider this.

Just repushing is fine for minor changes but more significant things
should be resubmitted.

Cheers,

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

[OE-core] [PATCH v3] linux-yocto: introduce 4.12 recipes

The 4.12 kernel will be the default/reference for the fall 2017
release.

These recipes represent the introduction of 4.12.7 + related kernel
meta data. Existing functionality has been validated against this
new kernel version, and older versions will be removed in separate
commits.

Signed-off-by: Bruce Ashfield 
---

v2: Adjusting the SRCREVs to fix a patch that no longer needed to be applied.

v3: fix x86-32 perf build failure

Bruce

 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   | 38 +++
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb | 25 
 meta/recipes-kernel/linux/linux-yocto_4.12.bb  | 44 ++
 3 files changed, 107 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.12.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
new file mode 100644
index ..de1fd935db2d
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -0,0 +1,38 @@
+KBRANCH ?= "standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_meta ?= "8a1c969d10005a90edad09ed6f57f1482c9196a5"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine 
\
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.12.7"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
new file mode 100644
index ..c69aa593ac16
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -0,0 +1,25 @@
+KBRANCH ?= "standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.12.7"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_meta ?= "8a1c969d10005a90edad09ed6f57f1482c9196a5"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine 
\
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "(qemux86$)"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
new file mode 100644
index ..d491a526cd76
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -0,0 +1,44 @@
+KBRANCH ?= "standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "standard/qemuarm64"
+KBRANCH_qemumips ?= "standard/mti-malta32"
+KBRANCH_qemuppc  ?= "standard/qemuppc"
+KBRANCH_qemux86  ?= "standard/base"
+KBRANCH_qemux86-64 ?= "standard/base"
+KBRANCH_qemumips64 ?= "standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "786a121709203e5597f9c9d20f48ad22fa1bf869"
+SRCREV_machine_qemuarm64 ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_machine_qemumips ?= "eeb9e31130e6fdf23d495d2c30f9010b45435147"
+SRCREV_machine_qemuppc ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_machine_qemux86 ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_machine_qemux86-64 ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_machine_qemumips64 ?= "7b5cb0054a88b1dd5f8d68fb1c5183c17a806faa"
+SRCREV_machine ?= "57af599929263e7bb6f2f369c9e4bc1e440528a9"
+SRCREV_meta ?= "8a1c969d10005a90edad09ed6f57f1482c9196a5"
+
+SRC_URI =

[OE-core] [PATCH] systemd: don't symlink /etc/resolv.conf if resolved is disabled

2017-08-21 Thread Carlos Alberto Lopez Perez

 * symlinking /etc/resolv.conf to /run/systemd/resolve/resolv.conf
   when resolved is not enabled is wrong, as this prevents network
   manager from handling the resolv.conf file itself and breaking
   DNS resolution.

   See: NetworkManager.conf manpage or https://git.io/v5UJQ

Signed-off-by: Carlos Alberto Lopez Perez 
---
 meta/recipes-core/systemd/systemd_234.bb | 7 +--
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/meta/recipes-core/systemd/systemd_234.bb 
b/meta/recipes-core/systemd/systemd_234.bb
index 4560cf4175..dddad62941 100644
--- a/meta/recipes-core/systemd/systemd_234.bb
+++ b/meta/recipes-core/systemd/systemd_234.bb
@@ -235,12 +235,7 @@ do_install() {
if [ -s ${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf ]; then
${@bb.utils.contains('PACKAGECONFIG', 'networkd', ':', 'sed -i 
-e "\$ad /run/systemd/netif/links 0755 root root -" 
${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf', d)}
fi
-   if ! ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true', 'false', 
d)}; then
-   echo 'L! ${sysconfdir}/resolv.conf - - - - 
../run/systemd/resolve/resolv.conf' >>${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
-   echo 'd /run/systemd/resolve 0755 root root -' 
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
-   echo 'f /run/systemd/resolve/resolv.conf 0644 root root' 
>>${D}${exec_prefix}/lib/tmpfiles.d/systemd.conf
-   ln -s ../run/systemd/resolve/resolv.conf 
${D}${sysconfdir}/resolv-conf.systemd
-   else
+   if ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'true', 'false', 
d)}; then
sed -i -e "s%^L! /etc/resolv.conf.*$%L! /etc/resolv.conf - - - 
- ../run/systemd/resolve/resolv.conf%g" 
${D}${exec_prefix}/lib/tmpfiles.d/etc.conf
ln -s ../run/systemd/resolve/resolv.conf 
${D}${sysconfdir}/resolv-conf.systemd
fi
-- 
2.11.0

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

Re: [OE-core] [meta-oe][PATCH] Dhrystone: add recipe 2.1

2017-08-21 Thread Khem Raj

On Mon, Aug 21, 2017 at 5:35 AM, Jussi Kukkonen
 wrote:
> On 21 August 2017 at 13:23, Jose Alarcon  wrote:
>>
>> Dhrystone is a synthetic computing benchmark program developed
>> in 1984 by Reinhold P. Weicker intended to be representative of
>> system (integer) programming.
>>
>> https://en.wikipedia.org/wiki/Dhrystone
>>
>> Signed-off-by: Jose Alarcon 
>> ---
>>  .../dhrystone/dhrystone-2.1/dhrystone.patch| 81
>> ++
>>  .../recipes-benchmark/dhrystone/dhrystone_2.1.bb   | 26 +++
>>  2 files changed, 107 insertions(+)
>>  create mode 100644
>> meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/dhrystone.patch
>>  create mode 100644 meta-oe/recipes-benchmark/dhrystone/dhrystone_2.1.bb
>
>
> Hi,
>
> Please send meta-oe patches to openembedded-de...@lists.openembedded.org.
>
> Also this part is unlikely to be welcome on oe-devel either:
>> LICENSE = "Proprietary"
>
> I think I remember seeing a dhrystone recipe submission with an open source
> license (NCSA maybe?) last year .

https://patchwork.openembedded.org/patch/129975/

a v2 was expected, which I cant find so it never got applied. if you
are interested rework the v1 and test it out. Submit a v2 and we can
take it further along the line.

>
> Cheers,
>   Jussi
>
> --
> ___
> 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 v2] oe/path.py: copyhardlinktree: don't overwrite existing symlinks

2017-08-21 Thread Ioan-Adrian Ratiu

Before GNU tar 1.24, only the archive creation command had the '-h'
argument to preserve and follow symlinks. After >= 1.24 via commit
14efeb9f956e38d7be (tar: --dereference consistency) the capability to
preserve symlinks was also added to the archive extraction command.

-h is default at archive creation but is not default at extraction,
meaning that it will replace symlinks with directories even if the
original filesystem directory tree and archive contains them.

Add -h to the copyhardlinktree extraction step so the build can
support symlinks in variables like ${DEPLOY_DIR_IPK/RPM/DEB}.

Signed-off-by: Ioan-Adrian Ratiu 
---
 meta/lib/oe/path.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oe/path.py b/meta/lib/oe/path.py
index 448a2b944e..1ea03d5d56 100644
--- a/meta/lib/oe/path.py
+++ b/meta/lib/oe/path.py
@@ -98,7 +98,7 @@ def copyhardlinktree(src, dst):
 if (os.stat(src).st_dev ==  os.stat(dst).st_dev):
 # Need to copy directories only with tar first since cp will error if 
two 
 # writers try and create a directory at the same time
-cmd = "cd %s; find . -type d -print | tar --xattrs 
--xattrs-include='*' -cf - -C %s -p --no-recursion --files-from - | tar 
--xattrs --xattrs-include='*' -xf - -C %s" % (src, src, dst)
+cmd = "cd %s; find . -type d -print | tar --xattrs 
--xattrs-include='*' -cf - -C %s -p --no-recursion --files-from - | tar 
--xattrs --xattrs-include='*' -xhf - -C %s" % (src, src, dst)
 subprocess.check_output(cmd, shell=True, stderr=subprocess.STDOUT)
 source = ''
 if os.path.isdir(src):
-- 
2.14.1

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

Re: [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request

On 2017-08-21 11:55 AM, Richard Purdie wrote:

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:

Here's the collected set of kernel changes that are ready for the M3
builds.

We have some kernel meta data changes:

kernel-yocto: configuration updates: x86 features
linux-yocto/4.1: fix fsl-ls10xx sdhci
linux-yocto: add usb-net configs by default

Some bug fixes:

kernel-yocto: ensure that only valid BSPs are built
linux-yocto/4.10: CVE & misc fixes

And the important changes are the addition of the 4.12 kernel + libc headers
and the removal of the 4.1 kernel.

I also have some -stable updates queued for the active kernel versions, but
they will come out once this series has made it into the tree, since I'm
trying to isolate any 4.12 issues from other -stable updates.

I built and booted all the qemu targets for 4.12, and have built for
core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
architectures. My testing didn't pick up any regressions, but I was battling
some other build errors (non kernel related) during my testing, so I can
never be 100% sure.

I've sent patches to poky to remove/bump any references to the 4.1 kernel
.. if I've missed any, I'm sure people will shout.

Thanks for the other fix, not got that tested yet as builds are still
ongoing. However there appears to be a perf issue:

https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
[and so on]

Aha. There's a difference in the clibrary that I was using. I'll have
a closer look once my switch over and build gets going.

Bruce

Cheers,

Richard

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

Re: [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request


On 2017-08-21 11:55 AM, Richard Purdie wrote:

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:

Here's the collected set of kernel changes that are ready for the M3
builds.

We have some kernel meta data changes:

   kernel-yocto: configuration updates: x86 features
   linux-yocto/4.1: fix fsl-ls10xx sdhci
   linux-yocto: add usb-net configs by default

Some bug fixes:

   kernel-yocto: ensure that only valid BSPs are built
   linux-yocto/4.10: CVE & misc fixes

And the important changes are the addition of the 4.12 kernel + libc headers
and the removal of the 4.1 kernel.

I also have some -stable updates queued for the active kernel versions, but
they will come out once this series has made it into the tree, since I'm
trying to isolate any 4.12 issues from other -stable updates.

I built and booted all the qemu targets for 4.12, and have built for
core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
architectures. My testing didn't pick up any regressions, but I was battling
some other build errors (non kernel related) during my testing, so I can
never be 100% sure.

I've sent patches to poky to remove/bump any references to the 4.1 kernel
.. if I've missed any, I'm sure people will shout.


Thanks for the other fix, not got that tested yet as builds are still
ongoing. However there appears to be a perf issue:

https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
[and so on]



Again, I'm not going to be much good on fixing this.

I of course have built (and run perf on target) for all the
architectures or I never would have sent the pull request.

I'll see if I can find something wrong on what my building
was producing, but otherwise, I have no way to reproduce it.

Bruce



Cheers,

Richard





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

Re: [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Here's the collected set of kernel changes that are ready for the M3
> builds.
> 
> We have some kernel meta data changes:
> 
>   kernel-yocto: configuration updates: x86 features
>   linux-yocto/4.1: fix fsl-ls10xx sdhci
>   linux-yocto: add usb-net configs by default
> 
> Some bug fixes:
> 
>   kernel-yocto: ensure that only valid BSPs are built
>   linux-yocto/4.10: CVE & misc fixes
> 
> And the important changes are the addition of the 4.12 kernel + libc headers
> and the removal of the 4.1 kernel.
> 
> I also have some -stable updates queued for the active kernel versions, but
> they will come out once this series has made it into the tree, since I'm
> trying to isolate any 4.12 issues from other -stable updates.
> 
> I built and booted all the qemu targets for 4.12, and have built for
> core-image-sato, core-image-kernel-dev, glibc and muslc for all of the
> architectures. My testing didn't pick up any regressions, but I was battling
> some other build errors (non kernel related) during my testing, so I can
> never be 100% sure.
> 
> I've sent patches to poky to remove/bump any references to the 4.1 kernel
> .. if I've missed any, I'm sure people will shout.

Thanks for the other fix, not got that tested yet as builds are still
ongoing. However there appears to be a perf issue:

https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/429/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_1/logs/stdio
https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/77/steps/BuildImages_2/logs/stdio
[and so on]

Cheers,

Richard



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

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Mon, Aug 21, 2017 at 11:16 AM, Peter Kjellerstedt <
peter.kjellerst...@axis.com> wrote:

> Just in case you missed it (as you didn’t comment on my comment about it),
> there was a typo in the log message as well.
>

Yup. Noticed that, it isn't the only typo ;)

This is a resend of a patch I sent a few weeks ago, so I'm not too worried
if it sits or not.

Cheers,

Bruce


>
>
> //Peter
>
>
>
> *From:* Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
> *Sent:* den 21 augusti 2017 17:14
> *To:* Peter Kjellerstedt 
> *Cc:* richard.pur...@linuxfoundation.org; openembedded-core@lists.
> openembedded.org
> *Subject:* Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
> BSPs are built
>
>
>
>
>
>
>
> On Mon, Aug 21, 2017 at 11:03 AM, Bruce Ashfield 
> wrote:
>
>
>
>
>
> On Mon, Aug 21, 2017 at 11:00 AM, Peter Kjellerstedt <
> peter.kjellerst...@axis.com> wrote:
>
> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> > Bruce Ashfield
> > Sent: den 21 augusti 2017 04:58
> > To: richard.pur...@linuxfoundation.org
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
> > BSPs are built
> >
> > There was a bug in the search routines responsible for locating
> > BSP definitions which returned a valid match if only the ktype
> > matched.
> >
> > This meant that someone looking for "qemux86foo" (which is an
> > invalid definition) would potentially end up building "qemuarm"
> > and be none the wiser (until it didn't boot).
> >
> > With this fix to the tools search routine, and improved return
> > code testing, we will now stop the build and report and error to
> > the user.
> >
> > [YOCTO: #11878]
> >
> > Signed-off-by: Bruce Ashfield 
> > ---
> >  meta/classes/kernel-yocto.bbclass   | 3 +++
> >  meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
> >  2 files changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/
> kernel-yocto.bbclass
> > index 1ca0756c4959..3c6df92131bc 100644
> > --- a/meta/classes/kernel-yocto.bbclass
> > +++ b/meta/classes/kernel-yocto.bbclass
> > @@ -143,6 +143,9 @@ do_kernel_metadata() {
> >
> >   # expand kernel features into their full path equivalents
> >   bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE}
> -DKTYPE=${LINUX_KERNEL_TYPE})
> > + if [ $? -ne 0 ] || [ -z "${bsp_definition}" ]; then
>
> Use $bsp_definition instead of ${bsp_definition} since it is a
> shell variable and not a bitbake variable.
>
>
>
> I always use ${...}, so I'm going to stay consistent with what is already
> in
>
> the file.
>
>
>
>
> Actually, after looking at the code in that bbclass, I see this
> used for a number of shell variables all over the place. This is
> actually bad, and you should rewrite the code to not use ${variable}
> for shell variables. The reason this is bad is because these
> variables unnecessarily end up in the sstate hash for these functions,
> and if someone actually happens to define a bitbake variable with the
> same name as one of those shell variables, the result will not be what
> is expected...
>
>
>
> Not something high on my priority list. It's been that way since the
> beginning.
>
>
>
> .. but I will loop back and take care of the issues before M4 closes. Just
> a bit busy
>
> pushing out the new kernels and a slew of bug fixes.
>
>
>
> This patch can be ignored (if needed) until I get back around to that.
>
>
>
> Cheers,
>
>
>
> Bruce
>
>
>
>
>
> Cheers,
>
>
>
> Bruce
>
>
>
>
> > + bbfatal_log "Could not locate BSP definiton for
> ${KMACHINE}/${LINUX_KERNEL_TYPE}."
>
> Change "definiton" to "definition".
>
> > + fi
> >   meta_dir=$(kgit --meta)
> >
> >   # run1: pull all the configuration fragments, no matter where they
> come from
> > diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> > index 2217a31076a2..4a78b897d34f 100644
> > --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> > +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> > @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;
> beginline=5;endline=9;md5=a6c2fa8aef1b
> >
> >  DEPENDS = "git-native"
> >
> > -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
> > +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"
> >  PR = "r12"
> >  PV = "0.2+git${SRCPV}"
> >
> > --
> > 2.5.0
>
> //Peter
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
>
>
> --
>
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>
>
>
>
>

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

2017-08-21 Thread Peter Kjellerstedt

Just in case you missed it (as you didn’t comment on my comment about it), 
there was a typo in the log message as well.

//Peter

From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
Sent: den 21 augusti 2017 17:14
To: Peter Kjellerstedt 
Cc: richard.pur...@linuxfoundation.org; openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs 
are built



On Mon, Aug 21, 2017 at 11:03 AM, Bruce Ashfield 
> wrote:


On Mon, Aug 21, 2017 at 11:00 AM, Peter Kjellerstedt 
> wrote:
> -Original Message-
> From: 
> openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org]
>  On Behalf Of
> Bruce Ashfield
> Sent: den 21 augusti 2017 04:58
> To: 
> richard.pur...@linuxfoundation.org
> Cc: 
> openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
> BSPs are built
>
> There was a bug in the search routines responsible for locating
> BSP definitions which returned a valid match if only the ktype
> matched.
>
> This meant that someone looking for "qemux86foo" (which is an
> invalid definition) would potentially end up building "qemuarm"
> and be none the wiser (until it didn't boot).
>
> With this fix to the tools search routine, and improved return
> code testing, we will now stop the build and report and error to
> the user.
>
> [YOCTO: #11878]
>
> Signed-off-by: Bruce Ashfield 
> >
> ---
>  meta/classes/kernel-yocto.bbclass   | 3 +++
>  
> meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>  | 2 +-
>  2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel-yocto.bbclass 
> b/meta/classes/kernel-yocto.bbclass
> index 1ca0756c4959..3c6df92131bc 100644
> --- a/meta/classes/kernel-yocto.bbclass
> +++ b/meta/classes/kernel-yocto.bbclass
> @@ -143,6 +143,9 @@ do_kernel_metadata() {
>
>   # expand kernel features into their full path equivalents
>   bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE} 
> -DKTYPE=${LINUX_KERNEL_TYPE})
> + if [ $? -ne 0 ] || [ -z "${bsp_definition}" ]; then
Use $bsp_definition instead of ${bsp_definition} since it is a
shell variable and not a bitbake variable.

I always use ${...}, so I'm going to stay consistent with what is already in
the file.


Actually, after looking at the code in that bbclass, I see this
used for a number of shell variables all over the place. This is
actually bad, and you should rewrite the code to not use ${variable}
for shell variables. The reason this is bad is because these
variables unnecessarily end up in the sstate hash for these functions,
and if someone actually happens to define a bitbake variable with the
same name as one of those shell variables, the result will not be what
is expected...

Not something high on my priority list. It's been that way since the beginning.

.. but I will loop back and take care of the issues before M4 closes. Just a 
bit busy
pushing out the new kernels and a slew of bug fixes.

This patch can be ignored (if needed) until I get back around to that.

Cheers,

Bruce


Cheers,

Bruce


> + bbfatal_log "Could not locate BSP definiton for 
> ${KMACHINE}/${LINUX_KERNEL_TYPE}."

Change "definiton" to "definition".

> + fi
>   meta_dir=$(kgit --meta)
>
>   # run1: pull all the configuration fragments, no matter where they come 
> from
> diff --git 
> a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>  
> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> index 2217a31076a2..4a78b897d34f 100644
> --- 
> a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ 
> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
> "file://git/tools/kgit;beginline=5;endline=9;md5=a6c2fa8aef1b
>
>  DEPENDS = 
>  %20DEPENDS%20=%20> "git-native"
>
> -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
> +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"
>  PR = "r12"
>  PV = "0.2+git${SRCPV}"
>
> --
> 2.5.0

//Peter

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

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Mon, Aug 21, 2017 at 11:03 AM, Bruce Ashfield 
wrote:

>
>
> On Mon, Aug 21, 2017 at 11:00 AM, Peter Kjellerstedt <
> peter.kjellerst...@axis.com> wrote:
>
>> > -Original Message-
>> > From: openembedded-core-boun...@lists.openembedded.org
>> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
>> > Bruce Ashfield
>> > Sent: den 21 augusti 2017 04:58
>> > To: richard.pur...@linuxfoundation.org
>> > Cc: openembedded-core@lists.openembedded.org
>> > Subject: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
>> > BSPs are built
>> >
>> > There was a bug in the search routines responsible for locating
>> > BSP definitions which returned a valid match if only the ktype
>> > matched.
>> >
>> > This meant that someone looking for "qemux86foo" (which is an
>> > invalid definition) would potentially end up building "qemuarm"
>> > and be none the wiser (until it didn't boot).
>> >
>> > With this fix to the tools search routine, and improved return
>> > code testing, we will now stop the build and report and error to
>> > the user.
>> >
>> > [YOCTO: #11878]
>> >
>> > Signed-off-by: Bruce Ashfield 
>> > ---
>> >  meta/classes/kernel-yocto.bbclass   | 3 +++
>> >  meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
>> >  2 files changed, 4 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/
>> kernel-yocto.bbclass
>> > index 1ca0756c4959..3c6df92131bc 100644
>> > --- a/meta/classes/kernel-yocto.bbclass
>> > +++ b/meta/classes/kernel-yocto.bbclass
>> > @@ -143,6 +143,9 @@ do_kernel_metadata() {
>> >
>> >   # expand kernel features into their full path equivalents
>> >   bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE}
>> -DKTYPE=${LINUX_KERNEL_TYPE})
>> > + if [ $? -ne 0 ] || [ -z "${bsp_definition}" ]; then
>>
>> Use $bsp_definition instead of ${bsp_definition} since it is a
>> shell variable and not a bitbake variable.
>>
>
> I always use ${...}, so I'm going to stay consistent with what is already
> in
> the file.
>
>
>>
>> Actually, after looking at the code in that bbclass, I see this
>> used for a number of shell variables all over the place. This is
>> actually bad, and you should rewrite the code to not use ${variable}
>> for shell variables. The reason this is bad is because these
>> variables unnecessarily end up in the sstate hash for these functions,
>> and if someone actually happens to define a bitbake variable with the
>> same name as one of those shell variables, the result will not be what
>> is expected...
>>
>
> Not something high on my priority list. It's been that way since the
> beginning.
>

.. but I will loop back and take care of the issues before M4 closes. Just
a bit busy
pushing out the new kernels and a slew of bug fixes.

This patch can be ignored (if needed) until I get back around to that.

Cheers,

Bruce


>
> Cheers,
>
> Bruce
>
>
>>
>> > + bbfatal_log "Could not locate BSP definiton for
>> ${KMACHINE}/${LINUX_KERNEL_TYPE}."
>>
>> Change "definiton" to "definition".
>>
>> > + fi
>> >   meta_dir=$(kgit --meta)
>> >
>> >   # run1: pull all the configuration fragments, no matter where
>> they come from
>> > diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> > index 2217a31076a2..4a78b897d34f 100644
>> > --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> > +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> > @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginli
>> ne=5;endline=9;md5=a6c2fa8aef1b
>> >
>> >  DEPENDS = "git-native"
>> >
>> > -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
>> > +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"
>> >  PR = "r12"
>> >  PV = "0.2+git${SRCPV}"
>> >
>> > --
>> > 2.5.0
>>
>> //Peter
>>
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end"
>



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

[OE-core] [PATCH v3] pkgconf: add recipe

2017-08-21 Thread Maxin B. John

pkgconf is a better replacement for pkg-config. Fedora 26 replaces the
system pkg-config implementation with pkgconf because it "provides better
support for handling .pc files and a stable library ABI/API for integrating
into applications." and is actively maintained, unlike pkg-config.

pkgconf aims to offer many improvements over pkg-config such as faster/more
efficient dependency resolver which "allows for the user to more conservatively
link their binaries -- which may be helpful in some environments, such as when
prelink(1) is being used.

pkgconf also aims to provide a more complete implementation of pkg-config.
The features most likely to benefit the Yocto Project build system are the
faster/more efficient dependency resolution and linker flag optimisation.

Move pkgconf recipe to oe-core from meta-pkgconf:
https://github.com/kergoth/meta-kergoth-wip/tree/master/meta-pkgconf

Links:
1. http://pkgconf.org
2. 
https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation
3. https://bugzilla.yoctoproject.org/show_bug.cgi?id=11308

Signed-off-by: Christopher Larson 
Signed-off-by: Maxin B. John 
---
To test this, after applying these patches, update "local.conf" as below:

PREFERRED_PROVIDER_pkgconfig = "pkgconf"
PREFERRED_PROVIDER_pkgconfig-native = "pkgconf-native"
PREFERRED_PROVIDER_nativesdk-pkgconfig = "nativesdk-pkgconf"

Changes in v2:
Fixes for mingw

Changes in v3:
Include the esdk fix
---
 meta/files/common-licenses/pkgconf |  10 +
 ...imal-tweaks-to-compile-with-Visual-C-2015.patch | 224 +
 .../0001-stdinc.h-fix-build-with-mingw.patch   |  48 +
 .../pkgconf/pkgconf/pkg-config-esdk.in |  24 +++
 .../pkgconf/pkgconf/pkg-config-native.in   |   6 +
 .../pkgconf/pkgconf/pkg-config-wrapper |  16 ++
 meta/recipes-devtools/pkgconf/pkgconf_1.3.7.bb |  73 +++
 7 files changed, 401 insertions(+)
 create mode 100644 meta/files/common-licenses/pkgconf
 create mode 100644 
meta/recipes-devtools/pkgconf/pkgconf/0001-Minimal-tweaks-to-compile-with-Visual-C-2015.patch
 create mode 100644 
meta/recipes-devtools/pkgconf/pkgconf/0001-stdinc.h-fix-build-with-mingw.patch
 create mode 100644 meta/recipes-devtools/pkgconf/pkgconf/pkg-config-esdk.in
 create mode 100644 meta/recipes-devtools/pkgconf/pkgconf/pkg-config-native.in
 create mode 100755 meta/recipes-devtools/pkgconf/pkgconf/pkg-config-wrapper
 create mode 100644 meta/recipes-devtools/pkgconf/pkgconf_1.3.7.bb

diff --git a/meta/files/common-licenses/pkgconf 
b/meta/files/common-licenses/pkgconf
new file mode 100644
index 000..81a5221
--- /dev/null
+++ b/meta/files/common-licenses/pkgconf
@@ -0,0 +1,10 @@
+Copyright (c) 2011, 2012, 2013, 2014, 2015, 2016, 2017
+pkgconf authors (see AUTHORS file in source directory).
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+This software is provided 'as is' and without any warranty, express or
+implied.  In no event shall the authors be liable for any damages arising
+from the use of this software.
diff --git 
a/meta/recipes-devtools/pkgconf/pkgconf/0001-Minimal-tweaks-to-compile-with-Visual-C-2015.patch
 
b/meta/recipes-devtools/pkgconf/pkgconf/0001-Minimal-tweaks-to-compile-with-Visual-C-2015.patch
new file mode 100644
index 000..3805ad3
--- /dev/null
+++ 
b/meta/recipes-devtools/pkgconf/pkgconf/0001-Minimal-tweaks-to-compile-with-Visual-C-2015.patch
@@ -0,0 +1,224 @@
+From 4d7b4d7c8e9966c593f472355607204c6c80fecb Mon Sep 17 00:00:00 2001
+From: Dan Kegel 
+Date: Sun, 4 Jun 2017 19:19:55 -0700
+Subject: [PATCH] Minimal tweaks to compile with Visual C 2015
+
+Upstream-Status: Backport
+
+Signed-off-by: Maxin B. John 
+---
+ getopt_long.c   |  2 ++
+ libpkgconf/bsdstubs.c   |  1 +
+ libpkgconf/libpkgconf.h |  2 +-
+ libpkgconf/path.c   | 10 +-
+ libpkgconf/pkg.c| 28 +++-
+ libpkgconf/stdinc.h |  9 +++--
+ 6 files changed, 35 insertions(+), 17 deletions(-)
+
+diff --git a/getopt_long.c b/getopt_long.c
+index afeb68d..5ce9bfd 100644
+--- a/getopt_long.c
 b/getopt_long.c
+@@ -62,7 +62,9 @@
+ #include 
+ #include 
+ #include 
++#ifndef _WIN32
+ #include 
++#endif
+ 
+ #define PKGCONF_HACK_LOGICAL_OR_ALL_VALUES
+ 
+diff --git a/libpkgconf/bsdstubs.c b/libpkgconf/bsdstubs.c
+index 8f70ff3..2c000ac 100644
+--- a/libpkgconf/bsdstubs.c
 b/libpkgconf/bsdstubs.c
+@@ -17,6 +17,7 @@
+  * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+  */
+ 
++#include 
+ #include 
+ #include 
+ 
+diff --git a/libpkgconf/libpkgconf.h b/libpkgconf/libpkgconf.h
+index 404bf0c..551d85d 100644
+--- a/libpkgconf/libpkgconf.h
 b/libpkgconf/libpkgconf.h
+@@ -310,7 +310,7 @@ void

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

On Mon, Aug 21, 2017 at 11:00 AM, Peter Kjellerstedt <
peter.kjellerst...@axis.com> wrote:

> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> > Bruce Ashfield
> > Sent: den 21 augusti 2017 04:58
> > To: richard.pur...@linuxfoundation.org
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
> > BSPs are built
> >
> > There was a bug in the search routines responsible for locating
> > BSP definitions which returned a valid match if only the ktype
> > matched.
> >
> > This meant that someone looking for "qemux86foo" (which is an
> > invalid definition) would potentially end up building "qemuarm"
> > and be none the wiser (until it didn't boot).
> >
> > With this fix to the tools search routine, and improved return
> > code testing, we will now stop the build and report and error to
> > the user.
> >
> > [YOCTO: #11878]
> >
> > Signed-off-by: Bruce Ashfield 
> > ---
> >  meta/classes/kernel-yocto.bbclass   | 3 +++
> >  meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
> >  2 files changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/kernel-yocto.bbclass
> b/meta/classes/kernel-yocto.bbclass
> > index 1ca0756c4959..3c6df92131bc 100644
> > --- a/meta/classes/kernel-yocto.bbclass
> > +++ b/meta/classes/kernel-yocto.bbclass
> > @@ -143,6 +143,9 @@ do_kernel_metadata() {
> >
> >   # expand kernel features into their full path equivalents
> >   bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE}
> -DKTYPE=${LINUX_KERNEL_TYPE})
> > + if [ $? -ne 0 ] || [ -z "${bsp_definition}" ]; then
>
> Use $bsp_definition instead of ${bsp_definition} since it is a
> shell variable and not a bitbake variable.
>

I always use ${...}, so I'm going to stay consistent with what is already in
the file.


>
> Actually, after looking at the code in that bbclass, I see this
> used for a number of shell variables all over the place. This is
> actually bad, and you should rewrite the code to not use ${variable}
> for shell variables. The reason this is bad is because these
> variables unnecessarily end up in the sstate hash for these functions,
> and if someone actually happens to define a bitbake variable with the
> same name as one of those shell variables, the result will not be what
> is expected...
>

Not something high on my priority list. It's been that way since the
beginning.

Cheers,

Bruce


>
> > + bbfatal_log "Could not locate BSP definiton for
> ${KMACHINE}/${LINUX_KERNEL_TYPE}."
>
> Change "definiton" to "definition".
>
> > + fi
> >   meta_dir=$(kgit --meta)
> >
> >   # run1: pull all the configuration fragments, no matter where they
> come from
> > diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> > index 2217a31076a2..4a78b897d34f 100644
> > --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> > +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> > @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;
> beginline=5;endline=9;md5=a6c2fa8aef1b
> >
> >  DEPENDS = "git-native"
> >
> > -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
> > +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"
> >  PR = "r12"
> >  PV = "0.2+git${SRCPV}"
> >
> > --
> > 2.5.0
>
> //Peter
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



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

Re: [OE-core] [PATCH] meta: move some text from oe-setup-builddir to conf-notes.txt

2017-08-21 Thread Ming Liu

Hi, Leonardo:

I would like to explain our scenario: we want to show our costumers the
following tips:
...
### Shell environment set up for AtlasCopco builds. ###

You can now start a build with:
F= D= M= bitbake  [-c task]
...

and they are duplicated with the header in oe-setup-buildir, I could not
find a way to override them without this patch. Or maybe you have any other
suggestions?

//Ming Liu


2017-08-21 16:47 GMT+02:00 Leonardo Sandoval <
leonardo.sandoval.gonza...@linux.intel.com>:

> On Mon, 2017-08-21 at 13:45 +0200, liu.min...@gmail.com wrote:
> > From: Ming Liu 
> >
> > This allows the end users to be able to override the entire notes
> > showing on the shell console. For instance, Our company uses a
> > external conf-notes.txt, and we run bitbake with some extra variables,
> > looks like: F=xxx D=xxx M=xxx bitbake , so we want to show
> > exactly these texts on the shell console, that's why we need this
> > change.
> >
>
> I do not clearly spot the real gain. oe-setup-buildir just plots the
> header and you can include what you specific stuff into conf-notes. The
> header string does not strictly belongs to conf-notes, at least not
> semantically.
>
>
> > Signed-off-by: Ming Liu 
> > ---
> >  meta/conf/conf-notes.txt  | 5 +
> >  scripts/oe-setup-builddir | 7 ---
> >  2 files changed, 5 insertions(+), 7 deletions(-)
> >
> > diff --git a/meta/conf/conf-notes.txt b/meta/conf/conf-notes.txt
> > index 2f2932b..f1a4f4d 100644
> > --- a/meta/conf/conf-notes.txt
> > +++ b/meta/conf/conf-notes.txt
> > @@ -1,3 +1,8 @@
> > +
> > +### Shell environment set up for builds. ###
> > +
> > +You can now run 'bitbake '
> > +
> >  Common targets are:
> >  core-image-minimal
> >  core-image-sato
> > diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
> > index ef49551..55d73ca 100755
> > --- a/scripts/oe-setup-builddir
> > +++ b/scripts/oe-setup-builddir
> > @@ -133,13 +133,6 @@ EOM
> >  #unset SHOWYPDOC
> >  fi
> >
> > -cat < > -
> > -### Shell environment set up for builds. ###
> > -
> > -You can now run 'bitbake '
> > -
> > -EOM
> >  if [ -z "$OECORENOTESCONF" ]; then
> >  OECORENOTESCONF="$OEROOT/meta/conf/conf-notes.txt"
> >  fi
> > --
> > 2.7.4
> >
>
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid BSPs are built

2017-08-21 Thread Peter Kjellerstedt

> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Bruce Ashfield
> Sent: den 21 augusti 2017 04:58
> To: richard.pur...@linuxfoundation.org
> Cc: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 8/9] kernel-yocto: ensure that only valid
> BSPs are built
> 
> There was a bug in the search routines responsible for locating
> BSP definitions which returned a valid match if only the ktype
> matched.
> 
> This meant that someone looking for "qemux86foo" (which is an
> invalid definition) would potentially end up building "qemuarm"
> and be none the wiser (until it didn't boot).
> 
> With this fix to the tools search routine, and improved return
> code testing, we will now stop the build and report and error to
> the user.
> 
> [YOCTO: #11878]
> 
> Signed-off-by: Bruce Ashfield 
> ---
>  meta/classes/kernel-yocto.bbclass   | 3 +++
>  meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
>  2 files changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/classes/kernel-yocto.bbclass 
> b/meta/classes/kernel-yocto.bbclass
> index 1ca0756c4959..3c6df92131bc 100644
> --- a/meta/classes/kernel-yocto.bbclass
> +++ b/meta/classes/kernel-yocto.bbclass
> @@ -143,6 +143,9 @@ do_kernel_metadata() {
> 
>   # expand kernel features into their full path equivalents
>   bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE} 
> -DKTYPE=${LINUX_KERNEL_TYPE})
> + if [ $? -ne 0 ] || [ -z "${bsp_definition}" ]; then

Use $bsp_definition instead of ${bsp_definition} since it is a 
shell variable and not a bitbake variable. 

Actually, after looking at the code in that bbclass, I see this 
used for a number of shell variables all over the place. This is 
actually bad, and you should rewrite the code to not use ${variable} 
for shell variables. The reason this is bad is because these 
variables unnecessarily end up in the sstate hash for these functions, 
and if someone actually happens to define a bitbake variable with the 
same name as one of those shell variables, the result will not be what 
is expected...

> + bbfatal_log "Could not locate BSP definiton for 
> ${KMACHINE}/${LINUX_KERNEL_TYPE}."

Change "definiton" to "definition".

> + fi
>   meta_dir=$(kgit --meta)
> 
>   # run1: pull all the configuration fragments, no matter where they come 
> from
> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb 
> b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> index 2217a31076a2..4a78b897d34f 100644
> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = 
> "file://git/tools/kgit;beginline=5;endline=9;md5=a6c2fa8aef1b
> 
>  DEPENDS = "git-native"
> 
> -SRCREV = "9cd2b626d652bec10c6bc75275b35bfee74d447c"
> +SRCREV = "0571411cc033c11df7827508dd786876ce2f8c83"
>  PR = "r12"
>  PV = "0.2+git${SRCPV}"
> 
> --
> 2.5.0

//Peter

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

[OE-core] Yocto Project Status WW34’17

2017-08-21 Thread Jolley, Stephen K

Current Dev Position: YP 2.4 M3

Next Deadline: YP 2.4 M3 Cut off is Aug. 21, 2017


SWAT team rotation: Juro -> Paul on Aug. 18, 2017.

SWAT team rotation: Paul -> Todor on Aug. 25, 2017.

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


Key Status/Updates:

·We’ve discovered problems with the 2.3.1 eSDK release binaries and are 
in the process of rebuilding these to fix sstate mirror urls. This was from 
autobuilder configuration being incorrect, not from any metadata issue.

·In the last week the autobuilder suffered overload issues around the 
NAS which meant that sstate, download and autobuilder functions were affected. 
The functions have been split between different servers meaning a rebuild of 
the NAS was required and this is ongoing.

·The impact on the Autobuilders from the NAS issues was significant and 
has slowed down patch testing.

·The OpenSSL 1.1 upgrade has been backed back to 1.0 due to too many 
reported issues. You can test 1.1 using PREFERRED_VERSION and we will move back 
to 1.1 likely in the next release, there just wasn’t enough time in the current 
one to reasonably expect issues to get resolved.

·Today is feature freeze for 2.4. There are several patches still in 
the queue and undergoing testing (python manifest changes, recipetool/devtool 
and kernel changes) as well as some bitbake server issues that need resolving 
before we can start 2.4 M3 builds.

·We did merge fixes for rpm dependency generation after realizing it 
was broken. This detects things like interpreter paths (e.g. scripts that 
require /bin/bash) and means some dependency issues are appearing in builds now 
this is working correctly again.


Planned upcoming dot releases:

YP 2.2.2 Cut off June 5, 2017 - Not ready to do an rc2 yet.

YP 2.2.2 Release by June, 16 2017

YP 2.3.2 Cut off Sept. 1, 2017

YP 2.3.2 Release by Sept. 15, 2017


Key YP 2.4 Dates are:

YP 2.4 M3 Cut off is Aug. 21, 2017

YP 2.4 M3 Release by Sept. 1, 2017

YP 2.4 M4 (Final) Cut off is Sept. 18, 2017

YP 2.4 M4 (Final) Release by Oct. 20, 2017


Tracking Metrics:

WDD 2476 (last week 2480)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

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

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

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


[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•   Work Telephone:(503) 712-0534
•Cell:   (208) 244-4460
• Email:  stephen.k.jol...@intel.com

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

Re: [OE-core] [PATCH] meta: move some text from oe-setup-builddir to conf-notes.txt

2017-08-21 Thread Leonardo Sandoval

On Mon, 2017-08-21 at 13:45 +0200, liu.min...@gmail.com wrote:
> From: Ming Liu 
> 
> This allows the end users to be able to override the entire notes
> showing on the shell console. For instance, Our company uses a
> external conf-notes.txt, and we run bitbake with some extra variables,
> looks like: F=xxx D=xxx M=xxx bitbake , so we want to show
> exactly these texts on the shell console, that's why we need this
> change.
> 

I do not clearly spot the real gain. oe-setup-buildir just plots the
header and you can include what you specific stuff into conf-notes. The
header string does not strictly belongs to conf-notes, at least not
semantically.


> Signed-off-by: Ming Liu 
> ---
>  meta/conf/conf-notes.txt  | 5 +
>  scripts/oe-setup-builddir | 7 ---
>  2 files changed, 5 insertions(+), 7 deletions(-)
> 
> diff --git a/meta/conf/conf-notes.txt b/meta/conf/conf-notes.txt
> index 2f2932b..f1a4f4d 100644
> --- a/meta/conf/conf-notes.txt
> +++ b/meta/conf/conf-notes.txt
> @@ -1,3 +1,8 @@
> +
> +### Shell environment set up for builds. ###
> +
> +You can now run 'bitbake '
> +
>  Common targets are:
>  core-image-minimal
>  core-image-sato
> diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
> index ef49551..55d73ca 100755
> --- a/scripts/oe-setup-builddir
> +++ b/scripts/oe-setup-builddir
> @@ -133,13 +133,6 @@ EOM
>  #unset SHOWYPDOC
>  fi
>  
> -cat < -
> -### Shell environment set up for builds. ###
> -
> -You can now run 'bitbake '
> -
> -EOM
>  if [ -z "$OECORENOTESCONF" ]; then
>  OECORENOTESCONF="$OEROOT/meta/conf/conf-notes.txt"
>  fi
> -- 
> 2.7.4
> 


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

[OE-core] ✗ patchtest: failure for "[v2] devtool/copy_buildsystem:..." and 1 more

== Series Details ==

Series: "[v2] devtool/copy_buildsystem:..." and 1 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/8393/
State : failure

== Summary ==


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



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



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

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

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

[OE-core] [PATCH v2 1/2] devtool/copy_buildsystem: adds meta-skeleton layer in the eSDK installation.

2017-08-21 Thread leonardo . sandoval . gonzalez

From: Juan M Cruz Alcaraz 

The eSDK installation requires the meta-skeleton layer.
The build system might use the meta-skeleton recipes as layout
to create custom recipes. An example is the recipetool script
that uses the meta-skeleton kernel recipe when creating a custom
kernel recipe.

[YOCTO #11102]

(From OE-Core rev: 5c9ef0734d23909b5694ed43cdbb205c2ba9ca95)

Signed-off-by: Juan M Cruz Alcaraz 
Signed-off-by: Richard Purdie 
---
 meta/lib/oe/copy_buildsystem.py | 12 
 1 file changed, 12 insertions(+)

diff --git a/meta/lib/oe/copy_buildsystem.py b/meta/lib/oe/copy_buildsystem.py
index e24488db10..ac2fae1ed1 100644
--- a/meta/lib/oe/copy_buildsystem.py
+++ b/meta/lib/oe/copy_buildsystem.py
@@ -32,6 +32,10 @@ class BuildSystem(object):
 
 corebase = os.path.abspath(self.d.getVar('COREBASE'))
 layers.append(corebase)
+# The bitbake build system uses the meta-skeleton layer as a layout
+# for common recipies, e.g: the recipetool script to create kernel 
recipies
+# Add the meta-skeleton layer to be included as part of the eSDK 
installation
+layers.append(os.path.join(corebase, 'meta-skeleton'))
 
 # Exclude layers
 for layer_exclude in self.layers_exclude:
@@ -128,6 +132,14 @@ class BuildSystem(object):
 line = line.replace('workspacelayer', 
workspace_newname)
 f.write(line)
 
+# meta-skeleton layer is added as part of the build system
+# but not as a layer included in the build, therefore it is
+# not reported to the function caller.
+for layer in layers_copied:
+if layer.endswith('/meta-skeleton'):
+layers_copied.remove(layer)
+break
+
 return layers_copied
 
 def generate_locked_sigs(sigfile, d):
-- 
2.12.3

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

[OE-core] [PATCH v2 2/2] build-appliance-image: include proxy on pip3 installation

2017-08-21 Thread leonardo . sandoval . gonzalez

From: Leonardo Sandoval 

Otherwise, we get timeouts, leading to errors:

pip._vendor.requests.exceptions.ConnectTimeout: 
HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded 
with url: /pypi/pip/json (Caused by 
ConnectTimeoutError(, 'Connection to pypi.python.org timed out. (connect 
timeout=5)'))
WARNING: 
TOPDIR/tmp/work/qemux86-poky-linux/build-appliance-image/15.0.0-r0/temp/run.do_populate_poky_src.185123:1
 exit 1 from 'pip3 install --user -I -U -v -r 
TOPDIR/tmp/work/qemux86-poky-linux/build-appliance-image/15.0.0-r0/rootfs/home/builder/poky/bitbake/toaster-requirements.txt'
DEBUG: Python function do_image finished

Complete log at [1]

[1] http://errors.yoctoproject.org/Errors/Build/43393/

Signed-off-by: Leonardo Sandoval 
---
 meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb 
b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
index db96a051a7..cd96a128a8 100644
--- a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
+++ b/meta/recipes-core/images/build-appliance-image_15.0.0.bb
@@ -100,7 +100,11 @@ fakeroot do_populate_poky_src () {
export STAGING_INCDIR=${STAGING_INCDIR_NATIVE}
export HOME=${IMAGE_ROOTFS}/home/builder
mkdir -p ${IMAGE_ROOTFS}/home/builder/.cache/pip
-   pip3 install --user -I -U -v -r 
${IMAGE_ROOTFS}/home/builder/poky/bitbake/toaster-requirements.txt
+   pip3_install_params="--user -I -U -v -r 
${IMAGE_ROOTFS}/home/builder/poky/bitbake/toaster-requirements.txt"
+   if [ -n "${http_proxy}" ]; then
+  pip3_install_params="${pip3_install_params} --proxy ${http_proxy}"
+   fi
+   pip3 install ${pip3_install_params}
chown -R builder.builder ${IMAGE_ROOTFS}/home/builder/.local
chown -R builder.builder ${IMAGE_ROOTFS}/home/builder/.cache
 }
-- 
2.12.3

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

[OE-core] [PATCH v2] linux-yocto: introduce 4.12 recipes

The 4.12 kernel will be the default/reference for the fall 2017
release.

These recipes represent the introduction of 4.12.7 + related kernel
meta data. Existing functionality has been validated against this
new kernel version, and older versions will be removed in separate
commits.

Signed-off-by: Bruce Ashfield 
---

v2: Adjusting the SRCREVs to fix a patch that no longer needed to be applied.

Bruce

 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb   | 38 +++
 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb | 25 
 meta/recipes-kernel/linux/linux-yocto_4.12.bb  | 44 ++
 3 files changed, 107 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_4.12.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
new file mode 100644
index ..1020da642650
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.12.bb
@@ -0,0 +1,38 @@
+KBRANCH ?= "standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_meta ?= "baf6e3d9b8c6efd32cfaf75a9bb8d55a558f006d"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine 
\
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "4.12.7"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = "(qemux86|qemux86-64|qemuarm|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES_append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES_append_qemuall=" cfg/virtio.scc"
+KERNEL_FEATURES_append_qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES_append_qemux86-64=" cfg/sound.scc"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
new file mode 100644
index ..c79f97fdfdc9
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.12.bb
@@ -0,0 +1,25 @@
+KBRANCH ?= "standard/tiny/common-pc"
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "4.12.7"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_meta ?= "baf6e3d9b8c6efd32cfaf75a9bb8d55a558f006d"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.12.git;branch=${KBRANCH};name=machine 
\
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "(qemux86$)"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.12.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
new file mode 100644
index ..af655315134f
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_4.12.bb
@@ -0,0 +1,44 @@
+KBRANCH ?= "standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH_qemuarm  ?= "standard/arm-versatile-926ejs"
+KBRANCH_qemuarm64 ?= "standard/qemuarm64"
+KBRANCH_qemumips ?= "standard/mti-malta32"
+KBRANCH_qemuppc  ?= "standard/qemuppc"
+KBRANCH_qemux86  ?= "standard/base"
+KBRANCH_qemux86-64 ?= "standard/base"
+KBRANCH_qemumips64 ?= "standard/mti-malta64"
+
+SRCREV_machine_qemuarm ?= "c0fb11c222383b78e54006d1437fb0793c516b52"
+SRCREV_machine_qemuarm64 ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_machine_qemumips ?= "46de539c9f055febba1913e192e68d938c320b44"
+SRCREV_machine_qemuppc ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_machine_qemux86 ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_machine_qemux86-64 ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_machine_qemumips64 ?= "d4522d6bf30f82d928b77d9c16932615b535e50b"
+SRCREV_machine ?= "418f93c560a4d83d078cb96a639af71786da9187"
+SRCREV_meta ?= "baf6e3d9b8c6efd32cfaf75a9bb8d55a558f006d"
+
+SRC_URI =

Re: [OE-core] [PATCH] gcc: Upgrade to 7.2.0 release

2017-08-21 Thread Khem Raj

On Mon, Aug 21, 2017 at 12:12 AM Martin Jansa 
wrote:

> Still reproducible without thumb:
> http://errors.yoctoproject.org/Errors/Details/152666/
>
> this might be also triggered by this upgrade:
> http://errors.yoctoproject.org/Errors/Details/152770/
>

May be passing -cpperraswarn to swig will help

> 
>
> or from glibc final upgrade or something else, hard to know when exactly
> it started as previous world builds were pretty much useless with all those
> openssl caused issues.
>
> On Mon, Aug 21, 2017 at 2:37 AM, Khem Raj  wrote:
>
>>
>> On Sun, Aug 20, 2017 at 5:31 PM Martin Jansa 
>> wrote:
>>
>>> Seems like python-matplotlib reliably triggers ICE in this version of
>>> gcc:
>>>
>>> http://errors.yoctoproject.org/Errors/Details/152664/
>>>
>>> I think I haven't seen this one with 7.1.
>>>
>>
>> Can you try disabling thumb mode and see if this works ?
>>
>>>
>>> On Tue, Aug 15, 2017 at 7:42 AM, Khem Raj  wrote:
>>>
 Drop upstreamed patches

 Signed-off-by: Khem Raj 
 ---
  ...r-Use-stack_t-instead-of-struct-sigaltsta.patch |  81 ---
  ...0-replace-struct-ucontext-with-ucontext_t.patch | 149
 -
  .../gcc/{gcc-7.1.inc => gcc-7.2.inc}   |  14 +-
  .../0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch |   0
  .../{gcc-7.1 => gcc-7.2}/0008-c99-snprintf.patch   |   0
  .../0009-gcc-poison-system-directories.patch   |   0
  .../0010-gcc-poison-dir-extend.patch   |   0
  .../0011-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch |   0
  .../0012-64-bit-multilib-hack.patch|   0
  .../0013-optional-libstdc.patch|   0
  ...0014-gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch |   0
  .../0015-COLLECT_GCC_OPTIONS.patch |   0
  ...efaults.h-in-B-instead-of-S-and-t-oe-in-B.patch |   0
  .../0017-fortran-cross-compile-hack.patch  |   0
  .../0018-cpp-honor-sysroot.patch   |   0
  .../0019-MIPS64-Default-to-N64-ABI.patch   |   0
  ...C_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch |   0
  ...0021-gcc-Fix-argument-list-too-long-error.patch |   0
  .../{gcc-7.1 => gcc-7.2}/0022-Disable-sdt.patch|   0
  .../gcc/{gcc-7.1 => gcc-7.2}/0023-libtool.patch|   0
  ...4-pass-fix-v4bx-to-linker-to-support-EABI.patch |   0
  ...tilib-config-files-from-B-instead-of-usin.patch |   0
  ...-libdir-from-.la-which-usually-points-to-.patch |   0
  .../gcc/{gcc-7.1 => gcc-7.2}/0027-export-CPP.patch |   0
  ...AltiVec-generation-on-powepc-linux-target.patch |   0
  ...-MULTILIB_OSDIRNAMES-and-other-multilib-o.patch |   0
  ...Ensure-target-gcc-headers-can-be-included.patch |   0
  ...-t-build-with-disable-dependency-tracking.patch |   0
  ...h-host-directory-during-relink-if-inst_pr.patch |   0
  ...IBS_DIR-replacement-instead-of-hardcoding.patch |   0
  .../0034-aarch64-Add-support-for-musl-ldso.patch   |   0
  ...ibcc1-fix-libcc1-s-install-path-and-rpath.patch |   0
  ...-handle-sysroot-support-for-nativesdk-gcc.patch |   0
  ...et-sysroot-gcc-version-specific-dirs-with.patch |   0
  ...-various-_FOR_BUILD-and-related-variables.patch |   0
  .../0039-nios2-Define-MUSL_DYNAMIC_LINKER.patch|   0
  ...shared-to-link-commandline-for-musl-targe.patch |   0
  ...c-libcpp-support-ffile-prefix-map-old-new.patch |   0
  ...ug-prefix-map-to-replace-ffile-prefix-map.patch |   0
  ...-fdebug-prefix-map-support-to-remap-sourc.patch |   0
  ...44-libgcc-Add-knob-to-use-ldbl-128-on-ppc.patch |   0
  ...bgcc-using-LDFLAGS-not-just-SHLIB_LDFLAGS.patch |   0
  ...e-alias-for-__cpu_indicator_init-instead-.patch |   0
  .../0047-sync-gcc-stddef.h-with-musl.patch |   0
  .../0048-gcc-Enable-static-PIE.patch   |   0
  .../fix-segmentation-fault-precompiled-hdr.patch   |   0
  ...s-canadian_7.1.bb => gcc-cross-canadian_7.2.bb} |   0
  ...oss-initial_7.1.bb => gcc-cross-initial_7.2.bb} |   0
  .../gcc/{gcc-cross_7.1.bb => gcc-cross_7.2.bb} |   0
  ...-initial_7.1.bb => gcc-crosssdk-initial_7.2.bb} |   0
  .../{gcc-crosssdk_7.1.bb => gcc-crosssdk_7.2.bb}   |   0
  .../gcc/{gcc-runtime_7.1.bb => gcc-runtime_7.2.bb} |   0
  ...gcc-sanitizers_7.1.bb => gcc-sanitizers_7.2.bb} |   0
  .../gcc/{gcc-source_7.1.bb => gcc-source_7.2.bb}   |   0
  .../gcc/{gcc_7.1.bb => gcc_7.2.bb} |   0
  ...libgcc-initial_7.1.bb => libgcc-initial_7.2.bb} |   0
  .../gcc/{libgcc_7.1.bb => libgcc_7.2.bb}   |   0
  .../gcc/{libgfortran_7.1.bb => libgfortran_7.2.bb} |   0
  58 files changed, 6 insertions(+), 238 deletions(-)
  delete mode 100644

Re: [OE-core] [PATCH 1/1] shadow: fix CVE-2017-12424

2017-08-21 Thread Randy MacLeod


On 2017-08-18 04:20 PM, Randy MacLeod wrote:

On 2017-08-16 07:34 AM, Jussi Kukkonen wrote:
On 16 August 2017 at 13:28, Chen Qi > wrote:


Backport a patch to fix CVE-2017-12424.

In shadow before 4.5, the newusers tool could be made to manipulate
internal data structures in ways unintended by the authors.

Reference link: https://nvd.nist.gov/vuln/detail/CVE-2017-12424


CVE: CVE-2017-12424


I don't object to the patch but I'm wondering if there is a reason we 
are taking the shadow sources from debian instead of the upstream 
github*? shadow 4.5 seems to have been out for months already but 
Debian hasn't taken it yet...


*) https://github.com/shadow-maint/shadow

Jussi



Good point. It's late in the release but maybe
not too late to update shadow.

Qi,
If you could give it a try and let us know if there are any
'gotchas' that would prevent or make the upgrade risky,
that would be great.


Turns out that Qi will only be able do this at the start of
the oe-core-2.5 development cycle.

../Randy




--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5

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

Re: [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request

On Mon, Aug 21, 2017 at 8:11 AM, Bruce Ashfield 
wrote:

>
>
> On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
>
>> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> > Hi all,
>> >
>> > Here's the collected set of kernel changes that are ready for the M3
>> > builds.
>> >
>> > We have some kernel meta data changes:
>> >
>> >   kernel-yocto: configuration updates: x86 features
>> >   linux-yocto/4.1: fix fsl-ls10xx sdhci
>> >   linux-yocto: add usb-net configs by default
>> >
>> > Some bug fixes:
>> >
>> >   kernel-yocto: ensure that only valid BSPs are built
>> >   linux-yocto/4.10: CVE & misc fixes
>> >
>> > And the important changes are the addition of the 4.12 kernel + libc
>> > headers
>> > and the removal of the 4.1 kernel.
>> >
>> > I also have some -stable updates queued for the active kernel
>> > versions, but
>> > they will come out once this series has made it into the tree, since
>> > I'm
>> > trying to isolate any 4.12 issues from other -stable updates.
>> >
>> > I built and booted all the qemu targets for 4.12, and have built for
>> > core-image-sato, core-image-kernel-dev, glibc and muslc for all of
>> > the
>> > architectures. My testing didn't pick up any regressions, but I was
>> > battling
>> > some other build errors (non kernel related) during my testing, so I
>> > can
>> > never be 100% sure.
>> >
>> > I've sent patches to poky to remove/bump any references to the 4.1
>> > kernel
>> > .. if I've missed any, I'm sure people will shout.
>>
>> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>>
>> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
>> steps/BuildImages_1/logs/stdio
>> 
>>
>> Error:
>>  Problem: conflicting requests
>>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>>
>
> Hmm. I've built that exact combination on two different builders in the
> past week
> and have never seen this.
>
> How do I find out about the environment on that machine ? Because I'm not
> going
> to be able to reproduce it here.
>

A little bit more information. Saul fixed this earlier this year, and I'm
still carrying
a patch that ensures that /usr/bin/awk is in the ver_linux script instead
of /bin/awk.
That fix used to satisfy a similar requirement.

That being said, I did notice that Saul's change was accepted upstream and
the
patch I'm carrying is not correctly applied (but it should be an invalid
patch, not
a reference to /bin/awk).

I've fixed that patch, and am building the build-appliance image now.

I will have a new set of SRCREVs for linux-yocto-4.12, but I can't say if
they'll
fix the particular issue that the autobuilder is seeing.

Bruce


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



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

Re: [OE-core] [meta-oe][PATCH] Dhrystone: add recipe 2.1

2017-08-21 Thread Jussi Kukkonen

On 21 August 2017 at 13:23, Jose Alarcon  wrote:

> Dhrystone is a synthetic computing benchmark program developed
> in 1984 by Reinhold P. Weicker intended to be representative of
> system (integer) programming.
>
> https://en.wikipedia.org/wiki/Dhrystone
>
> Signed-off-by: Jose Alarcon 
> ---
>  .../dhrystone/dhrystone-2.1/dhrystone.patch| 81
> ++
>  .../recipes-benchmark/dhrystone/dhrystone_2.1.bb   | 26 +++
>  2 files changed, 107 insertions(+)
>  create mode 100644 meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/
> dhrystone.patch
>  create mode 100644 meta-oe/recipes-benchmark/dhrystone/dhrystone_2.1.bb


Hi,

Please send meta-oe patches to openembedded-de...@lists.openembedded.org.

Also this part is unlikely to be welcome on oe-devel either:
> LICENSE = "Proprietary"

I think I remember seeing a dhrystone recipe submission with an open source
license (NCSA maybe?) last year .

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

[OE-core] ✗ patchtest: failure for Dhrystone: add recipe 2.1

== Series Details ==

Series: Dhrystone: add recipe 2.1
Revision: 1
URL   : https://patchwork.openembedded.org/series/8390/
State : failure

== Summary ==


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



* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/dhrystone.patch (possible 
values: Pending, Submitted, Accepted, Backport, Denied, Inappropriate)



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

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

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

[OE-core] [PATCH] connman: Fix for CVE-2017-12865

2017-08-21 Thread Sona Sarmadi

dnsproxy: Fix crash on malformed DNS response
If the response query string is malformed, we might access memory
pass the end of "name" variable in parse_response().

[YOCTO #11959]

Signed-off-by: Sona Sarmadi 
---
 .../connman/connman/CVE-2017-12865.patch   | 87 ++
 meta/recipes-connectivity/connman/connman_1.34.bb  |  1 +
 2 files changed, 88 insertions(+)
 create mode 100644 
meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch

diff --git a/meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch 
b/meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch
new file mode 100644
index 000..45f78f1
--- /dev/null
+++ b/meta/recipes-connectivity/connman/connman/CVE-2017-12865.patch
@@ -0,0 +1,87 @@
+From 5c281d182ecdd0a424b64f7698f32467f8f67b71 Mon Sep 17 00:00:00 2001
+From: Jukka Rissanen 
+Date: Wed, 9 Aug 2017 10:16:46 +0300
+Subject: dnsproxy: Fix crash on malformed DNS response
+
+If the response query string is malformed, we might access memory
+pass the end of "name" variable in parse_response().
+
+CVE: CVE-2017-12865
+Upstream-Status: Backport 
[https://git.kernel.org/pub/scm/network/connman/connman.git/patch/?id=5c281d182ecdd0a424b64f7698f32467f8f67b71]
+
+Signed-off-by: Sona Sarmadi 
+---
+ src/dnsproxy.c | 16 ++--
+ 1 file changed, 10 insertions(+), 6 deletions(-)
+
+diff --git a/src/dnsproxy.c b/src/dnsproxy.c
+index 38ac5bf..40b4f15 100644
+--- a/src/dnsproxy.c
 b/src/dnsproxy.c
+@@ -838,7 +838,7 @@ static struct cache_entry *cache_check(gpointer request, 
int *qtype, int proto)
+ static int get_name(int counter,
+   unsigned char *pkt, unsigned char *start, unsigned char *max,
+   unsigned char *output, int output_max, int *output_len,
+-  unsigned char **end, char *name, int *name_len)
++  unsigned char **end, char *name, size_t max_name, int *name_len)
+ {
+   unsigned char *p;
+ 
+@@ -859,7 +859,7 @@ static int get_name(int counter,
+ 
+   return get_name(counter + 1, pkt, pkt + offset, max,
+   output, output_max, output_len, end,
+-  name, name_len);
++  name, max_name, name_len);
+   } else {
+   unsigned label_len = *p;
+ 
+@@ -869,6 +869,9 @@ static int get_name(int counter,
+   if (*output_len > output_max)
+   return -ENOBUFS;
+ 
++  if ((*name_len + 1 + label_len + 1) > max_name)
++  return -ENOBUFS;
++
+   /*
+* We need the original name in order to check
+* if this answer is the correct one.
+@@ -900,14 +903,14 @@ static int parse_rr(unsigned char *buf, unsigned char 
*start,
+   unsigned char *response, unsigned int *response_size,
+   uint16_t *type, uint16_t *class, int *ttl, int *rdlen,
+   unsigned char **end,
+-  char *name)
++  char *name, size_t max_name)
+ {
+   struct domain_rr *rr;
+   int err, offset;
+   int name_len = 0, output_len = 0, max_rsp = *response_size;
+ 
+   err = get_name(0, buf, start, max, response, max_rsp,
+-  _len, end, name, _len);
++  _len, end, name, max_name, _len);
+   if (err < 0)
+   return err;
+ 
+@@ -1033,7 +1036,8 @@ static int parse_response(unsigned char *buf, int buflen,
+   memset(rsp, 0, sizeof(rsp));
+ 
+   ret = parse_rr(buf, ptr, buf + buflen, rsp, _len,
+-  type, class, ttl, , , name);
++  type, class, ttl, , , name,
++  sizeof(name) - 1);
+   if (ret != 0) {
+   err = ret;
+   goto out;
+@@ -1099,7 +1103,7 @@ static int parse_response(unsigned char *buf, int buflen,
+*/
+   ret = get_name(0, buf, next - rdlen, buf + buflen,
+   rsp, rsp_len, _len, ,
+-  name, _len);
++  name, sizeof(name) - 1, _len);
+   if (ret != 0) {
+   /* just ignore the error at this point */
+   ptr = next;
+-- 
+cgit v1.1
+
diff --git a/meta/recipes-connectivity/connman/connman_1.34.bb 
b/meta/recipes-connectivity/connman/connman_1.34.bb
index 868f940..dc2c688 100644
--- a/meta/recipes-connectivity/connman/connman_1.34.bb
+++ b/meta/recipes-connectivity/connman/connman_1.34.bb
@@ -7,6 +7,7 @@ SRC_URI  = 
"${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
 file://connman \

Re: [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request

On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > Hi all,
> >
> > Here's the collected set of kernel changes that are ready for the M3
> > builds.
> >
> > We have some kernel meta data changes:
> >
> >   kernel-yocto: configuration updates: x86 features
> >   linux-yocto/4.1: fix fsl-ls10xx sdhci
> >   linux-yocto: add usb-net configs by default
> >
> > Some bug fixes:
> >
> >   kernel-yocto: ensure that only valid BSPs are built
> >   linux-yocto/4.10: CVE & misc fixes
> >
> > And the important changes are the addition of the 4.12 kernel + libc
> > headers
> > and the removal of the 4.1 kernel.
> >
> > I also have some -stable updates queued for the active kernel
> > versions, but
> > they will come out once this series has made it into the tree, since
> > I'm
> > trying to isolate any 4.12 issues from other -stable updates.
> >
> > I built and booted all the qemu targets for 4.12, and have built for
> > core-image-sato, core-image-kernel-dev, glibc and muslc for all of
> > the
> > architectures. My testing didn't pick up any regressions, but I was
> > battling
> > some other build errors (non kernel related) during my testing, so I
> > can
> > never be 100% sure.
> >
> > I've sent patches to poky to remove/bump any references to the 4.1
> > kernel
> > .. if I've missed any, I'm sure people will shout.
>
> I added an extra patch for the ones you missed in meta-yocto-bsp ;-)
>
> Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
> steps/BuildImages_1/logs/stdio
>
> Error:
>  Problem: conflicting requests
>   - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64
>

Hmm. I've built that exact combination on two different builders in the
past week
and have never seen this.

How do I find out about the environment on that machine ? Because I'm not
going
to be able to reproduce it here.

Bruce


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



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

[OE-core] [meta-oe][PATCH] Dhrystone: add recipe 2.1

2017-08-21 Thread Jose Alarcon

Dhrystone is a synthetic computing benchmark program developed
in 1984 by Reinhold P. Weicker intended to be representative of
system (integer) programming.

https://en.wikipedia.org/wiki/Dhrystone

Signed-off-by: Jose Alarcon 
---
 .../dhrystone/dhrystone-2.1/dhrystone.patch| 81 ++
 .../recipes-benchmark/dhrystone/dhrystone_2.1.bb   | 26 +++
 2 files changed, 107 insertions(+)
 create mode 100644 
meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/dhrystone.patch
 create mode 100644 meta-oe/recipes-benchmark/dhrystone/dhrystone_2.1.bb

diff --git a/meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/dhrystone.patch 
b/meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/dhrystone.patch
new file mode 100644
index 000..ae93aba
--- /dev/null
+++ b/meta-oe/recipes-benchmark/dhrystone/dhrystone-2.1/dhrystone.patch
@@ -0,0 +1,81 @@
+dhrystone: fix compilation problems
+
+This patch fixes two compilation errors with original
+dhrystone sources:
+* Redefinition of times() with wrong return type
+  - Fixed by commenting out the unnecessary redefinition
+* Undefined identifier HZ
+  - Originally HZ was supposed to be the clock frequency
+value for times()
+  - For Linux, the frequency should come from sysconf
+  - This patch defines global varible HZ and initializes
+it from sysconf
+
+Additionally, this patch adds a simple Makefile.
+
+upstream-status : Pending
+
+Sign-off-by: Kimmo Surakka 
+Signed-off-by: Jose Alarcon 
+---
+
+diff -Naur dhry.orig/dhry_1.c dhry/dhry_1.c
+--- dhry.orig/dhry_1.c 2015-07-20 14:25:58.059945353 +0300
 dhry/dhry_1.c  2015-07-20 12:43:25.318945353 +0300
+@@ -45,11 +45,15 @@
+ 
+ #ifdef TIMES
+ struct tms  time_info;
+-extern  int times ();
++/* extern  int times (); */
+ /* see library function "times" */
+ #define Too_Small_Time 120
+ /* Measurements should last at least about 2 seconds */
+ #endif
++#ifndef HZ
++#include   /* sysconf */
++   long HZ;
++#endif
+ #ifdef TIME
+ extern long time();
+ /* see library function "time"  */
+@@ -84,6 +88,9 @@
+ 
+   /* Initializations */
+ 
++#ifndef HZ
++  HZ = sysconf(_SC_CLK_TCK);
++#endif
+   Next_Ptr_Glob = (Rec_Pointer) malloc (sizeof (Rec_Type));
+   Ptr_Glob = (Rec_Pointer) malloc (sizeof (Rec_Type));
+ 
+diff -Naur dhry.orig/dhry.h dhry/dhry.h
+--- dhry.orig/dhry.h   2015-07-20 14:25:58.054945353 +0300
 dhry/dhry.h2015-07-20 12:42:59.903945353 +0300
+@@ -420,4 +420,6 @@
+   } variant;
+   } Rec_Type, *Rec_Pointer;
+ 
+-
++#ifndef HZ
++   extern long HZ;
++#endif
+diff -Naur dhry.orig/Makefile dhry/Makefile
+--- dhry.orig/Makefile 1970-01-01 02:00:00.0 +0200
 dhry/Makefile  2015-07-20 14:10:45.832945353 +0300
+@@ -0,0 +1,15 @@
++CC=gcc
++
++all: dhry
++
++dhry: dhry_1.o dhry_2.o
++  $(CC) $(LDFLAGS) -o $@ $^ $(LOADLIBES) $(LDLIBS)
++
++dhry_1.o: dhry_1.c dhry.h
++
++dhry_2.o: dhry_2.c dhry.h
++
++clean:
++  rm -f *.o *~
++
++.PHONY: all clean
diff --git a/meta-oe/recipes-benchmark/dhrystone/dhrystone_2.1.bb 
b/meta-oe/recipes-benchmark/dhrystone/dhrystone_2.1.bb
new file mode 100644
index 000..a11e8cf
--- /dev/null
+++ b/meta-oe/recipes-benchmark/dhrystone/dhrystone_2.1.bb
@@ -0,0 +1,26 @@
+SUMMARY = "Dhrystone CPU benchmark"
+LICENSE = "Proprietary"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/files/common-licenses/Proprietary;md5=0557f9d92cf58f2ccdd50f62f8ac0b28"
+
+SRC_URI = "http://www.netlib.org/benchmark/dhry-c;downloadfilename=dhry-c.shar 
\
+   file://dhrystone.patch"
+SRC_URI[md5sum] = "75aa5909c174eed98c134be2f56307da"
+SRC_URI[sha256sum] = 
"038a7e9169787125c3451a6c941f3aca5db2d2f3863871afcdce154ef17f4e3e"
+
+# Need to override Makefile variables
+EXTRA_OEMAKE = "-e MAKEFLAGS="
+
+do_unpack() {
+[ -d ${S} ] || mkdir -p ${S}
+cd ${S}
+sh ${DL_DIR}/dhry-c.shar
+}
+do_install() {
+install -d ${D}${bindir}
+install -m 0755 ${S}/dhry ${D}${bindir}
+}
+
+# Prevent procedure merging as required by dhrystone.c:
+CFLAGS += "-fno-lto"
+
+LDFLAGS += "-fno-lto"
-- 
2.10.1

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

[OE-core] [PATCH] meta: move some text from oe-setup-builddir to conf-notes.txt

2017-08-21 Thread liu . ming50

From: Ming Liu 

This allows the end users to be able to override the entire notes
showing on the shell console. For instance, Our company uses a
external conf-notes.txt, and we run bitbake with some extra variables,
looks like: F=xxx D=xxx M=xxx bitbake , so we want to show
exactly these texts on the shell console, that's why we need this
change.

Signed-off-by: Ming Liu 
---
 meta/conf/conf-notes.txt  | 5 +
 scripts/oe-setup-builddir | 7 ---
 2 files changed, 5 insertions(+), 7 deletions(-)

diff --git a/meta/conf/conf-notes.txt b/meta/conf/conf-notes.txt
index 2f2932b..f1a4f4d 100644
--- a/meta/conf/conf-notes.txt
+++ b/meta/conf/conf-notes.txt
@@ -1,3 +1,8 @@
+
+### Shell environment set up for builds. ###
+
+You can now run 'bitbake '
+
 Common targets are:
 core-image-minimal
 core-image-sato
diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
index ef49551..55d73ca 100755
--- a/scripts/oe-setup-builddir
+++ b/scripts/oe-setup-builddir
@@ -133,13 +133,6 @@ EOM
 #unset SHOWYPDOC
 fi
 
-cat <'
-
-EOM
 if [ -z "$OECORENOTESCONF" ]; then
 OECORENOTESCONF="$OEROOT/meta/conf/conf-notes.txt"
 fi
-- 
2.7.4

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

[OE-core] [PATCH] base.bbclass: trim duplicated whitespaces from BUILDCFG_VARS

2017-08-21 Thread liu . ming50

From: Ming Liu 

To give a example:
Before the change, in our build console, TUNE_FEATURES looks like:
...
TUNE_FEATURES = "arm armv7a vfp  neoncortexa8"
...

After the change:
...
TUNE_FEATURES = "arm armv7a vfp neon cortexa8"
...

Signed-off-by: Ming Liu 
---
 meta/classes/base.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index 8c86977..07734ac 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -206,7 +206,7 @@ def buildcfg_vars(d):
 for var in statusvars:
 value = d.getVar(var)
 if value is not None:
-yield '%-17s = "%s"' % (var, value)
+yield '%-17s = "%s"' % (var, " ".join(value.split()))
 
 def buildcfg_neededvars(d):
 needed_vars = oe.data.typed_value("BUILDCFG_NEEDEDVARS", d)
-- 
2.7.4

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

Re: [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request

On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Hi all,
> 
> Here's the collected set of kernel changes that are ready for the M3
> builds.
> 
> We have some kernel meta data changes:
> 
>   kernel-yocto: configuration updates: x86 features
>   linux-yocto/4.1: fix fsl-ls10xx sdhci
>   linux-yocto: add usb-net configs by default
> 
> Some bug fixes:
> 
>   kernel-yocto: ensure that only valid BSPs are built
>   linux-yocto/4.10: CVE & misc fixes
> 
> And the important changes are the addition of the 4.12 kernel + libc
> headers
> and the removal of the 4.1 kernel.
> 
> I also have some -stable updates queued for the active kernel
> versions, but
> they will come out once this series has made it into the tree, since
> I'm
> trying to isolate any 4.12 issues from other -stable updates.
> 
> I built and booted all the qemu targets for 4.12, and have built for
> core-image-sato, core-image-kernel-dev, glibc and muslc for all of
> the
> architectures. My testing didn't pick up any regressions, but I was
> battling
> some other build errors (non kernel related) during my testing, so I
> can
> never be 100% sure.
> 
> I've sent patches to poky to remove/bump any references to the 4.1
> kernel
> .. if I've missed any, I'm sure people will shout.

I added an extra patch for the ones you missed in meta-yocto-bsp ;-)

Also, https://autobuilder.yocto.io/builders/build-appliance/builds/425/
steps/BuildImages_1/logs/stdio

Error: 
 Problem: conflicting requests
  - nothing provides /bin/awk needed by kernel-devsrc-1.0-r0.0.qemux86_64

Cheers,

Richard


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

Re: [OE-core] openssl10 unusable for many components

Yes, the 'revert' works for me, thanks.

On Mon, Aug 21, 2017 at 11:29 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Fri, 2017-08-18 at 19:29 +0200, Martin Jansa wrote:
> > Even with that patch to rename openssl10 back to openssl we still
> > need to solve the openssl-native which wasn't reverted back to 1.0.
> >
> > Upstream nodejs isn't going to be openssl-1.1 for a bit longer as
> > explained:
> > https://github.com/nodejs/node/pull/14761
> > https://github.com/nodejs/node/pull/11828
> > so it would make sense to revert native and nativesdk versions as
> > well - if it isn't done in oe-core, I'll do it in our own layers to
> > keep the builds going.
>
> Hopefully we have a working 'revert' back to 1.0 in master now as there
> was simply too much breakage for this release.
>
> I would ask that people do try and figure out how to solve some of the
> 1.1 issues in the meantime, hopefully people can enable 1.1 with some
> PREFERRED_VERSION tweaks.
>
> Cheers,
>
> Richard
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH V2] gnupg: 2.1.20 -> 2.1.23

2017-08-21 Thread Hongxu Jia

1. COPYING.LIB: Rename to COPYING.LGPL3.
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=3419a339d9c4e800bf30e9021e05982d8c1021c1

2. Rebase patches:
- pkgconfig.patch -> 0001
- use-pkgconfig-instead-of-npth-config.patch -> 0002
- dirmngr-uses-libgpg-error.patch -> 0003
- autogen.sh-fix-find-version-for-beta-checking.patch -> 0004

3. Fix gpg2 not found
...
dnf -vy makecache

|Cannot download 'http://192.168.7.1:33541': repomd.xml GPG signature
verification error: gpgme_engine_check_version() error: Invalid crypto
engine.
...

The upstream install gpg by default and no gpg2
...
commit a69464b0b6dac88b360a13d3faf19dd7f2a0e02b
Author: Werner Koch 
Date:   Sat Aug 5 14:39:32 2017 +0200

gpg: Install gpg by default under the name gpg.
...
Add --enable-gpg-is-gpg2 to revert it.

Signed-off-by: Hongxu Jia 
---
 ...-config-to-find-pth-instead-of-pth-config.patch | 105 +
 ...0002-use-pkgconfig-instead-of-npth-config.patch |  85 +
 .../gnupg/0003-dirmngr-uses-libgpg-error.patch |  32 +++
 ...gen.sh-fix-find-version-for-beta-checking.patch |  34 +++
 ...gen.sh-fix-find-version-for-beta-checking.patch |  31 --
 .../gnupg/gnupg/dirmngr-uses-libgpg-error.patch|  16 
 meta/recipes-support/gnupg/gnupg/pkgconfig.patch   |  90 --
 .../use-pkgconfig-instead-of-npth-config.patch |  72 --
 meta/recipes-support/gnupg/gnupg_2.1.20.bb |  45 -
 meta/recipes-support/gnupg/gnupg_2.1.23.bb |  46 +
 10 files changed, 302 insertions(+), 254 deletions(-)
 create mode 100644 
meta/recipes-support/gnupg/gnupg/0001-Use-pkg-config-to-find-pth-instead-of-pth-config.patch
 create mode 100644 
meta/recipes-support/gnupg/gnupg/0002-use-pkgconfig-instead-of-npth-config.patch
 create mode 100644 
meta/recipes-support/gnupg/gnupg/0003-dirmngr-uses-libgpg-error.patch
 create mode 100644 
meta/recipes-support/gnupg/gnupg/0004-autogen.sh-fix-find-version-for-beta-checking.patch
 delete mode 100644 
meta/recipes-support/gnupg/gnupg/autogen.sh-fix-find-version-for-beta-checking.patch
 delete mode 100644 
meta/recipes-support/gnupg/gnupg/dirmngr-uses-libgpg-error.patch
 delete mode 100644 meta/recipes-support/gnupg/gnupg/pkgconfig.patch
 delete mode 100644 
meta/recipes-support/gnupg/gnupg/use-pkgconfig-instead-of-npth-config.patch
 delete mode 100644 meta/recipes-support/gnupg/gnupg_2.1.20.bb
 create mode 100644 meta/recipes-support/gnupg/gnupg_2.1.23.bb

diff --git 
a/meta/recipes-support/gnupg/gnupg/0001-Use-pkg-config-to-find-pth-instead-of-pth-config.patch
 
b/meta/recipes-support/gnupg/gnupg/0001-Use-pkg-config-to-find-pth-instead-of-pth-config.patch
new file mode 100644
index 000..5c9c022
--- /dev/null
+++ 
b/meta/recipes-support/gnupg/gnupg/0001-Use-pkg-config-to-find-pth-instead-of-pth-config.patch
@@ -0,0 +1,105 @@
+From 59a3c76d4016ffc615f1c45184f4c6820061d69c Mon Sep 17 00:00:00 2001
+From: Richard Purdie 
+Date: Wed, 16 Aug 2017 11:14:12 +0800
+Subject: [PATCH 1/4] Use pkg-config to find pth instead of pth-config.
+
+Upstream-Status: Denied
+[not submitted but they've been clear they don't want a pkg-config
+dependency]
+
+RP 2014/5/22
+
+Signed-off-by: Richard Purdie 
+
+Rebase to 2.1.23
+Signed-off-by: Hongxu Jia 
+---
+ m4/gnupg-pth.m4 | 53 -
+ 1 file changed, 8 insertions(+), 45 deletions(-)
+
+diff --git a/m4/gnupg-pth.m4 b/m4/gnupg-pth.m4
+index 6dc9e0e..5892531 100644
+--- a/m4/gnupg-pth.m4
 b/m4/gnupg-pth.m4
+@@ -17,33 +17,9 @@ dnl implied warranty of MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.
+ # Taken and modified from the m4 macros which come with Pth.
+ AC_DEFUN([GNUPG_PTH_VERSION_CHECK],
+   [
+-_pth_version=`$PTH_CONFIG --version | awk 'NR==1 {print [$]3}'`
+ _req_version="ifelse([$1],,1.2.0,$1)"
++PKG_CHECK_MODULES(PTH, [pth >= $_req_version], [have_pth=yes], 
[have_pth=no])
+ 
+-AC_MSG_CHECKING(for PTH - version >= $_req_version)
+-for _var in _pth_version _req_version; do
+-eval "_val=\"\$${_var}\""
+-_major=`echo $_val | sed 
's/\([[0-9]]*\)\.\([[0-9]]*\)\([[ab.]]\)\([[0-9]]*\)/\1/'`
+-_minor=`echo $_val | sed 
's/\([[0-9]]*\)\.\([[0-9]]*\)\([[ab.]]\)\([[0-9]]*\)/\2/'`
+-_rtype=`echo $_val | sed 
's/\([[0-9]]*\)\.\([[0-9]]*\)\([[ab.]]\)\([[0-9]]*\)/\3/'`
+-_micro=`echo $_val | sed 
's/\([[0-9]]*\)\.\([[0-9]]*\)\([[ab.]]\)\([[0-9]]*\)/\4/'`
+-case $_rtype in
+-"a" ) _rtype=0 ;;
+-"b" ) _rtype=1 ;;
+-"." ) _rtype=2 ;;
+-esac
+-_hex=`echo dummy | awk '{ printf("%d%02d%1d%02d", major, minor, 
rtype, micro); }' \
+-  "major=$_major" "minor=$_minor" "rtype=$_rtype" "micro=$_micro"`
+-eval "${_var}_hex=\"\$_hex\""
+-done
+-have_pth=no

Re: [OE-core] openssl10 unusable for many components

On Fri, 2017-08-18 at 19:29 +0200, Martin Jansa wrote:
> Even with that patch to rename openssl10 back to openssl we still
> need to solve the openssl-native which wasn't reverted back to 1.0.
> 
> Upstream nodejs isn't going to be openssl-1.1 for a bit longer as
> explained:
> https://github.com/nodejs/node/pull/14761
> https://github.com/nodejs/node/pull/11828
> so it would make sense to revert native and nativesdk versions as
> well - if it isn't done in oe-core, I'll do it in our own layers to
> keep the builds going.

Hopefully we have a working 'revert' back to 1.0 in master now as there
was simply too much breakage for this release.

I would ask that people do try and figure out how to solve some of the
1.1 issues in the meantime, hopefully people can enable 1.1 with some
PREFERRED_VERSION tweaks.

Cheers,

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

[OE-core] [PATCH v2] kernel-module-split: rrecommend kernel-image instead of rdepend

2017-08-21 Thread Martin Hundebøll

Hard depending on the kernel makes it impossible to install kernel
modules without getting the kernel image installed too. This is
inconvenient in e.g. initramdisks, where the kernel is loaded from
outside the initramdisk.

Making the kernel modules rrecommend kernel-image- instead of
rdepending on it, makes it possible to install kernel modules without
the kernel image by setting "kernel-image" in BAD_RECOMMENDATIONS.

Signed-off-by: Martin Hundebøll 
---
 meta/classes/kernel-module-split.bbclass | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel-module-split.bbclass 
b/meta/classes/kernel-module-split.bbclass
index 1035525dac..78843c5474 100644
--- a/meta/classes/kernel-module-split.bbclass
+++ b/meta/classes/kernel-module-split.bbclass
@@ -120,6 +120,11 @@ python split_kernel_module_packages () {
 rdepends[dep] = []
 d.setVar('RDEPENDS_' + pkg, bb.utils.join_deps(rdepends, 
commasep=False))
 
+# let kernel modules runtime recommend kernel image
+rrecommends = bb.utils.explode_dep_versions2(d.getVar('RRECOMMENDS_' + 
pkg) or "")
+rrecommends['kernel-image'] = []
+d.setVar('RRECOMMENDS_' + pkg, bb.utils.join_deps(rrecommends, 
commasep=False))
+
 # Avoid automatic -dev recommendations for modules ending with -dev.
 d.setVarFlag('RRECOMMENDS_' + pkg, 'nodeprrecs', 1)
 
@@ -138,7 +143,7 @@ python split_kernel_module_packages () {
 postinst = d.getVar('pkg_postinst_modules')
 postrm = d.getVar('pkg_postrm_modules')
 
-modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
file_regex=module_regex, output_pattern=module_pattern, description='%s kernel 
module', postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
extra_depends='kernel-%s' % (d.getVar("KERNEL_VERSION")))
+modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
file_regex=module_regex, output_pattern=module_pattern, description='%s kernel 
module', postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
extra_depends='')
 if modules:
 metapkg = d.getVar('KERNEL_MODULES_META_PACKAGE')
 d.appendVar('RDEPENDS_' + metapkg, ' '+' '.join(modules))
-- 
2.14.1

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

[OE-core] ✗ patchtest: failure for kernel-module-split: rrecommend kernel-image instead of rdepend

== Series Details ==

Series: kernel-module-split: rrecommend kernel-image instead of rdepend
Revision: 1
URL   : https://patchwork.openembedded.org/series/8386/
State : failure

== Summary ==


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



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



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

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

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

Re: [OE-core] [oe-commits] [openembedded-core] 01/02: package.bbclass: Restore functionality to detect RPM dependencies

This seems to find a many more missed dependencies which is good thing.

There is +- 20 failures found in meta-oe recipes and there is still at
least one in oe-core:

ERROR: nativesdk-libcheck-0.10.0-r0 do_package_qa: QA Issue:
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/checkmk
contained in package nativesdk-libcheck requires
/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/gawk, but no
providers found in RDEPENDS_nativesdk-libcheck? [file-rdeps]

I wonder why this one wasn't catched by oe-core autobuilder.

On Wed, Aug 16, 2017 at 6:44 PM,  wrote:

> This is an automated email from the git hooks/post-receive script.
>
> rpurdie pushed a commit to branch master-next
> in repository openembedded-core.
>
> commit bf017930036f19b3d6df8e5b50d9979ee7045c5c
> Author: Peter Kjellerstedt 
> AuthorDate: Tue Aug 15 16:41:56 2017 -0500
>
> package.bbclass: Restore functionality to detect RPM dependencies
>
> During the transition to dnf and rpm4, the functionality to
> automatically make RPM determine dependencies was lost.
>
> Before the transition, an OE specific tool called rpmdeps-oecore had
> been added to the rpm suit. It was based on the rpmdeps tool that is
> part of rpm. For each file specified on its command line, it would
> output the provides and requires that RPM could determine.
>
> During the transition to rpm4, rpmdeps-oecore was replaced with the
> standard rpmdeps. However, what no one noticed was that unless rpmdeps
> is given options, e.g., -P or -R, to tell it what it should output, it
> will not output anything. Thus, it would do all the work to determine
> the requirements, but would keep silent about it. And since no output
> from rpmdeps is expected unless there are requirements, there were no
> warnings indicating that everything was not working as expected.
>
> Porting the old rpmdeps-oecore to work with rpm4 is not really
> possible since it relied on being able to access internals of RPM that
> are no longer available. However, it turned out that rpmdeps had a
> debug option, --rpmfcdebug, that would output exactly the information
> that we need, albeit in a different format and to stderr. To make this
> usable, rpmdeps has now received a new option, --alldeps, which sends
> the information we need to stdout.
>
> (From OE-Core rev: 958501b3d9201aaabb81ec644c6049e0c9b737e7)
>
> Signed-off-by: Peter Kjellerstedt 
> Signed-off-by: Mark Hatle 
> Signed-off-by: Richard Purdie 
> ---
>  meta/classes/package.bbclass |  5 ++--
>  meta/lib/oe/package.py   | 60 ++
> +-
>  2 files changed, 44 insertions(+), 21 deletions(-)
>
> diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> index d2fa617..2fe30da 100644
> --- a/meta/classes/package.bbclass
> +++ b/meta/classes/package.bbclass
> @@ -1453,7 +1453,7 @@ if [ x"$D" = "x" ]; then
>  fi
>  }
>
> -RPMDEPS = "${STAGING_LIBDIR_NATIVE}/rpm/rpmdeps --rcfile
> ${STAGING_LIBDIR_NATIVE}/rpm/rpmrc  --macros 
> ${STAGING_LIBDIR_NATIVE}/rpm/macros
> --define '_rpmconfigdir ${STAGING_LIBDIR_NATIVE}/rpm/'"
> +RPMDEPS = "${STAGING_LIBDIR_NATIVE}/rpm/rpmdeps --alldeps"
>
>  # Collect perfile run-time dependency metadata
>  # Output:
> @@ -1470,7 +1470,6 @@ python package_do_filedeps() {
>  pkgdest = d.getVar('PKGDEST')
>  packages = d.getVar('PACKAGES')
>  rpmdeps = d.getVar('RPMDEPS')
> -magic = d.expand("${STAGING_DIR_NATIVE}${datadir_native}/misc/
> magic.mgc")
>
>  def chunks(files, n):
>  return [files[i:i+n] for i in range(0, len(files), n)]
> @@ -1482,7 +1481,7 @@ python package_do_filedeps() {
>  if pkg.endswith('-dbg') or pkg.endswith('-doc') or
> pkg.find('-locale-') != -1 or pkg.find('-localedata-') != -1 or
> pkg.find('-gconv-') != -1 or pkg.find('-charmap-') != -1 or
> pkg.startswith('kernel-module-') or pkg.endswith('-src'):
>  continue
>  for files in chunks(pkgfiles[pkg], 100):
> -pkglist.append((pkg, files, rpmdeps, pkgdest, magic))
> +pkglist.append((pkg, files, rpmdeps, pkgdest))
>
>  processed = oe.utils.multiprocess_exec( pkglist,
> oe.package.filedeprunner)
>
> diff --git a/meta/lib/oe/package.py b/meta/lib/oe/package.py
> index 43748b2..a79c668 100644
> --- a/meta/lib/oe/package.py
> +++ b/meta/lib/oe/package.py
> @@ -162,44 +162,68 @@ def file_translate(file):
>  def filedeprunner(arg):
>  import re, subprocess, shlex
>
> -(pkg, pkgfiles, rpmdeps, pkgdest, magic) = arg
> +(pkg, pkgfiles, rpmdeps, pkgdest) = arg
>  provides = {}
>  requires = {}
>
> -r = re.compile(r'[<>=]+ +[^ ]*')
> +file_re = re.compile(r'\s+\d+\s(.*)')
> +dep_re = re.compile(r'\s+(\S)\s+(.*)')
> +r = re.compile(r'[<>=]+\s+\S*')
>
>

Re: [OE-core] [PATCH] pango: 1.40.6 -> 1.40.10

2017-08-21 Thread Huang, Qiyu

Dear Jussi

Well， I just modify the patch to make it adapt new version, but I really don't 
understand what does it claims to do.

huangqy

From: Jussi Kukkonen [mailto:jussi.kukko...@intel.com]
Sent: Thursday, August 17, 2017 2:35 PM
To: Huang, Qiyu 
Cc: Patches and discussions about the oe-core layer 

Subject: Re: [OE-core] [PATCH] pango: 1.40.6 -> 1.40.10

On 17 August 2017 at 08:50, Huang Qiyu 
> wrote:
1) Upgrade pango from 1.40.6 to 1.40.10.
2) Modify 0001-Enforce-recreation-of-docs-pango.types-it-is-build-c.patch for 
pango 1.40.10.

I admit I didn't understand the patch even before this but especially now that 
pango.types is apparently no longer shipped, how does the patch do what it 
claims to do?

Jussi



Signed-off-by: Huang Qiyu 
>
---
 ...reation-of-docs-pango.types-it-is-build-c.patch | 104 ++---
 .../pango/{pango_1.40.6.bb => 
pango_1.40.10.bb}|   4 +-
 2 files changed, 10 insertions(+), 98 deletions(-)
 rename meta/recipes-graphics/pango/{pango_1.40.6.bb => 
pango_1.40.10.bb} (92%)

diff --git 
a/meta/recipes-graphics/pango/pango/0001-Enforce-recreation-of-docs-pango.types-it-is-build-c.patch
 
b/meta/recipes-graphics/pango/pango/0001-Enforce-recreation-of-docs-pango.types-it-is-build-c.patch
index 6784a10..481f267 100644
--- 
a/meta/recipes-graphics/pango/pango/0001-Enforce-recreation-of-docs-pango.types-it-is-build-c.patch
+++ 
b/meta/recipes-graphics/pango/pango/0001-Enforce-recreation-of-docs-pango.types-it-is-build-c.patch
@@ -1,6 +1,3 @@
-From 526a6a9fc9a1cfe75c521c8bb39b61754fe42fe8 Mon Sep 17 00:00:00 2001
-From: Alexander Kanavin >
-Date: Fri, 2 Sep 2016 14:00:24 +0300
 Subject: [PATCH] Enforce recreation of docs/pango.types; it is build
  configuration-specific.

@@ -8,14 +5,15 @@ In particular, it needs to exclude references to PangoXft if 
Xft is not availabl

 Upstream-Status: Pending
 Signed-off-by: Alexander Kanavin 
>
+
+Update for pango 1.40.10.
+Signed-off-by: Huang Qiyu 
>
 ---
- docs/Makefile.am | 17 
- docs/pango.types | 80 
- 2 files changed, 5 insertions(+), 92 deletions(-)
- delete mode 100644 docs/pango.types
+ docs/Makefile.am | 17 +
+ 1 file changed, 5 insertions(+), 12 deletions(-)

 diff --git a/docs/Makefile.am b/docs/Makefile.am
-index f5f1317..8947a99 100644
+index f5f1317..76b8661 100644
 --- a/docs/Makefile.am
 +++ b/docs/Makefile.am
 @@ -49,6 +49,10 @@ IGNORE_HFILES=  \
@@ -52,96 +50,10 @@ index f5f1317..8947a99 100644
version.xml.in  \
 -  check.docs  \
 -  pango.types
-+  check.docs
++check.docs

  # force doc rebulid after configure
  dist-hook-local: dist-local-check-no-cross-references all-local
-diff --git a/docs/pango.types b/docs/pango.types
-deleted file mode 100644
-index 7d93cda..000
 a/docs/pango.types
-+++ /dev/null
-@@ -1,80 +0,0 @@
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--#include 
--
--pango_alignment_get_type
--pango_attr_list_get_type
--pango_attr_type_get_type
--pango_bidi_type_get_type
--pango_cairo_fc_font_map_get_type
--pango_cairo_font_get_type
--pango_cairo_font_map_get_type
--pango_color_get_type
--pango_context_get_type
--pango_coverage_level_get_type
--pango_direction_get_type
--pango_ellipsize_mode_get_type
--pango_engine_get_type
--pango_engine_lang_get_type
--pango_engine_shape_get_type
--pango_fc_decoder_get_type
--pango_fc_font_get_type
--pango_fc_font_map_get_type
--pango_font_description_get_type
--pango_font_face_get_type
--pango_font_family_get_type
--pango_font_get_type
--pango_font_map_get_type
--pango_font_mask_get_type
--pango_font_metrics_get_type
--pango_fontset_get_type
--pango_fontset_simple_get_type
--pango_ft2_font_map_get_type
--pango_glyph_item_get_type
--pango_glyph_item_iter_get_type
--pango_glyph_string_get_type
--pango_gravity_get_type
--pango_gravity_hint_get_type
--pango_item_get_type
--pango_language_get_type
--pango_layout_get_type
--pango_layout_iter_get_type
--pango_layout_line_get_type
--pango_matrix_get_type
--pango_ot_info_get_type
--pango_ot_ruleset_get_type
--pango_render_part_get_type
--pango_renderer_get_type
--pango_script_get_type
--pango_stretch_get_type
--pango_style_get_type

[OE-core] [PATCH] kernel-module-split: rrecommend kernel-image instead of rdepend

2017-08-21 Thread Martin Hundebøll

Hard depending on the kernel makes it impossible to install kernel
modules without getting the kernel image installed too. This is
inconvenient in e.g. initramdisks, where the kernel is loaded from
outside the initramdisk.

Making the kernel modules rrecommend kernel-image- instead of
rdepending on it, makes it possible to install kernel modules without
the kernel image by setting "kernel-image" in BAD_RECOMMENDATIONS.

Signed-off-by: Martin Hundebøll 
---
 meta/classes/kernel-module-split.bbclass | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel-module-split.bbclass 
b/meta/classes/kernel-module-split.bbclass
index ba9cc1517e..7a0260e3db 100644
--- a/meta/classes/kernel-module-split.bbclass
+++ b/meta/classes/kernel-module-split.bbclass
@@ -120,6 +120,11 @@ python split_kernel_module_packages () {
 rdepends[dep] = []
 d.setVar('RDEPENDS_' + pkg, bb.utils.join_deps(rdepends, 
commasep=False))
 
+# let kernel modules runtime recommend kernel image
+rrecommends = bb.utils.explode_dep_versions2(d.getVar('RRECOMMENDS_' + 
pkg) or "")
+rrecommends['kernel-image'] = []
+d.setVar('RRECOMMENDS_' + pkg, bb.utils.join_deps(rrecommends, 
commasep=False))
+
 # Avoid automatic -dev recommendations for modules ending with -dev.
 d.setVarFlag('RRECOMMENDS_' + pkg, 'nodeprrecs', 1)
 
@@ -138,7 +143,7 @@ python split_kernel_module_packages () {
 postinst = d.getVar('pkg_postinst_modules')
 postrm = d.getVar('pkg_postrm_modules')
 
-modules = do_split_packages(d, root='/lib/modules', 
file_regex=module_regex, output_pattern=module_pattern, description='%s kernel 
module', postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
extra_depends='kernel-%s' % (d.getVar("KERNEL_VERSION")))
+modules = do_split_packages(d, root='/lib/modules', 
file_regex=module_regex, output_pattern=module_pattern, description='%s kernel 
module', postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
extra_depends='')
 if modules:
 metapkg = d.getVar('KERNEL_MODULES_META_PACKAGE')
 d.appendVar('RDEPENDS_' + metapkg, ' '+' '.join(modules))
-- 
2.14.1

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

Re: [OE-core] [PATCH 01/10] oeqa/targetcontrol.py: simplify checking for qemu_use_kvm


Ping.

// Robert

On 08/09/2017 05:46 PM, Robert Yang wrote:



On 08/08/2017 11:30 PM, Richard Purdie wrote:

On Mon, 2017-07-31 at 02:50 -0700, Robert Yang wrote:

The "if qemu_use_kvm" is not needed.

Signed-off-by: Robert Yang 
---
 meta/lib/oeqa/targetcontrol.py | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/targetcontrol.py
b/meta/lib/oeqa/targetcontrol.py
index 3255e3a5c63..11e6c820e85 100644
--- a/meta/lib/oeqa/targetcontrol.py
+++ b/meta/lib/oeqa/targetcontrol.py
@@ -132,9 +132,8 @@ class QemuTarget(BaseTarget):
 dump_host_cmds = d.getVar("testimage_dump_host")
 dump_dir = d.getVar("TESTIMAGE_DUMP_DIR")
 qemu_use_kvm = d.getVar("QEMU_USE_KVM")
-if qemu_use_kvm and \
-   (qemu_use_kvm == "True" and "x86" in d.getVar("MACHINE") or \
-d.getVar("MACHINE") in qemu_use_kvm.split()):
+if qemu_use_kvm == "True" and "x86" in d.getVar("MACHINE") or \
+d.getVar("MACHINE") in qemu_use_kvm.split():
 use_kvm = True
 else:
 use_kvm = False



It is needed since qemu_use_kvm could be None and None.split() will
cause an error.


Thanks, I removed from the repo:

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

// Robert



Cheers,

Richard


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

[OE-core] [PATCH 3/5] tcl: 8.6.6 -> 0.8.7

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/tcltk/{tcl_8.6.6.bb => tcl_8.6.7.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-devtools/tcltk/{tcl_8.6.6.bb => tcl_8.6.7.bb} (95%)

diff --git a/meta/recipes-devtools/tcltk/tcl_8.6.6.bb 
b/meta/recipes-devtools/tcltk/tcl_8.6.7.bb
similarity index 95%
rename from meta/recipes-devtools/tcltk/tcl_8.6.6.bb
rename to meta/recipes-devtools/tcltk/tcl_8.6.7.bb
index 5cecf65..d00d2dc 100644
--- a/meta/recipes-devtools/tcltk/tcl_8.6.6.bb
+++ b/meta/recipes-devtools/tcltk/tcl_8.6.7.bb
@@ -24,8 +24,8 @@ SRC_URI = "${BASE_SRC_URI} \
file://alter-includedir.patch \
file://run-ptest \
 "
-SRC_URI[md5sum] = "5193aea8107839a79df8ac709552ecb7"
-SRC_URI[sha256sum] = 
"a265409781e4b3edcc4ef822533071b34c3dc6790b893963809b9fe221befe07"
+SRC_URI[md5sum] = "5673aaf45b5de5d8dd80bb3daaeb8838"
+SRC_URI[sha256sum] = 
"7c6b8f84e37332423cfe5bae503440d88450da8cc1243496249faa5268026ba5"
 
 SRC_URI_class-native = "${BASE_SRC_URI}"
 
-- 
2.10.2

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

[OE-core] [PATCH 2/5] libbsd: 0.8.5 -> 0.8.6

Signed-off-by: Robert Yang 
---
 meta/recipes-support/libbsd/{libbsd_0.8.5.bb => libbsd_0.8.6.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/libbsd/{libbsd_0.8.5.bb => libbsd_0.8.6.bb} (92%)

diff --git a/meta/recipes-support/libbsd/libbsd_0.8.5.bb 
b/meta/recipes-support/libbsd/libbsd_0.8.6.bb
similarity index 92%
rename from meta/recipes-support/libbsd/libbsd_0.8.5.bb
rename to meta/recipes-support/libbsd/libbsd_0.8.6.bb
index 6a6b669..182543f 100644
--- a/meta/recipes-support/libbsd/libbsd_0.8.5.bb
+++ b/meta/recipes-support/libbsd/libbsd_0.8.6.bb
@@ -42,8 +42,8 @@ SRC_URI_append_libc-musl  = " \
 file://0002-Remove-funopen.patch \
 "
 
-SRC_URI[md5sum] = "f1a0dc285f5d21ea40ef5bfc9b647346"
-SRC_URI[sha256sum] = 
"7647d024f41389305272c263da933a6f2a978213c1801592f47e68d83ac05b28"
+SRC_URI[md5sum] = "4ab7bec639af17d0aacb50222b479110"
+SRC_URI[sha256sum] = 
"467fbf9df1f49af11f7f686691057c8c0a7613ae5a870577bef9155de39f9687"
 
 inherit autotools pkgconfig
 
-- 
2.10.2

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

[OE-core] [PATCH 1/5] git: 2.13.2 -> 2.13.3

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/git/git_2.13.2.bb | 11 ---
 meta/recipes-devtools/git/git_2.13.3.bb | 11 +++
 2 files changed, 11 insertions(+), 11 deletions(-)
 delete mode 100644 meta/recipes-devtools/git/git_2.13.2.bb
 create mode 100644 meta/recipes-devtools/git/git_2.13.3.bb

diff --git a/meta/recipes-devtools/git/git_2.13.2.bb 
b/meta/recipes-devtools/git/git_2.13.2.bb
deleted file mode 100644
index e7cae40..000
--- a/meta/recipes-devtools/git/git_2.13.2.bb
+++ /dev/null
@@ -1,11 +0,0 @@
-require git.inc
-
-EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
- 
ac_cv_fread_reads_directories=${ac_cv_fread_reads_directories=yes} \
- "
-EXTRA_OEMAKE += "NO_GETTEXT=1"
-
-SRC_URI[tarball.md5sum] = "894583cddfb0ec3b0156484966f9db9c"
-SRC_URI[tarball.sha256sum] = 
"e19d450648d6d100eb93abaa5d06ffbc778394fb502354b7026d73e9bcbc3160"
-SRC_URI[manpages.md5sum] = "97384d23f2ee88d5ce51ffc75096bd3e"
-SRC_URI[manpages.sha256sum] = 
"1c2bd0a2340b2ef118b7b167a8fec6cc05eb18cad9043e6e7a95fd8a70bb8c4c"
diff --git a/meta/recipes-devtools/git/git_2.13.3.bb 
b/meta/recipes-devtools/git/git_2.13.3.bb
new file mode 100644
index 000..b3e3887
--- /dev/null
+++ b/meta/recipes-devtools/git/git_2.13.3.bb
@@ -0,0 +1,11 @@
+require git.inc
+
+EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
+ 
ac_cv_fread_reads_directories=${ac_cv_fread_reads_directories=yes} \
+ "
+EXTRA_OEMAKE += "NO_GETTEXT=1"
+
+SRC_URI[tarball.md5sum] = "d2dc550f6693ba7e5b16212b2714f59f"
+SRC_URI[tarball.sha256sum] = 
"1497001772f630d49809e981672edfe3e3ce1a1d18e905cd539c4d2f4dbcd75a"
+SRC_URI[manpages.md5sum] = "3037d11a4f4cdd19435871c267ca48b4"
+SRC_URI[manpages.sha256sum] = 
"f9b302eeb08ce08934e7afb42280ce9294411fbf5f7b6ac3fcc236e8031f10c5"
-- 
2.10.2

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

[OE-core] [PATCH 0/5] Packages upgrade

The following changes since commit 5c9ef0734d23909b5694ed43cdbb205c2ba9ca95:

  devtool/copy_buildsystem: adds meta-skeleton layer in the eSDK installation. 
(2017-08-19 22:15:25 +0100)

are available in the git repository at:

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

Robert Yang (5):
  git: 2.13.2 -> 2.13.3
  libbsd: 0.8.5 -> 0.8.6
  tcl: 8.6.6 -> 0.8.7
  e2fsprogs: 1.43.4 -> 1.43.5
  strace: 4.17 -> 4.18

 ...-with-exit-status-0-if-no-errors-were-fix.patch | 255 -
 .../e2fsprogs/e2fsprogs-1.43-sysmacros.patch   | 130 ---
 .../{e2fsprogs_1.43.4.bb => e2fsprogs_1.43.5.bb}   |   4 +-
 meta/recipes-devtools/git/git_2.13.2.bb|  11 -
 meta/recipes-devtools/git/git_2.13.3.bb|  11 +
 ...8-replace-struct-ucontext-with-ucontext_t.patch |  31 ---
 .../strace/strace/Makefile-ptest.patch |   2 +-
 .../strace/strace/update-gawk-paths.patch  |  58 ++---
 .../strace/{strace_4.17.bb => strace_4.18.bb}  |   7 +-
 .../tcltk/{tcl_8.6.6.bb => tcl_8.6.7.bb}   |   4 +-
 .../libbsd/{libbsd_0.8.5.bb => libbsd_0.8.6.bb}|   4 +-
 11 files changed, 49 insertions(+), 468 deletions(-)
 delete mode 100644 
meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
 delete mode 100644 
meta/recipes-devtools/e2fsprogs/e2fsprogs/e2fsprogs-1.43-sysmacros.patch
 rename meta/recipes-devtools/e2fsprogs/{e2fsprogs_1.43.4.bb => 
e2fsprogs_1.43.5.bb} (95%)
 delete mode 100644 meta/recipes-devtools/git/git_2.13.2.bb
 create mode 100644 meta/recipes-devtools/git/git_2.13.3.bb
 delete mode 100644 
meta/recipes-devtools/strace/strace/0008-replace-struct-ucontext-with-ucontext_t.patch
 rename meta/recipes-devtools/strace/{strace_4.17.bb => strace_4.18.bb} (83%)
 rename meta/recipes-devtools/tcltk/{tcl_8.6.6.bb => tcl_8.6.7.bb} (95%)
 rename meta/recipes-support/libbsd/{libbsd_0.8.5.bb => libbsd_0.8.6.bb} (92%)

-- 
2.10.2

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

[OE-core] [PATCH 5/5] strace: 4.17 -> 4.18

- Updated update-gawk-paths.patch.
- Updated Makefile-ptest.patch
- Removed 0008-replace-struct-ucontext-with-ucontext_t.patch which is already in
  the source.
- The LIC_FILES_CHKSUM is changed because the years have been updated,
  the contents are the same.

Signed-off-by: Robert Yang 
---
 ...8-replace-struct-ucontext-with-ucontext_t.patch | 31 
 .../strace/strace/Makefile-ptest.patch |  2 +-
 .../strace/strace/update-gawk-paths.patch  | 58 +++---
 .../strace/{strace_4.17.bb => strace_4.18.bb}  |  7 ++-
 4 files changed, 33 insertions(+), 65 deletions(-)
 delete mode 100644 
meta/recipes-devtools/strace/strace/0008-replace-struct-ucontext-with-ucontext_t.patch
 rename meta/recipes-devtools/strace/{strace_4.17.bb => strace_4.18.bb} (83%)

diff --git 
a/meta/recipes-devtools/strace/strace/0008-replace-struct-ucontext-with-ucontext_t.patch
 
b/meta/recipes-devtools/strace/strace/0008-replace-struct-ucontext-with-ucontext_t.patch
deleted file mode 100644
index 1985d81..000
--- 
a/meta/recipes-devtools/strace/strace/0008-replace-struct-ucontext-with-ucontext_t.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From 07f71a12cb88919c6113284fc43bf4967e5e2bc1 Mon Sep 17 00:00:00 2001
-From: Khem Raj 
-Date: Wed, 28 Jun 2017 11:36:57 -0700
-Subject: [PATCH 8/8] replace struct ucontext with ucontext_t
-
-glibc >= 2.26 has dropped the tag struct ucontext
-from ucontext_t type
-
-Upstream-Status: Submitted
-
-Signed-off-by: Khem Raj 

- linux/arm/arch_sigreturn.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/linux/arm/arch_sigreturn.c b/linux/arm/arch_sigreturn.c
-index b60dad8..a2b7100 100644
 a/linux/arm/arch_sigreturn.c
-+++ b/linux/arm/arch_sigreturn.c
-@@ -9,7 +9,7 @@ arch_sigreturn(struct tcb *tcp)
- #ifdef AARCH64
-   tcp->currpers == 0 ?
-   (*aarch64_sp_ptr + SIZEOF_STRUCT_SIGINFO +
--   offsetof(struct ucontext, uc_sigmask)) :
-+   offsetof(ucontext_t, uc_sigmask)) :
- #endif
-   (*arm_sp_ptr +
-OFFSETOF_STRUCT_UCONTEXT_UC_SIGMASK);
--- 
-2.13.2
-
diff --git a/meta/recipes-devtools/strace/strace/Makefile-ptest.patch 
b/meta/recipes-devtools/strace/strace/Makefile-ptest.patch
index 07ea0b3..97bcc90 100644
--- a/meta/recipes-devtools/strace/strace/Makefile-ptest.patch
+++ b/meta/recipes-devtools/strace/strace/Makefile-ptest.patch
@@ -51,7 +51,7 @@ index 5aa7f89..a55a355 100644
 +  install $(srcdir)/$$file $(DESTDIR)/$(TESTDIR); \
 +  sed -i -e 's/$${srcdir=.}/./g' $(DESTDIR)/$(TESTDIR)/$$file; \
 +  done
-+  for i in net net-fd scm_rights-fd sigaction; do sed -i -e 
's/$$srcdir/./g' $(DESTDIR)/$(TESTDIR)/$$i.test; done
++  for i in net scm_rights-fd rt_sigaction; do sed -i -e 's/$$srcdir/./g' 
$(DESTDIR)/$(TESTDIR)/$$i.test; done
 -- 
 2.13.2
 
diff --git a/meta/recipes-devtools/strace/strace/update-gawk-paths.patch 
b/meta/recipes-devtools/strace/strace/update-gawk-paths.patch
index 94ee53c..f6ffa8e 100644
--- a/meta/recipes-devtools/strace/strace/update-gawk-paths.patch
+++ b/meta/recipes-devtools/strace/strace/update-gawk-paths.patch
@@ -12,20 +12,20 @@ Upstream-Status: Inappropriate [configuration]
 
 Signed-off-by: Andre McCurdy 
 ---
- mpers.awk| 2 +-
- tests-m32/caps.awk   | 2 +-
- tests-m32/match.awk  | 2 +-
- tests-m32/sigaction.awk  | 2 +-
- tests-mx32/caps.awk  | 2 +-
- tests-mx32/match.awk | 2 +-
- tests-mx32/sigaction.awk | 2 +-
- tests/caps.awk   | 2 +-
- tests/match.awk  | 2 +-
- tests/sigaction.awk  | 2 +-
+ mpers.awk   | 2 +-
+ tests-m32/caps.awk  | 2 +-
+ tests-m32/match.awk | 2 +-
+ tests-m32/rt_sigaction.awk  | 2 +-
+ tests-mx32/caps.awk | 2 +-
+ tests-mx32/match.awk| 2 +-
+ tests-mx32/rt_sigaction.awk | 2 +-
+ tests/caps.awk  | 2 +-
+ tests/match.awk | 2 +-
+ tests/rt_sigaction.awk  | 2 +-
  10 files changed, 10 insertions(+), 10 deletions(-)
 
 diff --git a/mpers.awk b/mpers.awk
-index 99248c5..ff10520 100644
+index fe54763..b5238a8 100644
 --- a/mpers.awk
 +++ b/mpers.awk
 @@ -1,4 +1,4 @@
@@ -35,7 +35,7 @@ index 99248c5..ff10520 100644
  # Copyright (c) 2015 Elvira Khabirova 
  # Copyright (c) 2015-2016 Dmitry V. Levin 
 diff --git a/tests-m32/caps.awk b/tests-m32/caps.awk
-index 67003ac..a66f1f0 100644
+index c6e31ef..5efc6cc 100644
 --- a/tests-m32/caps.awk
 +++ b/tests-m32/caps.awk
 @@ -1,4 +1,4 @@
@@ -54,18 +54,18 @@ index abfbae9..f2740bf 100644
  #
  # Copyright (c) 2014-2015 Dmitry V. Levin 
  # All rights reserved.
-diff --git a/tests-m32/sigaction.awk b/tests-m32/sigaction.awk
-index 5c6b6d0..3e14464 100644
 a/tests-m32/sigaction.awk
-+++ b/tests-m32/sigaction.awk
+diff

[OE-core] [PATCH 4/5] e2fsprogs: 1.43.4 -> 1.43.5

Removed the following 2 patches which are already in the source:
- 0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
- e2fsprogs-1.43-sysmacros.patch

Signed-off-by: Robert Yang 
---
 ...-with-exit-status-0-if-no-errors-were-fix.patch | 255 -
 .../e2fsprogs/e2fsprogs-1.43-sysmacros.patch   | 130 ---
 .../{e2fsprogs_1.43.4.bb => e2fsprogs_1.43.5.bb}   |   4 +-
 3 files changed, 1 insertion(+), 388 deletions(-)
 delete mode 100644 
meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
 delete mode 100644 
meta/recipes-devtools/e2fsprogs/e2fsprogs/e2fsprogs-1.43-sysmacros.patch
 rename meta/recipes-devtools/e2fsprogs/{e2fsprogs_1.43.4.bb => 
e2fsprogs_1.43.5.bb} (95%)

diff --git 
a/meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
 
b/meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
deleted file mode 100644
index 1d17520..000
--- 
a/meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-exit-with-exit-status-0-if-no-errors-were-fix.patch
+++ /dev/null
@@ -1,255 +0,0 @@
-From bf9f3b6d5b10d19218b4ed904c12b22e36ec57dd Mon Sep 17 00:00:00 2001
-From: Theodore Ts'o 
-Date: Thu, 16 Feb 2017 22:02:35 -0500
-Subject: [PATCH] e2fsck: exit with exit status 0 if no errors were fixed
-
-Previously, e2fsck would exit with a status code of 1 even though the
-only changes that it made to the file system were various
-optimziations and not fixing file system corruption.  Since the man
-page states that an exit status of 1 means "file system errors
-corrupted", fix e2fsck to return an exit status of 0.
-
-Upstream-Status: Backport
-
-Signed-off-by: Theodore Ts'o 
-Signed-off-by: Daniel Schultz 

- e2fsck/e2fsck.conf.5.in |  7 +++
- e2fsck/journal.c|  1 +
- e2fsck/problem.c|  8 +---
- e2fsck/problemP.h   |  1 +
- e2fsck/unix.c   | 20 
- tests/f_collapse_extent_tree/expect.1   |  2 +-
- tests/f_compress_extent_tree_level/expect.1 |  2 +-
- tests/f_convert_bmap/expect.1   |  2 +-
- tests/f_convert_bmap_and_extent/expect.1|  2 +-
- tests/f_extent_htree/expect.1   |  2 +-
- tests/f_jnl_errno/expect.1  |  2 +-
- tests/f_journal/expect.1|  2 +-
- tests/f_orphan/expect.1 |  2 +-
- tests/f_orphan_extents_inode/expect.1   |  2 +-
- tests/f_rehash_dir/expect.1 |  2 +-
- tests/f_unsorted_EAs/expect.1   |  2 +-
- 16 files changed, 41 insertions(+), 18 deletions(-)
-
-diff --git a/e2fsck/e2fsck.conf.5.in b/e2fsck/e2fsck.conf.5.in
-index 1848bdb..0bfc76a 100644
 a/e2fsck/e2fsck.conf.5.in
-+++ b/e2fsck/e2fsck.conf.5.in
-@@ -303,6 +303,13 @@ of 'should this problem be fixed?'.  The
- option even overrides the
- .B -y
- option given on the command-line (just for the specific problem, of course).
-+.TP
-+.I not_a_fix
-+This boolean option, it set to true, marks the problem as
-+one where if the user gives permission to make the requested change,
-+it does not mean that the file system had a problem which has since
-+been fixed.  This is used for requests to optimize the file system's
-+data structure, such as pruning an extent tree.
- @TDB_MAN_COMMENT@.SH THE [scratch_files] STANZA
- @TDB_MAN_COMMENT@The following relations are defined in the
- @TDB_MAN_COMMENT@.I [scratch_files]
-diff --git a/e2fsck/journal.c b/e2fsck/journal.c
-index 46fe7b4..c4f58f1 100644
 a/e2fsck/journal.c
-+++ b/e2fsck/journal.c
-@@ -572,6 +572,7 @@ static void clear_v2_journal_fields(journal_t *journal)
-   if (!fix_problem(ctx, PR_0_CLEAR_V2_JOURNAL, ))
-   return;
- 
-+  ctx->flags |= E2F_FLAG_PROBLEMS_FIXED;
-   memset(((char *) journal->j_superblock) + V1_SB_SIZE, 0,
-  ctx->fs->blocksize-V1_SB_SIZE);
-   mark_buffer_dirty(journal->j_sb_buffer);
-diff --git a/e2fsck/problem.c b/e2fsck/problem.c
-index 34a671e..4b25069 100644
 a/e2fsck/problem.c
-+++ b/e2fsck/problem.c
-@@ -1276,12 +1276,12 @@ static struct e2fsck_problem problem_table[] = {
-   /* Inode extent tree could be shorter */
-   { PR_1E_CAN_COLLAPSE_EXTENT_TREE,
- N_("@i %i @x tree (at level %b) could be shorter.  "),
--PROMPT_FIX, PR_NO_OK | PR_PREEN_NO | PR_PREEN_OK },
-+PROMPT_FIX, PR_NO_OK | PR_PREEN_NO | PR_PREEN_OK | PR_NOT_A_FIX },
- 
-   /* Inode extent tree could be narrower */
-   { PR_1E_CAN_NARROW_EXTENT_TREE,
- N_("@i %i @x tree (at level %b) could be narrower.  "),
--PROMPT_FIX, PR_NO_OK | PR_PREEN_NO | PR_PREEN_OK },
-+PROMPT_FIX, PR_NO_OK | PR_PREEN_NO | PR_PREEN_OK | PR_NOT_A_FIX },
- 
-   /* Pass 2 errors */

Re: [OE-core] [PATCH] oe/path.py: copyhardlinktree: don't overwrite existing symlinks

2017-08-21 Thread Ioan-Adrian Ratiu

On Fri, 18 Aug 2017, Richard Purdie  wrote:
> On Wed, 2017-08-16 at 14:13 +0300, Ioan-Adrian Ratiu wrote:
>> Starting with tar>=1.26 the default behaviour when extracting is to
>> overwrite symlinks and a '-h' flag was added for tar to follow them.
>>
>> The primary use case for this is to allow ${DEPLOY_DIR_IPK/RPM/DEB}
>> to
>> be symlinks and avoid copyhardlinktree replacing those symlinks with
>> a
>> normal directory.
>>
>> Signed-off-by: Ioan-Adrian Ratiu 
>> ---
>>  meta/lib/oe/path.py | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Does the -h option exist for tar < 1.26?

Actually it was introduced for extraction in tar 1.24, but for the
archiving command it existed much longer (I went back and confirmed
until release 1.14 in 2004 where the tar git log ends).

The tar git commit which added -h for extraction in 1.24 is:
14efeb9f956e38d7be (tar: --dereference consistency)

-h is set by default when creating archives for systems supporting
symlinks, but -h when extracting is not set by default.

Sorry for the 1.24/1.26 mixup, I'll ammend the patch msg in v2.

Do you want me to do some version checking? (GNU tar 1.24 was released
in 2011).

Ionel

>
> Cheers,
>
> Richard
National Instruments Romania S.R.L.
--
B-dul 21 Decembrie 1989, nr. 77, A2
Cluj-Napoca 400604, Romania
C.I.F.: RO17961616 | O.R.C.: J12/3337/2005
Telefon: +40 264 406428 | Fax: +40 264 406429
E-mail: office.c...@ni.com
Web: romania.ni.com

Vanzari si suport tehnic:
Telefon gratuit : 0800 070071
E-mail vanzari: ni.roma...@ni.com
E-mail suport tehnic: techsupp...@ni.com
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] gcc: Upgrade to 7.2.0 release

Still reproducible without thumb:
http://errors.yoctoproject.org/Errors/Details/152666/

this might be also triggered by this upgrade:
http://errors.yoctoproject.org/Errors/Details/152770/

or from glibc final upgrade or something else, hard to know when exactly it
started as previous world builds were pretty much useless with all those
openssl caused issues.

On Mon, Aug 21, 2017 at 2:37 AM, Khem Raj  wrote:

>
> On Sun, Aug 20, 2017 at 5:31 PM Martin Jansa 
> wrote:
>
>> Seems like python-matplotlib reliably triggers ICE in this version of gcc:
>>
>> http://errors.yoctoproject.org/Errors/Details/152664/
>>
>> I think I haven't seen this one with 7.1.
>>
>
> Can you try disabling thumb mode and see if this works ?
>
>>
>> On Tue, Aug 15, 2017 at 7:42 AM, Khem Raj  wrote:
>>
>>> Drop upstreamed patches
>>>
>>> Signed-off-by: Khem Raj 
>>> ---
>>>  ...r-Use-stack_t-instead-of-struct-sigaltsta.patch |  81 ---
>>>  ...0-replace-struct-ucontext-with-ucontext_t.patch | 149
>>> -
>>>  .../gcc/{gcc-7.1.inc => gcc-7.2.inc}   |  14 +-
>>>  .../0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch |   0
>>>  .../{gcc-7.1 => gcc-7.2}/0008-c99-snprintf.patch   |   0
>>>  .../0009-gcc-poison-system-directories.patch   |   0
>>>  .../0010-gcc-poison-dir-extend.patch   |   0
>>>  .../0011-gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch |   0
>>>  .../0012-64-bit-multilib-hack.patch|   0
>>>  .../0013-optional-libstdc.patch|   0
>>>  ...0014-gcc-disable-MASK_RELAX_PIC_CALLS-bit.patch |   0
>>>  .../0015-COLLECT_GCC_OPTIONS.patch |   0
>>>  ...efaults.h-in-B-instead-of-S-and-t-oe-in-B.patch |   0
>>>  .../0017-fortran-cross-compile-hack.patch  |   0
>>>  .../0018-cpp-honor-sysroot.patch   |   0
>>>  .../0019-MIPS64-Default-to-N64-ABI.patch   |   0
>>>  ...C_DYNAMIC_LINKER-and-UCLIBC_DYNAMIC_LINKE.patch |   0
>>>  ...0021-gcc-Fix-argument-list-too-long-error.patch |   0
>>>  .../{gcc-7.1 => gcc-7.2}/0022-Disable-sdt.patch|   0
>>>  .../gcc/{gcc-7.1 => gcc-7.2}/0023-libtool.patch|   0
>>>  ...4-pass-fix-v4bx-to-linker-to-support-EABI.patch |   0
>>>  ...tilib-config-files-from-B-instead-of-usin.patch |   0
>>>  ...-libdir-from-.la-which-usually-points-to-.patch |   0
>>>  .../gcc/{gcc-7.1 => gcc-7.2}/0027-export-CPP.patch |   0
>>>  ...AltiVec-generation-on-powepc-linux-target.patch |   0
>>>  ...-MULTILIB_OSDIRNAMES-and-other-multilib-o.patch |   0
>>>  ...Ensure-target-gcc-headers-can-be-included.patch |   0
>>>  ...-t-build-with-disable-dependency-tracking.patch |   0
>>>  ...h-host-directory-during-relink-if-inst_pr.patch |   0
>>>  ...IBS_DIR-replacement-instead-of-hardcoding.patch |   0
>>>  .../0034-aarch64-Add-support-for-musl-ldso.patch   |   0
>>>  ...ibcc1-fix-libcc1-s-install-path-and-rpath.patch |   0
>>>  ...-handle-sysroot-support-for-nativesdk-gcc.patch |   0
>>>  ...et-sysroot-gcc-version-specific-dirs-with.patch |   0
>>>  ...-various-_FOR_BUILD-and-related-variables.patch |   0
>>>  .../0039-nios2-Define-MUSL_DYNAMIC_LINKER.patch|   0
>>>  ...shared-to-link-commandline-for-musl-targe.patch |   0
>>>  ...c-libcpp-support-ffile-prefix-map-old-new.patch |   0
>>>  ...ug-prefix-map-to-replace-ffile-prefix-map.patch |   0
>>>  ...-fdebug-prefix-map-support-to-remap-sourc.patch |   0
>>>  ...44-libgcc-Add-knob-to-use-ldbl-128-on-ppc.patch |   0
>>>  ...bgcc-using-LDFLAGS-not-just-SHLIB_LDFLAGS.patch |   0
>>>  ...e-alias-for-__cpu_indicator_init-instead-.patch |   0
>>>  .../0047-sync-gcc-stddef.h-with-musl.patch |   0
>>>  .../0048-gcc-Enable-static-PIE.patch   |   0
>>>  .../fix-segmentation-fault-precompiled-hdr.patch   |   0
>>>  ...s-canadian_7.1.bb => gcc-cross-canadian_7.2.bb} |   0
>>>  ...oss-initial_7.1.bb => gcc-cross-initial_7.2.bb} |   0
>>>  .../gcc/{gcc-cross_7.1.bb => gcc-cross_7.2.bb} |   0
>>>  ...-initial_7.1.bb => gcc-crosssdk-initial_7.2.bb} |   0
>>>  .../{gcc-crosssdk_7.1.bb => gcc-crosssdk_7.2.bb}   |   0
>>>  .../gcc/{gcc-runtime_7.1.bb => gcc-runtime_7.2.bb} |   0
>>>  ...gcc-sanitizers_7.1.bb => gcc-sanitizers_7.2.bb} |   0
>>>  .../gcc/{gcc-source_7.1.bb => gcc-source_7.2.bb}   |   0
>>>  .../gcc/{gcc_7.1.bb => gcc_7.2.bb} |   0
>>>  ...libgcc-initial_7.1.bb => libgcc-initial_7.2.bb} |   0
>>>  .../gcc/{libgcc_7.1.bb => libgcc_7.2.bb}   |   0
>>>  .../gcc/{libgfortran_7.1.bb => libgfortran_7.2.bb} |   0
>>>  58 files changed, 6 insertions(+), 238 deletions(-)
>>>  delete mode 100644 meta/recipes-devtools/gcc/gcc-
>>> 7.1/0049-libsanitizer-Use-stack_t-instead-of-struct-sigaltsta.patch
>>>  delete mode 100644 meta/recipes-devtools/gcc/gcc-
>>> 7.1/0050-replace-struct-ucontext-with-ucontext_t.patch
>>>  rename meta/recipes-devtools/gcc/{gcc-7.1.inc => gcc-7.2.inc} (91%)
>>>  rename meta/recipes-devtools/gcc/{gcc-7.1 =>

Re: [OE-core] [PATCH] insane.bbclass: write QA issues to log file only when thei are in ERROR_QA or WARN_QA

Just notice typo in subject s/thei/they/g, will resend soon, in the
meantime is there some feedback on this?

Alternatively we can write them with NOTE: WARN: ERROR: prefix like with
the logger, so that the qa.log can be filtered by severity of the issue.

TL;DR; version:
In my jenkins builds I'm printing content of qa.log at the end of usually
very long build log, so that they are easier to spot in one place and
because I get a lot of "version-going-backwards" warnings which I'm not
interested in anymore at all, I've removed them from ERROR_QA - but then I
was wondering why I still see very long list of "version-going-backwards"
warnings, but those were from qa.log. It would work for me fine to just
"grep -v ^NOTE: qa.log" at the end of jenkins build if the alternative
solution is more acceptable.

On Mon, Aug 21, 2017 at 8:56 AM, Martin Jansa 
wrote:

> * QA check which aren't included in WARN_QA and ERROR_QA are shown
>   during the build only as NOTE message (not shown at all with default
>   knotty setting), so it might be surprising to see them later in qa.log
>   file
>
> Signed-off-by: Martin Jansa 
> ---
>  meta/classes/insane.bbclass | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
> index b7177c9b32..44e4a01c92 100644
> --- a/meta/classes/insane.bbclass
> +++ b/meta/classes/insane.bbclass
> @@ -184,12 +184,13 @@ def package_qa_write_error(type, error, d):
>  f.write("%s: %s [%s]\n" % (p, error, type))
>
>  def package_qa_handle_error(error_class, error_msg, d):
> -package_qa_write_error(error_class, error_msg, d)
>  if error_class in (d.getVar("ERROR_QA") or "").split():
> +package_qa_write_error(error_class, error_msg, d)
>  bb.error("QA Issue: %s [%s]" % (error_msg, error_class))
>  d.setVar("QA_SANE", False)
>  return False
>  elif error_class in (d.getVar("WARN_QA") or "").split():
> +package_qa_write_error(error_class, error_msg, d)
>  bb.warn("QA Issue: %s [%s]" % (error_msg, error_class))
>  else:
>  bb.note("QA Issue: %s [%s]" % (error_msg, error_class))
> --
> 2.14.0
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] insane.bbclass: write QA issues to log file only when thei are in ERROR_QA or WARN_QA