[OE-core] [PATCH] boost: Replace math::static_lcm with integer

2016-09-12 Thread jackie.huang
From: Jackie Huang 

Replace math with integer according to the commit upstream:
---
de05d62aea8e7309026806acf76370e5b1ed9cf3
Replace math::gcd,lcm with integer.
---

or it fails with:
./boost/pool/pool.hpp:363:28: error: 'math' has not been declared

Signed-off-by: Jackie Huang 
---
 meta/recipes-support/boost/boost/boost-CVE-2012-2677.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/boost/boost/boost-CVE-2012-2677.patch 
b/meta/recipes-support/boost/boost/boost-CVE-2012-2677.patch
index 0cd97cc..917617a 100644
--- a/meta/recipes-support/boost/boost/boost-CVE-2012-2677.patch
+++ b/meta/recipes-support/boost/boost/boost-CVE-2012-2677.patch
@@ -26,7 +26,7 @@ index c47b11f..417a1e0 100644
 +size_type max_chunks() const
 +{ //! Calculated maximum number of memory chunks that can be allocated in 
a single call by this Pool.
 +  size_type partition_size = alloc_size();
-+  size_type POD_size = math::static_lcm::value + sizeof(size_type);
++  size_type POD_size = integer::static_lcm::value + sizeof(size_type);
 +  size_type max_chunks = (std::numeric_limits::max() - 
POD_size) / alloc_size();
 +
 +  return max_chunks;
-- 
2.8.1

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


[OE-core] [PATCH] shadow: use relaxed usernames

2016-09-12 Thread mingli.yu
From: Shan Hai 

The groupadd from shadow does not allow upper case group names, the
same is true for the upstream shadow. But distributions like
Debian/Ubuntu/CentOS has their own way to cope with this problem,
this patch is picked up from CentOS release 7.0 to relax the usernames
restrictions to allow the upper case group names, and the relaxation is
POSIX compliant because POSIX indicate that usernames are composed of
characters from the portable filename character set [A-Za-z0-9._-].

Signed-off-by: Shan Hai 
Signed-off-by: Mingli Yu 
---
 .../shadow/files/shadow-relaxed-usernames.patch| 100 +
 meta/recipes-extended/shadow/shadow.inc|   1 +
 2 files changed, 101 insertions(+)
 create mode 100644 
meta/recipes-extended/shadow/files/shadow-relaxed-usernames.patch

diff --git a/meta/recipes-extended/shadow/files/shadow-relaxed-usernames.patch 
b/meta/recipes-extended/shadow/files/shadow-relaxed-usernames.patch
new file mode 100644
index 000..1af04d5
--- /dev/null
+++ b/meta/recipes-extended/shadow/files/shadow-relaxed-usernames.patch
@@ -0,0 +1,100 @@
+
+The groupadd from shadow does not allow upper case group names, the
+same is true for the upstream shadow. But distributions like
+Debian/Ubuntu/CentOS has their own way to cope with this problem,
+this patch is picked up from CentOS release 7.0 to relax the usernames
+restrictions to allow the upper case group names, and the relaxation is
+POSIX compliant because POSIX indicate that usernames are composed of 
+characters from the portable filename character set [A-Za-z0-9._-].
+
+Upstream-Status: Pending
+
+Signed-off-by: Shan Hai  
+
+diff -urpN a/libmisc/chkname.c b/libmisc/chkname.c
+index 5089112..f40a0da 100644
+--- a/libmisc/chkname.c
 b/libmisc/chkname.c
+@@ -49,21 +49,28 @@
+ static bool is_valid_name (const char *name)
+ {
+   /*
+-   * User/group names must match [a-z_][a-z0-9_-]*[$]
+-   */
+-  if (('\0' == *name) ||
+-  !((('a' <= *name) && ('z' >= *name)) || ('_' == *name))) {
++ * User/group names must match gnu e-regex:
++ *[a-zA-Z0-9_.][a-zA-Z0-9_.-]{0,30}[a-zA-Z0-9_.$-]?
++ *
++ * as a non-POSIX, extension, allow "$" as the last char for
++ * sake of Samba 3.x "add machine script"
++ */
++  if ( ('\0' == *name) ||
++ !((*name >= 'a' && *name <= 'z') ||
++   (*name >= 'A' && *name <= 'Z') ||
++   (*name >= '0' && *name <= '9') ||
++   (*name == '_') || (*name == '.') 
++)) {
+   return false;
+   }
+ 
+   while ('\0' != *++name) {
+-  if (!(( ('a' <= *name) && ('z' >= *name) ) ||
+-( ('0' <= *name) && ('9' >= *name) ) ||
+-('_' == *name) ||
+-('-' == *name) ||
+-('.' == *name) ||
+-( ('$' == *name) && ('\0' == *(name + 1)) )
+-   )) {
++if (!(  (*name >= 'a' && *name <= 'z') ||
++(*name >= 'A' && *name <= 'Z') ||
++(*name >= '0' && *name <= '9') ||
++(*name == '_') || (*name == '.') || (*name == '-') ||
++(*name == '$' && *(name + 1) == '\0') 
++ )) {
+   return false;
+   }
+   }
+diff -urpN a/man/groupadd.8.xml b/man/groupadd.8.xml
+index 230fd0c..94f7807 100644
+--- a/man/groupadd.8.xml
 b/man/groupadd.8.xml
+@@ -222,12 +222,6 @@
+
+  CAVEATS
+  
+-   Groupnames must start with a lower case letter or an underscore,
+-   followed by lower case letters, digits, underscores, or dashes.
+-   They can end with a dollar sign.
+-   In regular expression terms: [a-z_][a-z0-9_-]*[$]?
+- 
+- 
+Groupnames may only be up to _NAME_MAX_LENGTH; characters long.
+  
+  
+diff -urpN a/man/useradd.8.xml b/man/useradd.8.xml
+index 5dec989..fe623b9 100644
+--- a/man/useradd.8.xml
 b/man/useradd.8.xml
+@@ -336,7 +336,7 @@
+   
+   
+ 
+-  Do no create the user's home directory, even if the system
++  Do not create the user's home directory, even if the system
+   wide setting from /etc/login.defs
+   (CREATE_HOME) is set to
+   yes.
+@@ -607,12 +607,6 @@
+ 
+ 
+ 
+-  Usernames must start with a lower case letter or an underscore,
+-  followed by lower case letters, digits, underscores, or dashes.
+-  They can end with a dollar sign.
+-  In regular expression terms: [a-z_][a-z0-9_-]*[$]?
+-
+-
+   Usernames may only be up to 32 characters long.
+ 
+   
diff --git a/meta/recipes-extended/shadow/shadow.inc 
b/meta/recipes-extended/shadow/shadow.inc
index 5605876..35a18f8 100644
--- 

[OE-core] [PATCH] xinetd: add Init Script Actions to xinetd script

2016-09-12 Thread mingli.yu
From: Shan Hai 

The chkconfig fails to list the xinetd service because the xinetd
lacks Init Script Actions in it, add the actions to fix it.

Signed-off-by: Shan Hai 
Signed-off-by: Mingli Yu 
---
 meta/recipes-extended/xinetd/xinetd/xinetd.init | 12 +++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/xinetd/xinetd/xinetd.init 
b/meta/recipes-extended/xinetd/xinetd/xinetd.init
index 777c2c8..a021410 100644
--- a/meta/recipes-extended/xinetd/xinetd/xinetd.init
+++ b/meta/recipes-extended/xinetd/xinetd/xinetd.init
@@ -1,5 +1,15 @@
 #!/bin/sh
-#
+### BEGIN INIT INFO
+# Provides:  inetd
+# Required-Start:$local_fs $remote_fs
+# Required-Stop: $local_fs $remote_fs
+# Should-Start:  $syslog
+# Should-Stop:   $syslog
+# Default-Start: 2 3 4 5
+# Default-Stop:  0 1 6
+# Short-Description: Start or stop the xinetd daemon.
+### END INIT INFO
+
 # /etc/init.d/xinetd  --  script to start and stop xinetd.
 
 # Source function library.
-- 
2.8.1

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


Re: [OE-core] [PATCH] rootfs.py: support absolute paths in IMAGE_DEVICE_TABLES

2016-09-12 Thread Andre McCurdy
On Mon, Sep 12, 2016 at 5:17 PM, Mark Hatle  wrote:
> On 9/12/16 6:00 PM, Andre McCurdy wrote:
>> Paths relative to BBPATH are fine if device table files are always
>> static and contained somewhere within a meta layer. However if device
>> tables are created dynamically, they will be located somewhere within
>> ${TMPDIR} and most conveniently referenced via an absolute path.
>>
>> The legacy IMAGE_DEVICE_TABLE variable supported an absolute path,
>> therefore make IMAGE_DEVICE_TABLES support absolute paths too, to
>> avoid users who need dynamic device table files being dependent on
>> the legacy variable.
>>
>> Signed-off-by: Andre McCurdy 
>> ---
>>  meta/lib/oe/rootfs.py | 9 ++---
>>  1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
>> index a348b97..32cce64 100644
>> --- a/meta/lib/oe/rootfs.py
>> +++ b/meta/lib/oe/rootfs.py
>> @@ -352,8 +352,8 @@ class Rootfs(object, metaclass=ABCMeta):
>>  """
>>  Create devfs:
>>  * IMAGE_DEVICE_TABLE is the old name to an absolute path to a device 
>> table file
>> -* IMAGE_DEVICE_TABLES is a new name for a file, or list of files, 
>> seached
>> -  for in the BBPATH
>> +* IMAGE_DEVICE_TABLES is the new name for a file, or list of files, 
>> which may be
>> +  either absolute paths or paths relative to BBPATH.
>>  If neither are specified then the default name of 
>> files/device_table-minimal.txt
>>  is searched for in the BBPATH (same as the old version.)
>>  """
>> @@ -367,7 +367,10 @@ class Rootfs(object, metaclass=ABCMeta):
>>  if devtables is None:
>>  devtables = 'files/device_table-minimal.txt'
>>  for devtable in devtables.split():
>> -devtable_list.append("%s" % 
>> bb.utils.which(self.d.getVar('BBPATH', True), devtable))
>> +if os.path.isabs(devtable):
>> +devtable_list.append(devtable)
>> +else:
>> +devtable_list.append("%s" % 
>> bb.utils.which(self.d.getVar('BBPATH', True), devtable))
>
> I'm wondering if maybe this is a bug in "bb.utils.which", I thought it would
> return back -- in the case of an absolute path -- if the thing existed or not,
> otherwise would search the BBPATH.  (I'm using the command line version of
> 'which' as my behavioral thinking.)

Hmmm. The behaviour of "bb.utils.which" in the case of an absolute
path is actually to return back the absolute path - but only if the
file exists. If the file doesn't exist, you get back an empty string.
Unfortunately all the test cases I was trying were files which didn't
exist.

But perhaps the bigger issue is that result returned by
self._exec_shell_cmd() isn't checked, so it doesn't really matter
whether devtable_list ends up containing an empty string or an
absolute path to a file which doesn't exist. There's no error or
feedback to the user that something has gone wrong in either case.

Is it really intentional to silently skip over IMAGE_DEVICE_TABLES
entries which don't exist?

> If it is an issue, then it would need a fix in bitbake, and I believe the
> existing code should then work.
>
> (Asking about the behavior on the bitbake list might be worth while in this 
> case.)
>
>>
>>  for devtable in devtable_list:
>>  self._exec_shell_cmd(["makedevs", "-r",
>>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v2] groff: not ship /usr/bin/glilypond

2016-09-12 Thread Yu, Mingli

Any update?

Thanks,


On 2016年09月06日 10:39, mingli...@windriver.com wrote:

From: Mingli Yu 

Not ship /usr/bin/glilypond and related files such
as man file /usr/share/man/man1/glilypond.1 and other
three files related to glilypond under
/usr/lib/groff/glilypond in embedded system, it is because:

- Remove the confusion about glilypond fails to run
   because it lacks dependency on File::HomeDir perl
   module

- We don't often have need for sheet music conversion
   in groff in embedded or IoT devices (glilypond
   transforms sheet music written in the lilypond language
   into the groff language using the .PSPIC request, such
   that groff can transform it into a format that can be
   displayed directly).

Signed-off-by: Mingli Yu 
---
  meta/recipes-extended/groff/groff_1.22.3.bb | 5 +
  1 file changed, 5 insertions(+)

diff --git a/meta/recipes-extended/groff/groff_1.22.3.bb 
b/meta/recipes-extended/groff/groff_1.22.3.bb
index af5acbe..dd241f3 100644
--- a/meta/recipes-extended/groff/groff_1.22.3.bb
+++ b/meta/recipes-extended/groff/groff_1.22.3.bb
@@ -62,6 +62,11 @@ do_install_append() {
if [ -f ${SPECIAL_AWK} ]; then
sed -i -e 's:#!.*awk:#! ${USRBINPATH}/awk:' ${SPECIAL_AWK}
fi
+
+   # not ship /usr/bin/glilypond and its releated files in embedded target 
system
+   rm -rf ${D}${bindir}/glilypond
+   rm -rf ${D}${libdir}/groff/glilypond
+   rm -rf ${D}${mandir}/man1/glilypond*
  }

  do_install_append_class-native() {


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


[OE-core] About runqemu's use cases

2016-09-12 Thread Robert Yang


Hello,

We have a new oe-core/scripts/runqemu now, and I'd like to add something
like "runqemu test" in the future to avoid regressions. It would help a
lot if you can provide the info about how do you use runqemu. There is
a bug tracking this:

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

You can reply here or reply in the bug.

--
Thanks

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


[OE-core] [PATCH 0/1] Optimisation for eSDK tests

2016-09-12 Thread Paul Eggleton
This should reduce the time taken to test the extensible SDK by many
minutes. No doubt there are many other optimisations we could make but
this is a start.


The following changes since commit 4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac:

  oeqa.runtime.smart: work around smart race issues (2016-09-09 12:12:17 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/extsdk-test-fix
  
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/extsdk-test-fix

Paul Eggleton (1):
  oeqa/sdkext/devtool: use a smaller module to test node.js functionality

 meta/lib/oeqa/sdkext/devtool.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.5.5

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


[OE-core] [PATCH 1/1] oeqa/sdkext/devtool: use a smaller module to test node.js functionality

2016-09-12 Thread Paul Eggleton
The "forever" package, despite its innocent description, actually drags
in a surprising number of dependencies and as a result the nodejs test
takes up to 10 minutes as a result. Pick a different example with a much
more reasonable set of dependencies.

Addresses part of [YOCTO #10254].

Signed-off-by: Paul Eggleton 
---
 meta/lib/oeqa/sdkext/devtool.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/sdkext/devtool.py b/meta/lib/oeqa/sdkext/devtool.py
index ba12799..65f41f6 100644
--- a/meta/lib/oeqa/sdkext/devtool.py
+++ b/meta/lib/oeqa/sdkext/devtool.py
@@ -91,7 +91,7 @@ class DevtoolTest(oeSDKExtTest):
 @testcase(1478)
 @skipUnlessPassed('test_devtool_location')
 def test_recipes_for_nodejs(self):
-package_nodejs = "npm://registry.npmjs.org;name=forever;version=0.15.1"
+package_nodejs = "npm://registry.npmjs.org;name=winston;version=2.2.0"
 self._run('devtool add %s ' % package_nodejs)
 try:
 self._run('devtool build %s ' % package_nodejs)
-- 
2.5.5

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


[OE-core] [PATCH 2/4] meta: implement key baserunner features

2016-09-12 Thread jwang
From: zjh 

Baserunner contains three features:
1. load cases from a manifest file
2. load cases from a package such as "oeqa.runtime"
3. create runner engine based on pyunit textrunner

Signed-off-by: zjh 
---
 meta/lib/base/baserunner.py | 44 ++--
 1 file changed, 38 insertions(+), 6 deletions(-)

diff --git a/meta/lib/base/baserunner.py b/meta/lib/base/baserunner.py
index 56b838e..d59872f 100755
--- a/meta/lib/base/baserunner.py
+++ b/meta/lib/base/baserunner.py
@@ -31,30 +31,62 @@ class FakeOptions(object):
 class TestRunnerBase(object):
 '''test runner base '''
 def __init__(self, context=None):
-self.tclist = []
+self.testslist = []
 self.runner = None
 self.context = context if context else TestContext()
+self.test_options = None
 self.test_result = None
 self.run_time = None
 
+def __del__(self):
+"""
+Because unittest.TestCase is a class object, it will exist as long as 
the python virtual machine process.
+So tc can't be released if we don't release them explicitly.
+"""
+if hasattr(unittest.TestCase, "tc"):
+delattr(unittest.TestCase, "tc")
+
+@staticmethod
+def get_tc_from_manifest(fname):
+'''get tc list from manifest format '''
+with open(fname, "r") as f:
+tclist = [n.strip() for n in f.readlines() \
+if n.strip() and not n.strip().startswith('#')]
+return tclist
 
 def configure(self, options=FakeOptions()):
 '''configure before testing'''
-pass
+self.test_options = options
+self.runner = unittest.TextTestRunner(stream=sys.stderr, \
+  verbosity=2)
 
 def result(self):
 '''output test result '''
-pass
+return self.test_result
 
 def loadtest(self, names=None):
 '''load test suite'''
-pass
+if names is None:
+names = self.testslist
+testloader = unittest.TestLoader()
+tclist = []
+for name in names:
+tset = testloader.loadTestsFromName(name)
+if tset.countTestCases() > 0:
+tclist.append(tset)
+elif tset._tests == []:
+tclist.append(testloader.discover(name, "[!_]*.py", 
os.path.curdir))
+return testloader.suiteClass(tclist)
 
 def runtest(self, testsuite):
 '''run test suite'''
-pass
+starttime = time.time()
+self.test_result = self.runner.run(testsuite)
+self.run_time = time.time() - starttime
 
 def start(self, testsuite):
 '''start testing'''
-pass
+setattr(unittest.TestCase, "tc", self.context)
+self.runtest(testsuite)
+self.result()
 
-- 
2.1.4

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


[OE-core] [PATCH 4/4] meta: modify runexported script to inherit the features from baserunner

2016-09-12 Thread jwang
From: zjh 

Signed-off-by: zjh 
---
 meta/classes/testexport.bbclass |  2 ++
 meta/lib/base/baserunner.py | 21 -
 meta/lib/oeqa/runexported.py| 12 +++-
 3 files changed, 33 insertions(+), 2 deletions(-)

diff --git a/meta/classes/testexport.bbclass b/meta/classes/testexport.bbclass
index 15fa470..c65ad55 100644
--- a/meta/classes/testexport.bbclass
+++ b/meta/classes/testexport.bbclass
@@ -128,6 +128,8 @@ def exportTests(d,tc):
 for f in files:
 shutil.copy2(os.path.join(root, f), os.path.join(exportpath, 
"oeqa/runtime/files"))
 
+# copy base*
+shutil.copytree(os.path.join(meta_layer, "lib", "base"), 
os.path.join(exportpath, "base"))
 # Create tar file for common parts of testexport
 create_tarball(d, "testexport.tar.gz", d.getVar("TEST_EXPORT_DIR", True))
 
diff --git a/meta/lib/base/baserunner.py b/meta/lib/base/baserunner.py
index d59872f..9b38f1b 100755
--- a/meta/lib/base/baserunner.py
+++ b/meta/lib/base/baserunner.py
@@ -57,9 +57,28 @@ class TestRunnerBase(object):
 def configure(self, options=FakeOptions()):
 '''configure before testing'''
 self.test_options = options
-self.runner = unittest.TextTestRunner(stream=sys.stderr, \
+if options.xunit:
+try:
+from xmlrunner import XMLTestRunner
+except ImportError:
+raise Exception("unittest-xml-reporting not installed")
+self.runner = XMLTestRunner(stream=sys.stderr, \
+verbosity=2, output=options.xunit)
+else:
+self.runner = unittest.TextTestRunner(stream=sys.stderr, \
   verbosity=2)
 
+if options.manifest:
+fbname, fext = os.path.splitext(os.path.basename(options.manifest))
+assert fbname == "manifest" or fext == ".manifest", \
+  "Please specify file name like xxx.manifest or manifest.xxx"
+self.tclist = self.get_tc_from_manifest(options.manifest)
+
+if options.tests:
+tcs = [t[0:-3] if t.endswith(".py") else t[0:-1] \
+   if t.endswith("/") else t for t in 
options.tests]
+self.tclist.extend([tc.replace("/", ".") for tc in tcs])
+
 def result(self):
 '''output test result '''
 return self.test_result
diff --git a/meta/lib/oeqa/runexported.py b/meta/lib/oeqa/runexported.py
index 5886739..18e9543 100755
--- a/meta/lib/oeqa/runexported.py
+++ b/meta/lib/oeqa/runexported.py
@@ -69,6 +69,9 @@ class MyDataDict(dict):
 def getVar(self, key, unused = None):
 return self.get(key, "")
 
+class RunExportTestContext(ExportTestContext):
+_configure_in_init = False
+
 def main():
 
 parser = argparse.ArgumentParser()
@@ -81,6 +84,12 @@ def main():
 specified in the json if that directory actually exists or it will 
error out.")
 parser.add_argument("-l", "--log-dir", dest="log_dir", help="This sets the 
path for TEST_LOG_DIR. If not specified \
 the current dir is used. This is used for usually creating a ssh 
log file and a scp test file.")
+parser.add_argument("-f", "--manifest", dest="manifest",
+help="The test list file"),
+parser.add_argument("-x", "--xunit", dest="xunit",
+help="Output result path of in xUnit XML format"),
+parser.add_argument("-e", "--tests", dest="tests", action="append",
+help="Run tests by dot separated module path"),
 parser.add_argument("json", help="The json file exported by the build 
system", default="testdata.json", nargs='?')
 
 args = parser.parse_args()
@@ -114,7 +123,8 @@ def main():
 setattr(target, key, loaded["target"][key])
 
 target.exportStart()
-tc = ExportTestContext(d, target, True)
+tc = RunExportTestContext(d, target, True)
+tc.configure(args)
 tc.loadTests()
 tc.runTests()
 
-- 
2.1.4

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


[OE-core] [PATCH 3/4] meta: use baserunner in oetest

2016-09-12 Thread jwang
From: zjh 

enable two features from baserunner:
1. loadtest
2. read test cases from manifest file

Signed-off-by: zjh 
---
 meta/lib/oeqa/oetest.py | 24 ++--
 1 file changed, 14 insertions(+), 10 deletions(-)

diff --git a/meta/lib/oeqa/oetest.py b/meta/lib/oeqa/oetest.py
index 4a740fb..9211cec 100644
--- a/meta/lib/oeqa/oetest.py
+++ b/meta/lib/oeqa/oetest.py
@@ -28,6 +28,8 @@ except ImportError:
 pass
 from oeqa.utils.decorators import LogResults, gettag, getResults
 from oeqa.utils import avoid_paths_in_environ
+from base.baserunner import TestRunnerBase
+
 
 logger = logging.getLogger("BitBake")
 
@@ -203,8 +205,10 @@ def custom_verbose(msg, *args, **kwargs):
 logger.info(_buffer_logger.rstrip("\n"), *args, **kwargs)
 _buffer_logger = ""
 
-class TestContext(object):
+class TestContext(TestRunnerBase):
+_configure_in_init = True
 def __init__(self, d, exported=False):
+super(TestContext, self).__init__(self)
 self.d = d
 
 self.testsuites = self._get_test_suites()
@@ -223,6 +227,9 @@ class TestContext(object):
 self.imagefeatures = d.getVar("IMAGE_FEATURES", True).split()
 self.distrofeatures = d.getVar("DISTRO_FEATURES", True).split()
 
+if self._configure_in_init:
+self.configure()
+
 # get testcase list from specified file
 # if path is a relative path, then relative to build/conf/
 def _read_testlist(self, fpath, builddir):
@@ -329,9 +336,7 @@ class TestContext(object):
 def loadTests(self):
 setattr(oeTest, "tc", self)
 
-testloader = unittest.TestLoader()
-testloader.sortTestMethodsUsing = None
-suites = [testloader.loadTestsFromName(name) for name in 
self.testslist]
+suites = self.loadtest(self.testslist)
 suites = filterByTagExp(suites, getattr(self, "tagexp", None))
 
 # Determine dependencies between suites by looking for 
@skipUnlessPassed
@@ -376,9 +381,9 @@ class TestContext(object):
 def cmpfunc(a, b):
 return cmp((a.depth, a.index), (b.depth, b.index))
 
-suites.sort(key=functools.cmp_to_key(cmpfunc))
+suites._tests.sort(key=functools.cmp_to_key(cmpfunc))
 
-self.suite = testloader.suiteClass(suites)
+self.suite = suites
 
 return self.suite
 
@@ -387,11 +392,10 @@ class TestContext(object):
 if hasattr(self, "tagexp") and self.tagexp:
 logger.info("Filter test cases by tags: %s" % self.tagexp)
 logger.info("Found %s tests" % self.suite.countTestCases())
-runner = unittest.TextTestRunner(verbosity=2)
 if 'bb' in sys.modules:
-runner.stream.write = custom_verbose
-
-return runner.run(self.suite)
+self.runner.stream.write = custom_verbose
+self.start(self.suite)
+return self.result()
 
 class RuntimeTestContext(TestContext):
 def __init__(self, d, target, exported=False):
-- 
2.1.4

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


[OE-core] [PATCH 1/4] meta: introduce a small baserunner framework

2016-09-12 Thread jwang
From: zjh 

Signed-off-by: zjh 
---
 meta/lib/base/baserunner.py | 60 +
 1 file changed, 60 insertions(+)
 create mode 100755 meta/lib/base/baserunner.py

diff --git a/meta/lib/base/baserunner.py b/meta/lib/base/baserunner.py
new file mode 100755
index 000..56b838e
--- /dev/null
+++ b/meta/lib/base/baserunner.py
@@ -0,0 +1,60 @@
+#!/usr/bin/env python
+# Copyright (C) 2013 Intel Corporation
+#
+# Released under the MIT license (see COPYING.MIT)
+
+# Base unittest module used by testrunner
+# This provides the common test runner functionalities including manifest 
input,
+# xunit output, timeout, tag filtering.
+
+"""Base testrunner"""
+
+from __future__ import absolute_import
+import os
+import sys
+import time
+import unittest
+import shutil
+
+class TestContext(object):
+'''test context which inject into testcase'''
+def __init__(self):
+self.target = None
+
+class FakeOptions(object):
+'''This class just use for configure's defualt arg.
+   Usually, we use this object in a non comandline environment.'''
+timeout = 0
+def __getattr__(self, name):
+return None
+
+class TestRunnerBase(object):
+'''test runner base '''
+def __init__(self, context=None):
+self.tclist = []
+self.runner = None
+self.context = context if context else TestContext()
+self.test_result = None
+self.run_time = None
+
+
+def configure(self, options=FakeOptions()):
+'''configure before testing'''
+pass
+
+def result(self):
+'''output test result '''
+pass
+
+def loadtest(self, names=None):
+'''load test suite'''
+pass
+
+def runtest(self, testsuite):
+'''run test suite'''
+pass
+
+def start(self, testsuite):
+'''start testing'''
+pass
+
-- 
2.1.4

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


Re: [OE-core] [PATCH] rootfs.py: support absolute paths in IMAGE_DEVICE_TABLES

2016-09-12 Thread Mark Hatle
On 9/12/16 6:00 PM, Andre McCurdy wrote:
> Paths relative to BBPATH are fine if device table files are always
> static and contained somewhere within a meta layer. However if device
> tables are created dynamically, they will be located somewhere within
> ${TMPDIR} and most conveniently referenced via an absolute path.
> 
> The legacy IMAGE_DEVICE_TABLE variable supported an absolute path,
> therefore make IMAGE_DEVICE_TABLES support absolute paths too, to
> avoid users who need dynamic device table files being dependent on
> the legacy variable.
> 
> Signed-off-by: Andre McCurdy 
> ---
>  meta/lib/oe/rootfs.py | 9 ++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
> index a348b97..32cce64 100644
> --- a/meta/lib/oe/rootfs.py
> +++ b/meta/lib/oe/rootfs.py
> @@ -352,8 +352,8 @@ class Rootfs(object, metaclass=ABCMeta):
>  """
>  Create devfs:
>  * IMAGE_DEVICE_TABLE is the old name to an absolute path to a device 
> table file
> -* IMAGE_DEVICE_TABLES is a new name for a file, or list of files, seached
> -  for in the BBPATH
> +* IMAGE_DEVICE_TABLES is the new name for a file, or list of files, 
> which may be
> +  either absolute paths or paths relative to BBPATH.
>  If neither are specified then the default name of 
> files/device_table-minimal.txt
>  is searched for in the BBPATH (same as the old version.)
>  """
> @@ -367,7 +367,10 @@ class Rootfs(object, metaclass=ABCMeta):
>  if devtables is None:
>  devtables = 'files/device_table-minimal.txt'
>  for devtable in devtables.split():
> -devtable_list.append("%s" % 
> bb.utils.which(self.d.getVar('BBPATH', True), devtable))
> +if os.path.isabs(devtable):
> +devtable_list.append(devtable)
> +else:
> +devtable_list.append("%s" % 
> bb.utils.which(self.d.getVar('BBPATH', True), devtable))

I'm wondering if maybe this is a bug in "bb.utils.which", I thought it would
return back -- in the case of an absolute path -- if the thing existed or not,
otherwise would search the BBPATH.  (I'm using the command line version of
'which' as my behavioral thinking.)

If it is an issue, then it would need a fix in bitbake, and I believe the
existing code should then work.

(Asking about the behavior on the bitbake list might be worth while in this 
case.)

>  
>  for devtable in devtable_list:
>  self._exec_shell_cmd(["makedevs", "-r",
> 

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


[OE-core] [PATCH] rootfs.py: support absolute paths in IMAGE_DEVICE_TABLES

2016-09-12 Thread Andre McCurdy
Paths relative to BBPATH are fine if device table files are always
static and contained somewhere within a meta layer. However if device
tables are created dynamically, they will be located somewhere within
${TMPDIR} and most conveniently referenced via an absolute path.

The legacy IMAGE_DEVICE_TABLE variable supported an absolute path,
therefore make IMAGE_DEVICE_TABLES support absolute paths too, to
avoid users who need dynamic device table files being dependent on
the legacy variable.

Signed-off-by: Andre McCurdy 
---
 meta/lib/oe/rootfs.py | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
index a348b97..32cce64 100644
--- a/meta/lib/oe/rootfs.py
+++ b/meta/lib/oe/rootfs.py
@@ -352,8 +352,8 @@ class Rootfs(object, metaclass=ABCMeta):
 """
 Create devfs:
 * IMAGE_DEVICE_TABLE is the old name to an absolute path to a device table 
file
-* IMAGE_DEVICE_TABLES is a new name for a file, or list of files, seached
-  for in the BBPATH
+* IMAGE_DEVICE_TABLES is the new name for a file, or list of files, which 
may be
+  either absolute paths or paths relative to BBPATH.
 If neither are specified then the default name of 
files/device_table-minimal.txt
 is searched for in the BBPATH (same as the old version.)
 """
@@ -367,7 +367,10 @@ class Rootfs(object, metaclass=ABCMeta):
 if devtables is None:
 devtables = 'files/device_table-minimal.txt'
 for devtable in devtables.split():
-devtable_list.append("%s" % 
bb.utils.which(self.d.getVar('BBPATH', True), devtable))
+if os.path.isabs(devtable):
+devtable_list.append(devtable)
+else:
+devtable_list.append("%s" % 
bb.utils.which(self.d.getVar('BBPATH', True), devtable))
 
 for devtable in devtable_list:
 self._exec_shell_cmd(["makedevs", "-r",
-- 
1.9.1

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


[OE-core] [PATCH] image.bbclass: add IMAGE_DEVICE_TABLE to rootfs[vardeps]

2016-09-12 Thread Andre McCurdy
IMAGE_DEVICE_TABLE and IMAGE_DEVICE_TABLES are both referenced by
_create_devfs, therefore ensure that rootfs is rebuilt if changes
are made to either variable.

Signed-off-by: Andre McCurdy 
---
 meta/classes/image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 8c8b8a2..96eaa45 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -116,7 +116,7 @@ python () {
 
 def rootfs_variables(d):
 from oe.rootfs import variable_depends
-variables = 
['IMAGE_DEVICE_TABLES','BUILD_IMAGES_FROM_FEEDS','IMAGE_TYPES_MASKED','IMAGE_ROOTFS_ALIGNMENT','IMAGE_OVERHEAD_FACTOR','IMAGE_ROOTFS_SIZE','IMAGE_ROOTFS_EXTRA_SPACE',
+variables = 
['IMAGE_DEVICE_TABLE','IMAGE_DEVICE_TABLES','BUILD_IMAGES_FROM_FEEDS','IMAGE_TYPES_MASKED','IMAGE_ROOTFS_ALIGNMENT','IMAGE_OVERHEAD_FACTOR','IMAGE_ROOTFS_SIZE','IMAGE_ROOTFS_EXTRA_SPACE',
  
'IMAGE_ROOTFS_MAXSIZE','IMAGE_NAME','IMAGE_LINK_NAME','IMAGE_MANIFEST','DEPLOY_DIR_IMAGE','RM_OLD_IMAGE','IMAGE_FSTYPES','IMAGE_INSTALL_COMPLEMENTARY','IMAGE_LINGUAS',
  
'MULTILIBRE_ALLOW_REP','MULTILIB_TEMP_ROOTFS','MULTILIB_VARIANTS','MULTILIBS','ALL_MULTILIB_PACKAGE_ARCHS','MULTILIB_GLOBAL_VARIANTS','BAD_RECOMMENDATIONS','NO_RECOMMENDATIONS',
  
'PACKAGE_ARCHS','PACKAGE_CLASSES','TARGET_VENDOR','TARGET_ARCH','TARGET_OS','OVERRIDES','BBEXTENDVARIANT','FEED_DEPLOYDIR_BASE_URI','INTERCEPT_DIR','USE_DEVFS',
-- 
1.9.1

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


[OE-core] State of bitbake world 2016-09-11

2016-09-12 Thread Martin Jansa
== Number of issues - stats ==
{| class='wikitable'
!|Date   !!colspan='3'|Failed tasks 
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='12'|QA !!Comment
|-
||  ||qemuarm   ||qemux86   ||qemux86_64
||qemuarm||max||min ||qemux86||max||min ||all   ||already-stripped  
||libdir||textrel   ||build-deps||file-rdeps
||version-going-backwards   ||host-user-contaminated
||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname   ||  
|-
||2016-09-11||6 ||8 ||7 ||19||6 ||4 ||22||8 
||6 ||0 ||0 ||0 ||1 ||8 
||3 ||12||0 ||1 ||0 
||0 ||0 ||0 ||  
|}

http://www.openembedded.org/wiki/Bitbake_World_Status

== Failed tasks 2016-09-11 ==

INFO: jenkins-job.sh-1.8.10 Complete log available at 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.report.20160912_102042.log

=== common (5) ===
* 
meta-openembedded/meta-networking/recipes-extended/iscsitarget/iscsitarget_1.4.20.3+svn502.bb:do_compile
* 
meta-openembedded/meta-networking/recipes-kernel/netmap/netmap-modules_git.bb:do_compile
* 
meta-openembedded/meta-python/recipes-devtools/python/python-unidiff_0.5.2.bb:do_populate_sysroot
* meta-qt5/recipes-qt/qt5/qtwebkit_git.bb:do_compile
* 
openembedded-core/meta/recipes-support/libunwind/libunwind_git.bb:do_compile

=== common-x86 (2) ===
* 
meta-browser/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb:do_patch
* 
meta-openembedded/meta-oe/recipes-support/vboxguestdrivers/vboxguestdrivers_5.1.4.bb:do_install

=== qemuarm (1) ===
* 
meta-openembedded/meta-networking/recipes-connectivity/dhcpcd/dhcpcd_6.11.3.bb:do_fetch

=== qemux86 (1) ===
* meta-browser/recipes-browser/chromium/chromium_52.0.2743.76.bb:do_compile

=== qemux86_64 (0) ===

=== Number of failed tasks (21) ===
{| class=wikitable
|-
|| qemuarm  || 6 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.world.qemuarm.20160910_213946.log/
 || http://errors.yoctoproject.org/Errors/Build/21399/
|-
|| qemux86  || 8 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.world.qemux86.20160910_213952.log/
 || http://errors.yoctoproject.org/Errors/Build/21400/
|-
|| qemux86_64   || 7 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.world.qemux86-64.20160911_094330.log/
 || http://errors.yoctoproject.org/Errors/Build/21410/
|}

=== PNBLACKLISTs (118) ===

=== QA issues (25) ===
{| class=wikitable
!| Count||Issue
|-
||0 ||already-stripped
|-
||0 ||host-user-contaminated
|-
||0 ||invalid-pkgconfig
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||12||version-going-backwards
|-
||1 ||installed-vs-shipped
|-
||1 ||textrel
|-
||3 ||file-rdeps
|-
||8 ||build-deps
|}



=== Failed dependencies for qemuarm (19) ===

Complete log: 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log/
Found differences: 
* WARN: libdrm: libdrm-tests rdepends on cunit, but it isn't a build 
dependency?
* WARN: libdrm: libdrm-tests rdepends on libdrm-amdgpu, but it isn't a 
build dependency?
* WARN: jasper: jasper-bin rdepends on freeglut, but it isn't a build 
dependency?
* WARN: jasper: jasper-bin rdepends on libgl-mesa, but it isn't a build 
dependency?
* WARN: jasper: jasper-bin rdepends on libglu, but it isn't a build 
dependency?
* WARN: enchant: enchant rdepends on hunspell, but it isn't a build 
dependency?
Found errors: 
* ERROR: 19 issues were found in these recipes: enchant iscsitarget jasper 
libdrm libunwind netmap-modules python-unidiff qtwebkit samba

=== Recipes failing with maximal dependencies for qemuarm (6) ===
* iscsitarget -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log//2_max/failed/iscsitarget.log
* libunwind -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log//2_max/failed/libunwind.log
* netmap-modules -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log//2_max/failed/netmap-modules.log
* python-unidiff -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log//2_max/failed/python-unidiff.log
* qtwebkit -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log//2_max/failed/qtwebkit.log
* samba -- 
http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.qemuarm.20160911_090900.log//2_max/failed/samba.log

=== Recipes failing with minimal dependencies for qemuarm (4) ===
* iscsitarget -- 

[OE-core] [PATCH] oe-selftest: check for coverage version before starting tests

2016-09-12 Thread Humberto Ibarra
python coverage versions lower than 4.x have problems with some distros. Adding 
the 4.x version as requirement to continue with coverage tracking.

[YOCTO #10207]

Signed-off-by: Humberto Ibarra 
---
 scripts/oe-selftest | 4 
 1 file changed, 4 insertions(+)

diff --git a/scripts/oe-selftest b/scripts/oe-selftest
index 72bf4dd..d9ffd40 100755
--- a/scripts/oe-selftest
+++ b/scripts/oe-selftest
@@ -605,6 +605,10 @@ def buildResultClass(args):
 if self.coverage_installed:
 log.info("Coverage is enabled")
 
+major_version = int(coverage.version.__version__[0])
+if major_version < 4:
+log.error("python coverage %s installed. Require 
version 4 or greater." % coverage.version.__version__)
+self.stop()
 # In case the user has not set the variable 
COVERAGE_PROCESS_START,
 # create a default one and export it. The 
COVERAGE_PROCESS_START
 # value indicates where the coverage configuration file 
resides
-- 
2.4.11

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


Re: [OE-core] [PATCH] bitbake: fetch2: Make SRCREV_FORMAT name substitution safer

2016-09-12 Thread Ulf Magnusson
On Mon, Sep 12, 2016 at 10:11 PM, Ulf Magnusson  wrote:
> Given two names "foo" and "foobar" and SRCREV_FORMAT = "foo_foobar",
> "foo" might currently get substituted twice. Work around the issue by
> sorting the list of names by length and substituting longer names first.
>
> Signed-off-by: Ulf Magnusson 
> ---
>  bitbake/lib/bb/fetch2/__init__.py | 5 -
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/bitbake/lib/bb/fetch2/__init__.py 
> b/bitbake/lib/bb/fetch2/__init__.py
> index 11c75cc..4ca024e 100644
> --- a/bitbake/lib/bb/fetch2/__init__.py
> +++ b/bitbake/lib/bb/fetch2/__init__.py
> @@ -764,7 +764,10 @@ def get_srcrev(d, method_name='sortable_revision'):
>  seenautoinc = False
>  for scm in scms:
>  ud = urldata[scm]
> -for name in ud.names:
> +# Sort the list of names and replace the longest names first. Given 
> two
> +# names "foo" and "foobar", this prevents "foo" being substituted 
> twice
> +# in "foo_foobar" (and "foobar" from not being substituted at all).
> +for name in sorted(ud.names, key=len, reverse=True):
>  autoinc, rev = getattr(ud.method, method_name)(ud, d, name)
>  seenautoinc = seenautoinc or autoinc
>  if len(rev) > 10:
> --
> 2.5.0
>

Hrm... the bitbake-devel mailing list would be a better fit. Sent it there too.

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


[OE-core] [PATCH] makedevs: don't restrict device node paths to 40 characters

2016-09-12 Thread Andre McCurdy
40 character paths work OK for device nodes in /dev but not for
device nodes created in a chroot, LXC container, etc.

Since the 'path' array is already a 4k buffer, the sscanf 40
character limit seems to be a typo or historical mis-merge. Update
the sscanf limit and bring the code in sync with the Buildroot
version:

  
https://git.buildroot.net/buildroot/commit/?id=8876b6751e0bc19a3754290061808f0f8420708e

Signed-off-by: Andre McCurdy 
---
 meta/recipes-devtools/makedevs/makedevs/makedevs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/makedevs/makedevs/makedevs.c 
b/meta/recipes-devtools/makedevs/makedevs/makedevs.c
index 7471f3f..cba7681 100644
--- a/meta/recipes-devtools/makedevs/makedevs/makedevs.c
+++ b/meta/recipes-devtools/makedevs/makedevs/makedevs.c
@@ -360,7 +360,7 @@ static int interpret_table_entry(char *line)
unsigned long mode = 0755, uid = 0, gid = 0, major = 0, minor = 0;
unsigned long start = 0, increment = 1, count = 0;
 
-   if (0 > sscanf(line, "%40s %c %lo %40s %40s %lu %lu %lu %lu %lu", path,
+   if (0 > sscanf(line, "%4095s %c %lo %40s %40s %lu %lu %lu %lu %lu", 
path,
, , usr_buf, grp_buf, , , ,
, ))
{
-- 
1.9.1

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


[OE-core] [PATCH] bitbake: fetch2: Make SRCREV_FORMAT name substitution safer

2016-09-12 Thread Ulf Magnusson
Given two names "foo" and "foobar" and SRCREV_FORMAT = "foo_foobar",
"foo" might currently get substituted twice. Work around the issue by
sorting the list of names by length and substituting longer names first.

Signed-off-by: Ulf Magnusson 
---
 bitbake/lib/bb/fetch2/__init__.py | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/bitbake/lib/bb/fetch2/__init__.py 
b/bitbake/lib/bb/fetch2/__init__.py
index 11c75cc..4ca024e 100644
--- a/bitbake/lib/bb/fetch2/__init__.py
+++ b/bitbake/lib/bb/fetch2/__init__.py
@@ -764,7 +764,10 @@ def get_srcrev(d, method_name='sortable_revision'):
 seenautoinc = False
 for scm in scms:
 ud = urldata[scm]
-for name in ud.names:
+# Sort the list of names and replace the longest names first. Given two
+# names "foo" and "foobar", this prevents "foo" being substituted twice
+# in "foo_foobar" (and "foobar" from not being substituted at all).
+for name in sorted(ud.names, key=len, reverse=True):
 autoinc, rev = getattr(ud.method, method_name)(ud, d, name)
 seenautoinc = seenautoinc or autoinc
 if len(rev) > 10:
-- 
2.5.0

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


[OE-core] [PATCH 0/3] linux-yocto: version bumps

2016-09-12 Thread Bruce Ashfield
Hi all,

Here is the latest round of version bumps to 4.1, 4.4 and 4.8. -stable
for 4.1 and 4.4 and the latest -rc for 4.8.

These have passed sanity tests locally, but it is a lot of kernel and arch
combinations, so I'll be standing by if anything happens because of these
updates.

Cheers,

Bruce

The following changes since commit 2679a347c576f5411fbe802d2f6201c94036ecb2:

  maintainers.inc: rename gtk-doc-stub to gtk-doc, reassign to me (2016-09-09 
12:12:59 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (3):
  linux-yocto/4.1: update to 4.1.32
  linux-yocto/4.4: update to 4.4.20
  linux-yocto/4.8: update to v4.8-rc6

 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.1.bb  | 20 ++--
 meta/recipes-kernel/linux/linux-yocto_4.4.bb  | 20 ++--
 meta/recipes-kernel/linux/linux-yocto_4.8.bb  | 18 +-
 9 files changed, 45 insertions(+), 45 deletions(-)

-- 
2.5.0

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


[OE-core] [PATCH 3/3] linux-yocto/4.8: update to v4.8-rc6

2016-09-12 Thread Bruce Ashfield
Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.8.bb  | 18 +-
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
index ff726815d2a3..10dd349eb002 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
+SRCREV_machine ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
 SRCREV_meta ?= "25fb74eaaef249519f25e243e7f9bf0cab0e1781"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.8.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.8-rc5"
+LINUX_VERSION ?= "4.8-rc6"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
index 6f62d22aa4c5..50a54a1a48ea 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb
@@ -4,12 +4,12 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.8-rc5"
+LINUX_VERSION ?= "4.8-rc6"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
+SRCREV_machine ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
 SRCREV_meta ?= "25fb74eaaef249519f25e243e7f9bf0cab0e1781"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.8.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.8.bb
index b0e2a7673745..f4f4bfe855ec 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.8.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.8.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "9a91ef47f85a741d842b876267b29f8ded751f68"
-SRCREV_machine_qemuarm64 ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
-SRCREV_machine_qemumips ?= "40c7a721efe2822fdb7df4b2902a1994add40a77"
-SRCREV_machine_qemuppc ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
-SRCREV_machine_qemux86 ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
-SRCREV_machine_qemux86-64 ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
-SRCREV_machine_qemumips64 ?= "fe4805532e149324939bf9d8415ed43dac357709"
-SRCREV_machine ?= "9e7ee5155e3466824abe94eebb641c63ab5cd5f2"
+SRCREV_machine_qemuarm ?= "29b1dac023fac237c408620aaa79a60a611dc2df"
+SRCREV_machine_qemuarm64 ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
+SRCREV_machine_qemumips ?= "edb3f19ae13818cd5af56f21566e843c975ba897"
+SRCREV_machine_qemuppc ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
+SRCREV_machine_qemux86 ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
+SRCREV_machine_qemux86-64 ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
+SRCREV_machine_qemumips64 ?= "c583570fc64c2e01e3cf51edd0e732ee6789c9ef"
+SRCREV_machine ?= "e6e0dea72e605a070373bd52c6c2637202ce4b38"
 SRCREV_meta ?= "25fb74eaaef249519f25e243e7f9bf0cab0e1781"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.8.git;name=machine;branch=${KBRANCH}; 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.8;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.8-rc5"
+LINUX_VERSION ?= "4.8-rc6"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.5.0

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


[OE-core] [PATCH 2/3] linux-yocto/4.4: update to 4.4.20

2016-09-12 Thread Bruce Ashfield
Integrating the korg -stable release.

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.4.bb  | 20 ++--
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
index e7057005d115..a97a14b66e32 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "a52822c864c50cc5e42939d217a8559fbf853fde"
-SRCREV_meta ?= "59290c5f6192da2eccf478d37a8f9f88134822b3"
+SRCREV_machine ?= "76a02384d86df7b7499755f1650b5299740f5473"
+SRCREV_meta ?= "e66032e2d93da24c6b9137dbbe66008c77f6d4aa"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.4.18"
+LINUX_VERSION ?= "4.4.20"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
index e73754519c6a..6befd233b317 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.4.18"
+LINUX_VERSION ?= "4.4.20"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "a67e1ae4bf3570e93f8d8fe33b1830de058c1b72"
-SRCREV_meta ?= "59290c5f6192da2eccf478d37a8f9f88134822b3"
+SRCREV_machine ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_meta ?= "e66032e2d93da24c6b9137dbbe66008c77f6d4aa"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.4.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
index 6e5a7c7920ab..ec493cbd55f1 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.4.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "2505d9c2441eb638d55b330144988d1730065074"
-SRCREV_machine_qemuarm64 ?= "a67e1ae4bf3570e93f8d8fe33b1830de058c1b72"
-SRCREV_machine_qemumips ?= "544caf9c03c40c2de6b93db9a767e568e0baaa8f"
-SRCREV_machine_qemuppc ?= "a67e1ae4bf3570e93f8d8fe33b1830de058c1b72"
-SRCREV_machine_qemux86 ?= "a67e1ae4bf3570e93f8d8fe33b1830de058c1b72"
-SRCREV_machine_qemux86-64 ?= "a67e1ae4bf3570e93f8d8fe33b1830de058c1b72"
-SRCREV_machine_qemumips64 ?= "c1b45251a5fabfb0f2aba3a0168d8a952a2cd827"
-SRCREV_machine ?= "a67e1ae4bf3570e93f8d8fe33b1830de058c1b72"
-SRCREV_meta ?= "59290c5f6192da2eccf478d37a8f9f88134822b3"
+SRCREV_machine_qemuarm ?= "a064c27e528be59412a892f3ed3ef8efe1f1d601"
+SRCREV_machine_qemuarm64 ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_machine_qemumips ?= "d644de0138c623c2b5e8a6a143a24234fd2cfb27"
+SRCREV_machine_qemuppc ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_machine_qemux86 ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_machine_qemux86-64 ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_machine_qemumips64 ?= "1fb08e61877b56fcbf800bfc66305b7a563c5f99"
+SRCREV_machine ?= "7d1401a0dd9bebfe49937ca7d9785972e0cc76d0"
+SRCREV_meta ?= "e66032e2d93da24c6b9137dbbe66008c77f6d4aa"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.4.18"
+LINUX_VERSION ?= "4.4.20"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.5.0

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


[OE-core] [PATCH 1/3] linux-yocto/4.1: update to 4.1.32

2016-09-12 Thread Bruce Ashfield
Integrating the korg stable update

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb   |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.1.bb  | 20 ++--
 3 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb
index f0d6a81a9c54..4308a07a9765 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "b88e2b5805213daeb0136fdd8c840dc0254a3d21"
-SRCREV_meta ?= "9d0f0db8442a5ccb3f2ce81e2e43d96b6515a45a"
+SRCREV_machine ?= "ee83bffe0f76032fe0a0b7fde436f0f596101df2"
+SRCREV_meta ?= "b30b6b9ef215433b28e8966c73ebb6b98a7f4d1f"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.1.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.1.30"
+LINUX_VERSION ?= "4.1.32"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
index 092a224451e1..2294a3db87da 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb
@@ -4,13 +4,13 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "4.1.30"
+LINUX_VERSION ?= "4.1.32"
 
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
-SRCREV_meta ?= "9d0f0db8442a5ccb3f2ce81e2e43d96b6515a45a"
+SRCREV_machine ?= "93b1a6cee7d4a4437a1c0edf3e54ffe78edb4462"
+SRCREV_meta ?= "b30b6b9ef215433b28e8966c73ebb6b98a7f4d1f"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_4.1.bb 
b/meta/recipes-kernel/linux/linux-yocto_4.1.bb
index e23d7da58881..f4006b74d096 100644
--- a/meta/recipes-kernel/linux/linux-yocto_4.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_4.1.bb
@@ -11,20 +11,20 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "9c5e96205316d167379d101d808a6cda93adc335"
-SRCREV_machine_qemuarm64 ?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
-SRCREV_machine_qemumips ?= "9e531cb59dd7dfa2026637cc456a7bdcbdb50275"
-SRCREV_machine_qemuppc ?= "32968ddd9357f72dfd427f5b3eda62c4a49833c7"
-SRCREV_machine_qemux86 ?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
-SRCREV_machine_qemux86-64 ?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
-SRCREV_machine_qemumips64 ?= "106ed721d21c595dfb993a8990c3a29830dfc166"
-SRCREV_machine ?= "0847ed67f89b5a8bbaaa0a7b6cfa2a99ef34834f"
-SRCREV_meta ?= "9d0f0db8442a5ccb3f2ce81e2e43d96b6515a45a"
+SRCREV_machine_qemuarm ?= "4db58705727e27bea8ccf805bd5c7d04d2d029ed"
+SRCREV_machine_qemuarm64 ?= "93b1a6cee7d4a4437a1c0edf3e54ffe78edb4462"
+SRCREV_machine_qemumips ?= "d6237b3b244b894d4b3479ecf37acef041416dfa"
+SRCREV_machine_qemuppc ?= "8520e65497ae10e14c38c76920a3457dc64349bf"
+SRCREV_machine_qemux86 ?= "93b1a6cee7d4a4437a1c0edf3e54ffe78edb4462"
+SRCREV_machine_qemux86-64 ?= "93b1a6cee7d4a4437a1c0edf3e54ffe78edb4462"
+SRCREV_machine_qemumips64 ?= "d0524e144cd15a3c0edf768f68400968a4477cbe"
+SRCREV_machine ?= "93b1a6cee7d4a4437a1c0edf3e54ffe78edb4462"
+SRCREV_meta ?= "b30b6b9ef215433b28e8966c73ebb6b98a7f4d1f"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto-4.1.git;name=machine;branch=${KBRANCH}; 
\

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.1;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "4.1.30"
+LINUX_VERSION ?= "4.1.32"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.5.0

-- 
___
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/24: gnutls: update to 3.5.3

2016-09-12 Thread Burton, Ross
On 11 September 2016 at 23:37, Martin Jansa  wrote:

> Default qemux86 as shown in:
> http://logs.nslu2-linux.org/buildlogs/oe/world/log.report.
> 20160910_205641.log
>

Yeah I can replicate this, must be a 32-bit x86 thing, or something.
Annoying.

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


Re: [OE-core] [meta-oe][meta-networking][PATCH] cmake-native: add dependency on openssl-native libidn-native

2016-09-12 Thread Martin Jansa
On Mon, Sep 12, 2016 at 07:05:46PM +0200, Martin Jansa wrote:
> From: Martin Jansa 

Sent by accident (as subject tags suggests), but fixes
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9639
as well.

> 
> Signed-off-by: Martin Jansa 
> ---
>  meta/recipes-devtools/cmake/cmake-native_3.6.1.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb 
> b/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb
> index 33930fb..c4d22d8 100644
> --- a/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb
> +++ b/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb
> @@ -2,7 +2,7 @@ require cmake.inc
>  inherit native
>  
>  # Using cmake's internal libarchive, so some dependencies are needed
> -DEPENDS += "bzip2-native zlib-native"
> +DEPENDS += "bzip2-native zlib-native openssl-native libidn-native"
>  
>  SRC_URI += "\
>  file://cmlibarchive-disable-ext2fs.patch \
> -- 
> 2.10.0
> 

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


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


[OE-core] [meta-oe][meta-networking][PATCH] cmake-native: add dependency on openssl-native libidn-native

2016-09-12 Thread Martin Jansa
From: Martin Jansa 

Signed-off-by: Martin Jansa 
---
 meta/recipes-devtools/cmake/cmake-native_3.6.1.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb 
b/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb
index 33930fb..c4d22d8 100644
--- a/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb
+++ b/meta/recipes-devtools/cmake/cmake-native_3.6.1.bb
@@ -2,7 +2,7 @@ require cmake.inc
 inherit native
 
 # Using cmake's internal libarchive, so some dependencies are needed
-DEPENDS += "bzip2-native zlib-native"
+DEPENDS += "bzip2-native zlib-native openssl-native libidn-native"
 
 SRC_URI += "\
 file://cmlibarchive-disable-ext2fs.patch \
-- 
2.10.0

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


Re: [OE-core] [PATCH] image.bbclass: Do not expand variables in IMAGE_CMD vardepsexclude

2016-09-12 Thread Richard Purdie
On Tue, 2016-09-13 at 00:05 +1000, Jonathan Liu wrote:
> Hi Richard,
> 
> On 12 September 2016 at 20:19, Richard Purdie
>  wrote:
> > 
> > On Sun, 2016-09-11 at 22:14 +1000, Jonathan Liu wrote:
> > > 
> > > This fixes tashhash mismatch errors creating images when
> > > IMAGE_CMD
> > > references a variable whose value is always changing even though
> > > the
> > > variable is specified in IMAGE_CMD vardepsexclude.
> > > 
> > > Signed-off-by: Jonathan Liu 
> > > ---
> > >  meta/classes/image.bbclass | 4 
> > >  1 file changed, 4 insertions(+)
> > > 
> > > diff --git a/meta/classes/image.bbclass
> > > b/meta/classes/image.bbclass
> > > index 8c8b8a2..f85ea86 100644
> > > --- a/meta/classes/image.bbclass
> > > +++ b/meta/classes/image.bbclass
> > > @@ -441,6 +441,10 @@ python () {
> > >  localdata.delVar('DATETIME')
> > >  localdata.delVar('TMPDIR')
> > > 
> > > +vardepsexclude = d.getVarFlag('IMAGE_CMD',
> > > 'vardepsexclude',
> > > True) or ''
> > > +vardepsexclude += ' ' + (d.getVarFlag('IMAGE_CMD_' +
> > > realt,
> > > 'vardepsexclude', True) or '')
> > > +for var in vardepsexclude.split():
> > > +localdata.delVar(var)
> > >  image_cmd = localdata.getVar("IMAGE_CMD", True)
> > >  vardeps.add('IMAGE_CMD_' + realt)
> > >  if image_cmd:
> > I think this is complicating an already fragile situation and it
> > worries me. Can you be more specific about which variable is
> > causing
> > problems here?
> See IMAGEDATESTAMP variable in:
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/clas
> ses/sdcard_image-rpi.bbclass
> https://github.com/linux-sunxi/meta-sunxi/blob/master/classes/sdcard_
> image-sunxi.bbclass
> 
> You can test by changing to:
> IMAGEDATESTAMP = "${@time.clock()}"

I appreciate this doesn't solve the underlying problem but is there a
reason they can't just use ${DATE} there?

I mention this since DATE/TIME are handled by bitbake specially so that
for example if your build rolls over midnight, it doesn't explode
badly. If your images is generated pre midnight but them processed
afterwards, I can see things working badly for that code...

Cheers,

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


Re: [OE-core] [PATCH 1/1] qemurunner: print out the runqemu command

2016-09-12 Thread Brian Avery
true, you do, kind of.

This commit explicitly prints out what the runqemu cmd is (for instance
"runqemu snapshot -m 1024"), which is a lot easier to enter if you want to
rerun qemu the way the test did.

It's not a big deal, I just ended up adding it while i was trying to figure
out how the tests were getting started and where my params were ending up.
Your's prints out the long complete cmd line, mine prints out the shortcut
:).  The long one is definitely necessary. Mine is a convenience.

-b
an intel employee.

On Mon, Sep 12, 2016 at 1:19 AM, Joshua Lock 
wrote:

> On Fri, 2016-09-09 at 09:38 -0700, bavery wrote:
> > This logs the launch command that was used for runqemu while running
> > -c
> > testimage.  This way, if I'd like to easily launch qemu manually in
> > order to debug a failed test, I know what commmand was run to create
> > the qemu instance.
>
> I already have this in my runqemu output:
>
> runqemu - INFO - Running
> /home/joshuagl/Projects/poky/build/tmp/sysroots/x86_64-
> linux/usr/bin/qemu-system-ppc -net
> tap,vlan=0,ifname=tap0,script=no,downscript=no -net nic,model=pcnet  -
> machine mac99 -cpu G4 -m 256 -drive file=/home/joshuagl/mess/35/core-
> image-lsb-qemuppc-20160902090100.rootfs.ext4,if=virtio,format=raw  -
> show-cursor -usb -usbdevice tablet -device virtio-rng-pci -kernel
> /home/joshuagl/mess/35/vmlinux-qemuppc.bin -append 'root=/dev/vda rw
> highres=off  mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0
> console=ttyS0 console=tty'
>
>
> --
> ___
> 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


Re: [OE-core] [PATCH 00/26] Krogoth-next: stagged changes

2016-09-12 Thread akuster808



On 09/08/2016 01:00 PM, Andre McCurdy wrote:

On Thu, Sep 8, 2016 at 8:55 AM, Armin Kuster  wrote:

The following changes are being considered for krogoth-next.
If I am missing something, please let me know.

Perhaps this one:

   
http://git.openembedded.org/openembedded-core/commit/?id=c03b32bd71dbe04f2f239556fea0b53215e403d7


got it.
Armin


?


The following changes since commit aad7166704021d82ad3a5ec468552f8f10360d41:

   curl: security fix for CVE-2016-5421 (2016-09-02 08:48:29 +0100)

are available in the git repository at:

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

Alejandro Hernandez (1):
   initramfs-live-boot: Make sure we kill udev before switching root when
 live booting

Armin Kuster (2):
   tiff: Security fix CVE-2015-8781
   tiff: Security fix CVE-2015-8784

Henry Bruce (1):
   npm: npm.bbclass now adds nodejs to RDEPENDS

Jackie Huang (1):
   e2fsprogs: Fix missing check for permission denied.

Jacob Kroon (1):
   bitbake.conf/toolchain-scripts.bbclass: Remove debug prefix mappings
 in SDK

Jeremy Puhlman (2):
   Fix random python backtrace in mutlilib handling code.
   bitbake.conf: set READELF for cross compilation

Jonathan Liu (1):
   meta/classes: fix bb.build.FuncFailed typos

Khem Raj (3):
   python{3}-numpy: Predefine of sizeof off_t on mips/mipsel/ppc
   systemd: Create missing sysusers offline
   gdb: Cache gnu gettext config vars for musl builds

Markus Lehtonen (1):
   base.bbclass wipe ${S} before unpacking source

Pascal Bach (1):
   gcc, qemuppc: Explicitly disable forcing SPE flags for 4.9

Reinette Chatre (1):
   binutils: advance SRCREV to obtain versioned symbols

Richard Purdie (2):
   busybox: Backport makefile fix from upstream
   busybox: Add parallel make fix

Ross Burton (1):
   cml1: fix tasks after default [dirs] changed

Sona Sarmadi (2):
   sudo: CVE-2015-8239
   curl: security fix for CVE-2016-7141

Stefan Agner (1):
   busybox: Fix busybox-init on non-tty consoles

Stephano Cetola (1):
   systemd: allow add users as a rootfs postprocess cmd

Tanu Kaskinen (1):
   pulseaudio: fix crash when disconnecting bluetooth devices

Yi Zhao (3):
   tiff: Security fix CVE-2016-3186
   tiff: Security fix CVE-2016-5321
   tiff: Security fix CVE-2016-5323

  meta/classes/base.bbclass  |  18 +-
  meta/classes/cml1.bbclass  |   2 +
  meta/classes/grub-efi.bbclass  |   2 +-
  meta/classes/gummiboot.bbclass |   4 +-
  meta/classes/multilib_global.bbclass   |   3 +-
  meta/classes/npm.bbclass   |   1 +
  meta/classes/rootfs-postcommands.bbclass   |  43 +-
  meta/classes/syslinux.bbclass  |   2 +-
  meta/classes/toolchain-scripts.bbclass |   3 +
  meta/conf/bitbake.conf |   9 +-
  meta/recipes-core/busybox/busybox.inc  |   4 +-
  .../busybox/busybox/makefile-fix-backport.patch|  40 ++
  .../busybox/busybox/parallel-make-fix.patch|  65 ++
  meta/recipes-core/busybox/busybox_1.24.1.bb|   2 +
  meta/recipes-core/initrdscripts/files/init-live.sh |   4 +-
  meta/recipes-core/systemd/systemd_229.bb   |   8 +-
  meta/recipes-devtools/binutils/binutils-2.26.inc   |   2 +-
  ...s-fix-missing-check-for-permission-denied.patch |  32 +
  meta/recipes-devtools/e2fsprogs/e2fsprogs_git.bb   |   3 +
  ...AltiVec-generation-on-powepc-linux-target.patch |  11 +
  meta/recipes-devtools/gdb/gdb_7.10.1.bb|   5 +
  .../python/python-numpy/arm/numpyconfig.h  |   1 +
  .../python/python-numpy/mips/_numpyconfig.h|   1 +
  .../python/python-numpy/powerpc/_numpyconfig.h |   1 +
  .../sudo/sudo/CVE-2015-8239-1.patch| 699 +
  .../sudo/sudo/CVE-2015-8239-2.patch|  45 ++
  meta/recipes-extended/sudo/sudo_1.8.15.bb  |   2 +
  .../libtiff/files/CVE-2015-8781.patch  | 195 ++
  .../libtiff/files/CVE-2015-8784.patch  |  73 +++
  .../libtiff/files/CVE-2016-3186.patch  |  24 +
  .../libtiff/files/CVE-2016-5321.patch  |  49 ++
  .../libtiff/files/CVE-2016-5323.patch  | 107 
  meta/recipes-multimedia/libtiff/tiff_4.0.6.bb  |   5 +
  ...th-don-t-create-the-HSP-HFP-profile-twice.patch | 343 ++
  .../pulseaudio/pulseaudio_8.0.bb   |   1 +
  meta/recipes-support/curl/curl/CVE-2016-7141.patch |  50 ++
  meta/recipes-support/curl/curl_7.47.1.bb   |   1 +
  37 files changed, 1813 insertions(+), 47 deletions(-)
  create mode 100644 
meta/recipes-core/busybox/busybox/makefile-fix-backport.patch
  create mode 100644 meta/recipes-core/busybox/busybox/parallel-make-fix.patch
  create mode 100644 

Re: [OE-core] [PATCH v2 0/8] Fix BUILD_* family of variables

2016-09-12 Thread Jérémy Rosen



On 12/09/2016 17:22, Burton, Ross wrote:
It's in my staging branch and works for me, just needs a run through 
the AB and then a decision on whether it is a bug fix (good for M4) or 
enhancement (too late for M3)...



If I can weight on that one

it's technically a bug-fix, but the fix is only usefull in the far 
future, once gcc-7 is out and current master is in maintainence mode and 
doesn't compile with gcc-7

so no need to rush it in.

However that serie is probably usefull on krogoth and definitely usefull 
on jethro. (I originally made it for jethro) so if it needs to be 
accepted to allow backporting, maybe it's worth rushing it...



Ross

On 12 September 2016 at 16:19, Jérémy Rosen > wrote:


Any news ?



On 07/09/2016 11:08, Jérémy Rosen wrote:

The BUILD_* family of variables allow the user to specify the
name of the host
compiler to use at build time. This feature is particularly
important for long
term maintainance. Future versions of gcc might not be
compatible with old
yocto distributions and we can't assume that "gcc" is the
correct name for the
compiler.

This problem is already an issue with Jethro which can't be
compiled on a
machine wher gcc-6 is the default compiler. pkgconfig-native
will refuse to
compile because it uses -Werror and gcc-6 has new warnings
compared to gcc-5

This patch serie fixes multiple hard-coded references to gcc
in various recipes
and build infrastructure

This patch was tested by building core-image-minimal for
qemu-x86_64 with a
directory with the following content added to the PATH

  g++ -> /bin/false
  gcc -> /bin/false
  myg++ -> /usr/bin/g++
  mygcc -> /usr/bin/gcc

And the following variables added to local.conf

export BUILD_CC = "mygcc"
export BUILD_CXX = "myg++"
export BUILD_CPP = "mygcc -E"
export BUILD_CCLD = "mygcc"

---
V2
* rewording in some commits messages
* no need for a patch to KConfig, use OE_RUNMAKE_FLAGS instead
* change all patch titles to use : in the short commit message
* rpm : manually remove files instead of calling make distclean
* libpcre : explicitely set CCLD_FOR_BUILD in the recipe since
it's the only
   recipe using it.
* glibc patch has been submited upstream

It would be interesting to modify yocto's builders to use the
BUILD_*
variable in order to have some early warning wrt gcc polution
in recipes, but
seeing the various recipes I had to patch, I would expect such
a change to
trigger a high number of build failures.

Jérémy Rosen (8):
   cross: export CC family from BUILD_* for cross compilers
   linux-yocto: allow overriding compiler name in KConfig
   linux-libc-headers: allow overriding compiler name in KConfig
   busybox: allow overriding compiler name in KConfig
   sanity: fix hardcoded references to gcc
   glibc: remove hard-coded reference to gcc -E
   rpm: manually cleanup sysck
   libpcre: explicitely specify CCLD_FOR_BUILD for this recipe

  meta/classes/cross.bbclass   |
12 
  meta/classes/kernel.bbclass  |  1 +
  meta/classes/sanity.bbclass  |
14 +++---
  meta/recipes-core/busybox/busybox.inc  
 |  2 +-
 
meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch

| 39 +++
  meta/recipes-core/glibc/glibc_2.24.bb 
   |  3 ++-
  meta/recipes-devtools/rpm/rpm_5.4.16.bb
  |  2 +-
 
meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc

   |  2 ++
  meta/recipes-support/libpcre/libpcre_8.39.bb

|  2 ++

  9 files changed, 67 insertions(+), 10 deletions(-)
  create mode 100644

meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch


-- 
___

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

http://lists.openembedded.org/mailman/listinfo/openembedded-core





-- 
___

Re: [OE-core] [PATCH] image.bbclass: do not check size of the debugfs image

2016-09-12 Thread Burton, Ross
Well there must have been some list/gmail snafu, as I definitely don't have
this patch locally but patchwork has it.  I wonder what else I'm missing...

Ross

On 12 September 2016 at 16:26, André Draszik  wrote:

> ping
>
> On Mo, 2016-09-05 at 09:34 +0100, André Draszik wrote:
> > The debugfs is supposed to be used in addition to the
> > normal image for debugging purposes, it doesn't make
> > sense to artificially limit its maximum size.
> >
> > Signed-off-by: André Draszik 
> > ---
> >  meta/classes/image.bbclass | 6 ++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> > index 07bd2d6..cb7d06d 100644
> > --- a/meta/classes/image.bbclass
> > +++ b/meta/classes/image.bbclass
> > @@ -538,6 +538,12 @@ def get_rootfs_size(d):
> >  base_size += rootfs_alignment - 1
> >  base_size -= base_size % rootfs_alignment
> >
> > +# Do not check image size of the debugfs image. This is not supposed
> > +# to be deployed, etc. so it doesn't make sense to limit the size
> > +# of the debug.
> > +if (d.getVar('IMAGE_BUILDING_DEBUGFS', True) or "") == "true":
> > +return base_size
> > +
> >  # Check the rootfs size against IMAGE_ROOTFS_MAXSIZE (if set)
> >  if rootfs_maxsize:
> >  rootfs_maxsize_int = int(rootfs_maxsize)
> --
> ___
> 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


Re: [OE-core] [yocto] Subjects for YP Developer Day at ELCE

2016-09-12 Thread Burton, Ross
On 12 September 2016 at 15:48, William Mills  wrote:

> 5) Can Yocto [cross-]build snaps or flatpaks?
>

Just because it's interesting, note that the standard freedesktop.org
flatpak runtime is in fact bootstrapped through a custom OE distro.

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


Re: [OE-core] [PATCH] image.bbclass: do not check size of the debugfs image

2016-09-12 Thread André Draszik
ping

On Mo, 2016-09-05 at 09:34 +0100, André Draszik wrote:
> The debugfs is supposed to be used in addition to the
> normal image for debugging purposes, it doesn't make
> sense to artificially limit its maximum size.
> 
> Signed-off-by: André Draszik 
> ---
>  meta/classes/image.bbclass | 6 ++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 07bd2d6..cb7d06d 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -538,6 +538,12 @@ def get_rootfs_size(d):
>  base_size += rootfs_alignment - 1
>  base_size -= base_size % rootfs_alignment
>  
> +# Do not check image size of the debugfs image. This is not supposed
> +# to be deployed, etc. so it doesn't make sense to limit the size
> +# of the debug.
> +if (d.getVar('IMAGE_BUILDING_DEBUGFS', True) or "") == "true":
> +return base_size
> +
>  # Check the rootfs size against IMAGE_ROOTFS_MAXSIZE (if set)
>  if rootfs_maxsize:
>  rootfs_maxsize_int = int(rootfs_maxsize)
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] image.bbclass: also mask debugfs versions of masked images

2016-09-12 Thread André Draszik
ping

On Mo, 2016-09-05 at 09:33 +0100, André Draszik wrote:
> When IMAGE_GEN_DEBUGFS is enabled, and IMAGE_FSTYPES_DEBUGFS is left
> at its default (as suggested by local.conf.sample.extended),
> recipe parsing fails:
> 
>   bitbake kern-tools-native # or anything else for that matter
>   ERROR: /meta/recipes-core/images/build-appliance-
> image_15.0.0.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry
> 'debugfs_vmdk' - possibly invalid type name or missing support class
>   ERROR: Failed to parse recipe: /meta/recipes-
> core/images/build-appliance-image_15.0.0.bb
> 
>   Summary: There was 1 WARNING message shown.
>   Summary: There were 2 ERROR messages shown, returning a non-zero exit
> code.
> 
> i.e. bitbake doesn't even finish parsing...
> 
> Since IMAGE_FSTYPES_DEBUGFS is based on IMAGE_FSTYPES, and
> since the build-appliance-image is setting IMAGE_FSTYPES
> to vmdk, image.bbclass/image_types.bbclass will be trying
> to build a debugfs_vmdk, causing the error, as this is not
> implemented.
> 
> One solution to solving this problem could be as simple as
> adding a line
>   IMAGE_FSTYPES_DEBUGFS_remove = "vmdk"
> to the build-appliance-image recipe, but that is very
> specific to the error encountered and carries the risk of
> the error being reintroduced in another recipe.
> 
> Another solution could be to add 'debugfs_vmdk' to
> IMAGE_TYPES_MASKED in image-vm.bbclass, but again, this
> approach doesn't seem generic enough.
> 
> None of the live and vm type images have an implementation
> for building a debugfs version, it doesn't seem to make
> sense to build debugfs versions of any of them anyway, and
> given IMAGE_TYPES_MASKED appears to be intended for those
> image types exclusively, it seems the right approach is to
> unconditionally also mask all debugfs_ flavours from
> IMAGE_TYPES_MASKED to achieve a generic solution.
> 
> Do that so.
> 
> Signed-off-by: André Draszik 
> ---
>  meta/classes/image.bbclass | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 8c8b8a2..07bd2d6 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -415,6 +415,7 @@ python () {
>  d.appendVarFlag('do_image', 'vardeps', ' '.join(vardeps))
>  
>  maskedtypes = (d.getVar('IMAGE_TYPES_MASKED', True) or "").split()
> +maskedtypes = [dbg + t for t in maskedtypes for dbg in ("",
> "debugfs_")]
>  
>  for t in basetypes:
>  vardeps = set()
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH][V3] rpm: remove redundant removals

2016-09-12 Thread Ross Burton
These were noticed by the use of bashisms (rm *.{foo,bar}) and lots of these rm
commands are deleting files which don't exist in the first place.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/rpm/rpm_5.4.16.bb | 36 -
 1 file changed, 36 deletions(-)

diff --git a/meta/recipes-devtools/rpm/rpm_5.4.16.bb 
b/meta/recipes-devtools/rpm/rpm_5.4.16.bb
index 9f78dee..dd6e103 100644
--- a/meta/recipes-devtools/rpm/rpm_5.4.16.bb
+++ b/meta/recipes-devtools/rpm/rpm_5.4.16.bb
@@ -554,54 +554,20 @@ do_install_append() {
install -m 0755 ${WORKDIR}/pythondeps.sh 
${D}/${libdir}/rpm/pythondeps.sh
install -m 0755 ${WORKDIR}/perfile_rpmdeps.sh 
${D}/${libdir}/rpm/perfile_rpmdeps.sh
 
-   # Remove unpackaged files (based on list in rpm.spec)
-   rm -f 
${D}/${libdir}/rpm/{Specfile.pm,cpanflute,cpanflute2,rpmdiff,rpmdiff.cgi,sql.prov,sql.req,tcl.req,trpm}
-
-   rm -f ${D}/${mandir}/man8/rpmcache.8*
-   rm -f ${D}/${mandir}/man8/rpmgraph.8*
-   rm -f ${D}/${mandir}/*/man8/rpmcache.8*
-   rm -f ${D}/${mandir}/*/man8/rpmgraph.8*
-   rm -rf ${D}/${mandir}/{fr,ko}
-
rm -f ${D}/${includedir}/popt.h
rm -f ${D}/${libdir}/libpopt.*
rm -f ${D}/${libdir}/pkgconfig/popt.pc
rm -f ${D}/${datadir}/locale/*/LC_MESSAGES/popt.mo
rm -f ${D}/${mandir}/man3/popt.3
 
-   rm -f ${D}/${mandir}/man1/xar.1*
-   rm -f ${D}/${bindir}/xar
-   rm -rf ${D}/${includedir}/xar
-   rm -f ${D}/${libdir}/libxar*
-
-   rm -f ${D}/${bindir}/lz*
-   rm -f ${D}/${bindir}/unlzma
-   rm -f ${D}/${bindir}/unxz
-   rm -f ${D}/${bindir}/xz*
-   rm -rf ${D}/${includedir}/lzma*
-   rm -f ${D}/${mandir}/man1/lz*.1
-   rm -f ${D}/${libdir}/pkgconfig/liblzma*
-
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/*.a
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/*.la
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/rpm/*.a
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/rpm/*.la
 
-   #find ${D}/${libdir}/perl5 -type f -a \( -name perllocal.pod -o -name 
.packlist \
-   #   -o \( -name '*.bs' -a -empty \) \) -exec rm -f {} ';'
-   #find ${D}/${libdir}/perl5 -type d -depth -exec rmdir {} 2>/dev/null ';'
-
rm -f ${D}/${libdir}/rpm/dbconvert.sh
-
rm -f ${D}/${libdir}/rpm/libsqldb.*
 
-   # We don't want, nor need the Mandriva multiarch items
-   rm -f ${D}/${bindir}/multiarch-dispatch
-   rm -f ${D}/${bindir}/multiarch-platform
-   rm -f ${D}/${libdir}/rpm/check-multiarch-files
-   rm -f ${D}/${libdir}/rpm/mkmultiarch
-   rm -f ${D}/${includedir}/multiarch-dispatch.h
-
rm -f ${D}/${libdir}/rpm/gstreamer.sh
rm -f ${D}/${libdir}/rpm/gem_helper.rb
rm -f ${D}/${libdir}/rpm/rubygems.rb
@@ -610,12 +576,10 @@ do_install_append() {
rm -f ${D}/${libdir}/rpm/macros.d/kernel
rm -f ${D}/${libdir}/rpm/macros.d/gstreamer
rm -f ${D}/${libdir}/rpm/bin/mgo
-   rm -f ${D}/${libdir}/rpm/bin/dbconvert
rm -f ${D}/${libdir}/rpm/bin/pom2spec
 
rm -rf ${D}/var/lib/wdj ${D}/var/cache/wdj
rm -f ${D}/${libdir}/rpm/bin/api-sanity-checker.pl
-
 }
 
 do_install_append_class-target() {
-- 
2.8.1

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


Re: [OE-core] [PATCH v2 0/8] Fix BUILD_* family of variables

2016-09-12 Thread Burton, Ross
It's in my staging branch and works for me, just needs a run through the AB
and then a decision on whether it is a bug fix (good for M4) or enhancement
(too late for M3)...

Ross

On 12 September 2016 at 16:19, Jérémy Rosen  wrote:

> Any news ?
>
>
>
> On 07/09/2016 11:08, Jérémy Rosen wrote:
>
>> The BUILD_* family of variables allow the user to specify the name of the
>> host
>> compiler to use at build time. This feature is particularly important for
>> long
>> term maintainance. Future versions of gcc might not be compatible with old
>> yocto distributions and we can't assume that "gcc" is the correct name
>> for the
>> compiler.
>>
>> This problem is already an issue with Jethro which can't be compiled on a
>> machine wher gcc-6 is the default compiler. pkgconfig-native will refuse
>> to
>> compile because it uses -Werror and gcc-6 has new warnings compared to
>> gcc-5
>>
>> This patch serie fixes multiple hard-coded references to gcc in various
>> recipes
>> and build infrastructure
>>
>> This patch was tested by building core-image-minimal for qemu-x86_64 with
>> a
>> directory with the following content added to the PATH
>>
>>   g++ -> /bin/false
>>   gcc -> /bin/false
>>   myg++ -> /usr/bin/g++
>>   mygcc -> /usr/bin/gcc
>>
>> And the following variables added to local.conf
>>
>> export BUILD_CC = "mygcc"
>> export BUILD_CXX = "myg++"
>> export BUILD_CPP = "mygcc -E"
>> export BUILD_CCLD = "mygcc"
>>
>> ---
>> V2
>> * rewording in some commits messages
>> * no need for a patch to KConfig, use OE_RUNMAKE_FLAGS instead
>> * change all patch titles to use : in the short commit message
>> * rpm : manually remove files instead of calling make distclean
>> * libpcre : explicitely set CCLD_FOR_BUILD in the recipe since it's the
>> only
>>recipe using it.
>> * glibc patch has been submited upstream
>>
>> It would be interesting to modify yocto's builders to use the BUILD_*
>> variable in order to have some early warning wrt gcc polution in recipes,
>> but
>> seeing the various recipes I had to patch, I would expect such a change to
>> trigger a high number of build failures.
>>
>> Jérémy Rosen (8):
>>cross: export CC family from BUILD_* for cross compilers
>>linux-yocto: allow overriding compiler name in KConfig
>>linux-libc-headers: allow overriding compiler name in KConfig
>>busybox: allow overriding compiler name in KConfig
>>sanity: fix hardcoded references to gcc
>>glibc: remove hard-coded reference to gcc -E
>>rpm: manually cleanup sysck
>>libpcre: explicitely specify CCLD_FOR_BUILD for this recipe
>>
>>   meta/classes/cross.bbclass
>>   | 12 
>>   meta/classes/kernel.bbclass
>>|  1 +
>>   meta/classes/sanity.bbclass
>>| 14 +++---
>>   meta/recipes-core/busybox/busybox.inc
>>|  2 +-
>>   
>> meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch
>> | 39 +++
>>   meta/recipes-core/glibc/glibc_2.24.bb
>>|  3 ++-
>>   meta/recipes-devtools/rpm/rpm_5.4.16.bb
>>|  2 +-
>>   meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc
>>|  2 ++
>>   meta/recipes-support/libpcre/libpcre_8.39.bb
>> |  2 ++
>>   9 files changed, 67 insertions(+), 10 deletions(-)
>>   create mode 100644 meta/recipes-core/glibc/glibc/
>> 0001-locale-fix-hard-coded-reference-to-gcc-E.patch
>>
>>
> --
> ___
> 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


Re: [OE-core] [PATCH v2 0/8] Fix BUILD_* family of variables

2016-09-12 Thread Jérémy Rosen

Any news ?


On 07/09/2016 11:08, Jérémy Rosen wrote:

The BUILD_* family of variables allow the user to specify the name of the host
compiler to use at build time. This feature is particularly important for long
term maintainance. Future versions of gcc might not be compatible with old
yocto distributions and we can't assume that "gcc" is the correct name for the
compiler.

This problem is already an issue with Jethro which can't be compiled on a
machine wher gcc-6 is the default compiler. pkgconfig-native will refuse to
compile because it uses -Werror and gcc-6 has new warnings compared to gcc-5

This patch serie fixes multiple hard-coded references to gcc in various recipes
and build infrastructure

This patch was tested by building core-image-minimal for qemu-x86_64 with a
directory with the following content added to the PATH

  g++ -> /bin/false
  gcc -> /bin/false
  myg++ -> /usr/bin/g++
  mygcc -> /usr/bin/gcc

And the following variables added to local.conf

export BUILD_CC = "mygcc"
export BUILD_CXX = "myg++"
export BUILD_CPP = "mygcc -E"
export BUILD_CCLD = "mygcc"

---
V2
* rewording in some commits messages
* no need for a patch to KConfig, use OE_RUNMAKE_FLAGS instead
* change all patch titles to use : in the short commit message
* rpm : manually remove files instead of calling make distclean
* libpcre : explicitely set CCLD_FOR_BUILD in the recipe since it's the only
   recipe using it.
* glibc patch has been submited upstream

It would be interesting to modify yocto's builders to use the BUILD_*
variable in order to have some early warning wrt gcc polution in recipes, but
seeing the various recipes I had to patch, I would expect such a change to
trigger a high number of build failures.

Jérémy Rosen (8):
   cross: export CC family from BUILD_* for cross compilers
   linux-yocto: allow overriding compiler name in KConfig
   linux-libc-headers: allow overriding compiler name in KConfig
   busybox: allow overriding compiler name in KConfig
   sanity: fix hardcoded references to gcc
   glibc: remove hard-coded reference to gcc -E
   rpm: manually cleanup sysck
   libpcre: explicitely specify CCLD_FOR_BUILD for this recipe

  meta/classes/cross.bbclass
| 12 
  meta/classes/kernel.bbclass   
|  1 +
  meta/classes/sanity.bbclass   
| 14 +++---
  meta/recipes-core/busybox/busybox.inc 
|  2 +-
  
meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch
 | 39 +++
  meta/recipes-core/glibc/glibc_2.24.bb 
|  3 ++-
  meta/recipes-devtools/rpm/rpm_5.4.16.bb   
|  2 +-
  meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc 
|  2 ++
  meta/recipes-support/libpcre/libpcre_8.39.bb  
|  2 ++
  9 files changed, 67 insertions(+), 10 deletions(-)
  create mode 100644 
meta/recipes-core/glibc/glibc/0001-locale-fix-hard-coded-reference-to-gcc-E.patch



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


Re: [OE-core] [OE-Core][PATCH] valgrind: MIPS: Make toolchain basename generic

2016-09-12 Thread Zubair Lutfullah Kakakhel

Hi

On 09/08/2016 04:45 PM, akuster808 wrote:



On 09/08/2016 06:14 AM, Zubair Lutfullah Kakakhel wrote:

For the hard float case, COMPATIBLE_HOST should be set to ".*-linux"
since OE can support multiple distro layers, not just poky.

Signed-off-by: Zubair Lutfullah Kakakhel 


is this good for Krogoth too? it has the same version.


Yes. But we'd also need this commit from master

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb?id=d7268e9bbae93455a591bb4f73bfe4bf76497a1b

They can both be squashed into one commit.

Thanks,
ZubairLK



- armin


---
Pointed out by Andre McCurdy but patch v1 had already been accepted
and applied.
---
  meta/recipes-devtools/valgrind/valgrind_3.11.0.bb | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb 
b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
index 3d49131..42fd27f 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.11.0.bb
@@ -39,8 +39,8 @@ COMPATIBLE_HOST_armv5 = 'null'
  COMPATIBLE_HOST_armv6 = 'null'

  # valgrind doesn't like mips soft float
-COMPATIBLE_HOST_mips = "${@bb.utils.contains("TARGET_FPU", "soft", "null", 
"mips-poky-linux", d)}"
-COMPATIBLE_HOST_mipsel = "${@bb.utils.contains("TARGET_FPU", "soft", "null", 
"mipsel-poky-linux", d)}"
+COMPATIBLE_HOST_mips = "${@bb.utils.contains("TARGET_FPU", "soft", "null", 
".*-linux", d)}"
+COMPATIBLE_HOST_mipsel = "${@bb.utils.contains("TARGET_FPU", "soft", "null", 
".*-linux", d)}"

  inherit autotools ptest




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


Re: [OE-core] [yocto] Subjects for YP Developer Day at ELCE

2016-09-12 Thread William Mills


On 09/09/2016 11:51 AM, Jeff Osier-Mixon wrote:

Hi all - we are in the planning stages for DevDay at ELCE right now,
particularly the advanced track. This track changes every session,
usually to cover the things we are working on hardest - for example,
in San Diego we covered CROPS, devtool, the latest Toaster features,
and much more.

Whether you are able to attend DevDay or not, we would be grateful to
hear your suggestions for subjects to cover in the advanced track. We
are currently planning talks about CROPS, devtool and the ESDK,
Toaster, wic, smack, security, and a few other things. If you have a
burning desire to hear about something specific, please let us know.



*** Status and state of the art for read-only root filesystems.
1) r/o root + tmpfs only for ephemeral systems
2) r/o root + select r/w points (bind-volatile?)
3) r/o root + unionfs r/w

My interest would be in #1 & #2 as it is security related.
r/w mount would be nosuid, nodev, etc and perhaps noexec
A survey of the space should include #3 however.

I know there is a section in the developer manual for the basic 
mechanisms of r/o root but it appears a lot is left as an excrice for 
the user.  Are the full demo images etc?


*** What is the OE/YP response to Ubuntu-core?
4) Can Yocto build transactionally updated-able bundles for kernel and 
core-os/root-fs?

5) Can Yocto [cross-]build snaps or flatpaks?
6) Will snapd (or whatever flatpak needs) become 1st class ecosystem 
components?

Ex: meta-snappy has a lot of good work but is early days
Currently meta-snappy disables AppArmor & seccomp
snapd does only light ns & cgroup control and relies on
  AppArmor to do most of the containment
so snapd w/o AppArmor is a demo
[Arch is no better BTW]

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


[OE-core] [PATCH] rpm: remove redundant removals

2016-09-12 Thread Ross Burton
These were noticed by the use of bashisms (rm *.{foo,bar}) and lots of these rm
commands are deleting files which don't exist in the first place.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/rpm/rpm_5.4.16.bb | 37 -
 1 file changed, 37 deletions(-)

diff --git a/meta/recipes-devtools/rpm/rpm_5.4.16.bb 
b/meta/recipes-devtools/rpm/rpm_5.4.16.bb
index 9f78dee..ee300a0 100644
--- a/meta/recipes-devtools/rpm/rpm_5.4.16.bb
+++ b/meta/recipes-devtools/rpm/rpm_5.4.16.bb
@@ -554,54 +554,19 @@ do_install_append() {
install -m 0755 ${WORKDIR}/pythondeps.sh 
${D}/${libdir}/rpm/pythondeps.sh
install -m 0755 ${WORKDIR}/perfile_rpmdeps.sh 
${D}/${libdir}/rpm/perfile_rpmdeps.sh
 
-   # Remove unpackaged files (based on list in rpm.spec)
-   rm -f 
${D}/${libdir}/rpm/{Specfile.pm,cpanflute,cpanflute2,rpmdiff,rpmdiff.cgi,sql.prov,sql.req,tcl.req,trpm}
-
-   rm -f ${D}/${mandir}/man8/rpmcache.8*
-   rm -f ${D}/${mandir}/man8/rpmgraph.8*
-   rm -f ${D}/${mandir}/*/man8/rpmcache.8*
-   rm -f ${D}/${mandir}/*/man8/rpmgraph.8*
-   rm -rf ${D}/${mandir}/{fr,ko}
-
rm -f ${D}/${includedir}/popt.h
rm -f ${D}/${libdir}/libpopt.*
rm -f ${D}/${libdir}/pkgconfig/popt.pc
rm -f ${D}/${datadir}/locale/*/LC_MESSAGES/popt.mo
rm -f ${D}/${mandir}/man3/popt.3
 
-   rm -f ${D}/${mandir}/man1/xar.1*
-   rm -f ${D}/${bindir}/xar
-   rm -rf ${D}/${includedir}/xar
-   rm -f ${D}/${libdir}/libxar*
-
-   rm -f ${D}/${bindir}/lz*
-   rm -f ${D}/${bindir}/unlzma
-   rm -f ${D}/${bindir}/unxz
-   rm -f ${D}/${bindir}/xz*
-   rm -rf ${D}/${includedir}/lzma*
-   rm -f ${D}/${mandir}/man1/lz*.1
-   rm -f ${D}/${libdir}/pkgconfig/liblzma*
-
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/*.a
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/*.la
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/rpm/*.a
rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/rpm/*.la
 
-   #find ${D}/${libdir}/perl5 -type f -a \( -name perllocal.pod -o -name 
.packlist \
-   #   -o \( -name '*.bs' -a -empty \) \) -exec rm -f {} ';'
-   #find ${D}/${libdir}/perl5 -type d -depth -exec rmdir {} 2>/dev/null ';'
-
-   rm -f ${D}/${libdir}/rpm/dbconvert.sh
-
rm -f ${D}/${libdir}/rpm/libsqldb.*
 
-   # We don't want, nor need the Mandriva multiarch items
-   rm -f ${D}/${bindir}/multiarch-dispatch
-   rm -f ${D}/${bindir}/multiarch-platform
-   rm -f ${D}/${libdir}/rpm/check-multiarch-files
-   rm -f ${D}/${libdir}/rpm/mkmultiarch
-   rm -f ${D}/${includedir}/multiarch-dispatch.h
-
rm -f ${D}/${libdir}/rpm/gstreamer.sh
rm -f ${D}/${libdir}/rpm/gem_helper.rb
rm -f ${D}/${libdir}/rpm/rubygems.rb
@@ -610,12 +575,10 @@ do_install_append() {
rm -f ${D}/${libdir}/rpm/macros.d/kernel
rm -f ${D}/${libdir}/rpm/macros.d/gstreamer
rm -f ${D}/${libdir}/rpm/bin/mgo
-   rm -f ${D}/${libdir}/rpm/bin/dbconvert
rm -f ${D}/${libdir}/rpm/bin/pom2spec
 
rm -rf ${D}/var/lib/wdj ${D}/var/cache/wdj
rm -f ${D}/${libdir}/rpm/bin/api-sanity-checker.pl
-
 }
 
 do_install_append_class-target() {
-- 
2.8.1

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


Re: [OE-core] [PATCH] rpm: remove redundant removals

2016-09-12 Thread Burton, Ross
On 8 September 2016 at 20:19, Mark Hatle  wrote:

> > - rm -f ${D}/${mandir}/man8/rpmcache.8*
> > - rm -f ${D}/${mandir}/man8/rpmgraph.8*
> > - rm -f ${D}/${mandir}/*/man8/rpmcache.8*
> > - rm -f ${D}/${mandir}/*/man8/rpmgraph.8*
> > - rm -rf ${D}/${mandir}/{fr,ko}
>
> Above cases need to be removed.  We do not support the rpmcache or
> rpmgraph, and
> at least for a long time the man pages were being generated for them.  (If
> this
> is no longer true, and man pages ARE being generated they should be
> removed.)


These manpages are not installed in the first place.

> - rm -f ${D}/${includedir}/popt.h
> > - rm -f ${D}/${libdir}/libpopt.*
> > - rm -f ${D}/${libdir}/pkgconfig/popt.pc
> > - rm -f ${D}/${datadir}/locale/*/LC_MESSAGES/popt.mo
> > - rm -f ${D}/${mandir}/man3/popt.3
>
> We can use either an internal or external version of the popt library.  If
> the
> internal version is used, we MUST remove all of these files.  If the
> external
> version is used, the RPM won't end up doing anything.


Okay, restored.


> > - rm -f ${D}/${mandir}/man1/xar.1*
> > - rm -f ${D}/${bindir}/xar
> > - rm -rf ${D}/${includedir}/xar
> > - rm -f ${D}/${libdir}/libxar*
>

xar is a PACKAGECONFIG which is disabled by default, so removing the files
if it is enabled seems wrong.


> > - rm -f ${D}/${bindir}/lz*
> > - rm -f ${D}/${bindir}/unlzma
> > - rm -f ${D}/${bindir}/unxz
> > - rm -f ${D}/${bindir}/xz*
> > - rm -rf ${D}/${includedir}/lzma*
> > - rm -f ${D}/${mandir}/man1/lz*.1
> > - rm -f ${D}/${libdir}/pkgconfig/liblzma*
>
> Above files may be generated in some configurations.  (Possible that is no
> longer true.


Doesn't appear to be true any more: rpm links to an external xz.


>  > - rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/*.a

>   rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/*.la
> > - rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/rpm/*.a
> >   rm -f ${D}${PYTHON_SITEPACKAGES_DIR}/rpm/*.la
>
> The .a files were removed because we didn't want anyone statically linking
> to
> python.a, not sure they they were being produced to begin with.. but that
> is why
> that was there.


Nothing is installing these but I suspect this is a side-effect of Poky's
no-static-libs change, so I'll remove this.

> - rm -f ${D}/${libdir}/rpm/libsqldb.*
> > -
>
> If 'sqlite' support is enabled in RPM, the above should be removed.  It
> will
> clash with external components.


Done.


>
> > - # We don't want, nor need the Mandriva multiarch items
> > - rm -f ${D}/${bindir}/multiarch-dispatch
> > - rm -f ${D}/${bindir}/multiarch-platform
> > - rm -f ${D}/${libdir}/rpm/check-multiarch-files
> > - rm -f ${D}/${libdir}/rpm/mkmultiarch
> > - rm -f ${D}/${includedir}/multiarch-dispatch.h
> > -
>
> Again, some configs may produce these.. if they're not produced in our
> config we
> can remove it.


Not anymore apparently:

noinst_SCRIPTS += multiarch-dispatch multiarch-platform
noinst_SCRIPTS += check-multiarch-files mkmultiarch
noinst_HEADERS = multiarch-dispatch.h


> >   rm -f ${D}/${libdir}/rpm/gstreamer.sh
> >   rm -f ${D}/${libdir}/rpm/gem_helper.rb
> >   rm -f ${D}/${libdir}/rpm/rubygems.rb
> > @@ -610,12 +567,10 @@ do_install_append() {
> >   rm -f ${D}/${libdir}/rpm/macros.d/kernel
> >   rm -f ${D}/${libdir}/rpm/macros.d/gstreamer
> >   rm -f ${D}/${libdir}/rpm/bin/mgo
> > - rm -f ${D}/${libdir}/rpm/bin/dbconvert
>
> dbconvert is not useful for us.. it used to be provided, so we removed it.


This doesn't get installed anymore.

V2 incoming.

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


[OE-core] gnutls 3.5.3 & linux 3.10

2016-09-12 Thread Jack Mitchell
is anybody else seeing issues building gnutls with a 3.10 kernel on the 
target and failing at SYS_getrandom? I believe the breakage was 
introduced here


** libgnutls: Use getrandom where available via the syscall interface.
This works around an issue of not-using getrandom even if it exists
since glibc doesn't declare such function.

but AFAIU if the getrandom syscall isn't available it should fallback to 
using /dev/urandom but instead my compile step is just failing. Anyone 
else hitting this problem?


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


[OE-core] [oe-core] [PATCH] [krogoth] gobject-introspection.bbclass: disable introspection for -native and -nativesdk recipes

2016-09-12 Thread Zeeshan Ali
From: Alexander Kanavin 

It is not necessary for those targets, adds to the build time, and pulls
in the unneeded qemu-native dependency.

(From OE-Core rev: be18364edd5cd2c664f68120063a1e147563faab)

Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
---
 meta/classes/gobject-introspection.bbclass | 14 --
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/meta/classes/gobject-introspection.bbclass 
b/meta/classes/gobject-introspection.bbclass
index 2d73e40..cc7ca5a 100644
--- a/meta/classes/gobject-introspection.bbclass
+++ b/meta/classes/gobject-introspection.bbclass
@@ -3,13 +3,23 @@
 # This sets up autoconf-based recipes to build introspection data (or not),
 # depending on distro and machine features (see gobject-introspection-data 
class).
 inherit gobject-introspection-data
-EXTRA_OECONF_prepend = "${@bb.utils.contains('GI_DATA_ENABLED', 'True', 
'--enable-introspection', '--disable-introspection', d)} "
+EXTRA_OECONF_prepend_class-target = "${@bb.utils.contains('GI_DATA_ENABLED', 
'True', '--enable-introspection', '--disable-introspection', d)} "
+
+# When building native recipes, disable introspection, as it is not necessary,
+# pulls in additional dependencies, and makes build times longer
+EXTRA_OECONF_prepend_class-native = "--disable-introspection "
+EXTRA_OECONF_prepend_class-nativesdk = "--disable-introspection "
 
 UNKNOWN_CONFIGURE_WHITELIST_append = " --enable-introspection 
--disable-introspection"
 
 # Generating introspection data depends on a combination of native and target
 # introspection tools, and qemu to run the target tools.
-DEPENDS_append = " gobject-introspection gobject-introspection-native 
qemu-native"
+DEPENDS_append_class-target = " gobject-introspection 
gobject-introspection-native qemu-native"
+
+# Even though introspection is disabled on -native, gobject-introspection 
package is still
+# needed for m4 macros.
+DEPENDS_append_class-native = " gobject-introspection-native"
+DEPENDS_append_class-nativesdk = " gobject-introspection-native"
 
 # This is necessary for python scripts to succeed - distutils fails if these
 # are not set
-- 
2.7.4

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


Re: [OE-core] [PATCH] image.bbclass: Do not expand variables in IMAGE_CMD vardepsexclude

2016-09-12 Thread Jonathan Liu
Hi Richard,

On 12 September 2016 at 20:19, Richard Purdie
 wrote:
> On Sun, 2016-09-11 at 22:14 +1000, Jonathan Liu wrote:
>> This fixes tashhash mismatch errors creating images when IMAGE_CMD
>> references a variable whose value is always changing even though the
>> variable is specified in IMAGE_CMD vardepsexclude.
>>
>> Signed-off-by: Jonathan Liu 
>> ---
>>  meta/classes/image.bbclass | 4 
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
>> index 8c8b8a2..f85ea86 100644
>> --- a/meta/classes/image.bbclass
>> +++ b/meta/classes/image.bbclass
>> @@ -441,6 +441,10 @@ python () {
>>  localdata.delVar('DATETIME')
>>  localdata.delVar('TMPDIR')
>>
>> +vardepsexclude = d.getVarFlag('IMAGE_CMD', 'vardepsexclude',
>> True) or ''
>> +vardepsexclude += ' ' + (d.getVarFlag('IMAGE_CMD_' + realt,
>> 'vardepsexclude', True) or '')
>> +for var in vardepsexclude.split():
>> +localdata.delVar(var)
>>  image_cmd = localdata.getVar("IMAGE_CMD", True)
>>  vardeps.add('IMAGE_CMD_' + realt)
>>  if image_cmd:
>
> I think this is complicating an already fragile situation and it
> worries me. Can you be more specific about which variable is causing
> problems here?

See IMAGEDATESTAMP variable in:
https://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/classes/sdcard_image-rpi.bbclass
https://github.com/linux-sunxi/meta-sunxi/blob/master/classes/sdcard_image-sunxi.bbclass

You can test by changing to:
IMAGEDATESTAMP = "${@time.clock()}"

>
> I'm starting to wonder if we should have an explicit flag set here for
> "problem" variables and we'd default to the values "DATETIME TMPDIR"
> which are already handled in the code. You'd then just need to extend
> that value. Using vardepsexclude seems to partially but not completely
> match?
>
> Incidentally, I really want to complete some of the rework in this area
> so we get to "proper" functions and can stop playing games like this. I
> just haven't had the time to do that and this point in the release
> cycle isn't the right time to do that.
>
> Cheers,
>
> Richard
>
>

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


Re: [OE-core] [PATCH] ltp: 20160126 -> 20160510

2016-09-12 Thread Alexander Kanavin

On 09/11/2016 05:11 PM, Wang Xin wrote:

1) Upgrade ltp from 20160126 to 20160510.
2) Modify some patches, since the data has been changed.
0011-Rename-sigset-variable-to-sigset1.patch
0030-lib-Use-PTHREAD_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch
3) Delete some patches, since they are no use.
0001-ltp-Don-t-link-against-libfl.patch
0006-sendfile-Use-off64_t-instead-of-__off64_t.patch
0012-fsstress.c-Replace-__int64_t-with-int64_t.patch
0013-include-fcntl.h-for-getting-O_-definitions.patch
0014-hyperthreading-Include-sys-types.h-for-pid_t-definit.patch
0015-mincore01-Rename-PAGESIZE-to-pagesize.patch
0016-ustat-Change-header-from-ustat.h-to-sys-ustat.h.patch
0017-replace-sigval_t-with-union-sigval.patch
0019-tomoyo-Replace-canonicalize_file_name-with-realpath.patch
0032-regen.sh-Include-asm-unistd.h-explicitly.patch

Signed-off-by: Wang Xin 
---
 .../0011-Rename-sigset-variable-to-sigset1.patch   | 60 +++---
 ...READ_MUTEX_RECURSIVE-in-place-of-PTHREAD_.patch |  6 +--
 .../ltp/{ltp_20160126.bb => ltp_20160510.bb}   | 12 +
 3 files changed, 34 insertions(+), 44 deletions(-)


The patches' deletions are absent from the patch.

Alex

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


[OE-core] [PATCH 2/2] classes/gobject-introspecton-data: lazy assign GI_DATA_ENABLED

2016-09-12 Thread Ross Burton
By letting a recipe assign GI_DATA_ENABLED trivially there is a simple and clear
way to disable gobject-introspection for specific build configurations.

Signed-off-by: Ross Burton 
---
 meta/classes/gobject-introspection-data.bbclass | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/meta/classes/gobject-introspection-data.bbclass 
b/meta/classes/gobject-introspection-data.bbclass
index b1bdd26..2ef6846 100644
--- a/meta/classes/gobject-introspection-data.bbclass
+++ b/meta/classes/gobject-introspection-data.bbclass
@@ -3,7 +3,5 @@
 #
 # It should be used in recipes to determine whether introspection data should 
be built,
 # so that qemu use can be avoided when necessary.
-GI_DATA_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 
'gobject-introspection-data', \
+GI_DATA_ENABLED ?= "${@bb.utils.contains('DISTRO_FEATURES', 
'gobject-introspection-data', \
   bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 
'True', 'False', d), 'False', d)}"
-
-
-- 
2.8.1

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


[OE-core] [PATCH 1/2] classes/gtk-doc: lazy assign GTKDOC_ENABLED

2016-09-12 Thread Ross Burton
By letting a recipe assign GTKDOC_ENABLED trivially there is a simple and clear
way to disable gtk-doc for specific build configurations.

Signed-off-by: Ross Burton 
---
 meta/classes/gtk-doc.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass
index b2b6239..297eac6 100644
--- a/meta/classes/gtk-doc.bbclass
+++ b/meta/classes/gtk-doc.bbclass
@@ -7,7 +7,7 @@
 #
 # It should be used in recipes to determine whether gtk-doc based 
documentation should be built,
 # so that qemu use can be avoided when necessary.
-GTKDOC_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 'api-documentation', 
\
+GTKDOC_ENABLED ?= "${@bb.utils.contains('DISTRO_FEATURES', 
'api-documentation', \
   bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 
'True', 'False', d), 'False', d)}"
 
 EXTRA_OECONF_prepend_class-target = "${@bb.utils.contains('GTKDOC_ENABLED', 
'True', '--enable-gtk-doc --enable-gtk-doc-html --disable-gtk-doc-pdf', \
-- 
2.8.1

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


Re: [OE-core] [PATCH] image.bbclass: Do not expand variables in IMAGE_CMD vardepsexclude

2016-09-12 Thread Richard Purdie
On Sun, 2016-09-11 at 22:14 +1000, Jonathan Liu wrote:
> This fixes tashhash mismatch errors creating images when IMAGE_CMD
> references a variable whose value is always changing even though the
> variable is specified in IMAGE_CMD vardepsexclude.
> 
> Signed-off-by: Jonathan Liu 
> ---
>  meta/classes/image.bbclass | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 8c8b8a2..f85ea86 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -441,6 +441,10 @@ python () {
>  localdata.delVar('DATETIME')
>  localdata.delVar('TMPDIR')
>  
> +vardepsexclude = d.getVarFlag('IMAGE_CMD', 'vardepsexclude',
> True) or ''
> +vardepsexclude += ' ' + (d.getVarFlag('IMAGE_CMD_' + realt,
> 'vardepsexclude', True) or '')
> +for var in vardepsexclude.split():
> +localdata.delVar(var)
>  image_cmd = localdata.getVar("IMAGE_CMD", True)
>  vardeps.add('IMAGE_CMD_' + realt)
>  if image_cmd:

I think this is complicating an already fragile situation and it
worries me. Can you be more specific about which variable is causing
problems here?

I'm starting to wonder if we should have an explicit flag set here for
"problem" variables and we'd default to the values "DATETIME TMPDIR"
which are already handled in the code. You'd then just need to extend
that value. Using vardepsexclude seems to partially but not completely
match?

Incidentally, I really want to complete some of the rework in this area
so we get to "proper" functions and can stop playing games like this. I
just haven't had the time to do that and this point in the release
cycle isn't the right time to do that.

Cheers,

Richard


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


[OE-core] [PATCH v2] gst-player: specify PV

2016-09-12 Thread Markus Lehtonen
Define PV in order to avoid package version being plain "git". Use the
version number found from configure.ac plus the git revision.

Signed-off-by: Markus Lehtonen 
---
 meta/recipes-multimedia/gstreamer/gst-player_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-multimedia/gstreamer/gst-player_git.bb 
b/meta/recipes-multimedia/gstreamer/gst-player_git.bb
index 00ad941..2a4c9dc 100644
--- a/meta/recipes-multimedia/gstreamer/gst-player_git.bb
+++ b/meta/recipes-multimedia/gstreamer/gst-player_git.bb
@@ -12,6 +12,7 @@ SRC_URI = "git://github.com/sdroege/gst-player.git \
file://gst-player.desktop"
 
 SRCREV = "ea90e63c1064503f9ba5d59aa4ca604f13ca5def"
+PV = "0.0.1+git${SRCPV}"
 
 S = "${WORKDIR}/git"
 
-- 
2.6.6

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


Re: [OE-core] [PATCH] gst-player: include SRCPV in PV

2016-09-12 Thread Markus Lehtonen
On Fri, 2016-09-09 at 11:51 +0100, Burton, Ross wrote:
> 
> On 9 September 2016 at 06:57, Markus Lehtonen <
> markus.lehto...@linux.intel.com> wrote:
> > +PV = "git${SRCPV}"
> > 
> This breaks packaging for me, throwing interesting python exceptions.
Hmm, strange. I didn't see anything like that. From what I can tell,
changing PV from "git" to "git${SRCPV}" shouldn't cause anything like that.
> gst-player has a version in configure.ac, so this should be
> 0.0.1+git${SRCPV} I guess.
That looks better, I'll send v2 soon.
Thanks,
  Markus-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [RFC] iptables: add systemd helper unit to load/restore rules

2016-09-12 Thread Jack Mitchell



On 08/09/16 12:29, Jack Mitchell wrote:

From: Jack Mitchell 

there is currently no way to automatically load iptable rules
in OE. Add a systemd unit file to automatically load rules on
network connection. This is cribbed from the way ArchLinux
handles iptables with some minor modifications for OE. New rules
can be generated using 'iptables-save > iptables.rules'
---
 .../iptables/iptables/iptables.rules |  0
 .../iptables/iptables/iptables.service   | 13 +
 meta/recipes-extended/iptables/iptables_1.6.0.bb | 20 ++--
 3 files changed, 31 insertions(+), 2 deletions(-)
 create mode 100644 meta/recipes-extended/iptables/iptables/iptables.rules
 create mode 100644 meta/recipes-extended/iptables/iptables/iptables.service

diff --git a/meta/recipes-extended/iptables/iptables/iptables.rules 
b/meta/recipes-extended/iptables/iptables/iptables.rules
new file mode 100644
index 000..e69de29
diff --git a/meta/recipes-extended/iptables/iptables/iptables.service 
b/meta/recipes-extended/iptables/iptables/iptables.service
new file mode 100644
index 000..041316e
--- /dev/null
+++ b/meta/recipes-extended/iptables/iptables/iptables.service
@@ -0,0 +1,13 @@
+[Unit]
+Description=Packet Filtering Framework
+Before=network-pre.target
+Wants=network-pre.target
+
+[Service]
+Type=oneshot
+ExecStart=@SBINDIR@/iptables-restore /etc/iptables/iptables.rules
+ExecReload=@SBINDIR@/iptables-restore /etc/iptables/iptables.rules
+RemainAfterExit=yes
+
+[Install]
+WantedBy=multi-user.target
diff --git a/meta/recipes-extended/iptables/iptables_1.6.0.bb 
b/meta/recipes-extended/iptables/iptables_1.6.0.bb
index fbbe418..65430a1 100644
--- a/meta/recipes-extended/iptables/iptables_1.6.0.bb
+++ b/meta/recipes-extended/iptables/iptables_1.6.0.bb
@@ -22,13 +22,16 @@ SRC_URI = 
"http://netfilter.org/projects/iptables/files/iptables-${PV}.tar.bz2 \
file://types.h-add-defines-that-are-required-for-if_packet.patch \

file://0001-configure-Add-option-to-enable-disable-libnfnetlink.patch \

file://0002-configure.ac-only-check-conntrack-when-libnfnetlink-enabled.patch \
-  "
+   file://iptables.service \
+   file://iptables.rules \
+"
+
 SRC_URI_append_libc-musl = " file://0001-fix-build-with-musl.patch"

 SRC_URI[md5sum] = "27ba3451cb622467fc9267a176f19a31"
 SRC_URI[sha256sum] = 
"4bb72a0a0b18b5a9e79e87631ddc4084528e5df236bc7624472dcaa8480f1c60"

-inherit autotools pkgconfig
+inherit autotools pkgconfig systemd

 EXTRA_OECONF = "--with-kernel=${STAGING_INCDIR} \
"
@@ -48,3 +51,16 @@ do_configure_prepend() {
# Keep ax_check_linker_flags.m4 which belongs to autoconf-archive.
rm -f libtool.m4 lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4
 }
+
+do_install_append() {
+
+install -d ${D}${sysconfdir}/iptables
+install -m 0644 ${WORKDIR}/iptables.rules ${D}${sysconfdir}/iptables
+
+install -d ${D}${systemd_unitdir}/system
+install -m 0644 ${WORKDIR}/iptables.service 
${D}${systemd_unitdir}/system
+
+   sed -i -e 's,@SBINDIR@,${sbindir},g' 
${D}${systemd_unitdir}/system/iptables.service
+}
+
+SYSTEMD_SERVICE_${PN} = "iptables.service"



If there are no comments on this then I suggest we take it as it is. Not 
having a way to auto load iptables rules is just asking for 
layer/application specific hacks.

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


[OE-core] [PATCH 2/2] meta: cleanup d.getVar(var, 0)

2016-09-12 Thread Robert Yang
Signed-off-by: Robert Yang 
---
 meta/classes/base.bbclass  |  2 +-
 meta/classes/image.bbclass |  2 +-
 meta/classes/package.bbclass   |  2 +-
 meta/classes/recipe_sanity.bbclass | 22 +++---
 4 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index a31a53f..5a1bd3a 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -472,7 +472,7 @@ python () {
 else:
 raise bb.parse.SkipPackage("incompatible with machine %s (not in 
COMPATIBLE_MACHINE)" % d.getVar('MACHINE', True))
 
-source_mirror_fetch = d.getVar('SOURCE_MIRROR_FETCH', 0)
+source_mirror_fetch = d.getVar('SOURCE_MIRROR_FETCH', False)
 if not source_mirror_fetch:
 need_host = d.getVar('COMPATIBLE_HOST', True)
 if need_host:
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 8c8b8a2..8273401 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -359,7 +359,7 @@ python () {
 # Without de-duplication, gen_conversion_cmds() below
 # would create the same compression command multiple times.
 ctypes = set(d.getVar('CONVERSIONTYPES', True).split())
-old_overrides = d.getVar('OVERRIDES', 0)
+old_overrides = d.getVar('OVERRIDES', False)
 
 def _image_base_type(type):
 basetype = type
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index d0b2db6..a9ca141 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -1490,7 +1490,7 @@ python package_do_shlibs() {
 import re, pipes
 import subprocess as sub
 
-exclude_shlibs = d.getVar('EXCLUDE_FROM_SHLIBS', 0)
+exclude_shlibs = d.getVar('EXCLUDE_FROM_SHLIBS', False)
 if exclude_shlibs:
 bb.note("not generating shlibs")
 return
diff --git a/meta/classes/recipe_sanity.bbclass 
b/meta/classes/recipe_sanity.bbclass
index 295611f..add34df 100644
--- a/meta/classes/recipe_sanity.bbclass
+++ b/meta/classes/recipe_sanity.bbclass
@@ -8,7 +8,7 @@ def bad_runtime_vars(cfgdata, d):
 return
 
 for var in d.getVar("__recipe_sanity_badruntimevars", True).split():
-val = d.getVar(var, 0)
+val = d.getVar(var, False)
 if val and val != cfgdata.get(var):
 __note("%s should be %s_${PN}" % (var, var), d)
 
@@ -16,11 +16,11 @@ __recipe_sanity_reqvars = "DESCRIPTION"
 __recipe_sanity_reqdiffvars = ""
 def req_vars(cfgdata, d):
 for var in d.getVar("__recipe_sanity_reqvars", True).split():
-if not d.getVar(var, 0):
+if not d.getVar(var, False):
 __note("%s should be set" % var, d)
 
 for var in d.getVar("__recipe_sanity_reqdiffvars", True).split():
-val = d.getVar(var, 0)
+val = d.getVar(var, False)
 cfgval = cfgdata.get(var)
 
 if not val:
@@ -29,7 +29,7 @@ def req_vars(cfgdata, d):
 __note("%s should be defined to something other than default (%s)" 
% (var, cfgval), d)
 
 def var_renames_overwrite(cfgdata, d):
-renames = d.getVar("__recipe_sanity_renames", 0)
+renames = d.getVar("__recipe_sanity_renames", False)
 if renames:
 for (key, newkey, oldvalue, newvalue) in renames:
 if oldvalue != newvalue and oldvalue != cfgdata.get(newkey):
@@ -50,7 +50,7 @@ def can_use_autotools_base(cfgdata, d):
 if cfg.find(i) != -1:
 return False
 
-for clsfile in d.getVar("__inherit_cache", 0):
+for clsfile in d.getVar("__inherit_cache", False):
 (base, _) = os.path.splitext(os.path.basename(clsfile))
 if cfg.find("%s_do_configure" % base) != -1:
 __note("autotools_base usage needs verification, spotted 
%s_do_configure" % base, d)
@@ -60,7 +60,7 @@ def can_use_autotools_base(cfgdata, d):
 def can_delete_FILESPATH(cfgdata, d):
 expected = cfgdata.get("FILESPATH")
 expectedpaths = d.expand(expected)
-unexpanded = d.getVar("FILESPATH", 0)
+unexpanded = d.getVar("FILESPATH", False)
 filespath = d.getVar("FILESPATH", True).split(":")
 filespath = [os.path.normpath(f) for f in filespath if os.path.exists(f)]
 for fp in filespath:
@@ -73,7 +73,7 @@ def can_delete_FILESPATH(cfgdata, d):
 def can_delete_FILESDIR(cfgdata, d):
 expected = cfgdata.get("FILESDIR")
 #expected = "${@bb.utils.which(d.getVar('FILESPATH', True), '.')}"
-unexpanded = d.getVar("FILESDIR", 0)
+unexpanded = d.getVar("FILESDIR", False)
 if unexpanded is None:
 return False
 
@@ -90,7 +90,7 @@ def can_delete_others(p, cfgdata, d):
 for k in ["S", "PV", "PN", "DESCRIPTION", "DEPENDS",
   "SECTION", "PACKAGES", "EXTRA_OECONF", "EXTRA_OEMAKE"]:
 #for k in cfgdata:
-unexpanded = d.getVar(k, 0)
+unexpanded = d.getVar(k, False)
 cfgunexpanded = cfgdata.get(k)
 if not cfgunexpanded:
 continue
@@ -117,7 +117,7 @@ 

[OE-core] [PATCH 1/2] meta: cleanup d.getVar(var, 1)

2016-09-12 Thread Robert Yang
Signed-off-by: Robert Yang 
---
 meta/classes/kernel.bbclass   | 8 
 meta/classes/package_ipk.bbclass  | 2 +-
 meta/lib/oe/utils.py  | 4 ++--
 meta/recipes-devtools/apt/apt-native.inc  | 2 +-
 meta/recipes-devtools/cmake/cmake.inc | 2 +-
 .../kconfig-frontends/kconfig-frontends_3.12.0.0.bb   | 2 +-
 meta/recipes-devtools/vala/vala.inc   | 2 +-
 meta/recipes-support/boost/boost-1.61.0.inc   | 4 ++--
 8 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index d6a0ca8..b8fbbc5 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -127,9 +127,9 @@ PACKAGES_DYNAMIC += "^kernel-firmware-.*"
 export OS = "${TARGET_OS}"
 export CROSS_COMPILE = "${TARGET_PREFIX}"
 
-KERNEL_PRIORITY ?= 
"${@int(d.getVar('PV',1).split('-')[0].split('+')[0].split('.')[0]) * 1 + \
-   
int(d.getVar('PV',1).split('-')[0].split('+')[0].split('.')[1]) * 100 + \
-   
int(d.getVar('PV',1).split('-')[0].split('+')[0].split('.')[-1])}"
+KERNEL_PRIORITY ?= "${@int(d.getVar('PV', 
True).split('-')[0].split('+')[0].split('.')[0]) * 1 + \
+   int(d.getVar('PV', 
True).split('-')[0].split('+')[0].split('.')[1]) * 100 + \
+   int(d.getVar('PV', 
True).split('-')[0].split('+')[0].split('.')[-1])}"
 
 KERNEL_RELEASE ?= "${KERNEL_VERSION}"
 
@@ -140,7 +140,7 @@ KERNEL_IMAGEDEST = "boot"
 #
 # configuration
 #
-export CMDLINE_CONSOLE = "console=${@d.getVar("KERNEL_CONSOLE",1) or "ttyS0"}"
+export CMDLINE_CONSOLE = "console=${@d.getVar("KERNEL_CONSOLE", True) or 
"ttyS0"}"
 
 KERNEL_VERSION = "${@get_kernelversion_headers('${B}')}"
 
diff --git a/meta/classes/package_ipk.bbclass b/meta/classes/package_ipk.bbclass
index e32b9cb..930e154 100644
--- a/meta/classes/package_ipk.bbclass
+++ b/meta/classes/package_ipk.bbclass
@@ -245,7 +245,7 @@ python do_package_ipk () {
 
 os.chdir(basedir)
 ret = subprocess.call("PATH=\"%s\" %s %s %s" % 
(localdata.getVar("PATH", True),
-  
d.getVar("OPKGBUILDCMD",1), pkg, pkgoutdir), shell=True)
+  
d.getVar("OPKGBUILDCMD", True), pkg, pkgoutdir), shell=True)
 if ret != 0:
 bb.utils.unlockfile(lf)
 raise bb.build.FuncFailed("opkg-build execution failed")
diff --git a/meta/lib/oe/utils.py b/meta/lib/oe/utils.py
index 19db540..d6545b1 100644
--- a/meta/lib/oe/utils.py
+++ b/meta/lib/oe/utils.py
@@ -23,13 +23,13 @@ def ifelse(condition, iftrue = True, iffalse = False):
 return iffalse
 
 def conditional(variable, checkvalue, truevalue, falsevalue, d):
-if d.getVar(variable,1) == checkvalue:
+if d.getVar(variable, True) == checkvalue:
 return truevalue
 else:
 return falsevalue
 
 def less_or_equal(variable, checkvalue, truevalue, falsevalue, d):
-if float(d.getVar(variable,1)) <= float(checkvalue):
+if float(d.getVar(variable, True)) <= float(checkvalue):
 return truevalue
 else:
 return falsevalue
diff --git a/meta/recipes-devtools/apt/apt-native.inc 
b/meta/recipes-devtools/apt/apt-native.inc
index 59aa04e..9fa206e 100644
--- a/meta/recipes-devtools/apt/apt-native.inc
+++ b/meta/recipes-devtools/apt/apt-native.inc
@@ -17,7 +17,7 @@ python do_install () {
 }
 
 python do_install_config () {
-indir = os.path.dirname(d.getVar('FILE',1))
+indir = os.path.dirname(d.getVar('FILE', True))
 infile = open(oe.path.join(indir, 'files', 'apt.conf'), 'r')
 data = infile.read()
 infile.close()
diff --git a/meta/recipes-devtools/cmake/cmake.inc 
b/meta/recipes-devtools/cmake/cmake.inc
index 1a1896f..1f73b3a 100644
--- a/meta/recipes-devtools/cmake/cmake.inc
+++ b/meta/recipes-devtools/cmake/cmake.inc
@@ -9,7 +9,7 @@ LICENSE = "BSD"
 LIC_FILES_CHKSUM = "file://Copyright.txt;md5=052f86c15bbde68af55c7f7b340ab639 \
 
file://Source/cmake.h;beginline=1;endline=10;md5=341736dae83c9e344b53eeb1bc7d7bc2"
 
-CMAKE_MAJOR_VERSION = "${@'.'.join(d.getVar('PV',1).split('.')[0:2])}"
+CMAKE_MAJOR_VERSION = "${@'.'.join(d.getVar('PV', True).split('.')[0:2])}"
 
 SRC_URI = "https://cmake.org/files/v${CMAKE_MAJOR_VERSION}/cmake-${PV}.tar.gz \
file://support-oe-qt4-tools-names.patch \
diff --git 
a/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.12.0.0.bb 
b/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.12.0.0.bb
index 804186d..9b65a99 100644
--- a/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.12.0.0.bb
+++ b/meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.12.0.0.bb
@@ -32,7 +32,7 @@ EXTRA_OECONF += 

[OE-core] [PATCH 0/2] meta: cleanup d.getVar(var, 1) and d.getVar(var, 0)

2016-09-12 Thread Robert Yang
The following changes since commit 4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac:

  oeqa.runtime.smart: work around smart race issues (2016-09-09 12:12:17 +0100)

are available in the git repository at:

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

Robert Yang (2):
  meta: cleanup d.getVar(var, 1)
  meta: cleanup d.getVar(var, 0)

 meta/classes/base.bbclass  |  2 +-
 meta/classes/image.bbclass |  2 +-
 meta/classes/kernel.bbclass|  8 
 meta/classes/package.bbclass   |  2 +-
 meta/classes/package_ipk.bbclass   |  2 +-
 meta/classes/recipe_sanity.bbclass | 22 +++---
 meta/lib/oe/utils.py   |  4 ++--
 meta/recipes-devtools/apt/apt-native.inc   |  2 +-
 meta/recipes-devtools/cmake/cmake.inc  |  2 +-
 .../kconfig-frontends_3.12.0.0.bb  |  2 +-
 meta/recipes-devtools/vala/vala.inc|  2 +-
 meta/recipes-support/boost/boost-1.61.0.inc|  4 ++--
 12 files changed, 27 insertions(+), 27 deletions(-)

-- 
2.9.0

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


Re: [OE-core] [PATCH 1/1] qemurunner: print out the runqemu command

2016-09-12 Thread Joshua Lock
On Fri, 2016-09-09 at 09:38 -0700, bavery wrote:
> This logs the launch command that was used for runqemu while running
> -c
> testimage.  This way, if I'd like to easily launch qemu manually in
> order to debug a failed test, I know what commmand was run to create
> the qemu instance.

I already have this in my runqemu output:

runqemu - INFO - Running
/home/joshuagl/Projects/poky/build/tmp/sysroots/x86_64-
linux/usr/bin/qemu-system-ppc -net
tap,vlan=0,ifname=tap0,script=no,downscript=no -net nic,model=pcnet  -
machine mac99 -cpu G4 -m 256 -drive file=/home/joshuagl/mess/35/core-
image-lsb-qemuppc-20160902090100.rootfs.ext4,if=virtio,format=raw  -
show-cursor -usb -usbdevice tablet -device virtio-rng-pci -kernel
/home/joshuagl/mess/35/vmlinux-qemuppc.bin -append 'root=/dev/vda rw
highres=off  mem=256M ip=192.168.7.2::192.168.7.1:255.255.255.0
console=ttyS0 console=tty'


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


Re: [OE-core] [PATCH] mesa: update to 12.0.2

2016-09-12 Thread Andreas Müller
On Mon, Sep 12, 2016 at 9:42 AM, Jussi Kukkonen
 wrote:
> On 9 September 2016 at 19:19, Andreas Müller 
> wrote:
>>
>> * removed patch was applied mainline
>> * tested on RaspberryPi2 weston / lxqt / kde
>>
>> Signed-off-by: Andreas Müller 
>> ---
>>  .../mesa/files/clang-compile-PR89599.patch | 116
>> -
>>  .../mesa/{mesa-gl_12.0.1.bb => mesa-gl_12.0.2.bb}  |   0
>>  .../mesa/{mesa_12.0.1.bb => mesa_12.0.2.bb}|   5 +-
>
>
> 2.2 Milestone 3 is very close to release so this is unlikely to be accepted
> before 2.2 release scheduled next month. If you have a specific bug fix you
> need I suggest backporting.
>
>   Jussi
>
>
As far as I read mailing lists there were many improvements made for
RaspberryPi VC4. I understand that this update does not fit into
release cycle so forget this patch - I'll keep it in my branches.

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


Re: [OE-core] [PATCH] mesa: update to 12.0.2

2016-09-12 Thread Jussi Kukkonen
On 9 September 2016 at 19:19, Andreas Müller 
wrote:

> * removed patch was applied mainline
> * tested on RaspberryPi2 weston / lxqt / kde
>
> Signed-off-by: Andreas Müller 
> ---
>  .../mesa/files/clang-compile-PR89599.patch | 116
> -
>  .../mesa/{mesa-gl_12.0.1.bb => mesa-gl_12.0.2.bb}  |   0
>  .../mesa/{mesa_12.0.1.bb => mesa_12.0.2.bb}|   5 +-
>

2.2 Milestone 3 is very close to release so this is unlikely to be accepted
before 2.2 release scheduled next month. If you have a specific bug fix you
need I suggest backporting.

  Jussi


 3 files changed, 2 insertions(+), 119 deletions(-)
>  delete mode 100644 meta/recipes-graphics/mesa/
> files/clang-compile-PR89599.patch
>  rename meta/recipes-graphics/mesa/{mesa-gl_12.0.1.bb => mesa-gl_12.0.2.bb}
> (100%)
>  rename meta/recipes-graphics/mesa/{mesa_12.0.1.bb => mesa_12.0.2.bb}
> (77%)
>
> diff --git a/meta/recipes-graphics/mesa/files/clang-compile-PR89599.patch
> b/meta/recipes-graphics/mesa/files/clang-compile-PR89599.patch
> deleted file mode 100644
> index 48bd325..000
> --- a/meta/recipes-graphics/mesa/files/clang-compile-PR89599.patch
> +++ /dev/null
> @@ -1,116 +0,0 @@
> -From 5ec140c17b54c25920091501b665b9aa809cc5e8 Mon Sep 17 00:00:00 2001
> -From: Matt Turner 
> -Date: Mon, 11 Jul 2016 10:44:25 -0700
> -Subject: mapi: Massage code to allow clang to compile.
> -MIME-Version: 1.0
> -Content-Type: text/plain; charset=UTF-8
> -Content-Transfer-Encoding: 8bit
> -
> -According to https://llvm.org/bugs/show_bug.cgi?id=19778#c3 this code
> -was violating the spec, resulting in it failing to compile.
> -
> -Cc: mesa-sta...@lists.freedesktop.org
> -Co-authored-by: Tomasz Paweł Gajc 
> -Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89599
> -Reviewed-by: Emil Velikov 
> -
> -Upstream-Status: Backport
> -Signed-off-by: Khem Raj 
> -
> -diff --git a/configure.ac b/configure.ac
> -index 3799d8d..1ca8359 100644
>  a/configure.ac
> -+++ b/configure.ac
> -@@ -226,6 +226,7 @@ AX_GCC_FUNC_ATTRIBUTE([packed])
> - AX_GCC_FUNC_ATTRIBUTE([pure])
> - AX_GCC_FUNC_ATTRIBUTE([returns_nonnull])
> - AX_GCC_FUNC_ATTRIBUTE([unused])
> -+AX_GCC_FUNC_ATTRIBUTE([visibility])
> - AX_GCC_FUNC_ATTRIBUTE([warn_unused_result])
> - AX_GCC_FUNC_ATTRIBUTE([weak])
> -
> -diff --git a/src/mapi/entry_x86-64_tls.h b/src/mapi/entry_x86-64_tls.h
> -index 38faccc..c5262a1 100644
>  a/src/mapi/entry_x86-64_tls.h
> -+++ b/src/mapi/entry_x86-64_tls.h
> -@@ -25,6 +25,11 @@
> -  *Chia-I Wu 
> -  */
> -
> -+#ifdef HAVE_FUNC_ATTRIBUTE_VISIBIITY
> -+#define HIDDEN __attribute__((visibility("hidden")))
> -+#else
> -+#define HIDDEN
> -+#endif
> -
> - __asm__(".text\n"
> - ".balign 32\n"
> -@@ -54,8 +59,8 @@ entry_patch_public(void)
> - {
> - }
> -
> --static char
> --x86_64_entry_start[];
> -+extern char
> -+x86_64_entry_start[] HIDDEN;
> -
> - mapi_func
> - entry_get_public(int slot)
> -diff --git a/src/mapi/entry_x86_tls.h b/src/mapi/entry_x86_tls.h
> -index 46d2ece..231b409 100644
>  a/src/mapi/entry_x86_tls.h
> -+++ b/src/mapi/entry_x86_tls.h
> -@@ -27,6 +27,12 @@
> -
> - #include 
> -
> -+#ifdef HAVE_FUNC_ATTRIBUTE_VISIBIITY
> -+#define HIDDEN __attribute__((visibility("hidden")))
> -+#else
> -+#define HIDDEN
> -+#endif
> -+
> - __asm__(".text");
> -
> - __asm__("x86_current_tls:\n\t"
> -@@ -71,8 +77,8 @@ __asm__(".text");
> - extern unsigned long
> - x86_current_tls();
> -
> --static char x86_entry_start[];
> --static char x86_entry_end[];
> -+extern char x86_entry_start[] HIDDEN;
> -+extern char x86_entry_end[] HIDDEN;
> -
> - void
> - entry_patch_public(void)
> -diff --git a/src/mapi/entry_x86_tsd.h b/src/mapi/entry_x86_tsd.h
> -index ea7bacb..03d9735 100644
>  a/src/mapi/entry_x86_tsd.h
> -+++ b/src/mapi/entry_x86_tsd.h
> -@@ -25,6 +25,11 @@
> -  *Chia-I Wu 
> -  */
> -
> -+#ifdef HAVE_FUNC_ATTRIBUTE_VISIBIITY
> -+#define HIDDEN __attribute__((visibility("hidden")))
> -+#else
> -+#define HIDDEN
> -+#endif
> -
> - #define X86_ENTRY_SIZE 32
> -
> -@@ -58,8 +63,8 @@ __asm__(".balign 32\n"
> - #include 
> - #include "u_execmem.h"
> -
> --static const char x86_entry_start[];
> --static const char x86_entry_end[];
> -+extern const char x86_entry_start[] HIDDEN;
> -+extern const char x86_entry_end[] HIDDEN;
> -
> - void
> - entry_patch_public(void)
> ---
> -cgit v0.10.2
> -
> diff --git a/meta/recipes-graphics/mesa/mesa-gl_12.0.1.bb
> b/meta/recipes-graphics/mesa/mesa-gl_12.0.2.bb
> similarity index 100%
> rename from meta/recipes-graphics/mesa/mesa-gl_12.0.1.bb
> rename to meta/recipes-graphics/mesa/mesa-gl_12.0.2.bb
> diff --git a/meta/recipes-graphics/mesa/mesa_12.0.1.bb
> b/meta/recipes-graphics/mesa/mesa_12.0.2.bb
> similarity index 77%
> rename from meta/recipes-graphics/mesa/mesa_12.0.1.bb
> rename to 

[OE-core] [PATCH] x264: add textrel to INSANE_SKIP for cyclone5 machine

2016-09-12 Thread Sujith H
From: Fahad Usman 

This change help fix the warning message:

x264/r2491+gitAUTOINC+c8a773ebfc-r0/packages-split/x264/usr/lib/libx264.so.144' 
has relocations in .text [textrel]

Adding textrel to INSANE_SKIP resolves this issue.

Signed-off-by: Fahad Usman 
---
 meta/recipes-multimedia/x264/x264_git.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-multimedia/x264/x264_git.bb 
b/meta/recipes-multimedia/x264/x264_git.bb
index fa44f9c..379961a 100644
--- a/meta/recipes-multimedia/x264/x264_git.bb
+++ b/meta/recipes-multimedia/x264/x264_git.bb
@@ -48,6 +48,7 @@ do_install() {
 oe_runmake install DESTDIR=${D}
 }
 
-# PIC can't be enabled for 32-bit x86
+# PIC can't be enabled for 32-bit x86 and cyclone5
 INSANE_SKIP_${PN}_append_x86 = " textrel"
+INSANE_SKIP_${PN}_append_cyclone5 = " textrel"
 
-- 
1.9.1

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