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

2017-04-06 Thread Patrick Ohly
On Fri, 2017-04-07 at 08:38 +1200, Paul Eggleton wrote:
> On Thursday, 6 April 2017 1:36:05 AM NZST you wrote:
> >AssertionError: False is not true : Layer meta- changed 120
> > signatures, initial differences (first hash without, second with layer):
> 
> BTW, rather than self.assertTrue(False, ... ) you can just use self.fail(...) 
> and then you avoid this ugly "False is not True" bit.

I suspected that there must be something like that when changing the
message, but then was too lazy to look it up - thanks for pointing it
out ;-}

I'll change that in a V2.

-- 
Best Regards, Patrick Ohly

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



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


[OE-core] [PATCH 2/4] mkfontscale: Remove x11 requirement

2017-04-06 Thread Jussi Kukkonen
Build does not need libx11, so also does not need the distro feature.

Signed-off-by: Jussi Kukkonen 
---
 meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb 
b/meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb
index 31cf186..066f4a7 100644
--- a/meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb
+++ b/meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb
@@ -10,6 +10,9 @@ is used by the mkfontdir program."
 
 DEPENDS = "util-macros-native zlib libfontenc freetype xproto"
 
+# We don't actually need x11 as xorg-app-common claims
+REQUIRED_DISTRO_FEATURES = ""
+
 BBCLASSEXTEND = "native"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=2e0d129d05305176d1a790e0ac1acb7f"
-- 
2.1.4

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


[OE-core] [PATCH 0/4] Use fixed DISTRO_FEATURES for native

2017-04-06 Thread Jussi Kukkonen
Avoid signifant native task churn when DISTRO_FEATURES is changed
by defining a fixed DISTRO_FEATURES value (default is "") for native
recipes.

The xorg changes are all removals of x11 requirements (that were not
real) from recipes that have native versions.

I added a configuration default in bitbake.conf, let me know if this
is not a good place.

This seems to work fine (tested multiple different images) but I am
not really sure how to test it further... Suggestions are welcome, as
are results from autobuilder. 


Thanks,
  Jussi



The following changes since commit 633ad6c9f436f5d2b6ee1a005b697661a054a394:

  oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir 
(2017-04-06 10:13:39 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib jku/native-distro-features
  
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/native-distro-features

Jussi Kukkonen (4):
  mkfontdir: Remove x11 requirement
  mkfontscale: Remove x11 requirement
  xorg-font-common.inc: Remove x11 requirement
  native.bbclass: Use fixed DISTRO_FEATURES

 meta/classes/native.bbclass  | 12 
 meta/conf/bitbake.conf   |  2 ++
 meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb|  4 
 meta/recipes-graphics/xorg-app/mkfontscale_1.1.2.bb  |  3 +++
 meta/recipes-graphics/xorg-font/xorg-font-common.inc |  3 ---
 5 files changed, 17 insertions(+), 7 deletions(-)

-- 
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] native.bbclass: Use fixed DISTRO_FEATURES

2017-04-06 Thread Jussi Kukkonen
There seems to be no advantage to letting distro features affect
native builds. There is a significant disadvantage: a change to
DISTRO_FEATURES will trigger a lot of unnecessary native tasks. In a
test like this:
  $ bitbake core-image-minimal
  # append " systemd" to DISTRO_FEATURES
  $ bitbake core-image-minimal
The latter build takes 44 minutes (28%) of cpu-time less with this
patch (skipping 135 native tasks). Sadly wall clock time was not
affected as glibc remains the bottleneck.

Set DISTRO_FEATURES to a fixed value for native recipes to avoid the
unnecessary tasks: currently the default value is empty.

Do the variable setting in native_virtclass_handler() because otherwise
it could still be overridden by appends and the feature backfilling.
Shuffle the early returns so DISTRO_FEATURES gets set as long as
the packagename ends with "-native".

Signed-off-by: Jussi Kukkonen 
---
 meta/classes/native.bbclass | 12 
 meta/conf/bitbake.conf  |  2 ++
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/meta/classes/native.bbclass b/meta/classes/native.bbclass
index 1919fbc..fbca4c6 100644
--- a/meta/classes/native.bbclass
+++ b/meta/classes/native.bbclass
@@ -121,14 +121,18 @@ PATH_prepend = "${COREBASE}/scripts/native-intercept:"
 SSTATE_SCAN_CMD ?= "${SSTATE_SCAN_CMD_NATIVE}"
 
 python native_virtclass_handler () {
-classextend = e.data.getVar('BBCLASSEXTEND') or ""
-if "native" not in classextend:
-return
-
 pn = e.data.getVar("PN")
 if not pn.endswith("-native"):
 return
 
+# Set features here to prevent appends and distro features backfill
+# from modifying native distro features
+d.setVar("DISTRO_FEATURES", "${NATIVE_DISTRO_FEATURES}")
+
+classextend = e.data.getVar('BBCLASSEXTEND') or ""
+if "native" not in classextend:
+return
+
 def map_dependencies(varname, d, suffix = ""):
 if suffix:
 varname = varname + "_" + suffix
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 5e98d45..78a3470 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -789,6 +789,8 @@ MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS ?= ""
 EXTRA_IMAGE_FEATURES ??= ""
 IMAGE_FEATURES += "${EXTRA_IMAGE_FEATURES}"
 
+NATIVE_DISTRO_FEATURES ?= ""
+
 DISTRO_FEATURES_BACKFILL = "pulseaudio sysvinit bluez5 
gobject-introspection-data ldconfig"
 MACHINE_FEATURES_BACKFILL = "rtc qemu-usermode"
 
-- 
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] xorg-font-common.inc: Remove x11 requirement

2017-04-06 Thread Jussi Kukkonen
Remove the fake news about mkfontscale-native needing x11.

Signed-off-by: Jussi Kukkonen 
---
 meta/recipes-graphics/xorg-font/xorg-font-common.inc | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/meta/recipes-graphics/xorg-font/xorg-font-common.inc 
b/meta/recipes-graphics/xorg-font/xorg-font-common.inc
index cdbebcf..82a8487 100644
--- a/meta/recipes-graphics/xorg-font/xorg-font-common.inc
+++ b/meta/recipes-graphics/xorg-font/xorg-font-common.inc
@@ -16,9 +16,6 @@ S = "${WORKDIR}/${XORG_PN}-${PV}"
 
 inherit autotools pkgconfig distro_features_check
 
-# The mkfontscale-native requires x11 in DISTRO_FEATURES
-REQUIRED_DISTRO_FEATURES = "x11"
-
 EXTRA_OEMAKE += "FCCACHE=/bin/true 
UTIL_DIR=${STAGING_DIR_TARGET}\$\(MAPFILES_PATH\)"
 
 do_install_append() {
-- 
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] mkfontdir: Remove x11 requirement

2017-04-06 Thread Jussi Kukkonen
Build does not need libx11, so also does not need the distro feature.

Signed-off-by: Jussi Kukkonen 
---
 meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb 
b/meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb
index a453e24..371d9a1 100644
--- a/meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb
+++ b/meta/recipes-graphics/xorg-app/mkfontdir_1.0.7.bb
@@ -11,6 +11,10 @@ files."
 PE = "1"
 PR = "${INC_PR}.0"
 
+# We don't actually need x11 as xorg-app-common claims
+DEPENDS = "util-macros-native"
+REQUIRED_DISTRO_FEATURES = ""
+
 RDEPENDS_${PN} += "mkfontscale"
 RDEPENDS_${PN}_class-native += "mkfontscale-native"
 
-- 
2.1.4

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


Re: [OE-core] [PATCH] selftest/recipetool: skip create_git in case x11 feature is not present

2017-04-06 Thread Jussi Kukkonen
On 6 April 2017 at 19:41, 
wrote:

> From: Leonardo Sandoval 
>
> The unit test requires x11 as distro feature, otherwise it will fail
> while building the test requirements.
>

How about changing the test recipe to something non-x11 instead?


>
> [YOCTO #10903]
>
> Signed-off-by: Leonardo Sandoval  linux.intel.com>
> ---
>  meta/lib/oeqa/selftest/recipetool.py | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/lib/oeqa/selftest/recipetool.py
> b/meta/lib/oeqa/selftest/recipetool.py
> index d47b9dd..7bfb02f 100644
> --- a/meta/lib/oeqa/selftest/recipetool.py
> +++ b/meta/lib/oeqa/selftest/recipetool.py
> @@ -382,6 +382,8 @@ class RecipetoolTests(RecipetoolBase):
>
>  @testcase(1194)
>  def test_recipetool_create_git(self):
> +if 'x11' not in get_bb_var('DISTRO_FEATURES'):
> +self.skipTest('Test requires x11 as distro feature')
>  # Ensure we have the right data in shlibs/pkgdata
>  bitbake('libpng pango libx11 libxext jpeg libcheck')
>  # Try adding a recipe
> --
> 2.10.2
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] musl: Upgrade to latest tip

2017-04-06 Thread Khem Raj
* 54807d47 aarch64: add single instruction math functions
* b6e1fe0d fix strptime output for %C without %y
* 834ef7af fix processing of strptime %p format
* 85dfab7e fix off-by-one in strptime %j
* 9571c531 regex: fix newline matching with negated brackets
* e6917ece increase limit on locale name length from 15 to 23 bytes
* e4fc9ad7 search locale name variants for gettext translations
* 16319a5d make setlocale return a single name for LC_ALL if all categories 
match
* 0c53178e fix dlopen/dlsym regression opening libs already loaded at startup
* dbff2bb8 fix POSIX-format TZ dst transition times for southern hemisphere
* 74bca42e s390x: fix fpreg_t and remove unused per_struct
* a393d5cc precalculate gnu hash rather than doing it lazily in find_sym inner 
loop
* 8cba1dc4 fix threshold constants in j0f, y0f, j1f, y1f

Signed-off-by: Khem Raj 
---
 meta/recipes-core/musl/musl_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/musl/musl_git.bb 
b/meta/recipes-core/musl/musl_git.bb
index 39745f5bfbc..a88bc4d424e 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -3,7 +3,7 @@
 
 require musl.inc
 
-SRCREV = "cb525397bb053ea49cf160965477a17b17286eb3"
+SRCREV = "54807d47acecab778498ced88ce8f62bfa16e379"
 
 PV = "1.1.16+git${SRCPV}"
 
-- 
2.12.2

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


[OE-core] [PATCH 6/6] classes/buildhistory: save output file signatures for sstate tasks

2017-04-06 Thread Paul Eggleton
Save a file per task listing sha256sums for each file staged, i.e.
the output of the task. Some caveats:

1) This only covers sstate tasks since it uses SSTATEPOSTUNPACKFUNCS,
   however those are generally the most interesting in terms of output
   anyway.
2) The signature is taken before applying any relocations, so any
   relocated files will actually have different signatures, but that's
   churn that you probably won't want to see here.
3) At the moment if you run the same build twice without sstate you will
   very likely see changes in the output for certain tasks due to things
   like timestamps being present in the binary output. Fixing that is
   a general Linux ecosystem problem - see this page for our efforts to
   resolve it on our side:
 https://wiki.yoctoproject.org/wiki/Reproducible_Builds

NOTE: you need to set your BUILDHISTORY_FEATURES value to include
"task" to enable collection of these signatures as it is is disabled by
default.

Signed-off-by: Paul Eggleton 
---
 meta/classes/buildhistory.bbclass | 28 
 1 file changed, 28 insertions(+)

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index 0cafad5..748091d 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -47,6 +47,11 @@ sstate_install[vardepsexclude] += 
"buildhistory_emit_pkghistory"
 # then the value added to SSTATEPOSTINSTFUNCS:
 SSTATEPOSTINSTFUNCS[vardepvalueexclude] .= "| buildhistory_emit_pkghistory"
 
+# Similarly for our function that gets the output signatures
+SSTATEPOSTUNPACKFUNCS_append = " buildhistory_emit_outputsigs"
+sstate_installpkgdir[vardepsexclude] += "buildhistory_emit_outputsigs"
+SSTATEPOSTUNPACKFUNCS[vardepvalueexclude] .= "| buildhistory_emit_outputsigs"
+
 # All items excepts those listed here will be removed from a recipe's
 # build history directory by buildhistory_emit_pkghistory(). This is
 # necessary because some of these items (package directories, files that
@@ -292,6 +297,29 @@ python buildhistory_emit_pkghistory() {
 bb.build.exec_func("buildhistory_list_pkg_files", d)
 }
 
+python buildhistory_emit_outputsigs() {
+if not "task" in (d.getVar('BUILDHISTORY_FEATURES') or "").split():
+return
+
+taskoutdir = os.path.join(d.getVar('BUILDHISTORY_DIR'), 'task', 'output')
+bb.utils.mkdirhier(taskoutdir)
+currenttask = d.getVar('BB_CURRENTTASK')
+pn = d.getVar('PN')
+taskfile = os.path.join(taskoutdir, '%s.%s' % (pn, currenttask))
+
+cwd = os.getcwd()
+filesigs = {}
+for root, _, files in os.walk(cwd):
+for fname in files:
+if fname == 'fixmepath':
+continue
+fullpath = os.path.join(root, fname)
+filesigs[os.path.relpath(fullpath, cwd)] = 
bb.utils.sha256_file(fullpath)
+with open(taskfile, 'w') as f:
+for fpath, fsig in sorted(filesigs.items(), key=lambda item: item[0]):
+f.write('%s %s\n' % (fpath, fsig))
+}
+
 
 def write_recipehistory(rcpinfo, d):
 bb.debug(2, "Writing recipe history")
-- 
2.9.3

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


[OE-core] [PATCH 5/6] classes/uninative: set SSTATEPOSTUNPACKFUNCS[vardepvalueexclude] properly

2017-04-06 Thread Paul Eggleton
Append to the value with appendVarFlag() instead of setting it outright,
so that we can also append to it in other places. Accordingly, this
varflag is pipe-separated (since we want to be able to exclude any
string fragment, in this case including the leading space), thus put a
leading pipe character to play nicely with any existing value.

Signed-off-by: Paul Eggleton 
---
 meta/classes/uninative.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/uninative.bbclass b/meta/classes/uninative.bbclass
index b578031..8f34483 100644
--- a/meta/classes/uninative.bbclass
+++ b/meta/classes/uninative.bbclass
@@ -100,7 +100,7 @@ def enable_uninative(d):
 bb.debug(2, "Enabling uninative")
 d.setVar("NATIVELSBSTRING", "universal%s" % 
oe.utils.host_gcc_version(d))
 d.appendVar("SSTATEPOSTUNPACKFUNCS", " uninative_changeinterp")
-d.setVarFlag("SSTATEPOSTUNPACKFUNCS", "vardepvalueexclude", " 
uninative_changeinterp")
+d.appendVarFlag("SSTATEPOSTUNPACKFUNCS", "vardepvalueexclude", "| 
uninative_changeinterp")
 d.prependVar("PATH", 
"${STAGING_DIR}-uninative/${BUILD_ARCH}-linux${bindir_native}:")
 
 python uninative_changeinterp () {
-- 
2.9.3

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


[OE-core] [PATCH 4/6] buildhistory-diff: add option to compare actual signature differences

2017-04-06 Thread Paul Eggleton
Use the code underpinning bitbake-diffsigs to add an option to
buildhistory-diff to determine and display the differences between the
actual signature inputs, with a twist - we collapse identical
changes across different tasks, showing only the most recent task to
have that difference, meaning that there's less noise to wade through
when you just want to know what changed in order to cause some
rebuilding you're seeing.

Signed-off-by: Paul Eggleton 
---
 meta/lib/oe/buildhistory_analysis.py | 92 +---
 scripts/buildhistory-diff|  7 ++-
 2 files changed, 81 insertions(+), 18 deletions(-)

diff --git a/meta/lib/oe/buildhistory_analysis.py 
b/meta/lib/oe/buildhistory_analysis.py
index 449446f..3a5b7b6 100644
--- a/meta/lib/oe/buildhistory_analysis.py
+++ b/meta/lib/oe/buildhistory_analysis.py
@@ -13,7 +13,10 @@ import os.path
 import difflib
 import git
 import re
+import hashlib
+import collections
 import bb.utils
+import bb.tinfoil
 
 
 # How to display fields
@@ -410,7 +413,7 @@ def compare_dict_blobs(path, ablob, bblob, report_all, 
report_ver):
 return changes
 
 
-def compare_siglists(a_blob, b_blob):
+def compare_siglists(a_blob, b_blob, taskdiff=False):
 # FIXME collapse down a recipe's tasks?
 alines = a_blob.data_stream.read().decode('utf-8').splitlines()
 blines = b_blob.data_stream.read().decode('utf-8').splitlines()
@@ -429,26 +432,83 @@ def compare_siglists(a_blob, b_blob):
 adict = readsigs(alines)
 bdict = readsigs(blines)
 out = []
+
 changecount = 0
 addcount = 0
 removecount = 0
-for key in keys:
-siga = adict.get(key, None)
-sigb = bdict.get(key, None)
-if siga is not None and sigb is not None and siga != sigb:
-out.append('%s changed from %s to %s' % (key, siga, sigb))
-changecount += 1
-elif siga is None:
-out.append('%s was added' % key)
-addcount += 1
-elif sigb is None:
-removecount += 1
-out.append('%s was removed' % key)
+if taskdiff:
+with bb.tinfoil.Tinfoil() as tinfoil:
+tinfoil.prepare(config_only=True)
+
+changes = collections.OrderedDict()
+
+def compare_hashfiles(pn, taskname, hash1, hash2):
+hashes = [hash1, hash2]
+hashfiles = bb.siggen.find_siginfo(pn, taskname, hashes, 
tinfoil.config_data)
+
+if not taskname:
+(pn, taskname) = pn.rsplit('.', 1)
+pn = pnmap.get(pn, pn)
+desc = '%s.%s' % (pn, taskname)
+
+if len(hashfiles) == 0:
+out.append("Unable to find matching sigdata for %s with 
hashes %s or %s" % (desc, hash1, hash2))
+elif not hash1 in hashfiles:
+out.append("Unable to find matching sigdata for %s with 
hash %s" % (desc, hash1))
+elif not hash2 in hashfiles:
+out.append("Unable to find matching sigdata for %s with 
hash %s" % (desc, hash2))
+else:
+out2 = bb.siggen.compare_sigfiles(hashfiles[hash1], 
hashfiles[hash2], recursecb, collapsed=True)
+for line in out2:
+m = hashlib.sha256()
+m.update(line.encode('utf-8'))
+entry = changes.get(m.hexdigest(), (line, []))
+if desc not in entry[1]:
+changes[m.hexdigest()] = (line, entry[1] + [desc])
+
+# Define recursion callback
+def recursecb(key, hash1, hash2):
+compare_hashfiles(key, None, hash1, hash2)
+return []
+
+for key in keys:
+siga = adict.get(key, None)
+sigb = bdict.get(key, None)
+if siga is not None and sigb is not None and siga != sigb:
+changecount += 1
+(pn, taskname) = key.rsplit('.', 1)
+compare_hashfiles(pn, taskname, siga, sigb)
+elif siga is None:
+addcount += 1
+elif sigb is None:
+removecount += 1
+for key, item in changes.items():
+line, tasks = item
+if len(tasks) == 1:
+desc = tasks[0]
+elif len(tasks) == 2:
+desc = '%s and %s' % (tasks[0], tasks[1])
+else:
+desc = '%s and %d others' % (tasks[-1], len(tasks)-1)
+out.append('%s: %s' % (desc, line))
+else:
+for key in keys:
+siga = adict.get(key, None)
+sigb = bdict.get(key, None)
+if siga is not None and sigb is not None and siga != sigb:
+out.append('%s changed from %s to %s' % (key, siga, sigb))
+changecount += 1
+elif siga is None:
+out.append('%s was 

[OE-core] [PATCH 3/6] buildhistory-diff: add option to compare task signature list

2017-04-06 Thread Paul Eggleton
Having added writing out of the task signature list to buildhistory
(when BUILDHISTORY_FEATURES includes "task"), we now need a way to
compare the list. This just shows which tasks have been added / changed
signature / removed.

Signed-off-by: Paul Eggleton 
---
 meta/lib/oe/buildhistory_analysis.py | 49 ++--
 meta/lib/oe/sstatesig.py |  6 ++---
 scripts/buildhistory-diff|  5 +++-
 3 files changed, 54 insertions(+), 6 deletions(-)

diff --git a/meta/lib/oe/buildhistory_analysis.py 
b/meta/lib/oe/buildhistory_analysis.py
index 19b3bc4..449446f 100644
--- a/meta/lib/oe/buildhistory_analysis.py
+++ b/meta/lib/oe/buildhistory_analysis.py
@@ -1,6 +1,6 @@
 # Report significant differences in the buildhistory repository since a 
specific revision
 #
-# Copyright (C) 2012 Intel Corporation
+# Copyright (C) 2012-2013, 2016-2017 Intel Corporation
 # Author: Paul Eggleton 
 #
 # Note: requires GitPython 0.3.1+
@@ -410,13 +410,58 @@ def compare_dict_blobs(path, ablob, bblob, report_all, 
report_ver):
 return changes
 
 
-def process_changes(repopath, revision1, revision2='HEAD', report_all=False, 
report_ver=False):
+def compare_siglists(a_blob, b_blob):
+# FIXME collapse down a recipe's tasks?
+alines = a_blob.data_stream.read().decode('utf-8').splitlines()
+blines = b_blob.data_stream.read().decode('utf-8').splitlines()
+keys = []
+pnmap = {}
+def readsigs(lines):
+sigs = {}
+for line in lines:
+linesplit = line.split()
+if len(linesplit) > 2:
+sigs[linesplit[0]] = linesplit[2]
+if not linesplit[0] in keys:
+keys.append(linesplit[0])
+pnmap[linesplit[1]] = linesplit[0].rsplit('.', 1)[0]
+return sigs
+adict = readsigs(alines)
+bdict = readsigs(blines)
+out = []
+changecount = 0
+addcount = 0
+removecount = 0
+for key in keys:
+siga = adict.get(key, None)
+sigb = bdict.get(key, None)
+if siga is not None and sigb is not None and siga != sigb:
+out.append('%s changed from %s to %s' % (key, siga, sigb))
+changecount += 1
+elif siga is None:
+out.append('%s was added' % key)
+addcount += 1
+elif sigb is None:
+removecount += 1
+out.append('%s was removed' % key)
+out.append('Summary: %d tasks added, %d tasks removed, %d tasks modified 
(%.1f%%)' % (addcount, removecount, changecount, (changecount / 
float(len(bdict)) * 100)))
+return '\n'.join(out)
+
+
+def process_changes(repopath, revision1, revision2='HEAD', report_all=False, 
report_ver=False, sigs=False):
 repo = git.Repo(repopath)
 assert repo.bare == False
 commit = repo.commit(revision1)
 diff = commit.diff(revision2)
 
 changes = []
+
+if sigs:
+for d in diff.iter_change_type('M'):
+if d.a_blob.path == 'siglist.txt':
+changes.append(compare_siglists(d.a_blob, d.b_blob))
+return changes
+
 for d in diff.iter_change_type('M'):
 path = os.path.dirname(d.a_blob.path)
 if path.startswith('packages/'):
diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index 56b33ba..d5377db 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -217,9 +217,9 @@ class 
SignatureGeneratorOEBasicHash(bb.siggen.SignatureGeneratorBasicHash):
 for taskitem in self.taskhash:
 (fn, task) = taskitem.rsplit(".", 1)
 pn = self.lockedpnmap[fn]
-tasks.append((pn, task, self.taskhash[taskitem]))
-for (pn, task, taskhash) in sorted(tasks):
-f.write('%s.%s %s\n' % (pn, task, taskhash))
+tasks.append((pn, task, fn, self.taskhash[taskitem]))
+for (pn, task, fn, taskhash) in sorted(tasks):
+f.write('%s.%s %s %s\n' % (pn, task, fn, taskhash))
 
 def checkhashes(self, missed, ret, sq_fn, sq_task, sq_hash, sq_hashfn, d):
 warn_msgs = []
diff --git a/scripts/buildhistory-diff b/scripts/buildhistory-diff
index e03ccc5..e8e3e11 100755
--- a/scripts/buildhistory-diff
+++ b/scripts/buildhistory-diff
@@ -33,6 +33,9 @@ def main():
 parser.add_option("-a", "--report-all",
 help = "Report all changes, not just the default significant ones",
 action="store_true", dest="report_all", default=False)
+parser.add_option("-s", "--signatures",
+help = "Report on signature differences instead of output",
+action="store_true", dest="sigs", default=False)
 
 options, args = parser.parse_args(sys.argv)
 
@@ -86,7 +89,7 @@ def main():
 
 import gitdb
 try:
-changes = 
oe.buildhistory_analysis.process_changes(options.buildhistory_dir, fromrev, 
torev, options.report_all, options.report_ver)
+changes = 
oe.buildhistory_analysis.process_changes(opt

[OE-core] [PATCH 0/6] Add optional task signatures to buildhistory

2017-04-06 Thread Paul Eggleton
If you're looking to compare task signatures between builds, that can
actually be a bit difficult to do if you don't have anything printed
out (e.g. from an error) with some signatures to look for. buildhistory
already makes a commit (or several commits) for each build, so we can
actually write the signatures into buildhistory so that we can compare
them later. If available (via the tasks actually having run, or by
explicitly creating them), we can even use the siginfo/sigdata files
to dig down and find out exactly what caused the signature changes.

Finally, add sha256sums for each file staged by every shared state task
so that we can see when a task re-executes if the file contents has
changed.

(All of this functionality defaults to off, you need to add "task" to
BUILDHISTORY_FEATURES in order to enable it).

There's also a small fix making it a bit easier to run the
buildhistory-diff script from the buildhistory repository.

NOTE: this patch series requires some of the patches in the set recently
sent to the bitbake-devel list.


The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:

  oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir 
(2017-04-06 10:13:34 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-sigs
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/buildhistory-sigs

Paul Eggleton (6):
  buildhistory-diff: operate from buildhistory directory
  classes/buildhistory: write out task signatures on every build
  buildhistory-diff: add option to compare task signature list
  buildhistory-diff: add option to compare actual signature differences
  classes/uninative: set SSTATEPOSTUNPACKFUNCS[vardepvalueexclude] properly
  classes/buildhistory: save output file signatures for sstate tasks

 meta/classes/buildhistory.bbclass|  40 +
 meta/classes/uninative.bbclass   |   2 +-
 meta/lib/oe/buildhistory_analysis.py | 109 ++-
 meta/lib/oe/sstatesig.py |  10 
 scripts/buildhistory-diff|  13 -
 5 files changed, 170 insertions(+), 4 deletions(-)

-- 
2.9.3

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


[OE-core] [PATCH 2/6] classes/buildhistory: write out task signatures on every build

2017-04-06 Thread Paul Eggleton
If we want to determine what changed since the last build, one angle
from which to look at it is to check the signatures. However, if we
don't actually have the signatures from the last build we don't have
anywhere to start. Save the signatures on each build in order to give us
the starting point.

NOTE: you need to set your BUILDHISTORY_FEATURES value to include
"task" to enable collection of these signatures as it is is disabled by
default.

Signed-off-by: Paul Eggleton 
---
 meta/classes/buildhistory.bbclass | 12 
 meta/lib/oe/sstatesig.py  | 10 ++
 2 files changed, 22 insertions(+)

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index 109b375..0cafad5 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -596,6 +596,17 @@ POPULATE_SDK_POST_HOST_COMMAND[vardepvalueexclude] .= "| 
buildhistory_list_insta
 SDK_POSTPROCESS_COMMAND_append = " buildhistory_get_sdkinfo ; 
buildhistory_get_extra_sdkinfo; "
 SDK_POSTPROCESS_COMMAND[vardepvalueexclude] .= "| buildhistory_get_sdkinfo ; 
buildhistory_get_extra_sdkinfo; "
 
+python buildhistory_write_sigs() {
+if not "task" in (d.getVar('BUILDHISTORY_FEATURES') or "").split():
+return
+
+# Create sigs file
+if hasattr(bb.parse.siggen, 'dump_siglist'):
+taskoutdir = os.path.join(d.getVar('BUILDHISTORY_DIR'), 'task')
+bb.utils.mkdirhier(taskoutdir)
+bb.parse.siggen.dump_siglist(os.path.join(taskoutdir, 'tasksigs.txt'))
+}
+
 def buildhistory_get_build_id(d):
 if d.getVar('BB_WORKERCONTEXT') != '1':
 return ""
@@ -761,6 +772,7 @@ python buildhistory_eventhandler() {
 shutil.rmtree(olddir)
 if e.data.getVar("BUILDHISTORY_COMMIT") == "1":
 bb.note("Writing buildhistory")
+bb.build.exec_func("buildhistory_write_sigs", d)
 localdata = bb.data.createCopy(e.data)
 localdata.setVar('BUILDHISTORY_BUILD_FAILURES', 
str(e._failures))
 interrupted = getattr(e, '_interrupted', 0)
diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index 13fd3bd..56b33ba 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -211,6 +211,16 @@ class 
SignatureGeneratorOEBasicHash(bb.siggen.SignatureGeneratorBasicHash):
 f.write('"\n')
 f.write('SIGGEN_LOCKEDSIGS_TYPES_%s = "%s"' % (self.machine, " 
".join(l)))
 
+def dump_siglist(self, sigfile):
+with open(sigfile, "w") as f:
+tasks = []
+for taskitem in self.taskhash:
+(fn, task) = taskitem.rsplit(".", 1)
+pn = self.lockedpnmap[fn]
+tasks.append((pn, task, self.taskhash[taskitem]))
+for (pn, task, taskhash) in sorted(tasks):
+f.write('%s.%s %s\n' % (pn, task, taskhash))
+
 def checkhashes(self, missed, ret, sq_fn, sq_task, sq_hash, sq_hashfn, d):
 warn_msgs = []
 error_msgs = []
-- 
2.9.3

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


[OE-core] [PATCH 1/6] buildhistory-diff: operate from buildhistory directory

2017-04-06 Thread Paul Eggleton
If the cwd is named "buildhistory" and the user hasn't specified an
alternative path on the command line, then assume that the current
directory is the buildhistory directory. This makes it easier to run
buildhistory-diff and also interact with the buildhistory git repository
as you no longer have to jump into the buildhistory directory and up to
the parent again when doing so.

Signed-off-by: Paul Eggleton 
---
 scripts/buildhistory-diff | 5 +
 1 file changed, 5 insertions(+)

diff --git a/scripts/buildhistory-diff b/scripts/buildhistory-diff
index d8ca12d..e03ccc5 100755
--- a/scripts/buildhistory-diff
+++ b/scripts/buildhistory-diff
@@ -46,6 +46,11 @@ def main():
 sys.exit(1)
 
 if not os.path.exists(options.buildhistory_dir):
+if options.buildhistory_dir == 'buildhistory/':
+cwd = os.getcwd()
+if os.path.basename(cwd) == 'buildhistory':
+options.buildhistory_dir = cwd
+if not os.path.exists(options.buildhistory_dir):
 sys.stderr.write('Buildhistory directory "%s" does not exist\n\n' % 
options.buildhistory_dir)
 parser.print_help()
 sys.exit(1)
-- 
2.9.3

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


Re: [OE-core] [PATCH 1/2] scripts: change way we find native tools (pseudo)

2017-04-06 Thread Robert Yang



On 04/07/2017 10:48 AM, Brian Avery wrote:

Hi Robert,

I was definitely looking at only the extract-rootfs issue and didn't remember
seeing your above patch.  I agree that we need a broader solution than the one I
did. I tried applying yours but had some issues. Your patch did fix the
runqemu-extract-rootfs, but not when I had INHERIT+= " rm_work ".  Also, I had
trouble running the oe-run-native script. It seems like the help is reversed
from what order it is expecting?  I may be missing something, it's getting late;
but I'll look at it tomoro and see if I can't expand on your patch for a more
generic solution. Issues from the run below.
ty,
b
an intel employee


$ bitbake bmap-tools-native -caddto_recipe_sysroot

$ oe-run-native bmap-tools-native bmaptool


That's odd, it is the right order as the help text shows, it works well for me.
Maybe he/you can try to add "set -x" in the recipe to see what happend.

$ bitbake bmap-tools-native -caddto_recipe_sysroot
$ oe-run-native bmap-tools-native bmaptool
Running bitbake -e bmap-tools-native
PSEUDO 
/buildarea/lyang1/test_q2/tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/bin/pseudo 
is not found.

usage: bmaptool [-h] [--version] [-q] [-d] {create,copy} ...
bmaptool: error: too few arguments

// Robert



Running bitbake -e bmaptool

ERROR: Nothing PROVIDES 'bmaptool'. Close matches:

  bmap-tools

  mtools

There was an error running bitbake to determine STAGING_DIR_NATIVE

Here is the output from bitbake -e bmaptool

WARNING: Host distribution "ubuntu-14.04" has not been validated with this
version of the build system; you may possibly experience unexpected failures. It
is recommended that you use a tested distribution. Loading cache...done. Loaded
1299 entries from dependency cache. Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

$ oe-run-native bmaptool bmap-tools-native

Running bitbake -e bmap-tools-native

PSEUDO
…/tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/bin/pseudo
is not found.

Error: Unable to find '' in
.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/bin:.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/bin:.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/sbin:.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/sbin

bavery@bavery-WS-DESK:...$ oe-run-native

oe-run-native: error: the following arguments are required: 


Usage: oe-run-native native-recipe tool [parameters]


OpenEmbedded run-native - runs native tools


arguments:

  native-recipe   The recipe which provoides tool

  toolNative tool to run




On Thu, Apr 6, 2017 at 3:26 AM, Robert Yang mailto:liezhi.y...@windriver.com>> wrote:

Hi Brian and RP,

This patch can't fix the problem of scripts/oe-run-native, it only can
run the native tools which is depended by meta-ide-support, for example:

$ bitbake bmap-tools-native meta-ide-support
$ oe-run-native bmaptool --help # exmaple from dev-manual-start.xml

Error: Unable to find 'bmaptool' in native sysroot

I think that we need consider the patch that I had sent before:

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


Robert Yang (1):
  oe-find-native-sysroot: work with RSS


Subject: [PATCH 1/1] oe-find-native-sysroot: work with RSS

The generic STAGING_DIR_NATIVE is gone since RSS, so when find
OECORE_NATIVE_SYSROOT, the user has to specify which recipe's
STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT.

* The usage is changed from ". oe-find-native-sysroot" to
  ". oe-find-native-sysroot ".
* The oe-run-native's usage has changed from
  "oe-run-native tool" to "oe-run-native native-recipe tool".

Signed-off-by: Robert Yang mailto:liezhi.y...@windriver.com>>
---
 scripts/oe-find-native-sysroot | 56 
--
 scripts/oe-run-native  | 15 +++
 scripts/runqemu-export-rootfs  |  2 +-
 scripts/runqemu-extract-sdk|  2 +-
 4 files changed, 49 insertions(+), 26 deletions(-)

diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot
index 3f4c29da8a..59fe3f3118 100755
--- a/scripts/oe-find-native-sysroot
+++ b/scripts/oe-find-native-sysroot
@@ -9,7 +9,7 @@
 # it, e.g:
 #
 # SYSROOT_SETUP_SCRIPT=`which oe-find-native-sysroot`
-# . $SYSROOT_SETUP_SCRIPT
+# . $SYSROOT_SETUP_SCRIPT 
 #
 # This script will terminate execution of your calling program unless
 # you set a variable $SKIP_STRICT_SYSROOT_CHECK to a non-empty string
@@ -30,8 +

Re: [OE-core] [PATCH 1/2] scripts: change way we find native tools (pseudo)

2017-04-06 Thread Brian Avery
Hi Robert,

I was definitely looking at only the extract-rootfs issue and didn't
remember seeing your above patch.  I agree that we need a broader solution
than the one I did. I tried applying yours but had some issues. Your patch
did fix the runqemu-extract-rootfs, but not when I had INHERIT+= " rm_work
".  Also, I had trouble running the oe-run-native script. It seems like the
help is reversed from what order it is expecting?  I may be missing
something, it's getting late; but I'll look at it tomoro and see if I can't
expand on your patch for a more generic solution. Issues from the run below.
ty,
b
an intel employee


$ bitbake bmap-tools-native -caddto_recipe_sysroot

$ oe-run-native bmap-tools-native bmaptool

Running bitbake -e bmaptool

ERROR: Nothing PROVIDES 'bmaptool'. Close matches:

  bmap-tools

  mtools

There was an error running bitbake to determine STAGING_DIR_NATIVE

Here is the output from bitbake -e bmaptool

WARNING: Host distribution "ubuntu-14.04" has not been validated with this
version of the build system; you may possibly experience unexpected
failures. It is recommended that you use a tested distribution. Loading
cache...done. Loaded 1299 entries from dependency cache. Summary: There was
1 WARNING message shown. Summary: There was 1 ERROR message shown,
returning a non-zero exit code.

$ oe-run-native bmaptool bmap-tools-native

Running bitbake -e bmap-tools-native

PSEUDO
…/tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/bin/pseudo
is not found.

Error: Unable to find '' in
.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/bin:.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/bin:.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/usr/sbin:.../tmp/work/x86_64-linux/bmap-tools-native/3.2-r0/recipe-sysroot-native/sbin

bavery@bavery-WS-DESK:...$ oe-run-native

oe-run-native: error: the following arguments are required: 


Usage: oe-run-native native-recipe tool [parameters]


OpenEmbedded run-native - runs native tools


arguments:

  native-recipe   The recipe which provoides tool

  toolNative tool to run




On Thu, Apr 6, 2017 at 3:26 AM, Robert Yang 
wrote:

> Hi Brian and RP,
>
> This patch can't fix the problem of scripts/oe-run-native, it only can
> run the native tools which is depended by meta-ide-support, for example:
>
> $ bitbake bmap-tools-native meta-ide-support
> $ oe-run-native bmaptool --help # exmaple from dev-manual-start.xml
>
> Error: Unable to find 'bmaptool' in native sysroot
>
> I think that we need consider the patch that I had sent before:
>
>   git://git.openembedded.org/openembedded-core-contrib rbt/rssfix
>   http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/rssfix
>
> Robert Yang (1):
>   oe-find-native-sysroot: work with RSS
>
>
> Subject: [PATCH 1/1] oe-find-native-sysroot: work with RSS
>
> The generic STAGING_DIR_NATIVE is gone since RSS, so when find
> OECORE_NATIVE_SYSROOT, the user has to specify which recipe's
> STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT.
>
> * The usage is changed from ". oe-find-native-sysroot" to
>   ". oe-find-native-sysroot ".
> * The oe-run-native's usage has changed from
>   "oe-run-native tool" to "oe-run-native native-recipe tool".
>
> Signed-off-by: Robert Yang 
> ---
>  scripts/oe-find-native-sysroot | 56 --
> 
>  scripts/oe-run-native  | 15 +++
>  scripts/runqemu-export-rootfs  |  2 +-
>  scripts/runqemu-extract-sdk|  2 +-
>  4 files changed, 49 insertions(+), 26 deletions(-)
>
> diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysro
> ot
> index 3f4c29da8a..59fe3f3118 100755
> --- a/scripts/oe-find-native-sysroot
> +++ b/scripts/oe-find-native-sysroot
> @@ -9,7 +9,7 @@
>  # it, e.g:
>  #
>  # SYSROOT_SETUP_SCRIPT=`which oe-find-native-sysroot`
> -# . $SYSROOT_SETUP_SCRIPT
> +# . $SYSROOT_SETUP_SCRIPT 
>  #
>  # This script will terminate execution of your calling program unless
>  # you set a variable $SKIP_STRICT_SYSROOT_CHECK to a non-empty string
> @@ -30,8 +30,8 @@
>  # with this program; if not, write to the Free Software Foundation, Inc.,
>  # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
>
> -if [ "$1" = '--help' -o "$1" = '-h' ] ; then
> -echo 'Usage: oe-find-native-sysroot [-h|--help]'
> +if [ "$1" = '--help' -o "$1" = '-h' -o $# -ne 1 ] ; then
> +echo 'Usage: oe-find-native-sysroot  [-h|--help]'
>  echo ''
>  echo 'OpenEmbedded find-native-sysroot - helper script to set'
>  echo 'environment variables OECORE_NATIVE_SYSROOT and PSEUDO'
> @@ -39,11 +39,31 @@ if [ "$1" = '--help' -o "$1" = '-h' ] ; then
>  echo 'executable binary'
>  echo ''
>  echo 'options:'
> +echo '  recipe  its STAGING_DIR_NATIVE is used as native
> sysroot'
>  echo '  -h, --help  show this help message and exit'
>  echo ''
>  exit 

[OE-core] [morty][PATCH 0/1] packagegroup-core-standalone-sdk-target: add libssp

2017-04-06 Thread Paul Eggleton
Backport this to morty since if you want runtime support for stack-smashing
protection when building with gcc you need this library.


The following changes since commit ddf907ca95a19f54785079b4396935273b3747f6:

  Revert "file: update SRCREV for 5.28 to fix fetch fail on missing commit" 
(2017-03-21 22:17:57 +)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/libssp-sdk-morty
  
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/libssp-sdk-morty

Paul Eggleton (1):
  packagegroup-core-standalone-sdk-target: add libssp

 .../packagegroups/packagegroup-core-standalone-sdk-target.bb | 5 +
 1 file changed, 5 insertions(+)

-- 
2.9.3

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


[OE-core] [morty][PATCH 1/1] packagegroup-core-standalone-sdk-target: add libssp

2017-04-06 Thread Paul Eggleton
If you want to be able to use -fstack-protector then you need the
runtime support - you can either write this yourself or use libssp
supplied with GCC. If you're using GCC then it seems likely that you'd
just be using libssp, so include in the SDK by default; however use
RRECOMMENDS just in case it's been disabled or you aren't using GCC.

(From OE-Core rev: 6c990655e35bb3a14d59555662ec5802c9980028)

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
---
 .../packagegroups/packagegroup-core-standalone-sdk-target.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git 
a/meta/recipes-core/packagegroups/packagegroup-core-standalone-sdk-target.bb 
b/meta/recipes-core/packagegroups/packagegroup-core-standalone-sdk-target.bb
index 274e11a..43fc599 100644
--- a/meta/recipes-core/packagegroups/packagegroup-core-standalone-sdk-target.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-core-standalone-sdk-target.bb
@@ -12,3 +12,8 @@ RDEPENDS_${PN} = "\
 libstdc++-dev \
 ${LIBC_DEPENDENCIES} \
 "
+
+RRECOMMENDS_${PN} = "\
+libssp \
+libssp-dev \
+"
-- 
2.9.3

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


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

2017-04-06 Thread Richard Purdie
On Wed, 2017-04-05 at 23:41 -0700, Robert Yang wrote:
> The following changes since commit
> 3a1cce659156ef2654a55a6e3c6922fa2dc780e4:
> 
>   glibc: fix nativesdk ldd RTLDLIST (2017-04-05 23:22:06 +0100)
> 
> are available in the git repository at:
> 
>   git://git.openembedded.org/openembedded-core-contrib rbt/qemu
>   http://cgit.openembedded.org/openembedded-core-contrib/log/?h=rbt/q
> emu
> 
> Robert Yang (6):
>   runqemu: fix 2 typos
>   runqemu: support env vars explicitly
>   runqemu: use self.rootfs to replace self.nfs_dir
>   runqemu: run without arguments
>   runqemu: use realpath for imgdir
>   runqemu: do not rely on grepping images

Something in here breaks the use of "bitbake xxx-image -c testimage":

https://autobuilder.yocto.io/builders/nightly-arm/builds/280

[basically all sanity tests failed in that build]

Cheers,

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


Re: [OE-core] [PATCH] ethtool: fix 4.8 checksums

2017-04-06 Thread Martin Jansa
See other ethtool change on ML from this week.

On Fri, Apr 7, 2017 at 12:58 AM, Jianxun Zhang <
jianxun.zh...@linux.intel.com> wrote:

> The mismatched checksums cause fatching failed in my setup.
>
> Signed-off-by: Jianxun Zhang 
> ---
> I am not sure why I got this issue today, but it seems the upstream
> package has different checksums.
>
> Maintainer could help to check if this is a false patch.
>
>  meta/recipes-extended/ethtool/ethtool_4.8.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-extended/ethtool/ethtool_4.8.bb
> b/meta/recipes-extended/ethtool/ethtool_4.8.bb
> index afaf2e2..ce3eaf3 100644
> --- a/meta/recipes-extended/ethtool/ethtool_4.8.bb
> +++ b/meta/recipes-extended/ethtool/ethtool_4.8.bb
> @@ -11,8 +11,8 @@ SRC_URI = "https://downloads.yoctoproject.org/mirror/
> sources/ethtool-${PV}.tar.g
> file://avoid_parallel_tests.patch \
> "
>
> -SRC_URI[md5sum] = "28c4a4d85c33f573c49ff6d81ec094fd"
> -SRC_URI[sha256sum] = "1bd82ebe3d41de1b7b0d8f4fb18a8e
> 8466fba934c952bc5c5002836ffa8bb606"
> +SRC_URI[md5sum] = "992eab97607c64b7848edfd37f23da22"
> +SRC_URI[sha256sum] = "c8ea20b8d85898377ec130066008f9
> 241ebcdd95ac85dbcc2d50b32fe2e2f934"
>
>  inherit autotools ptest
>  RDEPENDS_${PN}-ptest += "make"
> --
> 2.7.4
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] ethtool: fix 4.8 checksums

2017-04-06 Thread Jianxun Zhang
The mismatched checksums cause fatching failed in my setup.

Signed-off-by: Jianxun Zhang 
---
I am not sure why I got this issue today, but it seems the upstream package has 
different checksums.

Maintainer could help to check if this is a false patch.

 meta/recipes-extended/ethtool/ethtool_4.8.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/ethtool/ethtool_4.8.bb 
b/meta/recipes-extended/ethtool/ethtool_4.8.bb
index afaf2e2..ce3eaf3 100644
--- a/meta/recipes-extended/ethtool/ethtool_4.8.bb
+++ b/meta/recipes-extended/ethtool/ethtool_4.8.bb
@@ -11,8 +11,8 @@ SRC_URI = 
"https://downloads.yoctoproject.org/mirror/sources/ethtool-${PV}.tar.g
file://avoid_parallel_tests.patch \
"
 
-SRC_URI[md5sum] = "28c4a4d85c33f573c49ff6d81ec094fd"
-SRC_URI[sha256sum] = 
"1bd82ebe3d41de1b7b0d8f4fb18a8e8466fba934c952bc5c5002836ffa8bb606"
+SRC_URI[md5sum] = "992eab97607c64b7848edfd37f23da22"
+SRC_URI[sha256sum] = 
"c8ea20b8d85898377ec130066008f9241ebcdd95ac85dbcc2d50b32fe2e2f934"
 
 inherit autotools ptest
 RDEPENDS_${PN}-ptest += "make"
-- 
2.7.4

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


[OE-core] [PATCH] mtd-utils: refresh patches now merged upstream

2017-04-06 Thread Andre McCurdy
Update Upstream-Status tags and apply 010-fix-rpmatch.patch
unconditionally, since it's merged unconditionally upstream.

Signed-off-by: Andre McCurdy 
---
 .../mtd/mtd-utils/0001-Fix-build-with-musl.patch   | 15 
 .../mtd/mtd-utils/010-fix-rpmatch.patch| 45 --
 .../mtd/mtd-utils/fix-armv7-neon-alignment.patch   | 21 +++---
 meta/recipes-devtools/mtd/mtd-utils_git.bb |  3 +-
 4 files changed, 66 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-devtools/mtd/mtd-utils/0001-Fix-build-with-musl.patch 
b/meta/recipes-devtools/mtd/mtd-utils/0001-Fix-build-with-musl.patch
index 6a9bd1c..bf3f98f 100644
--- a/meta/recipes-devtools/mtd/mtd-utils/0001-Fix-build-with-musl.patch
+++ b/meta/recipes-devtools/mtd/mtd-utils/0001-Fix-build-with-musl.patch
@@ -1,19 +1,18 @@
-From e16fa28bc57c29923ab60af2ac343da83e1992d8 Mon Sep 17 00:00:00 2001
+From 4dab9bed1033f797ef9b482c77342fe3fe26d0be Mon Sep 17 00:00:00 2001
 From: Khem Raj 
 Date: Tue, 6 Oct 2015 23:51:34 +
 Subject: [PATCH] Fix build with musl
 
-Upstream-Status: Pending
+Upstream-Status: Backport
 
 Signed-off-by: Khem Raj 
+Signed-off-by: David Oberhollenzer 
 ---
- mkfs.jffs2.c  | 44 ++--
- recv_image.c  |  1 -
- serve_image.c |  1 -
- 3 files changed, 42 insertions(+), 4 deletions(-)
+ jffsX-utils/mkfs.jffs2.c | 1 +
+ 1 file changed, 1 insertion(+)
 
-diff --git a/mkfs.jffs2.c b/mkfs.jffs2.c
-index f09c0b2..ed2dc43 100644
+diff --git a/jffsX-utils/mkfs.jffs2.c b/jffsX-utils/mkfs.jffs2.c
+index 5446a16..ca5e0d5 100644
 --- a/jffsX-utils/mkfs.jffs2.c
 +++ b/jffsX-utils/mkfs.jffs2.c
 @@ -72,6 +72,7 @@
diff --git a/meta/recipes-devtools/mtd/mtd-utils/010-fix-rpmatch.patch 
b/meta/recipes-devtools/mtd/mtd-utils/010-fix-rpmatch.patch
index 7d783e7..853de6a 100644
--- a/meta/recipes-devtools/mtd/mtd-utils/010-fix-rpmatch.patch
+++ b/meta/recipes-devtools/mtd/mtd-utils/010-fix-rpmatch.patch
@@ -1,11 +1,48 @@
-Replace rpmatch() usage with checking first character of line
+From 82839c3c0371ca2a1643a99d7d01f5bc1c850b28 Mon Sep 17 00:00:00 2001
+From: David Oberhollenzer 
+Date: Thu, 2 Mar 2017 11:40:36 +0100
+Subject: [PATCH] Replace rpmatch() usage with checking first character of line
+
+This is based on the patch from Khem Raj used by openembedded. In
+addition to the original patch, this also removes the fallback
+implementation that was provided for C libraries that don't implement
+rpmatch.
+
+Upstream-Status: Backport
 
-Upstream-Status: Pending
 Signed-off-by: Khem Raj 
+Signed-off-by: David Oberhollenzer 
+---
+ include/common.h | 25 ++---
+ 1 file changed, 6 insertions(+), 19 deletions(-)
 
+diff --git a/include/common.h b/include/common.h
+index d0c706d..d609257 100644
 --- a/include/common.h
 +++ b/include/common.h
-@@ -122,10 +122,12 @@
+@@ -129,21 +129,6 @@ extern "C" {
+   fprintf(stderr, "%s: warning!: " fmt "\n", PROGRAM_NAME, 
##__VA_ARGS__); \
+ } while(0)
+ 
+-/* uClibc versions before 0.9.34 and musl don't have rpmatch() */
+-#if defined(__UCLIBC__) && \
+-  (__UCLIBC_MAJOR__ == 0 && \
+-  (__UCLIBC_MINOR__ < 9 || \
+-  (__UCLIBC_MINOR__ == 9 && __UCLIBC_SUBLEVEL__ < 34))) || \
+-  !defined(__GLIBC__)
+-#undef rpmatch
+-#define rpmatch __rpmatch
+-static inline int __rpmatch(const char *resp)
+-{
+-return (resp[0] == 'y' || resp[0] == 'Y') ? 1 :
+-  (resp[0] == 'n' || resp[0] == 'N') ? 0 : -1;
+-}
+-#endif
+-
+ /**
+  * prompt the user for confirmation
+  */
+@@ -164,10 +149,12 @@ static inline bool prompt(const char *msg, bool def)
}
  
if (strcmp("\n", line) != 0) {
@@ -22,3 +59,5 @@ Signed-off-by: Khem Raj 
puts("unknown response; please try again");
continue;
}
+-- 
+2.6.1
diff --git a/meta/recipes-devtools/mtd/mtd-utils/fix-armv7-neon-alignment.patch 
b/meta/recipes-devtools/mtd/mtd-utils/fix-armv7-neon-alignment.patch
index a279d84..6fc594f 100644
--- a/meta/recipes-devtools/mtd/mtd-utils/fix-armv7-neon-alignment.patch
+++ b/meta/recipes-devtools/mtd/mtd-utils/fix-armv7-neon-alignment.patch
@@ -1,16 +1,25 @@
-Upstream-Status: Pending
+From 7d026a85946a08b8167dcd792ea6660bf6a49e08 Mon Sep 17 00:00:00 2001
+From: Yuanjie Huang 
+Date: Thu, 2 Mar 2017 10:43:56 +0100
+Subject: [PATCH] Fix alignment trap triggered by NEON instructions
 
 NEON instruction VLD1.64 was used to copy 64 bits data after type
 casting, and they will trigger alignment trap.
 This patch uses memcpy to avoid alignment problem.
 
+Upstream-Status: Backport
+
 Signed-off-by: Yuanjie Huang 
+Signed-off-by: David Oberhollenzer 
+---
+ ubifs-utils/mkfs.ubifs/key.h | 16 ++--
+ 1 file changed, 10 insertions(+), 6 deletions(-)
 
-diff --git a/mkfs.ubifs/key.h b/mkfs.ubifs/key.h
-index d3a02d4..e7e9218 100644
+diff --git a/ubifs-utils/mkfs.ubifs/key.h b/ubifs-utils/mkfs.ubifs/key.h
+

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

2017-04-06 Thread Andrea Galbusera
Hi,

On Thu, Apr 6, 2017 at 10:11 PM, Ravi chandra reddy 
wrote:

> Hi,
> I am trying to generate LibIIO [open source by Analog Devices],
> however there is dependancy on Libxml2.
>

For libiio there is a recipe in meta-openembedded [1]. Are you using that
one?

[1] http://layers.openembedded.org/layerindex/recipe/57509/


> problem with Libxml2, it is dependant on *python*-lib, libdl, libz,
> libzma, libm
>
> for some reason with Yocto built Libxml2.so, i am encountering "undefined
> references error", which i am unable to solve [inspite of linking possible
> dependant libraries],
>
> if i get could the Libxml2.a, it packages all "REQUIRED ELEMENTS", so i
> assume, there WONT be any error in linking Libxml2 in Libiio.
>
> ==in short=
> Libiio ---linking---> Libxml2*.so* [yocto based] ---errors-> undefined
> referneces to .
>
> ==in short=
> Libiio ---linking---> Libxml2.a [yocto based] --> SHOULD solve and install
> libiio
>
> for me to generate Libxml2.a, i need to make/ask yocto build LIbxml2.a for
> me. i tried putting libxml2-staticdev  in the local.conf file and it gives
> me build error.
>
> all i want is Libxml2.a which is to be used by Libiio.so/Libiio.a to be
> used by an application [called in user space of AARCH linux]
>
>
> Thanks
> RC
>
> On Thu, Apr 6, 2017 at 3:17 PM, Matthew McClintock  > wrote:
>
>> On Thu, Apr 6, 2017 at 9:20 AM, Ravi chandra reddy 
>> wrote:
>> > Hi,
>> >  Is there any hidden pointer within these static dev packages. i
>> > expected the library to be .a format. what can i understand from these
>> > static dev packages, plz let me know.
>>
>> Can you expand on what you're trying to accomplish? Are you trying to
>> build a static binary? I don't think you actually are trying to
>> install libxml2.a on the running image are you? Maybe you really want
>> an SDK with a sysroot populated with static libraries so you can link
>> against them?
>>
>> -M
>>
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 2/2] lib/oe/sstatesig: avoid reporting duplicate siginfo files from sstate

2017-04-06 Thread Paul Eggleton
In find_siginfo(), which is used by bitbake-diffsigs among other things,
avoid adding a siginfo file from the sstate-cache where we've already
collected a sigdata file from the stamps directory with the same hash.
This avoids the possibility that the top two files (as picked by default
using the bitbake-diffsigs -t option) are for the same signature and
thus the tool would report no differences. In order to do that, just use
the hashfiles dict that we already have - we just need to change the
code to populate that even if we're collecting matching files without
looking for a fixed set of hashes (i.e. taskhashlist isn't set).

This replaces previous code in bitbake-diffsigs that attempted to filter
these out with limited success.

Signed-off-by: Paul Eggleton 
---
 meta/lib/oe/sstatesig.py | 20 ++--
 1 file changed, 14 insertions(+), 6 deletions(-)

diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index a76a031..8d93013 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -254,9 +254,6 @@ def find_siginfo(pn, taskname, taskhashlist, d):
 import fnmatch
 import glob
 
-if taskhashlist:
-hashfiles = {}
-
 if not taskname:
 # We have to derive pn and taskname
 key = pn
@@ -266,8 +263,15 @@ def find_siginfo(pn, taskname, taskhashlist, d):
 if key.startswith('virtual:native:'):
 pn = pn + '-native'
 
+hashfiles = {}
 filedates = {}
 
+def get_hashval(siginfo):
+if siginfo.endswith('.siginfo'):
+return siginfo.rpartition(':')[2].partition('_')[0]
+else:
+return siginfo.rpartition('.')[2]
+
 # First search in stamps dir
 localdata = d.createCopy()
 localdata.setVar('MULTIMACH_TARGET_SYS', '*')
@@ -297,6 +301,8 @@ def find_siginfo(pn, taskname, taskhashlist, d):
 filedates[fullpath] = os.stat(fullpath).st_mtime
 except OSError:
 continue
+hashval = get_hashval(fullpath)
+hashfiles[hashval] = fullpath
 
 if not taskhashlist or (len(filedates) < 2 and not foundall):
 # That didn't work, look in sstate-cache
@@ -320,9 +326,11 @@ def find_siginfo(pn, taskname, taskhashlist, d):
 
 matchedfiles = glob.glob(filespec)
 for fullpath in matchedfiles:
-if taskhashlist:
-hashfiles[hashval] = fullpath
-else:
+actual_hashval = get_hashval(fullpath)
+if actual_hashval in hashfiles:
+continue
+hashfiles[hashval] = fullpath
+if not taskhashlist:
 try:
 filedates[fullpath] = os.stat(fullpath).st_mtime
 except:
-- 
2.9.3

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


[OE-core] [PATCH 1/2] lib/oe/sstatesig: fix finding native siginfo files in sstate-cache

2017-04-06 Thread Paul Eggleton
When comparing signatures with bitbake-diffsigs -t or bitbake -S
printdiff, we use this find_siginfo() function implemented in this
module to find the siginfo/sigdata files corresponding to the tasks
we're looking for. However, native sstate files go into a
NATIVELSBSTRING subdirectory and there was no handling for this when
asking about native recipes.

I'm not even sure why we were walking SSTATE_DIR in order to find
this - we don't need to, we just need to run glob.glob() on the filespec
we calculate, which should be a little bit more efficient.

Signed-off-by: Paul Eggleton 
---
 meta/lib/oe/sstatesig.py | 25 +
 1 file changed, 9 insertions(+), 16 deletions(-)

diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index 13fd3bd..a76a031 100644
--- a/meta/lib/oe/sstatesig.py
+++ b/meta/lib/oe/sstatesig.py
@@ -318,22 +318,15 @@ def find_siginfo(pn, taskname, taskhashlist, d):
 sstatename = taskname[3:]
 filespec = '%s_%s.*.siginfo' % (localdata.getVar('SSTATE_PKG'), 
sstatename)
 
-if hashval != '*':
-sstatedir = "%s/%s" % (d.getVar('SSTATE_DIR'), hashval[:2])
-else:
-sstatedir = d.getVar('SSTATE_DIR')
-
-for root, dirs, files in os.walk(sstatedir):
-for fn in files:
-fullpath = os.path.join(root, fn)
-if fnmatch.fnmatch(fullpath, filespec):
-if taskhashlist:
-hashfiles[hashval] = fullpath
-else:
-try:
-filedates[fullpath] = 
os.stat(fullpath).st_mtime
-except:
-continue
+matchedfiles = glob.glob(filespec)
+for fullpath in matchedfiles:
+if taskhashlist:
+hashfiles[hashval] = fullpath
+else:
+try:
+filedates[fullpath] = os.stat(fullpath).st_mtime
+except:
+continue
 
 if taskhashlist:
 return hashfiles
-- 
2.9.3

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


[OE-core] [PATCH 0/2] OE-side fixes for bitbake-diffsigs

2017-04-06 Thread Paul Eggleton
Fixes for lib/oe/sstatesig.py corresponding to the bitbake-diffsigs
patchset I just sent to bitbake-devel.


The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:

  oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir 
(2017-04-06 10:13:34 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/diffsigs-fixes-oe
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/diffsigs-fixes-oe

Paul Eggleton (2):
  lib/oe/sstatesig: fix finding native siginfo files in sstate-cache
  lib/oe/sstatesig: avoid reporting duplicate siginfo files from sstate

 meta/lib/oe/sstatesig.py | 39 ---
 1 file changed, 20 insertions(+), 19 deletions(-)

-- 
2.9.3

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


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

2017-04-06 Thread Paul Eggleton
On Thursday, 6 April 2017 1:36:05 AM NZST you wrote:
>AssertionError: False is not true : Layer meta- changed 120
> signatures, initial differences (first hash without, second with layer):

BTW, rather than self.assertTrue(False, ... ) you can just use self.fail(...) 
and then you avoid this ugly "False is not True" bit.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


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

2017-04-06 Thread Ravi chandra reddy
Hi,
I am trying to generate LibIIO [open source by Analog Devices], however
there is dependancy on Libxml2.

problem with Libxml2, it is dependant on *python*-lib, libdl, libz, libzma,
libm

for some reason with Yocto built Libxml2.so, i am encountering "undefined
references error", which i am unable to solve [inspite of linking possible
dependant libraries],

if i get could the Libxml2.a, it packages all "REQUIRED ELEMENTS", so i
assume, there WONT be any error in linking Libxml2 in Libiio.

==in short=
Libiio ---linking---> Libxml2*.so* [yocto based] ---errors-> undefined
referneces to .

==in short=
Libiio ---linking---> Libxml2.a [yocto based] --> SHOULD solve and install
libiio

for me to generate Libxml2.a, i need to make/ask yocto build LIbxml2.a for
me. i tried putting libxml2-staticdev  in the local.conf file and it gives
me build error.

all i want is Libxml2.a which is to be used by Libiio.so/Libiio.a to be
used by an application [called in user space of AARCH linux]


Thanks
RC

On Thu, Apr 6, 2017 at 3:17 PM, Matthew McClintock 
wrote:

> On Thu, Apr 6, 2017 at 9:20 AM, Ravi chandra reddy 
> wrote:
> > Hi,
> >  Is there any hidden pointer within these static dev packages. i
> > expected the library to be .a format. what can i understand from these
> > static dev packages, plz let me know.
>
> Can you expand on what you're trying to accomplish? Are you trying to
> build a static binary? I don't think you actually are trying to
> install libxml2.a on the running image are you? Maybe you really want
> an SDK with a sysroot populated with static libraries so you can link
> against them?
>
> -M
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] libsdl: enable X11 for nativesdk

2017-04-06 Thread Martin Kelly
From: Martin Kelly 

Currently, the following situation fails:

- Build an SDK and image. Make the image support graphics but not X11.
- Extract SDK and copy image somewhere outside of the Yocto workspace. Do
  runqemu on the image.

This results in the error:
"Could not initialize SDL(No available video device) - exiting"

This error occurs because libSDL attempts to load libX11 for video devices. When
it fails, qemu also fails.

Note that the same runqemu command will work fine from within the Yocto
workspace environment because it will use the native libSDL -- which supports
X11 -- rather than the nativesdk libSDL. In addition, the command will work fine
as long as DISTRO_FEATURES includes x11, because then the nativesdk libSDL will
be compiled with X11 support.

Although the example above may seem a bit silly, this is actually a pretty bad
error because it breaks the ability to build an SDK and image on one machine and
run it on a different machine.

Fix the issue by building nativesdk-libsdl with X11 support -- even when
DISTRO_FEATURES does not include X11 -- as we already do for libsdl-native.

Signed-off-by: Martin Kelly 
---
 meta/recipes-graphics/libsdl/libsdl_1.2.15.bb  | 3 ++-
 meta/recipes-graphics/xorg-lib/libxcb_1.12.bb  | 1 +
 meta/recipes-graphics/xorg-lib/xorg-lib-common.inc | 1 +
 3 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb 
b/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
index c802a6f..89d84ab 100644
--- a/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
+++ b/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
@@ -43,8 +43,9 @@ EXTRA_OECONF = "--disable-static --enable-cdrom 
--enable-threads --enable-timers
 
 PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'alsa directfb 
pulseaudio x11', d)} \
${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 
'opengl', '', d)}"
+# Without X11 support, qemu will fail because SDL cannot find video devices.
 PACKAGECONFIG_class-native = "x11"
-PACKAGECONFIG_class-nativesdk = "${@bb.utils.filter('DISTRO_FEATURES', 'x11', 
d)}"
+PACKAGECONFIG_class-nativesdk = "x11"
 
 PACKAGECONFIG[alsa] = "--enable-alsa 
--disable-alsatest,--disable-alsa,alsa-lib"
 PACKAGECONFIG[pulseaudio] = 
"--enable-pulseaudio,--disable-pulseaudio,pulseaudio"
diff --git a/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb 
b/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb
index a38bdea..6d7e675 100644
--- a/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb
+++ b/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb
@@ -31,6 +31,7 @@ inherit autotools pkgconfig distro_features_check
 # The libxau and others requires x11 in DISTRO_FEATURES
 REQUIRED_DISTRO_FEATURES = "x11"
 REQUIRED_DISTRO_FEATURES_class-native = ""
+REQUIRED_DISTRO_FEATURES_class-nativesdk = ""
 
 export PYTHON = "python3"
 
diff --git a/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc 
b/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc
index 6f4e444..b397923 100644
--- a/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc
+++ b/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc
@@ -25,3 +25,4 @@ UNKNOWN_CONFIGURE_WHITELIST += "--enable-malloc0returnsnull 
--disable-malloc0ret
 
 REQUIRED_DISTRO_FEATURES ?= "x11"
 REQUIRED_DISTRO_FEATURES_class-native = ""
+REQUIRED_DISTRO_FEATURES_class-nativesdk = ""
-- 
2.1.4

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


[OE-core] [meta-oe][PATCH] libsdl: enable X11 for nativesdk

2017-04-06 Thread Martin Kelly
From: Martin Kelly 

Currently, the following situation fails:

- Build an SDK and image. Make the image support graphics but not X11.
- Extract SDK and copy image somewhere outside of the Yocto workspace. Do
  runqemu on the image.

This results in the error:
"Could not initialize SDL(No available video device) - exiting"

This error occurs because libSDL attempts to load libX11 for video devices. When
it fails, qemu also fails.

Note that the same runqemu command will work fine from within the Yocto
workspace environment because it will use the native libSDL -- which supports
X11 -- rather than the nativesdk libSDL. In addition, the command will work fine
as long as DISTRO_FEATURES includes x11, because then the nativesdk libSDL will
be compiled with X11 support.

Although the example above may seem a bit silly, this is actually a pretty bad
error because it breaks the ability to build an SDK and image on one machine and
run it on a different machine.

Fix the issue by building nativesdk-libsdl with X11 support -- even when
DISTRO_FEATURES does not include X11 -- as we already do for libsdl-native.

Signed-off-by: Martin Kelly 
---
 meta/recipes-graphics/libsdl/libsdl_1.2.15.bb  | 3 ++-
 meta/recipes-graphics/xorg-lib/libxcb_1.12.bb  | 1 +
 meta/recipes-graphics/xorg-lib/xorg-lib-common.inc | 1 +
 3 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb 
b/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
index c802a6f..89d84ab 100644
--- a/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
+++ b/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
@@ -43,8 +43,9 @@ EXTRA_OECONF = "--disable-static --enable-cdrom 
--enable-threads --enable-timers
 
 PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'alsa directfb 
pulseaudio x11', d)} \
${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 
'opengl', '', d)}"
+# Without X11 support, qemu will fail because SDL cannot find video devices.
 PACKAGECONFIG_class-native = "x11"
-PACKAGECONFIG_class-nativesdk = "${@bb.utils.filter('DISTRO_FEATURES', 'x11', 
d)}"
+PACKAGECONFIG_class-nativesdk = "x11"
 
 PACKAGECONFIG[alsa] = "--enable-alsa 
--disable-alsatest,--disable-alsa,alsa-lib"
 PACKAGECONFIG[pulseaudio] = 
"--enable-pulseaudio,--disable-pulseaudio,pulseaudio"
diff --git a/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb 
b/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb
index a38bdea..6d7e675 100644
--- a/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb
+++ b/meta/recipes-graphics/xorg-lib/libxcb_1.12.bb
@@ -31,6 +31,7 @@ inherit autotools pkgconfig distro_features_check
 # The libxau and others requires x11 in DISTRO_FEATURES
 REQUIRED_DISTRO_FEATURES = "x11"
 REQUIRED_DISTRO_FEATURES_class-native = ""
+REQUIRED_DISTRO_FEATURES_class-nativesdk = ""
 
 export PYTHON = "python3"
 
diff --git a/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc 
b/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc
index 6f4e444..b397923 100644
--- a/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc
+++ b/meta/recipes-graphics/xorg-lib/xorg-lib-common.inc
@@ -25,3 +25,4 @@ UNKNOWN_CONFIGURE_WHITELIST += "--enable-malloc0returnsnull 
--disable-malloc0ret
 
 REQUIRED_DISTRO_FEATURES ?= "x11"
 REQUIRED_DISTRO_FEATURES_class-native = ""
+REQUIRED_DISTRO_FEATURES_class-nativesdk = ""
-- 
2.1.4

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


[OE-core] [PATCH] qemu: use python2.7 instead of python2

2017-04-06 Thread Martin Kelly
From: Martin Kelly 

meta/conf/bitbake.conf puts python2.7 into the HOSTTOOLS variable but not
python2, so only python2.7 is guaranteed. In addition, on some distros -- such
as Amazon Linux -- /usr/bin/python2 doesn't exist but python2.7 does. So, use
python2.7 for the --python= argument in the qemu configure step.

Signed-off-by: Martin Kelly 
---
 meta/recipes-devtools/qemu/qemu.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/qemu/qemu.inc 
b/meta/recipes-devtools/qemu/qemu.inc
index 383cc64..0e1411a 100644
--- a/meta/recipes-devtools/qemu/qemu.inc
+++ b/meta/recipes-devtools/qemu/qemu.inc
@@ -29,7 +29,7 @@ EXTRA_OECONF = " \
 --with-system-pixman \
 --extra-cflags='${CFLAGS}' \
 "
-EXTRA_OECONF_append_class-native = " --python=${USRBINPATH}/python2"
+EXTRA_OECONF_append_class-native = " --python=${USRBINPATH}/python2.7"
 
 EXTRA_OEMAKE_append_class-native = " LD='${LD}' AR='${AR}' 
OBJCOPY='${OBJCOPY}' LDFLAGS='${LDFLAGS}'"
 
-- 
2.1.4

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


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

2017-04-06 Thread Matthew McClintock
On Thu, Apr 6, 2017 at 9:20 AM, Ravi chandra reddy  wrote:
> Hi,
>  Is there any hidden pointer within these static dev packages. i
> expected the library to be .a format. what can i understand from these
> static dev packages, plz let me know.

Can you expand on what you're trying to accomplish? Are you trying to
build a static binary? I don't think you actually are trying to
install libxml2.a on the running image are you? Maybe you really want
an SDK with a sysroot populated with static libraries so you can link
against them?

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


[OE-core] ✗ patchtest: failure for lsb: Remove bashisms from the rc.d functions

2017-04-06 Thread Patchwork
== Series Details ==

Series: lsb: Remove bashisms from the rc.d functions
Revision: 1
URL   : https://patchwork.openembedded.org/series/6209/
State : failure

== Summary ==


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



* Issue Added patch file is missing Upstream-Status in the header 
[test_upstream_status_presence] 
  Suggested fixAdd Upstream-Status:  to the header of 
meta/recipes-extended/lsb/lsbinitscripts/0002-rc.d-Remove-bashism-from-functions.patch
 (possible values: Pending, Submitted, Accepted, Backport, Denied, 
Inappropriate)



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

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

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


[OE-core] [RFC][PATCH] lsb: Remove bashisms from the rc.d functions

2017-04-06 Thread Marek Vasut
This bashism prevents functions from working on systems without bash,
ie. on systems with busybox shell or debian dash. Replace them with
bourne-compatible command instead.

Signed-off-by: Marek Vasut 
Cc: Ross Burton 
Cc: Richard Purdie 
---
NOTE: Does this lsbscripts have upstream somewhere ?
---
 .../0002-rc.d-Remove-bashism-from-functions.patch  | 48 ++
 meta/recipes-extended/lsb/lsbinitscripts_9.68.bb   |  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 
meta/recipes-extended/lsb/lsbinitscripts/0002-rc.d-Remove-bashism-from-functions.patch

diff --git 
a/meta/recipes-extended/lsb/lsbinitscripts/0002-rc.d-Remove-bashism-from-functions.patch
 
b/meta/recipes-extended/lsb/lsbinitscripts/0002-rc.d-Remove-bashism-from-functions.patch
new file mode 100644
index 00..44eed1cc18
--- /dev/null
+++ 
b/meta/recipes-extended/lsb/lsbinitscripts/0002-rc.d-Remove-bashism-from-functions.patch
@@ -0,0 +1,48 @@
+From b7601dcd4663a9cb936a6d2d224665bea69fcc50 Mon Sep 17 00:00:00 2001
+From: Marek Vasut 
+Date: Thu, 6 Apr 2017 19:15:56 +0200
+Subject: [PATCH] rc.d: Remove bashism from functions
+
+This bashism prevents functions from working on systems without bash,
+ie. on systems with busybox shell or debian dash. Replace them with
+bourne-compatible command instead.
+
+Signed-off-by: Marek Vasut 
+---
+ rc.d/init.d/functions | 9 ++---
+ 1 file changed, 2 insertions(+), 7 deletions(-)
+
+diff --git a/rc.d/init.d/functions b/rc.d/init.d/functions
+index 746b37d..3ba21ef 100644
+--- a/rc.d/init.d/functions
 b/rc.d/init.d/functions
+@@ -115,15 +115,11 @@ __kill_pids_term_kill_checkpids() {
+ local pid=
+ local pids=$*
+ local remaining=
+-local stat=
+ local stime=
+ 
+ for pid in $pids ; do
+ [ ! -e  "/proc/$pid" ] && continue
+-read -r line < "/proc/$pid/stat" 2> /dev/null
+-
+-stat=($line)
+-stime=${stat[21]}
++stime=`cut -d " " -f 22 < /proc/self/stat`
+ 
+ [ -n "$stime" ] && [ "$base_stime" -lt "$stime" ] && continue
+ remaining+="$pid "
+@@ -139,8 +135,7 @@ __kill_pids_term_kill() {
+ local try=0
+ local delay=3;
+ local pid=
+-local stat=($(< /proc/self/stat))
+-local base_stime=${stat[21]}
++local base_stime=`cut -d " " -f 22 < /proc/self/stat`
+ 
+ if [ "$1" = "-d" ]; then
+ delay=$2
+-- 
+2.11.0
+
diff --git a/meta/recipes-extended/lsb/lsbinitscripts_9.68.bb 
b/meta/recipes-extended/lsb/lsbinitscripts_9.68.bb
index 0c08fffcef..9ba0e01776 100644
--- a/meta/recipes-extended/lsb/lsbinitscripts_9.68.bb
+++ b/meta/recipes-extended/lsb/lsbinitscripts_9.68.bb
@@ -11,6 +11,7 @@ S="${WORKDIR}/initscripts-${PV}"
 SRC_URI = 
"http://pkgs.fedoraproject.org/repo/pkgs/initscripts/initscripts-${PV}.tar.bz2/6a51a5af38e01445f53989ed0727c3e1/initscripts-${PV}.tar.bz2
 \
file://functions.patch \

file://0001-functions-avoid-exit-1-which-causes-init-scripts-to-.patch \
+  file://0002-rc.d-Remove-bashism-from-functions.patch \
   " 
 
 SRC_URI[md5sum] = "6a51a5af38e01445f53989ed0727c3e1"
-- 
2.11.0

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


[OE-core] [PATCH] selftest/recipetool: skip create_git in case x11 feature is not present

2017-04-06 Thread leonardo . sandoval . gonzalez
From: Leonardo Sandoval 

The unit test requires x11 as distro feature, otherwise it will fail
while building the test requirements.

[YOCTO #10903]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/selftest/recipetool.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/lib/oeqa/selftest/recipetool.py 
b/meta/lib/oeqa/selftest/recipetool.py
index d47b9dd..7bfb02f 100644
--- a/meta/lib/oeqa/selftest/recipetool.py
+++ b/meta/lib/oeqa/selftest/recipetool.py
@@ -382,6 +382,8 @@ class RecipetoolTests(RecipetoolBase):
 
 @testcase(1194)
 def test_recipetool_create_git(self):
+if 'x11' not in get_bb_var('DISTRO_FEATURES'):
+self.skipTest('Test requires x11 as distro feature')
 # Ensure we have the right data in shlibs/pkgdata
 bitbake('libpng pango libx11 libxext jpeg libcheck')
 # Try adding a recipe
-- 
2.10.2

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


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

2017-04-06 Thread Aníbal Limón
Acked-by: Aníbal Limón 

On 04/05/2017 08:36 AM, Patrick Ohly wrote:
> I started applying yocto-compat-layer to some real BSP layers and ran
> into some usability issues with the tool.
> 
> I also didn't want to do the root cause analysis manually, so I
> automated the dependency analysis and the running of
> bitbake-diffsigs.
> 
> This patch series is based on Mark's "yocto-compat-layer.py updates"
> series. The last commit depends on Paul's "bitbake-diffsigs: add an
> option to find and compare specific signatures" patch from
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=paule/sigstuff&id=5bb69edfb4bbaa7373061daeb4f233a7e2f43a43
> 
> Regarding the BSP example that I ended up using: it actually was one
> of the better BSP layers and only had one problem in a "bitbake world"
> build instead of several as in other BSP layers. Nevertheless I
> obscured the name to protect the (not so) guilty in the commit
> messages ;-}
> 
> The two changes that show up in test_signatures look harmless at first
> glance, but probably would need to be done differently to avoid a
> false positive when doing the signature check.
> 
> Patrick Ohly (3):
>   yocto-compat-layer: fix also other command invocations
>   yocto-compat-layer: limit report of signature changes
>   yocto-compat-layer: include bitbake-diffsigs output
> 
>  scripts/lib/compatlayer/__init__.py | 55 +---
>  scripts/lib/compatlayer/cases/common.py | 87 --
>  2 files changed, 103 insertions(+), 39 deletions(-)
> 
> base-commit: f6b68a87a11a84c7baf7784fc71e07c6595d598b
> 



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


[OE-core] [PATCH] qemux86*.conf: changed dependency task for syslinux

2017-04-06 Thread Ed Bartosh
Changed dependency task for syslinux from do_build to
do_populate_sysroot as do_build dependency caused conflicts in
populating image recipe sysroot using conflicting recipes. This
makes do_image_wic task to fail with FileExistsError trying to
copy the same file from two conflicting recipes.

This should also speed up image creation a bit as do_populate_sysroot
task is faster than do_build.

[YOCTO #11295]

Signed-off-by: Ed Bartosh 
---
 meta/conf/machine/qemux86-64.conf | 2 +-
 meta/conf/machine/qemux86.conf| 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/conf/machine/qemux86-64.conf 
b/meta/conf/machine/qemux86-64.conf
index 150d745..10189cb 100644
--- a/meta/conf/machine/qemux86-64.conf
+++ b/meta/conf/machine/qemux86-64.conf
@@ -30,4 +30,4 @@ MACHINE_FEATURES += "x86"
 MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
 
 WKS_FILE ?= "directdisk.wks"
-do_image_wic[depends] += "syslinux:do_build 
syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+do_image_wic[depends] += "syslinux:do_populate_sysroot 
syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/qemux86.conf
index 1b478e9..c26dda2 100644
--- a/meta/conf/machine/qemux86.conf
+++ b/meta/conf/machine/qemux86.conf
@@ -29,4 +29,4 @@ MACHINE_FEATURES += "x86"
 MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
 
 WKS_FILE ?= "directdisk.wks"
-do_image_wic[depends] += "syslinux:do_build 
syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+do_image_wic[depends] += "syslinux:do_populate_sysroot 
syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
-- 
2.1.4

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


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

2017-04-06 Thread Ravi chandra reddy
Hi,
 Is there any hidden pointer within these static dev packages. i
expected the library to be .a format. what can i understand from these
static dev packages, plz let me know.


Thanks



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

> Hi,
>  is this what you are talking about
>
> root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-zynqmp/pkgdata/runtime#
> ls -ltr *libxml*
> -rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-ptest.packaged
> -rwxrwxrwx 2 root root 463307 Nov 21 14:05 libxml2-ptest
> -rwxrwxrwx 2 root root933 Nov 21 14:05 libxml2-staticdev
> -rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-dbg.packaged
> -rwxrwxrwx 2 root root  10526 Nov 21 14:05 libxml2-dbg
> -rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-dev.packaged
> -rwxrwxrwx 2 root root   3836 Nov 21 14:05 libxml2-dev
> -rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-doc.packaged
> -rwxrwxrwx 2 root root  17476 Nov 21 14:05 libxml2-doc
> -rwxrwxrwx 2 root root638 Nov 21 14:05 libxml2-locale
> -rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2.packaged
> -rwxrwxrwx 2 root root   4164 Nov 21 14:05 libxml2
> -rwxrwxrwx 2 root root628 Nov 21 14:05 libxml2-utils
> -rwxrwxrwx 2 root root  0 Nov 21 14:05 libxml2-python.packaged
> -rwxrwxrwx 2 root root   2910 Nov 21 14:05 libxml2-python
> root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-
> zynqmp/pkgdata/runtime#
> root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-
> zynqmp/pkgdata/runtime#
> root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-
> zynqmp/pkgdata/runtime#
> root@polar:~/zcu_yocto/poky/build/tmp/sysroots/zcu102-
> zynqmp/pkgdata/runtime#
>
> if not, then sorry, i didnt get you when you say "static dev packages"
>
> Thanks
>
>
> On Wed, Apr 5, 2017 at 2:26 PM, Matthew McClintock  > wrote:
>
>> Do you have the staticdev packages in your TMPDIR? E.g.
>>
>> tmp/work/cortexa15t2hf-neon-rdk-linux-gnueabi/libxml2/2.9.4-
>> r0/deploy-ipks/cortexa15t2hf-neon/libxml2-staticdev_2.9.4-
>> r0_cortexa15t2hf-neon.ipk
>>
>> -M
>>
>> On Wed, Apr 5, 2017 at 1:09 PM, Ravi chandra reddy 
>> wrote:
>> > Hi,
>> > Let me thank you guys for quick reply.
>> > let me put my  email in correct steps
>> >
>> > 1. below local/local.conf changes makes bitbake fail.
>> >
>> > IMAGE_INSTALL_append = "lib32-glibc
>> lib32-libgcc
>> > lib32-libstdc++ libedit libxml2-staticdev"
>> >
>> > error:=
>> > == i get the following
>> > errors==
>> > ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
>> > ERROR: Logfile of failure stored in:
>> > /home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-poky
>> -linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
>> > ERROR: Task 9
>> > (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-im
>> age-minimal.bb,
>> > do_rootfs) failed with exit code '1'
>> > NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to
>> be
>> > rerun and 1 failed.
>> > ===
>> >
>> > 2.  without staticdev changes [in local/local.conf], it
>> > [bitbake-core-image-minimal] goes through and it builds [but there is
>> only
>> > .so [dynamic library] generated]
>> >
>> > IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++ libedit
>> > libxml2"
>> >
>> >
>> > 3. i ran the search and found that all "no-static" lines are commented
>> >
>> > bitbake -e | grep static-libs
>> >
>> >
>> > and all the "no-static-libs.inc" are commented [#]
>> >
>> > Thanks
>> > RC
>> >
>> > On Wed, Apr 5, 2017 at 2:04 PM, Ravi chandra reddy > >
>> > wrote:
>> >>
>> >> Hi,
>> >>in local/local.conf it [bitbake core-image-minimal] fails, if i
>> use
>> >> libxml2-staticdev
>> >>
>> >>   # Specify the 32-bit libraries to be added to all images
>> >> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++
>> libedit
>> >> libxml2-staticdev"
>> >>
>> >> == i get the following
>> >> errors==
>> >> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
>> >> ERROR: Logfile of failure stored in:
>> >> /home/polar/zcu_yocto/poky/build/tmp/work/zcu102_zynqmp-poky
>> -linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.17721
>> >> ERROR: Task 9
>> >> (/home/polar/zcu_yocto/poky/meta/recipes-core/images/core-im
>> age-minimal.bb,
>> >> do_rootfs) failed with exit code '1'
>> >> NOTE: Tasks Summary: Attempted 2144 tasks of which 2143 didn't need to
>> be
>> >> rerun and 1 failed.
>> >> ===
>> >>
>> >> if i use as below, there is no issue. however there is no .so
>> >>
>> >> # Specify the 32-bit libraries to be added to all images
>> >> IMAGE_INSTALL_append = "lib32-glibc lib32-libgcc lib32-libstdc++
>> libedit
>> >> libxml2"
>> >>
>> >> i ran
>> >>
>> >> bitbake -e | grep static-libs
>> >>
>> >> and all the "no-static-libs.inc" are commented [#]
>> >>
>> >>

Re: [OE-core] [PATCH 0/2] Fixes for building on Fedora 26 (Alpha)

2017-04-06 Thread Khem Raj
On Thu, Apr 6, 2017 at 6:23 AM, Joshua Lock  wrote:
> As Fedora 26 has a new gcc [1] and a new system pkg-config implementation [2] 
> I
> wanted to do some testing on that host OS so that we might be able to get some
> fixes in before Pyro/2.3 is released.
>
> The following series were the only changes required to start building (I have
> tested core-image-minimal, core-image-base and core-image-sato) on Fedora 26.

gcc patch looks fine to me.

>
> 1. https://fedoraproject.org/wiki/Changes/GCC7
> 2. 
> https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation

I think we should think about making pkgconf as default too for OE in
next release cycle.

>
> The following changes since commit 633ad6c9f436f5d2b6ee1a005b697661a054a394:
>
>   oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir 
> (2017-04-06 10:13:39 +0100)
>
> are available in the git repository at:
>
>   git://git.yoctoproject.org/poky-contrib joshuagl/fedora26
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=joshuagl/fedora26
>
> Joshua Lock (2):
>   elfutils: fix building elfutils-native with GCC7
>   gcc-6.3: backport fix of check for empty string in ubsan.c
>
>  .../elfutils-0.168/Fix_one_GCC7_warning.patch  | 44 
> ++
>  .../elfutils/elfutils-0.168/fallthrough.patch  | 36 ++
>  meta/recipes-devtools/elfutils/elfutils_0.168.bb   |  3 ++
>  meta/recipes-devtools/gcc/gcc-6.3.inc  |  1 +
>  .../gcc/gcc-6.3/ubsan-fix-check-empty-string.patch | 28 ++
>  5 files changed, 112 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch
>  create mode 100644 
> meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch
>  create mode 100644 
> meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch
>
> --
> 2.9.3
> --
> ___
> 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] ca-certificates: Fix symlinks to the certificates in nativesdk

2017-04-06 Thread Serhii Popovych

Ping.

Any further comments on this change?

I covered at least one additional use case not covered by
generic symlink-relative.py call at post stage:

It is buildtools-tarball, where may add ca-certificates to use with
curl.

Change is simple: we create relative symlinks in update-ca-certificates
to ensure we always point to right data in SDK/buildtools-tarball.

Thanks,
Serhii

> Symlinks to certificates in buildtools-tarball at /etc/ssl/certs
> installed with absolute pathes making these sumlinks pointing
> outside of toolchain to the host system locations.
> 
> These locations may not contain some certificates (thus link to
> the certificate in toolchain is broken) or host system
> certificate may be revoked by CRL or outdated.
> 
> Since this change seems non intrusive for target package apply
> patch for all builds.
> 
> Cc: XE-Linux 
> Signed-off-by: Serhii Popovych 
> ---
>  ...ertificates-Use-relative-paths-when-linki.patch | 38 
> ++
>  .../ca-certificates/ca-certificates_20161130.bb|  1 +
>  2 files changed, 39 insertions(+)
>  create mode 100644 
> meta/recipes-support/ca-certificates/ca-certificates/0003-update-ca-certificates-Use-relative-paths-when-linki.patch
> 
> diff --git 
> a/meta/recipes-support/ca-certificates/ca-certificates/0003-update-ca-certificates-Use-relative-paths-when-linki.patch
>  
> b/meta/recipes-support/ca-certificates/ca-certificates/0003-update-ca-certificates-Use-relative-paths-when-linki.patch
> new file mode 100644
> index 000..8666e30
> --- /dev/null
> +++ 
> b/meta/recipes-support/ca-certificates/ca-certificates/0003-update-ca-certificates-Use-relative-paths-when-linki.patch
> @@ -0,0 +1,38 @@
> +From 912e7be8e7151bd4a2feed6d34f927d42b12bb7e Mon Sep 17 00:00:00 2001
> +From: Serhii Popovych 
> +Date: Wed, 16 Dec 2015 16:48:03 +0200
> +Subject: [PATCH] update-ca-certificates: Use relative paths when linking 
> certs
> +
> +Creating links in $ETCCERTSDIR (/etc/ssl/certs) with absolute
> +path could broke paths to the certificates in toolchains by
> +pointing to the outside of toolchain root directory. These
> +absolute paths may not exist in the host system or contain
> +certificates older than provided within toolchain.
> +
> +Use absolute pathes when creating symbolic links to the
> +certificates to ensure we always pointing to the toolchain
> +provied certificates.
> +
> +Upstream-Status: Pending
> +
> +Signed-off-by: Serhii Popovych 
> +---
> + sbin/update-ca-certificates | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/sbin/update-ca-certificates b/sbin/update-ca-certificates
> +index 3a5ffd3..cb3c1f1 100755
> +--- a/sbin/update-ca-certificates
>  b/sbin/update-ca-certificates
> +@@ -94,7 +94,7 @@ add() {
> +   -e 's/,/_/g').pem"
> +   if ! test -e "$PEM" || [ "$(readlink "$PEM")" != "${CERT##$SYSROOT}" ]
> +   then
> +-ln -sf "${CERT##$SYSROOT}" "$PEM"
> ++ln -sf "$(echo "${ETCCERTSDIR##$SYSROOT}" | sed -e 
> 's/\/[^/]\+/..\//g')${CERT##$SYSROOT/}" "$PEM"
> + echo "+$PEM" >> "$ADDED"
> +   fi
> +   # Add trailing newline to certificate, if it is missing (#635570)
> +-- 
> +2.3.0
> +
> diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb 
> b/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb
> index 42088b9..e6e17de 100644
> --- a/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb
> +++ b/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb
> @@ -17,6 +17,7 @@ SRCREV = "61b70a1007dc269d56881a0d480fc841daacc77c"
>  
>  SRC_URI = "git://anonscm.debian.org/collab-maint/ca-certificates.git \
> file://0002-update-ca-certificates-use-SYSROOT.patch \
> +   
> file://0003-update-ca-certificates-Use-relative-paths-when-linki.patch \
> 
> file://0001-update-ca-certificates-don-t-use-Debianisms-in-run-p.patch \
> file://update-ca-certificates-support-Toybox.patch \
> file://default-sysroot.patch \
> 
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 2/2] gcc-6.3: backport fix of check for empty string in ubsan.c

2017-04-06 Thread Joshua Lock
Building gcc-cross-initial with GCC7 on the host fails due to the
comparison of a pointer to an integer in ubsan_use_new_style_p, which
is forbidden by ISO C++:

ubsan.c:1474:23: error: ISO C++ forbids comparison between pointer and
integer [-fpermissive]
   || xloc.file == '\0' || xloc.file[0] == '\xff'

Backport the fix from upstream GCC to enable the build with GCC 7

Signed-off-by: Joshua Lock 
---
 meta/recipes-devtools/gcc/gcc-6.3.inc  |  1 +
 .../gcc/gcc-6.3/ubsan-fix-check-empty-string.patch | 28 ++
 2 files changed, 29 insertions(+)
 create mode 100644 
meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch

diff --git a/meta/recipes-devtools/gcc/gcc-6.3.inc 
b/meta/recipes-devtools/gcc/gcc-6.3.inc
index da7a083..71d0aff 100644
--- a/meta/recipes-devtools/gcc/gcc-6.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-6.3.inc
@@ -84,6 +84,7 @@ SRC_URI = "\
 "
 BACKPORTS = "\
file://CVE-2016-6131.patch \
+   file://ubsan-fix-check-empty-string.patch \
 "
 SRC_URI[md5sum] = "677a7623c7ef6ab99881bc4e048debb6"
 SRC_URI[sha256sum] = 
"f06ae7f3f790fbf0f018f6d40e844451e6bc3b7bc96e128e63b09825c1f8b29f"
diff --git 
a/meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch 
b/meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch
new file mode 100644
index 000..c012719
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch
@@ -0,0 +1,28 @@
+From 8db2cf6353c13f2a84cbe49b689654897906c499 Mon Sep 17 00:00:00 2001
+From: kyukhin 
+Date: Sat, 3 Sep 2016 10:57:05 +
+Subject: [PATCH] gcc/  * ubsan.c (ubsan_use_new_style_p): Fix check for empty
+ string.
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@239971 
138bc75d-0d04-0410-961f-82ee72b054a4
+
+Upstream-Status: Backport
+Signed-off-by: Joshua Lock 
+
+---
+ gcc/ubsan.c   | 2 +-
+ 2 files changed, 5 insertions(+), 1 deletion(-)
+
+Index: gcc-6.3.0/gcc/ubsan.c
+===
+--- gcc-6.3.0.orig/gcc/ubsan.c
 gcc-6.3.0/gcc/ubsan.c
+@@ -1471,7 +1471,7 @@ ubsan_use_new_style_p (location_t loc)
+ 
+   expanded_location xloc = expand_location (loc);
+   if (xloc.file == NULL || strncmp (xloc.file, "\1", 2) == 0
+-  || xloc.file == '\0' || xloc.file[0] == '\xff'
++  || xloc.file[0] == '\0' || xloc.file[0] == '\xff'
+   || xloc.file[1] == '\xff')
+ return false;
+ 
-- 
2.9.3

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


[OE-core] [PATCH 1/2] elfutils: fix building elfutils-native with GCC7

2017-04-06 Thread Joshua Lock
Backport a fix from upstream for a -Wformat-truncation=2 warning
and implement a simple fix for a -Wimplicit-fallthrough warning.

Signed-off-by: Joshua Lock 
---
 .../elfutils-0.168/Fix_one_GCC7_warning.patch  | 44 ++
 .../elfutils/elfutils-0.168/fallthrough.patch  | 36 ++
 meta/recipes-devtools/elfutils/elfutils_0.168.bb   |  3 ++
 3 files changed, 83 insertions(+)
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch

diff --git 
a/meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch 
b/meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch
new file mode 100644
index 000..d88f4eb
--- /dev/null
+++ b/meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch
@@ -0,0 +1,44 @@
+From 93c51144c3f664d4e9709da75a1d0fa00ea0fe95 Mon Sep 17 00:00:00 2001
+From: Mark Wielaard 
+Date: Sun, 12 Feb 2017 21:51:34 +0100
+Subject: [PATCH] libasm: Fix one GCC7 -Wformat-truncation=2 warning.
+
+Make sure that if we have really lots of labels the tempsym doesn't get
+truncated because it is too small to hold the whole name.
+
+This doesn't enable -Wformat-truncation=2 or fix other "issues" pointed
+out by enabling this warning because there are currently some issues
+with it. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79448
+
+Signed-off-by: Mark Wielaard 
+
+Upstream-Status: Backport 
(https://sourceware.org/git/?p=elfutils.git;a=commit;h=93c51144c3f664d4e9709da75a1d0fa00ea0fe95)
+Signed-off-by: Joshua Lock 
+
+---
+ libasm/ChangeLog| 6 +-
+ libasm/asm_newsym.c | 6 --
+ 2 files changed, 9 insertions(+), 3 deletions(-)
+
+Index: elfutils-0.168/libasm/asm_newsym.c
+===
+--- elfutils-0.168.orig/libasm/asm_newsym.c
 elfutils-0.168/libasm/asm_newsym.c
+@@ -1,5 +1,5 @@
+ /* Define new symbol for current position in given section.
+-   Copyright (C) 2002, 2005, 2016 Red Hat, Inc.
++   Copyright (C) 2002, 2005, 2016, 2017 Red Hat, Inc.
+This file is part of elfutils.
+Written by Ulrich Drepper , 2002.
+ 
+@@ -44,7 +44,9 @@ AsmSym_t *
+ asm_newsym (AsmScn_t *asmscn, const char *name, GElf_Xword size,
+   int type, int binding)
+ {
+-#define TEMPSYMLEN 10
++/* We don't really expect labels with many digits, but in theory it could
++   be 10 digits (plus ".L" and a zero terminator).  */
++#define TEMPSYMLEN 13
+   char tempsym[TEMPSYMLEN];
+   AsmSym_t *result;
+ 
diff --git a/meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch 
b/meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch
new file mode 100644
index 000..b2623f9
--- /dev/null
+++ b/meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch
@@ -0,0 +1,36 @@
+GCC7 adds -Wimplicit-fallthrough to warn when a switch case falls through,
+however this causes warnings (which are promoted to errors) with the elfutils
+patches from Debian for mips and parisc, which use fallthrough's by design.
+
+Explicitly mark the intentional fallthrough switch cases with a comment to
+disable the warnings where the fallthrough behaviour is desired.
+
+Upstream-Status: Pending [debian]
+Signed-off-by: Joshua Lock 
+
+Index: elfutils-0.168/backends/parisc_retval.c
+===
+--- elfutils-0.168.orig/backends/parisc_retval.c
 elfutils-0.168/backends/parisc_retval.c
+@@ -166,7 +166,7 @@ parisc_return_value_location_ (Dwarf_Die
+ return nloc_intregpair;
+ 
+   /* Else fall through.  */
+-  }
++  } // fallthrough
+ 
+ case DW_TAG_structure_type:
+ case DW_TAG_class_type:
+Index: elfutils-0.168/backends/mips_retval.c
+===
+--- elfutils-0.168.orig/backends/mips_retval.c
 elfutils-0.168/backends/mips_retval.c
+@@ -387,7 +387,7 @@ mips_return_value_location (Dwarf_Die *f
+   else
+ return nloc_intregpair;
+ }
+-}
++} // fallthrough
+ 
+   /* Fallthrough to handle large types */
+ 
diff --git a/meta/recipes-devtools/elfutils/elfutils_0.168.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.168.bb
index 9557933..3b8f2a3 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.168.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.168.bb
@@ -17,6 +17,7 @@ SRC_URI += "\
 file://0001-remove-the-unneed-checking.patch \
 file://0001-fix-a-stack-usage-warning.patch \
 file://aarch64_uio.patch \
+file://Fix_one_GCC7_warning.patch \
 file://shadow.patch \
 "
 
@@ -35,6 +36,8 @@ SRC_URI += "\
 file://debian/hurd_path.patch \
 file://debian/ignore_strmerge.diff \
 "
+# Fix the patches from Debian with GCC7
+SRC_URI += "file://fallthrough.patch"
 SRC_URI_append_libc-musl = " 
file://0001-build-Provide-alter

[OE-core] [PATCH 0/2] Fixes for building on Fedora 26 (Alpha)

2017-04-06 Thread Joshua Lock
As Fedora 26 has a new gcc [1] and a new system pkg-config implementation [2] I
wanted to do some testing on that host OS so that we might be able to get some
fixes in before Pyro/2.3 is released.

The following series were the only changes required to start building (I have 
tested core-image-minimal, core-image-base and core-image-sato) on Fedora 26.

1. https://fedoraproject.org/wiki/Changes/GCC7
2. 
https://fedoraproject.org/wiki/Changes/pkgconf_as_system_pkg-config_implementation

The following changes since commit 633ad6c9f436f5d2b6ee1a005b697661a054a394:

  oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir 
(2017-04-06 10:13:39 +0100)

are available in the git repository at:

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

Joshua Lock (2):
  elfutils: fix building elfutils-native with GCC7
  gcc-6.3: backport fix of check for empty string in ubsan.c

 .../elfutils-0.168/Fix_one_GCC7_warning.patch  | 44 ++
 .../elfutils/elfutils-0.168/fallthrough.patch  | 36 ++
 meta/recipes-devtools/elfutils/elfutils_0.168.bb   |  3 ++
 meta/recipes-devtools/gcc/gcc-6.3.inc  |  1 +
 .../gcc/gcc-6.3/ubsan-fix-check-empty-string.patch | 28 ++
 5 files changed, 112 insertions(+)
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.168/Fix_one_GCC7_warning.patch
 create mode 100644 
meta/recipes-devtools/elfutils/elfutils-0.168/fallthrough.patch
 create mode 100644 
meta/recipes-devtools/gcc/gcc-6.3/ubsan-fix-check-empty-string.patch

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


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

2017-04-06 Thread Martin Jansa
I still don't understand why not use standard update-alternatives and
install another package with your favorite openssl.conf which has higher
ALTERNATIVE_PRIORITY.

This way u-a will switch to new config even when you just install the
package which require it on the target later and will switch back to
default openssl.conf when the alternative package with config file is
uninstalled.

On Thu, Apr 6, 2017 at 12:55 PM, Jussi Kukkonen 
wrote:

> On 6 April 2017 at 12:23, David Vincent  wrote:
> >
> > On mercredi 5 avril 2017 09:30:52 CEST Jussi Kukkonen wrote:
> > > This apparently breaks key generation with openssl-native because the
> file
> > > doesn't exist.
> >
> > Looking at the recipe right now, I understand why key generation is
> broken for
> > native build (I should have been more careful). I see two ways of fixing
> it :
> > - either recreate the symlink in do_install_append_class_native
> > - or simply modifiyng the OPENSSL_CONF variable in the same task.
> >
> > >
> > > I can fix it by adding one more complication to the recipe (will send a
> > > patch) but I don't think the current solution is all that great: I've
> been
> > > looking at this patch for a while now and still don't really
> understand why
> > > it is needed and how these different packages interact. I'm sure it
> makes
> > > sense when you look at the other recipe but ... isn't it a bad sign
> that
> > > that context seems to be needed?
> >
> > OK, I will provide some context because maybe my approach was wrong. In
> some
> > of my builds, I require some images to have a very specific
> configuration to
> > make OpenSSL use engines. My idea was to provide a package for this task
> since
> > the default file can not be overridden (and in fact shouldn't be for the
> native
> > build).
>
>
> So previously openssl-conf package included etc/ssl/openssl.cnf and the
> symlink ${libdir}/ssl/openssl.conf. Nothing RDEPENDS on this package (but
> libcrypto RRECOMMENDS it).
>
> After your patch the actual configuration file is still installed. In a
> postinst
>   * ${libdir}/ssl/openssl.conf is removed if it exists (why? If it's for
> upgrading, then this should happen in a prerm or postrm)
>   * the symlink ${libdir}/ssl/openssl.conf is created
>
> My confusion is this: how does the above solve the problem you describe?
> If you've managed to use RCONFLICTS to prevent the configuration package
> from getting included in the image, why are changes to the package needed?
>
>
>
> Some alternative solutions to your problem I think might work:
> * openssl_%.bbappend with a do_install_append() that simply copies your
> conf file over the one from upstream recipe. No extra packages needed
> * BAD_RECOMMENDATIONS or PACKAGE_EXCLUDE to prevent openssl-conf from
> getting included in your image, then adding your own package with your
> configuration (does not work for dpkg I think)
>
> Jussi
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] sstate: Skip glibc do_stash_locale and gcc do_gcc_stash_builddir tasks

2017-04-06 Thread Richard Purdie
We never need these tasks as dependencies of other sstate tasks since
they're only ever needed to build artefacts so we can always skip them
and save some time/space.

Signed-off-by: Richard Purdie 
---
 meta/classes/sstate.bbclass | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index af58854..bc0ec54 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -915,6 +915,10 @@ def setscene_depvalid(task, taskdependees, notneeded, d, 
log=None):
 if taskdependees[task][1] == "do_populate_lic":
 return True
 
+# stash_locale and gcc_stash_builddir are never needed as a dependency for 
built objects
+if taskdependees[task][1] == "do_stash_locale" or taskdependees[task][1] 
== "do_gcc_stash_builddir":
+return True
+
 # We only need to trigger packagedata through direct dependencies
 # but need to preserve packagedata on packagedata links
 if taskdependees[task][1] == "do_packagedata":
-- 
2.7.4

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


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

2017-04-06 Thread Romain Perier
Hello,


Le 06/04/2017 à 13:38, Richard Purdie a écrit :
> On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote:
>> This commit updates the recipe to the last upstream tag. Then, as the
>> tarball no longer contains the pre-generated Makefile, inherit from
>> autotools
>>
>> [...]
>> -PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl
>> selinux', d)}"
>> +PACKAGECONFIG ?= "\
>> +${@bb.utils.contains('DISTRO_FEATURES', 'acl', 'acl', '', d)} \
>> +${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux',
>> '', d)} \
>> +"

Correct, I probably did something wrong during rebase.

> I'm not sure the above should be there, it reverts someone else's
> change?
>
> I am a little nervous of taking this at this point in the release
> too...

What do you think if we backport the systemd service and the systemd
timer from upstream into 3.9.1 and then add support for systemd in the
recipe ? (In the original patches, I have written systemd services
myself) The code of logrotate would be unchanged.

Regards,
Romain


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


[OE-core] [PATCH 3/4] nativesdk.bbclass: override TARGET_* flags

2017-04-06 Thread liu . ming50
From: Ming Liu 

Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a nativesdk recipe even they are
not in use at all.

This can lead a lot of churn when the nativesdk sysroot are shared by
machines while they have defined different TARGET_* flags.

Fix it by overriding with BUILDSDK_* flags.

Signed-off-by: Ming Liu 
---
 meta/classes/nativesdk.bbclass | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/classes/nativesdk.bbclass b/meta/classes/nativesdk.bbclass
index a97f5a7..ebcfb2d 100644
--- a/meta/classes/nativesdk.bbclass
+++ b/meta/classes/nativesdk.bbclass
@@ -43,6 +43,10 @@ TARGET_PREFIX = "${SDK_PREFIX}"
 TARGET_CC_ARCH = "${SDK_CC_ARCH}"
 TARGET_LD_ARCH = "${SDK_LD_ARCH}"
 TARGET_AS_ARCH = "${SDK_AS_ARCH}"
+TARGET_CPPFLAGS = "${BUILDSDK_CPPFLAGS}"
+TARGET_CFLAGS = "${BUILDSDK_CFLAGS}"
+TARGET_CXXFLAGS = "${BUILDSDK_CXXFLAGS}"
+TARGET_LDFLAGS = "${BUILDSDK_LDFLAGS}"
 TARGET_FPU = ""
 EXTRA_OECONF_GCC_FLOAT = ""
 
-- 
2.7.4

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


[OE-core] [PATCH 4/4] cross-canadian.bbclass: override TARGET_* flags

2017-04-06 Thread liu . ming50
From: Ming Liu 

Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a cross-canadian recipe even they
are not in use at all.

This can lead a lot of churn when the cross-canadian sysroot are shared
by machines while they have defined different TARGET_* flags.

Fix it by overriding with BUILDSDK_* flags.

Signed-off-by: Ming Liu 
---
 meta/classes/cross-canadian.bbclass | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/cross-canadian.bbclass 
b/meta/classes/cross-canadian.bbclass
index 3120f46..49388d4 100644
--- a/meta/classes/cross-canadian.bbclass
+++ b/meta/classes/cross-canadian.bbclass
@@ -115,6 +115,11 @@ HOST_CC_ARCH = "${SDK_CC_ARCH}"
 HOST_LD_ARCH = "${SDK_LD_ARCH}"
 HOST_AS_ARCH = "${SDK_AS_ARCH}"
 
+TARGET_CPPFLAGS = "${BUILDSDK_CPPFLAGS}"
+TARGET_CFLAGS = "${BUILDSDK_CFLAGS}"
+TARGET_CXXFLAGS = "${BUILDSDK_CXXFLAGS}"
+TARGET_LDFLAGS = "${BUILDSDK_LDFLAGS}"
+
 #assign DPKG_ARCH
 DPKG_ARCH = "${@debian_arch_map(d.getVar('SDK_ARCH'), '')}"
 
-- 
2.7.4

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


[OE-core] [PATCH 0/4] Fix some incorrect TARGET_-* flags

2017-04-06 Thread liu . ming50
From: Ming Liu 

I had found a lot of churn in sysroots when multiple MACHINEs are
sharing a same build folder, which is the case in my company, after
digging into it, I found it's caused by the TARGET_-* flags, they
are exported but not in use at all, they should be replaced by
particular flags for cross,crosssdk,nativesdk,cross-canadian, native
class does not need that because it's already done in:

commit 05a70ac30b37cab0952f1b9df501993a9dec70da:
[ native.bbclass: Override TARGET_ flags too ]

Ming Liu (4):
  cross.bbclass: override TARGET_* flags
  crosssdk.bbclass: override TARGET_* flags
  nativesdk.bbclass: override TARGET_* flags
  cross-canadian.bbclass: override TARGET_* flags

 meta/classes/cross-canadian.bbclass | 5 +
 meta/classes/cross.bbclass  | 5 +
 meta/classes/crosssdk.bbclass   | 5 +
 meta/classes/nativesdk.bbclass  | 4 
 4 files changed, 19 insertions(+)

-- 
2.7.4

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


[OE-core] [PATCH 2/4] crosssdk.bbclass: override TARGET_* flags

2017-04-06 Thread liu . ming50
From: Ming Liu 

Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a crosssdk recipe even they are
not in use at all.

This can lead a lot of churn when the crosssdk sysroot are shared by
machines while they have defined different TARGET_* flags.

Fix it by overriding with BUILD_* flags.

Signed-off-by: Ming Liu 
---
 meta/classes/crosssdk.bbclass | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/crosssdk.bbclass b/meta/classes/crosssdk.bbclass
index a5ffd97..ddb98d2 100644
--- a/meta/classes/crosssdk.bbclass
+++ b/meta/classes/crosssdk.bbclass
@@ -21,8 +21,13 @@ TARGET_PREFIX = "${SDK_PREFIX}"
 TARGET_CC_ARCH = "${SDK_CC_ARCH}"
 TARGET_LD_ARCH = "${SDK_LD_ARCH}"
 TARGET_AS_ARCH = "${SDK_AS_ARCH}"
+TARGET_CPPFLAGS = "${BUILD_CPPFLAGS}"
+TARGET_CFLAGS = "${BUILD_CFLAGS}"
+TARGET_CXXFLAGS = "${BUILD_CXXFLAGS}"
+TARGET_LDFLAGS = "${BUILD_LDFLAGS}"
 TARGET_FPU = ""
 
+
 target_libdir = "${SDKPATHNATIVE}${libdir_nativesdk}"
 target_includedir = "${SDKPATHNATIVE}${includedir_nativesdk}"
 target_base_libdir = "${SDKPATHNATIVE}${base_libdir_nativesdk}"
-- 
2.7.4

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


[OE-core] [PATCH 1/4] cross.bbclass: override TARGET_* flags

2017-04-06 Thread liu . ming50
From: Ming Liu 

Some TARGET_* flags are being exported in bitbake.conf currently, so
they are impacting all the tasks of a cross recipe even they are not
in use at all.

This can lead a lot of churn when the cross sysroot are shared by
machines while they have defined different TARGET_* flags.

And sometimes it even causes "Taskhash mismatch" errors.

Fix it by overriding with BUILD_* flags.

Signed-off-by: Ming Liu 
---
 meta/classes/cross.bbclass | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/cross.bbclass b/meta/classes/cross.bbclass
index 2602153..8757303 100644
--- a/meta/classes/cross.bbclass
+++ b/meta/classes/cross.bbclass
@@ -28,6 +28,11 @@ MULTIMACH_TARGET_SYS = 
"${BUILD_ARCH}${BUILD_VENDOR}-${BUILD_OS}"
 export PKG_CONFIG_DIR = "${exec_prefix}/lib/pkgconfig"
 export PKG_CONFIG_SYSROOT_DIR = ""
 
+TARGET_CPPFLAGS = "${BUILD_CPPFLAGS}"
+TARGET_CFLAGS = "${BUILD_CFLAGS}"
+TARGET_CXXFLAGS = "${BUILD_CXXFLAGS}"
+TARGET_LDFLAGS = "${BUILD_LDFLAGS}"
+
 CPPFLAGS = "${BUILD_CPPFLAGS}"
 CFLAGS = "${BUILD_CFLAGS}"
 CXXFLAGS = "${BUILD_CFLAGS}"
-- 
2.7.4

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


[OE-core] [PATCH v2] oe-selftest: test wic sparse_copy API

2017-04-06 Thread Ed Bartosh
Added new parameter 'api' to sparse_copy function to specify
underlying filemap API to use. By default sparse_copy will
try both available APIs.

Added test case for sparse_copy to wic test suite.

Signed-off-by: Ed Bartosh 
---
 meta/lib/oeqa/selftest/wic.py | 29 +
 scripts/lib/wic/filemap.py|  6 --
 2 files changed, 33 insertions(+), 2 deletions(-)

diff --git a/meta/lib/oeqa/selftest/wic.py b/meta/lib/oeqa/selftest/wic.py
index df5e060..0a2f7ff 100644
--- a/meta/lib/oeqa/selftest/wic.py
+++ b/meta/lib/oeqa/selftest/wic.py
@@ -24,6 +24,7 @@
 """Test cases for wic."""
 
 import os
+import sys
 import unittest
 
 from glob import glob
@@ -758,3 +759,31 @@ part /etc --source rootfs --ondisk mmcblk0 --fstype=ext4 
--exclude-path bin/ --r
 self.assertEqual(0, runCmd(cmd).status)
 self.remove_config(config)
 self.assertEqual(1, len(glob(self.resultdir + 
"sdimage-bootpart-*direct")))
+
+def test_sparse_copy(self):
+"""Test sparse_copy with FIEMAP and SEEK_HOLE filemap APIs"""
+libpath = os.path.join(get_bb_var('COREBASE'), 'scripts', 'lib', 'wic')
+sys.path.insert(0, libpath)
+from  filemap import FilemapFiemap, FilemapSeek, sparse_copy, 
ErrorNotSupp
+with NamedTemporaryFile("w", suffix=".wic-sparse") as sparse:
+src_name = sparse.name
+src_size = 1024 * 10
+sparse.truncate(src_size)
+# write one byte to the file
+with open(src_name, 'r+b') as sfile:
+sfile.seek(1024 * 4)
+sfile.write(b'\x00')
+dest = sparse.name + '.out'
+# copy src file to dest using different filemap APIs
+for api in (FilemapFiemap, FilemapSeek, None):
+if os.path.exists(dest):
+os.unlink(dest)
+try:
+sparse_copy(sparse.name, dest, api=api)
+except ErrorNotSupp:
+continue # skip unsupported API
+dest_stat = os.stat(dest)
+self.assertEqual(dest_stat.st_size, src_size)
+# 8 blocks is 4K (physical sector size)
+self.assertEqual(dest_stat.st_blocks, 8)
+os.unlink(dest)
diff --git a/scripts/lib/wic/filemap.py b/scripts/lib/wic/filemap.py
index 080668e..1f1aacc 100644
--- a/scripts/lib/wic/filemap.py
+++ b/scripts/lib/wic/filemap.py
@@ -530,9 +530,11 @@ def filemap(image, log=None):
 except ErrorNotSupp:
 return FilemapSeek(image, log)
 
-def sparse_copy(src_fname, dst_fname, offset=0, skip=0):
+def sparse_copy(src_fname, dst_fname, offset=0, skip=0, api=None):
 """Efficiently copy sparse file to or into another file."""
-fmap = filemap(src_fname)
+if not api:
+api = filemap
+fmap = api(src_fname)
 try:
 dst_file = open(dst_fname, 'r+b')
 except IOError:
-- 
2.1.4

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


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

2017-04-06 Thread Richard Purdie
On Wed, 2017-04-05 at 17:05 +0200, Romain Perier wrote:
> This commit updates the recipe to the last upstream tag. Then, as the
> tarball no longer contains the pre-generated Makefile, inherit from
> autotools
> 
> [...]

> -PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl
> selinux', d)}"
> +PACKAGECONFIG ?= "\
> +${@bb.utils.contains('DISTRO_FEATURES', 'acl', 'acl', '', d)} \
> +${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux',
> '', d)} \
> +"

I'm not sure the above should be there, it reverts someone else's
change?

I am a little nervous of taking this at this point in the release
too...

Cheers,

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


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

2017-04-06 Thread Richard Purdie
On Thu, 2017-04-06 at 08:48 +0300, Dmitry Rozhkov wrote:
> On Thu, 2017-04-06 at 05:32 +, Patchwork wrote:
> > 
> > == Series Details ==
> > 
> > Series: python3: fix run-time deps for core python3 libraries
> > (rev2)
> > Revision: 2
> > URL   : https://patchwork.openembedded.org/series/6164/
> > State : failure
> > 
> > == Summary ==
> > 
> > 
> > Thank you for submitting this patch series to OpenEmbedded Core.
> > This
> > is
> > an automated response. Several tests have been executed on the
> > proposed
> > series by patchtest resulting in the following failures:
> > 
> > 
> > 
> > * Issue Series does not apply on top of target branch
> > [test_series_merge_on_head] 
> >   Suggested fixRebase your series on top of targeted branch
> >   Targeted branch  master (currently at 3a1cce6591)
> So was my master at 3a1cce6591 when I submitted the patch (and still
> is). And I believe the first version had no problems with applying it
> too.

If you take your patch from the mailing list, it doesn't apply as there
was line wrapping that occurred. I was able to fix it and make it apply
though (so no need to resend).

Cheers,

Richard

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


[OE-core] [PATCH 1/2] sanity: Require bitbake 1.33.4

2017-04-06 Thread Richard Purdie
We need the bitbake bug in recrdeptask handling of missing tasks fixed in
order to apply a fix for OE-Core.

Signed-off-by: Richard Purdie 
---
 meta/conf/sanity.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/sanity.conf b/meta/conf/sanity.conf
index 616f11c..46bdbeb 100644
--- a/meta/conf/sanity.conf
+++ b/meta/conf/sanity.conf
@@ -3,7 +3,7 @@
 # See sanity.bbclass
 #
 # Expert users can confirm their sanity with "touch conf/sanity.conf"
-BB_MIN_VERSION = "1.33.3"
+BB_MIN_VERSION = "1.33.4"
 
 SANITY_ABIFILE = "${TMPDIR}/abi_version"
 
-- 
2.7.4

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


[OE-core] [PATCH 2/2] glibc/gcc/libgcc-initial: Delete do_build tasks for -initial

2017-04-06 Thread Richard Purdie
We've had a lot of users running into RSS issues where -initial recipes
were being installed into sysroots alongside their counterparts and
causing overlapping files issues.

In general this was through do_build dependencies. Such dependencies are
bad in general and I'd encourage people to compare the taskgraphs with
using a more specific dependency like do_populate_sysroot, do_image_complete
or do_deploy as often the more specific dependency will result in a much
cleaner build.

Regardless, we don't want -initial dependencies getting in the way like
this and there are cases a do_build dependency could make sense.

Deleting the do_build task in these cases makes sense since this is not
a build "endpoint" we'd ever want a user to use, its a behind the scenes
piece of bootstrappping.

Unfortunately to make this work, we need a newer bitbake version which
has a bitbake bug fixed.

Signed-off-by: Richard Purdie 
---
 meta/recipes-core/glibc/glibc-initial.inc   | 3 +++
 meta/recipes-devtools/gcc/gcc-cross-initial.inc | 4 
 meta/recipes-devtools/gcc/libgcc-initial.inc| 3 +++
 3 files changed, 10 insertions(+)

diff --git a/meta/recipes-core/glibc/glibc-initial.inc 
b/meta/recipes-core/glibc/glibc-initial.inc
index f94603c..b86e2fb 100644
--- a/meta/recipes-core/glibc/glibc-initial.inc
+++ b/meta/recipes-core/glibc/glibc-initial.inc
@@ -52,3 +52,6 @@ do_siteconfig () {
 }
 
 inherit nopackages
+
+# We really only want this built by things that need it, not any recrdeptask
+deltask do_build
diff --git a/meta/recipes-devtools/gcc/gcc-cross-initial.inc 
b/meta/recipes-devtools/gcc/gcc-cross-initial.inc
index 5c0208a..d440d88 100644
--- a/meta/recipes-devtools/gcc/gcc-cross-initial.inc
+++ b/meta/recipes-devtools/gcc/gcc-cross-initial.inc
@@ -82,3 +82,7 @@ do_populate_sysroot[sstate-outputdirs] = 
"${STAGING_DIR}-components/${PACKAGE_AR
 inherit nopackages
 
 COMPILERINITIAL = "-initial"
+
+
+# We really only want this built by things that need it, not any recrdeptask
+deltask do_build
diff --git a/meta/recipes-devtools/gcc/libgcc-initial.inc 
b/meta/recipes-devtools/gcc/libgcc-initial.inc
index 5b4bc3b..950ad86 100644
--- a/meta/recipes-devtools/gcc/libgcc-initial.inc
+++ b/meta/recipes-devtools/gcc/libgcc-initial.inc
@@ -15,3 +15,6 @@ EXTRA_OECONF += "--disable-shared"
 COMPILERINITIAL = "-initial"
 
 inherit nopackages
+
+# We really only want this built by things that need it, not any recrdeptask
+deltask do_build
-- 
2.7.4

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


Re: [OE-core] [PATCH] oe-selftest: test wic sparse_copy API

2017-04-06 Thread Richard Purdie
On Tue, 2017-04-04 at 14:10 +0300, Ed Bartosh wrote:
> Added new parameter 'api' to sparse_copy function to specify
> underlying filemap API to use. By default sparse_copy will
> try both available APIs.
> 
> Added test case for sparse_copy to wic test suite.
> 
> Signed-off-by: Ed Bartosh 
> ---
>  meta/lib/oeqa/selftest/wic.py | 26 ++
>  scripts/lib/wic/filemap.py|  6 --
>  2 files changed, 30 insertions(+), 2 deletions(-)

This failed on the autobuilder:

https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/244/steps/Running%20oe-selftest/logs/stdio

Cheers,

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


[OE-core] [PATCH] eudev: set LGPL-2.1+ for libudev package

2017-04-06 Thread Martin Jansa
Signed-off-by: Martin Jansa 
---
 meta/recipes-core/udev/eudev_3.2.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-core/udev/eudev_3.2.1.bb 
b/meta/recipes-core/udev/eudev_3.2.1.bb
index 4a1a26aade..bdfb5441ad 100644
--- a/meta/recipes-core/udev/eudev_3.2.1.bb
+++ b/meta/recipes-core/udev/eudev_3.2.1.bb
@@ -1,6 +1,7 @@
 SUMMARY = "eudev is a fork of systemd's udev"
 HOMEPAGE = "https://wiki.gentoo.org/wiki/Eudev";
-LICENSE = "GPLv2.0+"
+LICENSE = "GPLv2.0+ & LGPL-2.1+"
+LICENSE_libudev = "LGPL-2.1+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
 
 DEPENDS = "glib-2.0 glib-2.0-native gperf-native kmod libxslt-native 
util-linux"
-- 
2.12.2

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


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

2017-04-06 Thread Jussi Kukkonen
On 6 April 2017 at 12:23, David Vincent  wrote:
>
> On mercredi 5 avril 2017 09:30:52 CEST Jussi Kukkonen wrote:
> > This apparently breaks key generation with openssl-native because the
file
> > doesn't exist.
>
> Looking at the recipe right now, I understand why key generation is
broken for
> native build (I should have been more careful). I see two ways of fixing
it :
> - either recreate the symlink in do_install_append_class_native
> - or simply modifiyng the OPENSSL_CONF variable in the same task.
>
> >
> > I can fix it by adding one more complication to the recipe (will send a
> > patch) but I don't think the current solution is all that great: I've
been
> > looking at this patch for a while now and still don't really understand
why
> > it is needed and how these different packages interact. I'm sure it
makes
> > sense when you look at the other recipe but ... isn't it a bad sign that
> > that context seems to be needed?
>
> OK, I will provide some context because maybe my approach was wrong. In
some
> of my builds, I require some images to have a very specific configuration
to
> make OpenSSL use engines. My idea was to provide a package for this task
since
> the default file can not be overridden (and in fact shouldn't be for the
native
> build).


So previously openssl-conf package included etc/ssl/openssl.cnf and the
symlink ${libdir}/ssl/openssl.conf. Nothing RDEPENDS on this package (but
libcrypto RRECOMMENDS it).

After your patch the actual configuration file is still installed. In a
postinst
  * ${libdir}/ssl/openssl.conf is removed if it exists (why? If it's for
upgrading, then this should happen in a prerm or postrm)
  * the symlink ${libdir}/ssl/openssl.conf is created

My confusion is this: how does the above solve the problem you describe? If
you've managed to use RCONFLICTS to prevent the configuration package from
getting included in the image, why are changes to the package needed?



Some alternative solutions to your problem I think might work:
* openssl_%.bbappend with a do_install_append() that simply copies your
conf file over the one from upstream recipe. No extra packages needed
* BAD_RECOMMENDATIONS or PACKAGE_EXCLUDE to prevent openssl-conf from
getting included in your image, then adding your own package with your
configuration (does not work for dpkg I think)

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


Re: [OE-core] [PATCH 1/2] scripts: change way we find native tools (pseudo)

2017-04-06 Thread Robert Yang

Hi Brian and RP,

This patch can't fix the problem of scripts/oe-run-native, it only can
run the native tools which is depended by meta-ide-support, for example:

$ bitbake bmap-tools-native meta-ide-support
$ oe-run-native bmaptool --help # exmaple from dev-manual-start.xml

Error: Unable to find 'bmaptool' in native sysroot

I think that we need consider the patch that I had sent before:

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

Robert Yang (1):
  oe-find-native-sysroot: work with RSS


Subject: [PATCH 1/1] oe-find-native-sysroot: work with RSS

The generic STAGING_DIR_NATIVE is gone since RSS, so when find
OECORE_NATIVE_SYSROOT, the user has to specify which recipe's
STAGING_DIR_NATIVE will be used as OECORE_NATIVE_SYSROOT.

* The usage is changed from ". oe-find-native-sysroot" to
  ". oe-find-native-sysroot ".
* The oe-run-native's usage has changed from
  "oe-run-native tool" to "oe-run-native native-recipe tool".

Signed-off-by: Robert Yang 
---
 scripts/oe-find-native-sysroot | 56 --
 scripts/oe-run-native  | 15 +++
 scripts/runqemu-export-rootfs  |  2 +-
 scripts/runqemu-extract-sdk|  2 +-
 4 files changed, 49 insertions(+), 26 deletions(-)

diff --git a/scripts/oe-find-native-sysroot b/scripts/oe-find-native-sysroot
index 3f4c29da8a..59fe3f3118 100755
--- a/scripts/oe-find-native-sysroot
+++ b/scripts/oe-find-native-sysroot
@@ -9,7 +9,7 @@
 # it, e.g:
 #
 # SYSROOT_SETUP_SCRIPT=`which oe-find-native-sysroot`
-# . $SYSROOT_SETUP_SCRIPT
+# . $SYSROOT_SETUP_SCRIPT 
 #
 # This script will terminate execution of your calling program unless
 # you set a variable $SKIP_STRICT_SYSROOT_CHECK to a non-empty string
@@ -30,8 +30,8 @@
 # with this program; if not, write to the Free Software Foundation, Inc.,
 # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

-if [ "$1" = '--help' -o "$1" = '-h' ] ; then
-echo 'Usage: oe-find-native-sysroot [-h|--help]'
+if [ "$1" = '--help' -o "$1" = '-h' -o $# -ne 1 ] ; then
+echo 'Usage: oe-find-native-sysroot  [-h|--help]'
 echo ''
 echo 'OpenEmbedded find-native-sysroot - helper script to set'
 echo 'environment variables OECORE_NATIVE_SYSROOT and PSEUDO'
@@ -39,11 +39,31 @@ if [ "$1" = '--help' -o "$1" = '-h' ] ; then
 echo 'executable binary'
 echo ''
 echo 'options:'
+echo '  recipe  its STAGING_DIR_NATIVE is used as native 
sysroot'
 echo '  -h, --help  show this help message and exit'
 echo ''
 exit 2
 fi

+# Global vars
+BITBAKE_E=""
+OECORE_NATIVE_SYSROOT=""
+
+set_oe_native_sysroot(){
+echo "Running bitbake -e $1"
+BITBAKE_E="`bitbake -e $1`"
+OECORE_NATIVE_SYSROOT=`echo "$BITBAKE_E" | grep ^STAGING_DIR_NATIVE | cut 
-d '"' -f2`

+
+if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
+# This indicates that there was an error running bitbake -e that
+# the user needs to be informed of
+echo "There was an error running bitbake to determine 
STAGING_DIR_NATIVE"
+echo "Here is the output from bitbake -e $1"
+echo "$BITBAKE_E"
+exit 1
+fi
+}
+
 if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
 BITBAKE=`which bitbake 2> /dev/null`
 if [ "x$BITBAKE" != "x" ]; then
@@ -54,10 +74,10 @@ if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
 exit 1
 fi
 touch conf/sanity.conf
-OECORE_NATIVE_SYSROOT=`bitbake -e meta-ide-support | grep 
^RECIPE_SYSROOT_NATIVE | cut -d '"' -f2`

+set_oe_native_sysroot $1
 rm -f conf/sanity.conf
 else
-OECORE_NATIVE_SYSROOT=`bitbake -e meta-ide-support | grep 
^RECIPE_SYSROOT_NATIVE | cut -d '"' -f2`

+set_oe_native_sysroot $1
 fi
 else
 echo "Error: Unable to locate bitbake command."
@@ -69,21 +89,11 @@ if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
 fi
 fi

-if [ "x$OECORE_NATIVE_SYSROOT" = "x" ]; then
-# This indicates that there was an error running bitbake -e that
-# the user needs to be informed of
-echo "There was an error running bitbake to determine 
RECIPE_SYSROOT_NATIVE"
-echo "Here is the output from bitbake -e"
-bitbake -e
-exit 1
-fi
-
-# Set up pseudo command
-if [ ! -e "$OECORE_NATIVE_SYSROOT/usr/bin/pseudo" ]; then
-echo "Error: Unable to find pseudo binary in 
$OECORE_NATIVE_SYSROOT/usr/bin/"
+if [ ! -e "$OECORE_NATIVE_SYSROOT/" ]; then
+echo "Error: $OECORE_NATIVE_SYSROOT doesn't exist."

 if [ "x$OECORE_DISTRO_VERSION" = "x" ]; then
-echo "Have you run 'bitbake meta-ide-support'?"
+echo "Have you run 'bitbake $1 -caddto_recipe_sysroot'?"
 else
 echo "This shouldn't happen - something is wrong with your toolchain 
installation"

 fi
@@ -92,4 +102,12 @@ if [ ! -e "$OECORE_NATIVE_SYSROOT/usr/bin/pseudo" ]; then
 exit 1
 fi
 fi
-P

[OE-core] [PATCH 7/7] kmod: set ac_cv_path_DOLT_BASH to /usr/bin/env bash

2017-04-06 Thread Robert Yang
The shebang's length is usually 128 as defined in /usr/include/linux/binfmts.h:
  #define BINPRM_BUF_SIZE 128

So there would be errors when /path/to/hosttools/bash is longer than 128:

/bin/sh: ./doltcompile: [snip]: bad interpreter: No such file or directory

Set ac_cv_path_DOLT_BASH to "/usr/bin/env bash" to fix the problem.

Signed-off-by: Robert Yang 
---
 meta/recipes-kernel/kmod/kmod.inc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-kernel/kmod/kmod.inc 
b/meta/recipes-kernel/kmod/kmod.inc
index cfa409dbb3..ba80fc57a3 100644
--- a/meta/recipes-kernel/kmod/kmod.inc
+++ b/meta/recipes-kernel/kmod/kmod.inc
@@ -30,6 +30,8 @@ S = "${WORKDIR}/git"
 EXTRA_AUTORECONF += "--install --symlink"
 EXTRA_OECONF +=" --enable-tools --with-zlib"
 
+CACHED_CONFIGUREVARS += "ac_cv_path_DOLT_BASH='/usr/bin/env bash'"
+
 PACKAGECONFIG[debug] = "--enable-debug,--disable-debug"
 PACKAGECONFIG[logging] = " --enable-logging,--disable-logging"
 PACKAGECONFIG[manpages] = "--enable-manpages, --disable-manpages, 
libxslt-native xmlto-native"
-- 
2.11.0.rc2.dirty

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


[OE-core] [PATCH 6/7] autogen-native: fix POSIX_SHELL and perl

2017-04-06 Thread Robert Yang
The shebang's length is usually 128 as defined in /usr/include/linux/binfmts.h:
  #define BINPRM_BUF_SIZE 128

So there would be errors when /path/to/hosttools/perl is longer than 128.

This patch fixes the problem when POSIX_SHELL and perl are used as the 
interpreters.

Signed-off-by: Robert Yang 
---
 .../autogen/autogen-native_5.18.12.bb  |  3 ++
 ...2-autoopts-mk-tpl-config.sh-fix-perl-path.patch | 32 ++
 2 files changed, 35 insertions(+)
 create mode 100644 
meta/recipes-devtools/autogen/autogen/0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch

diff --git a/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb 
b/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb
index 0004389b11..853477cf7c 100644
--- a/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb
+++ b/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb
@@ -13,6 +13,7 @@ SRC_URI = 
"${GNU_MIRROR}/autogen/rel${PV}/autogen-${PV}.tar.gz \
file://mk-tpl-config.sh-force-exit-value-to-be-0-in-subproc.patch \
file://fix-script-err-when-processing-libguile.patch \

file://0001-config-libopts.m4-regenerate-it-from-config-libopts..patch \
+   file://0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch \
 "
 
 SRC_URI[md5sum] = "551d15ccbf5b5fc5658da375d5003389"
@@ -30,6 +31,8 @@ inherit autotools texinfo native pkgconfig
 export GUILE_LOAD_PATH = "${STAGING_DATADIR_NATIVE}/guile/2.0"
 export GUILE_LOAD_COMPILED_PATH = "${STAGING_LIBDIR_NATIVE}/guile/2.0/ccache"
 
+export POSIX_SHELL = "/usr/bin/env sh"
+
 do_install_append () {
create_wrapper ${D}/${bindir}/autogen \
GUILE_LOAD_PATH=${STAGING_DATADIR_NATIVE}/guile/2.0 \
diff --git 
a/meta/recipes-devtools/autogen/autogen/0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch
 
b/meta/recipes-devtools/autogen/autogen/0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch
new file mode 100644
index 00..d5fe143ce4
--- /dev/null
+++ 
b/meta/recipes-devtools/autogen/autogen/0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch
@@ -0,0 +1,32 @@
+From 9f69f3f5ef22bf1bcffb0e651efc260889cfaa46 Mon Sep 17 00:00:00 2001
+From: Robert Yang 
+Date: Mon, 13 Mar 2017 20:33:30 -0700
+Subject: [PATCH] autoopts/mk-tpl-config.sh: fix perl path
+
+Use "which perl" as shebang doesn't work when it is longer than
+BINPRM_BUF_SIZE which is 128 usually. So use "/usr/bin/env perl" to
+instead of.
+
+Upstream-Status: Pending
+
+Signed-off-by: Robert Yang 
+---
+ autoopts/mk-tpl-config.sh | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/autoopts/mk-tpl-config.sh b/autoopts/mk-tpl-config.sh
+index 093e808..8dfc6dd 100755
+--- a/autoopts/mk-tpl-config.sh
 b/autoopts/mk-tpl-config.sh
+@@ -98,7 +98,7 @@ fix_scripts() {
+ st=`sed 1q $f`
+ 
+ case "$st" in
+-*perl ) echo '#!' `which perl`
++*perl ) echo '#!/usr/bin/env perl'
+  sed 1d $f
+  ;;
+ 
+-- 
+2.10.2
+
-- 
2.11.0.rc2.dirty

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


[OE-core] [PATCH 4/7] m4: do_configure: fix "Argument list too long"

2017-04-06 Thread Robert Yang
Fixed when len(TMPDIR) =  410:
Can't exec "/bin/sh": Argument list too long at /usr/lib/perl/5.18/IO/File.pm 
line 65.

This is becuase it has a lot of m4 files, use relative path for them
can fix the problem.

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/m4/m4-1.4.18.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/m4/m4-1.4.18.inc 
b/meta/recipes-devtools/m4/m4-1.4.18.inc
index 5652b74308..d7c8648577 100644
--- a/meta/recipes-devtools/m4/m4-1.4.18.inc
+++ b/meta/recipes-devtools/m4/m4-1.4.18.inc
@@ -15,5 +15,8 @@ SRC_URI_append_class-target = "\
file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
   "
 
+# Fix "Argument list too long" error when len(TMPDIR) = 410
+acpaths = "-I ./m4"
+
 SRC_URI[md5sum] = "a09db287adf4e12a035029002d28"
 SRC_URI[sha256sum] = 
"ab2633921a5cd38e48797bf5521ad259bdc4b979078034a3b790d7fec5493fab"
-- 
2.11.0.rc2.dirty

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


[OE-core] [PATCH 5/7] guile: do_configure: fix "Argument list too long"

2017-04-06 Thread Robert Yang
Fixed when len(TMPDIR) =  410:
Can't exec "/bin/sh": Argument list too long at /usr/lib/perl/5.18/IO/File.pm 
line 65.

This is becuase it has a lot of m4 files, use relative path for them
can fix the problem.

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/guile/guile_2.0.14.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/guile/guile_2.0.14.bb 
b/meta/recipes-devtools/guile/guile_2.0.14.bb
index d2306e6a75..7a36ba0c3b 100644
--- a/meta/recipes-devtools/guile/guile_2.0.14.bb
+++ b/meta/recipes-devtools/guile/guile_2.0.14.bb
@@ -30,6 +30,9 @@ SRC_URI[sha256sum] = 
"e8442566256e1be14e51fc18839cd799b966bc5b16c6a1d7a7c35155a8
 inherit autotools gettext pkgconfig texinfo
 BBCLASSEXTEND = "native"
 
+# Fix "Argument list too long" error when len(TMPDIR) = 410
+acpaths = "-I ./m4"
+
 DEPENDS = "libunistring bdwgc gmp libtool libffi ncurses readline"
 # add guile-native only to the target recipe's DEPENDS
 DEPENDS_append_class-target = " guile-native libatomic-ops"
-- 
2.11.0.rc2.dirty

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


[OE-core] [PATCH 3/7] valgrind: set ac_cv_path_PERL to /usr/bin/env perl

2017-04-06 Thread Robert Yang
The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
  #define BINPRM_BUF_SIZE 128

So there would be errors when /path/to/hosttools/perl is longer than 128.

Set ac_cv_path_PERL to "/usr/bin/env perl" to fix the problem.

Signed-off-by: Robert Yang 
---
 meta/recipes-devtools/valgrind/valgrind_3.12.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/valgrind/valgrind_3.12.0.bb 
b/meta/recipes-devtools/valgrind/valgrind_3.12.0.bb
index a4a3e72ecd..62a96354cd 100644
--- a/meta/recipes-devtools/valgrind/valgrind_3.12.0.bb
+++ b/meta/recipes-devtools/valgrind/valgrind_3.12.0.bb
@@ -56,6 +56,8 @@ EXTRA_OECONF_append_arm = " 
--host=armv7${HOST_VENDOR}-${HOST_OS}"
 
 EXTRA_OEMAKE = "-w"
 
+CACHED_CONFIGUREVARS += "ac_cv_path_PERL='/usr/bin/env perl'"
+
 # valgrind likes to control its own optimisation flags. It generally defaults
 # to -O2 but uses -O0 for some specific test apps etc. Passing our own flags
 # (via CFLAGS) means we interfere with that. Only pass DEBUG_FLAGS to it
-- 
2.11.0.rc2.dirty

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


[OE-core] [PATCH 1/7] groff: replace "perl -w" with "use warnings"

2017-04-06 Thread Robert Yang
The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
  #define BINPRM_BUF_SIZE 128

There would be errors when @PERL@ (hostools/perl) is longer than 128,
use '/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
doesn't work:

/usr/bin/env: perl -w: No such file or directory

So replace "perl -w" with "use warnings" to make it work.

Signed-off-by: Robert Yang 
---
 .../0001-replace-perl-w-with-use-warnings.patch| 102 +
 meta/recipes-extended/groff/groff_1.22.3.bb|   3 +
 2 files changed, 105 insertions(+)
 create mode 100644 
meta/recipes-extended/groff/groff-1.22.3/0001-replace-perl-w-with-use-warnings.patch

diff --git 
a/meta/recipes-extended/groff/groff-1.22.3/0001-replace-perl-w-with-use-warnings.patch
 
b/meta/recipes-extended/groff/groff-1.22.3/0001-replace-perl-w-with-use-warnings.patch
new file mode 100644
index 00..f1db5b0653
--- /dev/null
+++ 
b/meta/recipes-extended/groff/groff-1.22.3/0001-replace-perl-w-with-use-warnings.patch
@@ -0,0 +1,102 @@
+From 5b574542070db286c89b3827e8f15ed4b3b39034 Mon Sep 17 00:00:00 2001
+From: Robert Yang 
+Date: Thu, 6 Apr 2017 01:46:00 -0700
+Subject: [PATCH] replace "perl -w" with "use warnings"
+
+The shebang's max length is usually 128 as defined in
+/usr/include/linux/binfmts.h:
+  #define BINPRM_BUF_SIZE 128
+
+There would be errors when @PERL@ is longer than 128, use
+'/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
+doesn't work:
+
+/usr/bin/env: perl -w: No such file or directory
+
+So replace "perl -w" with "use warnings" to make it work.
+
+Upstream-Status: Pending
+
+Signed-off-by: Robert Yang 
+---
+ font/devpdf/util/BuildFoundries.pl | 3 ++-
+ src/devices/gropdf/gropdf.pl   | 3 ++-
+ src/devices/gropdf/pdfmom.pl   | 3 ++-
+ src/utils/afmtodit/afmtodit.pl | 3 ++-
+ 4 files changed, 8 insertions(+), 4 deletions(-)
+
+diff --git a/font/devpdf/util/BuildFoundries.pl 
b/font/devpdf/util/BuildFoundries.pl
+index 39f2f0d..a2bfd8e 100644
+--- a/font/devpdf/util/BuildFoundries.pl
 b/font/devpdf/util/BuildFoundries.pl
+@@ -1,4 +1,4 @@
+-#!/usr/bin/perl -w
++#!/usr/bin/perl
+ #
+ #   BuildFoundries   : Given a Foundry file generate groff and download files
+ #   Deri James   : Monday 07 Feb 2011
+@@ -22,6 +22,7 @@
+ # along with this program. If not, see .
+ 
+ use strict;
++use warnings;
+ 
+ my $where=shift||'';
+ my $devps=shift||'../devps';
+diff --git a/src/devices/gropdf/gropdf.pl b/src/devices/gropdf/gropdf.pl
+index 035d123..b933b32 100644
+--- a/src/devices/gropdf/gropdf.pl
 b/src/devices/gropdf/gropdf.pl
+@@ -1,4 +1,4 @@
+-#!@PERL@ -w
++#!@PERL@
+ #
+ # gropdf  : PDF post processor for groff
+ #
+@@ -21,6 +21,7 @@
+ # along with this program. If not, see .
+ 
+ use strict;
++use warnings;
+ use Getopt::Long qw(:config bundling);
+ use Compress::Zlib;
+ 
+diff --git a/src/devices/gropdf/pdfmom.pl b/src/devices/gropdf/pdfmom.pl
+index beec820..4b46ea4 100644
+--- a/src/devices/gropdf/pdfmom.pl
 b/src/devices/gropdf/pdfmom.pl
+@@ -1,4 +1,4 @@
+-#!@PERL@ -w
++#!@PERL@
+ #
+ # pdfmom  : Frontend to run groff -mom to produce PDFs
+ # Deri James  : Friday 16 Mar 2012
+@@ -24,6 +24,7 @@
+ # along with this program. If not, see .
+ 
+ use strict;
++use warnings;
+ use File::Temp qw/tempfile/;
+ my @cmd;
+ my $dev='pdf';
+diff --git a/src/utils/afmtodit/afmtodit.pl b/src/utils/afmtodit/afmtodit.pl
+index 4f2ce83..5c078ff 100644
+--- a/src/utils/afmtodit/afmtodit.pl
 b/src/utils/afmtodit/afmtodit.pl
+@@ -1,4 +1,4 @@
+-#! /usr/bin/perl -w
++#! /usr/bin/perl
+ # -*- Perl -*-
+ # Copyright (C) 1989-2014  Free Software Foundation, Inc.
+ #  Written by James Clark (j...@jclark.com)
+@@ -19,6 +19,7 @@
+ # along with this program. If not, see .
+ 
+ use strict;
++use warnings;
+ 
+ @afmtodit.tables@
+ 
+-- 
+2.10.2
+
diff --git a/meta/recipes-extended/groff/groff_1.22.3.bb 
b/meta/recipes-extended/groff/groff_1.22.3.bb
index dd241f3f84..7472f59825 100644
--- a/meta/recipes-extended/groff/groff_1.22.3.bb
+++ b/meta/recipes-extended/groff/groff_1.22.3.bb
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
 SRC_URI = "${GNU_MIRROR}/groff/groff-${PV}.tar.gz \
file://groff-1.22.2-correct-man.local-install-path.patch \
file://0001-Unset-need_charset_alias-when-building-for-musl.patch \
+   file://0001-replace-perl-w-with-use-warnings.patch \
 "
 
 SRC_URI[md5sum] = "cc825fa64bc7306a885f2fb2268d3ec5"
@@ -24,6 +25,8 @@ inherit autotools texinfo
 EXTRA_OECONF = "--without-x"
 PARALLEL_MAKE = ""
 
+CACHED_CONFIGUREVARS += "ac_cv_path_PERL='/usr/bin/env perl'"
+
 do_configure_prepend() {
if [ "${BUILD_SYS}" != "${HOST_SYS}" ]; then
sed -i \
-- 
2.11.0.rc2.dirty

-- 

[OE-core] [PATCH 2/7] mc: replace "perl -w" with "use warnings"

2017-04-06 Thread Robert Yang
The shebang's max length is usually 128 as defined in
/usr/include/linux/binfmts.h:
  #define BINPRM_BUF_SIZE 128

There would be errors when @PERL@ (hostools/perl) is longer than 128,
use '/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
doesn't work:

/usr/bin/env: perl -w: No such file or directory

So replace "perl -w" with "use warnings" to make it work.

Signed-off-by: Robert Yang 
---
 .../0001-mc-replace-perl-w-with-use-warnings.patch | 129 +
 meta/recipes-extended/mc/mc_4.8.18.bb  |   3 +
 2 files changed, 132 insertions(+)
 create mode 100644 
meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch

diff --git 
a/meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch 
b/meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch
new file mode 100644
index 00..bf8037cd28
--- /dev/null
+++ 
b/meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch
@@ -0,0 +1,129 @@
+From cdc7c278212ae836eecb4cc9d42c29443cc128a0 Mon Sep 17 00:00:00 2001
+From: Robert Yang 
+Date: Thu, 6 Apr 2017 02:24:28 -0700
+Subject: [PATCH] mc: replace "perl -w" with "use warnings"
+
+The shebang's max length is usually 128 as defined in
+/usr/include/linux/binfmts.h:
+  #define BINPRM_BUF_SIZE 128
+
+There would be errors when @PERL@ is longer than 128, use
+'/usr/bin/env perl' can fix the problem, but '/usr/bin/env perl -w'
+doesn't work:
+
+/usr/bin/env: perl -w: No such file or directory
+
+So replace "perl -w" with "use warnings" to make it work.
+
+The man2hlp.in already has "use warnings;", so just remove '-w' is OK.
+
+Upstream-Status: Pending
+
+Signed-off-by: Robert Yang 
+---
+ src/man2hlp/man2hlp.in   | 2 +-
+ src/vfs/extfs/helpers/a+.in  | 4 +++-
+ src/vfs/extfs/helpers/mailfs.in  | 3 ++-
+ src/vfs/extfs/helpers/patchfs.in | 3 ++-
+ src/vfs/extfs/helpers/ulib.in| 4 +++-
+ src/vfs/extfs/helpers/uzip.in| 3 ++-
+ 6 files changed, 13 insertions(+), 6 deletions(-)
+
+diff --git a/src/man2hlp/man2hlp.in b/src/man2hlp/man2hlp.in
+index f095830..558a674 100644
+--- a/src/man2hlp/man2hlp.in
 b/src/man2hlp/man2hlp.in
+@@ -1,4 +1,4 @@
+-#! @PERL@ -w
++#! @PERL@
+ #
+ #  Man page to help file converter
+ #  Copyright (C) 1994, 1995, 1998, 2000, 2001, 2002, 2003, 2004, 2005,
+diff --git a/src/vfs/extfs/helpers/a+.in b/src/vfs/extfs/helpers/a+.in
+index 579441c..fe446f4 100644
+--- a/src/vfs/extfs/helpers/a+.in
 b/src/vfs/extfs/helpers/a+.in
+@@ -1,4 +1,4 @@
+-#! @PERL@ -w
++#! @PERL@
+ #
+ # External filesystem for mc, using mtools
+ # Written Ludek Brukner , 1997
+@@ -9,6 +9,8 @@
+ 
+ # These mtools components must be in PATH for this to work
+ 
++use warnings;
++
+ sub quote {
+ $_ = shift(@_);
+ s/([^\w\/.+-])/\\$1/g;
+diff --git a/src/vfs/extfs/helpers/mailfs.in b/src/vfs/extfs/helpers/mailfs.in
+index e9455be..059f41f 100644
+--- a/src/vfs/extfs/helpers/mailfs.in
 b/src/vfs/extfs/helpers/mailfs.in
+@@ -1,6 +1,7 @@
+-#! @PERL@ -w
++#! @PERL@
+ 
+ use bytes;
++use warnings;
+ 
+ # MC extfs for (possibly compressed) Berkeley style mailbox files
+ # Peter Daum  (Jan 1998, mc-4.1.24)
+diff --git a/src/vfs/extfs/helpers/patchfs.in 
b/src/vfs/extfs/helpers/patchfs.in
+index ef407de..3ad4b53 100644
+--- a/src/vfs/extfs/helpers/patchfs.in
 b/src/vfs/extfs/helpers/patchfs.in
+@@ -1,4 +1,4 @@
+-#! @PERL@ -w
++#! @PERL@
+ #
+ # Written by Adam Byrtek , 2002
+ # Rewritten by David Sterba , 2009
+@@ -9,6 +9,7 @@
+ 
+ use bytes;
+ use strict;
++use warnings;
+ use POSIX;
+ use File::Temp 'tempfile';
+ 
+diff --git a/src/vfs/extfs/helpers/ulib.in b/src/vfs/extfs/helpers/ulib.in
+index 418611f..82c7ccf 100644
+--- a/src/vfs/extfs/helpers/ulib.in
 b/src/vfs/extfs/helpers/ulib.in
+@@ -1,9 +1,11 @@
+-#! @PERL@ -w
++#! @PERL@
+ #
+ # VFS to manage the gputils archives.
+ # Written by Molnár Károly (prot...@freemail.hu) 2012
+ #
+ 
++use warnings;
++
+ my %month = ('jan' => '01', 'feb' => '02', 'mar' => '03',
+  'apr' => '04', 'may' => '05', 'jun' => '06',
+  'jul' => '07', 'aug' => '08', 'sep' => '09',
+diff --git a/src/vfs/extfs/helpers/uzip.in b/src/vfs/extfs/helpers/uzip.in
+index b1c4f90..c8eb335 100644
+--- a/src/vfs/extfs/helpers/uzip.in
 b/src/vfs/extfs/helpers/uzip.in
+@@ -1,4 +1,4 @@
+-#! @PERL@ -w
++#! @PERL@
+ #
+ # zip file archive Virtual File System for Midnight Commander
+ # Version 1.4.0 (2001-08-07).
+@@ -9,6 +9,7 @@
+ use POSIX;
+ use File::Basename;
+ use strict;
++use warnings;
+ 
+ #
+ # Configuration options
+-- 
+2.10.2
+
diff --git a/meta/recipes-extended/mc/mc_4.8.18.bb 
b/meta/recipes-extended/mc/mc_4.8.18.bb
index 78abb275ba..17f3f73af7 100644
--- a/meta/recipes-extended/mc/mc_4.8.18.bb
+++ b/meta/recipes-extended/mc/mc_4.8.18.bb
@@ -7,6 +7,7 @@ DEPENDS = "ncurses glib-2.0 util-linux"
 RDEPENDS_${PN} = "ncurses-terminfo"
 
 SRC_URI = "http://www.midnight-commander.org/downloads/${BPN}-${PV}.tar.bz2 \
+ 

[OE-core] [PATCH 0/7 V2] fixes for building in long path (length = 410)

2017-04-06 Thread Robert Yang
* V2:
  Use '/usr/bin/env foo' rather than /usr/bin/foo or /bin/foo as shebang.

// Robert

The following changes since commit 901659a51cd53625a93f57a9c5865e90a07ec09d:

  oeqa/runtime/utils/targetbuildproject: use parent classes defaults tmpdir 
(2017-04-06 10:13:34 +0100)

are available in the git repository at:

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

Robert Yang (7):
  groff: replace "perl -w" with "use warnings"
  mc: replace "perl -w" with "use warnings"
  valgrind: set ac_cv_path_PERL to /usr/bin/env perl
  m4: do_configure: fix "Argument list too long"
  guile: do_configure: fix "Argument list too long"
  autogen-native: fix POSIX_SHELL and perl
  kmod: set ac_cv_path_DOLT_BASH to /usr/bin/env bash

 .../autogen/autogen-native_5.18.12.bb  |   3 +
 ...2-autoopts-mk-tpl-config.sh-fix-perl-path.patch |  32 +
 meta/recipes-devtools/guile/guile_2.0.14.bb|   3 +
 meta/recipes-devtools/m4/m4-1.4.18.inc |   3 +
 meta/recipes-devtools/valgrind/valgrind_3.12.0.bb  |   2 +
 .../0001-replace-perl-w-with-use-warnings.patch| 102 
 meta/recipes-extended/groff/groff_1.22.3.bb|   3 +
 .../0001-mc-replace-perl-w-with-use-warnings.patch | 129 +
 meta/recipes-extended/mc/mc_4.8.18.bb  |   3 +
 meta/recipes-kernel/kmod/kmod.inc  |   2 +
 10 files changed, 282 insertions(+)
 create mode 100644 
meta/recipes-devtools/autogen/autogen/0002-autoopts-mk-tpl-config.sh-fix-perl-path.patch
 create mode 100644 
meta/recipes-extended/groff/groff-1.22.3/0001-replace-perl-w-with-use-warnings.patch
 create mode 100644 
meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch

-- 
2.11.0.rc2.dirty

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


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

2017-04-06 Thread David Vincent
On mercredi 5 avril 2017 09:30:52 CEST Jussi Kukkonen wrote:
> This apparently breaks key generation with openssl-native because the file
> doesn't exist.

Looking at the recipe right now, I understand why key generation is broken for 
native build (I should have been more careful). I see two ways of fixing it :
- either recreate the symlink in do_install_append_class_native
- or simply modifiyng the OPENSSL_CONF variable in the same task.

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

OK, I will provide some context because maybe my approach was wrong. In some 
of my builds, I require some images to have a very specific configuration to 
make OpenSSL use engines. My idea was to provide a package for this task since 
the default file can not be overridden (and in fact shouldn't be for the native 
build). This way, using RCONFLICTS I can provide a new configuration package 
for these specific builds while maintaining the default behavior for all 
others.

> 
> Jussi
> 

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


[OE-core] ✗ patchtest: failure for Remove all use of fedorahosted SRC_URI [YOCTO #11226] (rev3)

2017-04-06 Thread Patchwork
== Series Details ==

Series: Remove all use of fedorahosted SRC_URI [YOCTO #11226] (rev3)
Revision: 3
URL   : https://patchwork.openembedded.org/series/6116/
State : failure

== Summary ==


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



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



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

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

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


[OE-core] [PATCH v3 6/8] liberation-fonts: replace fedorahosted.org SRC_URI with pagure.io source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb 
b/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb
index bda82e7..74212e7 100644
--- a/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb
+++ b/meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb
@@ -2,7 +2,7 @@ SUMMARY = "Liberation(tm) Fonts"
 DESCRIPTION = "The Liberation(tm) Fonts is a font family originally \
 created by Ascender(c) which aims at metric compatibility with \
 Arial, Times New Roman, Courier New."
-HOMEPAGE = "https://fedorahosted.org/liberation-fonts/";
+HOMEPAGE = "https://releases.pagure.org/liberation-fonts/";
 BUGTRACKER = "https://bugzilla.redhat.com/";
 
 RECIPE_NO_UPDATE_REASON = "2.x depends on fontforge package, which is not yet 
provided in oe-core"
@@ -17,7 +17,7 @@ inherit allarch fontcache
 
 FONT_PACKAGES = "${PN}"
 
-SRC_URI = 
"https://fedorahosted.org/releases/l/i/liberation-fonts/liberation-fonts-${PV}.tar.gz
 \
+SRC_URI = 
"https://releases.pagure.org/liberation-fonts/liberation-fonts-${PV}.tar.gz \
file://30-liberation-aliases.conf"
 
 SRC_URI[md5sum] = "4846797ef0fc70b0cbaede2514677c58"
-- 
2.7.4

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


[OE-core] [PATCH v3 7/8] chkconfig: replace fedorahosted.org SRC_URI with github.com source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to update
the SRC_URI to point to github.com.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb 
b/meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb
index e839026..e29fb99 100644
--- a/meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb
+++ b/meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb
@@ -6,7 +6,7 @@ of the drudgery of manually editing the symbolic links."
 
 RECIPE_NO_UPDATE_REASON = "Version 1.5 requires selinux"
 
-HOMEPAGE = "http://fedorahosted.org/releases/c/h/chkconfig";
+HOMEPAGE = "https://github.com/fedora-sysv";
 
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=5574c6965ae5f583e55880e397fbb018"
@@ -16,12 +16,18 @@ PROVIDES += "virtual/update-alternatives"
 
 PR = "r7"
 
-SRC_URI = "http://fedorahosted.org/releases/c/h/chkconfig/${BPN}-${PV}.tar.bz2 
\
+S = "${WORKDIR}/${BPN}-${BPN}-${PV}"
+
+UPSTREAM_CHECK_URI = "https://github.com/fedora-sysv/${BPN}/releases";
+
+SRC_URI = 
"https://github.com/fedora-sysv/chkconfig/archive/chkconfig-${PV}.tar.gz \
file://replace_caddr_t.patch \
   "
 
-SRC_URI[md5sum] = "c2039ca67f2749fe0c06ef7c6f8ee246"
-SRC_URI[sha256sum] = 
"18b497d25b2cada955c72810e45fcad8280d105f17cf45e2970f18271211de68"
+# Checksum changed due to tarball source folder changes in upstream
+
+SRC_URI[md5sum] = "3f51ac38a234be5278b3a2d9705eda5e"
+SRC_URI[sha256sum] = 
"bf1e81f0d7cc999b536c9fe7877abf584a4082fd03c9d2597b6f090966579b40"
 
 inherit gettext
 
-- 
2.7.4

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


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

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-extended/logrotate/logrotate_3.9.1.bb | 19 +++
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb 
b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
index 9c2dfe0..5cbd9ff 100644
--- a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
+++ b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
@@ -1,6 +1,6 @@
 SUMMARY = "Rotates, compresses, removes and mails system log files"
 SECTION = "console/utils"
-HOMEPAGE = "https://fedorahosted.org/logrotate/";
+HOMEPAGE = "https://github.com/logrotate/logrotate/issues";
 LICENSE = "GPLv2"
 
 # TODO: logrotate 3.8.8 adds autotools/automake support, update recipe to use 
it.
@@ -10,14 +10,25 @@ DEPENDS="coreutils popt"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=18810669f13b87348459e611d31ab760"
 
-SRC_URI = 
"https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.gz \
+# When updating logrotate to latest upstream, SRC_URI should point to
+# a proper release tarball from https://github.com/logrotate/logrotate/releases
+# and we have to take the snapshot for now because there is no such
+# tarball available for 3.9.1.
+
+S = "${WORKDIR}/${PN}-r3-9-1"
+
+UPSTREAM_CHECK_URI = "https://github.com/${PN}/${PN}/releases";
+
+SRC_URI = "https://github.com/${PN}/${PN}/archive/r3-9-1.tar.gz \
file://act-as-mv-when-rotate.patch \
file://update-the-manual.patch \
file://disable-check-different-filesystems.patch \
 "
 
-SRC_URI[md5sum] = "4492b145b6d542e4a2f41e77fa199ab0"
-SRC_URI[sha256sum] = 
"022769e3288c80981559a8421703c88e8438b447235e36dd3c8e97cd94c52545"
+# Checksum changed due to tarball source folder changes in upstream
+   
+SRC_URI[md5sum] = "8572b7c2cf9ade09a8a8e10098500fb3"
+SRC_URI[sha256sum] = 
"5bf8e478c428e7744fefa465118f8296e7e771c981fb6dffb7527856a0ea3617"
 
 PACKAGECONFIG ?= "${@bb.utils.filter('DISTRO_FEATURES', 'acl selinux', d)}"
 
-- 
2.7.4

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


[OE-core] [PATCH v3 5/8] libnewt: replace fedorahosted.org SRC_URI with pagure.io source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-extended/newt/libnewt_0.52.19.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/newt/libnewt_0.52.19.bb 
b/meta/recipes-extended/newt/libnewt_0.52.19.bb
index a26ce1f..de76ce2 100644
--- a/meta/recipes-extended/newt/libnewt_0.52.19.bb
+++ b/meta/recipes-extended/newt/libnewt_0.52.19.bb
@@ -8,7 +8,7 @@ shared library needed by programs built with newt, as well as a 
\
 /usr/bin/dialog replacement called whiptail.  Newt is based on the \
 slang library."
 
-HOMEPAGE = "https://fedorahosted.org/newt/";
+HOMEPAGE = "https://releases.pagure.org/newt/";
 SECTION = "libs"
 
 LICENSE = "LGPLv2"
@@ -17,7 +17,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=5f30f0716dfdd0d91eb439ebec522ec2"
 # slang needs to be >= 2.2
 DEPENDS = "slang popt"
 
-SRC_URI = "https://fedorahosted.org/releases/n/e/newt/newt-${PV}.tar.gz \
+SRC_URI = "https://releases.pagure.org/newt/newt-${PV}.tar.gz \
file://fix_SHAREDDIR.patch \
file://cross_ar.patch \
file://Makefile.in-Add-tinfo-library-to-the-linking-librari.patch \
-- 
2.7.4

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


[OE-core] [PATCH v3 8/8] cronie: replace fedorahosted.org SRC_URI with github.com source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com. This github link
is distributions to fedoreproject.org and the contact
Mailing list: cronie-devel AT lists.fedorahosted DOT org

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-extended/cronie/cronie_1.5.1.bb | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-extended/cronie/cronie_1.5.1.bb 
b/meta/recipes-extended/cronie/cronie_1.5.1.bb
index ad616d5..cfb8c21 100644
--- a/meta/recipes-extended/cronie/cronie_1.5.1.bb
+++ b/meta/recipes-extended/cronie/cronie_1.5.1.bb
@@ -3,7 +3,7 @@ DESCRIPTION = "Cronie contains the standard UNIX daemon crond 
that runs \
 specified programs at scheduled times and related tools. It is based on the \
 original cron and has security and configuration enhancements like the \
 ability to use pam and SELinux."
-HOMEPAGE = "https://fedorahosted.org/cronie/";
+HOMEPAGE = "https://github.com/cronie-crond/cronie/";
 BUGTRACKER = "https://bugzilla.redhat.com";
 
 # Internet Systems Consortium License
@@ -14,7 +14,9 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=dd2a592170760e1386c769e1043b3722 \
 
 SECTION = "utils"
 
-SRC_URI = "https://fedorahosted.org/releases/c/r/cronie/cronie-${PV}.tar.gz \
+UPSTREAM_CHECK_URI = "https://github.com/cronie-crond/${BPN}/releases/";
+
+SRC_URI = 
"https://github.com/cronie-crond/cronie/releases/download/cronie-${PV}/cronie-${PV}.tar.gz
 \
file://crond.init \
file://crontab \
file://crond.service \
-- 
2.7.4

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


[OE-core] [PATCH v3 2/8] xmlto: replace fedorahosted.org SRC_URI with pagure.io source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-devtools/xmlto/xmlto_0.0.28.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/xmlto/xmlto_0.0.28.bb 
b/meta/recipes-devtools/xmlto/xmlto_0.0.28.bb
index ce5d1e0..6216d77 100644
--- a/meta/recipes-devtools/xmlto/xmlto_0.0.28.bb
+++ b/meta/recipes-devtools/xmlto/xmlto_0.0.28.bb
@@ -1,11 +1,11 @@
 SUMMARY = "A shell-script tool for converting XML files to various formats"
-HOMEPAGE = "https://fedorahosted.org/xmlto/";
+HOMEPAGE = "https://releases.pagure.org/xmlto/";
 SECTION = "docs/xmlto"
 LICENSE = "GPLv2"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552"
 
-SRC_URI = "https://fedorahosted.org/releases/x/m/xmlto/xmlto-${PV}.tar.gz \
+SRC_URI = "https://releases.pagure.org/xmlto/xmlto-${PV}.tar.gz \
file://configure.in-drop-the-test-of-xmllint-and-xsltproc.patch \
file://catalog.xml \
 "
-- 
2.7.4

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


[OE-core] [PATCH v3 3/8] libuser: replace fedorahosted.org SRC_URI with pagure.io source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to pagure.io. pagure.io is a
replacement for fedorahosted.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/recipes-extended/libuser/libuser_0.62.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-extended/libuser/libuser_0.62.bb 
b/meta/recipes-extended/libuser/libuser_0.62.bb
index 6960d71..1765346 100644
--- a/meta/recipes-extended/libuser/libuser_0.62.bb
+++ b/meta/recipes-extended/libuser/libuser_0.62.bb
@@ -1,8 +1,8 @@
 SUMMARY = "user and group account administration library"
 DESCRIPTION = "The libuser library implements a standardized interface for 
manipulating and administering user \
 and group accounts"
-HOMEPAGE = "https://fedorahosted.org/libuser/";
-BUGTRACKER = "https://fedorahosted.org/libuser/newticket";
+HOMEPAGE = "https://pagure.io/libuser";
+BUGTRACKER = "https://pagure.io/libuser/issues";
 
 LICENSE = "LGPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=5f30f0716dfdd0d91eb439ebec522ec2 \
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=5f30f0716dfdd0d91eb439ebec522ec2 \
 
 SECTION = "base"
 
-SRC_URI = "https://fedorahosted.org/releases/l/i/libuser/libuser-${PV}.tar.xz \
+SRC_URI = "https://releases.pagure.org/libuser/libuser-${PV}.tar.xz \
file://0001-Check-for-issetugid.patch \
file://0002-remove-unused-execinfo.h.patch \

file://0001-modules-files.c-parse_field-fix-string-formating-in-.patch \
-- 
2.7.4

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


[OE-core] [PATCH v3 1/8] selftest/recipetool: replace fedorahosted.org SRC_URI with github.com source

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

fedorahosted.org was retired on March 1st, 2017. This is to
update the SRC_URI to point to github.com.

[YOCTO #11226]

Signed-off-by: Choong YinThong 
---
 meta/lib/oeqa/selftest/recipetool.py | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/lib/oeqa/selftest/recipetool.py 
b/meta/lib/oeqa/selftest/recipetool.py
index d62c8bb..d47b9dd 100644
--- a/meta/lib/oeqa/selftest/recipetool.py
+++ b/meta/lib/oeqa/selftest/recipetool.py
@@ -369,15 +369,15 @@ class RecipetoolTests(RecipetoolBase):
 tempsrc = os.path.join(self.tempdir, 'srctree')
 os.makedirs(tempsrc)
 recipefile = os.path.join(self.tempdir, 'logrotate_3.8.7.bb')
-srcuri = 
'https://fedorahosted.org/releases/l/o/logrotate/logrotate-3.8.7.tar.gz'
+srcuri = 'https://github.com/logrotate/logrotate/archive/r3-8-7.tar.gz'
 result = runCmd('recipetool create -o %s %s -x %s' % (recipefile, 
srcuri, tempsrc))
 self.assertTrue(os.path.isfile(recipefile))
 checkvars = {}
 checkvars['LICENSE'] = 'GPLv2'
 checkvars['LIC_FILES_CHKSUM'] = 
'file://COPYING;md5=18810669f13b87348459e611d31ab760'
-checkvars['SRC_URI'] = 
'https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.gz'
-checkvars['SRC_URI[md5sum]'] = '99e08503ef24c3e2e3ff74cc5f3be213'
-checkvars['SRC_URI[sha256sum]'] = 
'f6ba691f40e30e640efa2752c1f9499a3f9738257660994de70a45fe00d12b64'
+checkvars['SRC_URI'] = 
'https://github.com/logrotate/logrotate/archive/r3-8-7.tar.gz'
+checkvars['SRC_URI[md5sum]'] = '6b1aa0e0d07eda3c9a2526520850397a'
+checkvars['SRC_URI[sha256sum]'] = 
'dece4bfeb9d8374a0ecafa34be139b5a697db5c926dcc69a9b8715431a22e733'
 self._test_recipe_contents(recipefile, checkvars, [])
 
 @testcase(1194)
-- 
2.7.4

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


[OE-core] [PATCH v3 0/8] Remove all use of fedorahosted SRC_URI [yocto #11226]

2017-04-06 Thread yin . thong . choong
From: Choong YinThong 

Fedorahosted.org was retired on March 1st, 2017.
Replace all fedorahosted.org SRC_URI with source pagure.io and github.com.

Choong YinThong (8):
  selftest/recipetool: replace fedorahosted.org SRC_URI with github.com
source
  xmlto: replace fedorahosted.org SRC_URI with pagure.io source
  libuser: replace fedorahosted.org SRC_URI with pagure.io source
  logrotate: replace fedorahosted.org SRC_URI with github.com source
  libnewt: replace fedorahosted.org SRC_URI with pagure.io source
  liberation-fonts: replace fedorahosted.org SRC_URI with pagure.io
source
  chkconfig: replace fedorahosted.org SRC_URI with github.com source
  cronie: replace fedorahosted.org SRC_URI with github.com source

 meta/lib/oeqa/selftest/recipetool.py  |  8 
 meta/recipes-devtools/xmlto/xmlto_0.0.28.bb   |  4 ++--
 meta/recipes-extended/chkconfig/chkconfig_1.3.58.bb   | 14 ++
 meta/recipes-extended/cronie/cronie_1.5.1.bb  |  6 --
 meta/recipes-extended/libuser/libuser_0.62.bb |  6 +++---
 meta/recipes-extended/logrotate/logrotate_3.9.1.bb| 19 +++
 meta/recipes-extended/newt/libnewt_0.52.19.bb |  4 ++--
 .../ttf-fonts/liberation-fonts_1.04.bb|  4 ++--
 8 files changed, 42 insertions(+), 23 deletions(-)

-- 
2.7.4

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


[OE-core] [PATCH] ed: update SRC_URI to yoctoproject mirror

2017-04-06 Thread Maxin B. John
Upstream has removed the 1.14.1 release from ftp.gnu.org and
moved on to the latest 1.14.2. Since we don't want to upgrade
at this point of time, temporarily move the SRC_URI to yoctoproject
mirror.

Signed-off-by: Maxin B. John 
---
 meta/recipes-extended/ed/ed_1.14.1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-extended/ed/ed_1.14.1.bb 
b/meta/recipes-extended/ed/ed_1.14.1.bb
index 5d89a87..23d1f5a 100644
--- a/meta/recipes-extended/ed/ed_1.14.1.bb
+++ b/meta/recipes-extended/ed/ed_1.14.1.bb
@@ -11,7 +11,8 @@ SECTION = "base"
 # LSB states that ed should be in /bin/
 bindir = "${base_bindir}"
 
-SRC_URI = "${GNU_MIRROR}/ed/ed-${PV}.tar.lz"
+#SRC_URI = "${GNU_MIRROR}/ed/ed-${PV}.tar.lz"
+SRC_URI = "http://downloads.yoctoproject.org/mirror/sources/${BP}.tar.lz";
 
 SRC_URI[md5sum] = "7f4a54fa7f366479f03654b8af645fd0"
 SRC_URI[sha256sum] = 
"ffb97eb8f2a2b5a71a9b97e3872adce953aa1b8958e04c5b7bf11d556f32552a"
-- 
2.4.0

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


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

2017-04-06 Thread Peter Kjellerstedt
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: den 5 april 2017 16:44
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCHv2 3/3] base-files: profile: Simplify
> setting variables conditionally
> 
> On Wed, 2017-04-05 at 15:46 +0200, Peter Kjellerstedt wrote:
> > It is preferred to use `[  ] || ...` instead of
> > `[  ] && ...` as the latter leaves $? set to 1.
> 
> Your patch and the description above don't match. There are changes
> here which aren't  and are stylistic changes instead

Well, the intended meaning was that whatever  was used in the  
first example should be negated in the second one, not to mean an explicit 
negate operator should be used, e.g., if the first  is 
[ -z "$VAR" ], the second one would be [ "$VAR" ], not [ ! -z "$VAR" ].

Maybe my examples are just confusing things and I should just remove
them?

> afaict. We're past feature freeze so whilst I'm interested in genuine
> bugs, I do not really want code churn which just introduces risk.

As long as you take the second patch (which is a genuine bug), I am fine 
(the first one is pure whitespace clean up, so it should be safe to take 
as well).

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

//Peter

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


[OE-core] [PATCH] oe-build-perf-report-email.py: fix one file path

2017-04-06 Thread Markus Lehtonen
Sending report email was not working correctly if the script was given
an html report path that contained directory components.

Signed-off-by: Markus Lehtonen 
---
 scripts/contrib/oe-build-perf-report-email.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/contrib/oe-build-perf-report-email.py 
b/scripts/contrib/oe-build-perf-report-email.py
index 7f4274efed..81b58ab020 100755
--- a/scripts/contrib/oe-build-perf-report-email.py
+++ b/scripts/contrib/oe-build-perf-report-email.py
@@ -243,7 +243,7 @@ def main(argv=None):
 html_report = None
 if args.html:
 scrape_html_report(args.html, outdir, args.phantomjs_args)
-html_report = os.path.join(outdir, args.html)
+html_report = os.path.join(outdir, os.path.basename(args.html))
 
 if args.to:
 log.info("Sending email to %s", ', '.join(args.to))
-- 
2.12.0

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


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

2017-04-06 Thread Andrej Valek
ntpd: NTP server denial of service flaw

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

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

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

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