[OE-core] [PATCH V2 4/4] go: Fix build with -buildmode=pie

[Khem Raj]

Signed-off-by: Khem Raj 
---
Changes in V2: Add Signed-off-by

 meta/recipes-devtools/go/go-1.9.inc|  1 +
 ...dmode-pie-forces-external-linking-mode-on.patch | 47 ++
 2 files changed, 48 insertions(+)
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch

diff --git a/meta/recipes-devtools/go/go-1.9.inc 
b/meta/recipes-devtools/go/go-1.9.inc
index 0b0aca3fbe..65adaa8d72 100644
--- a/meta/recipes-devtools/go/go-1.9.inc
+++ b/meta/recipes-devtools/go/go-1.9.inc
@@ -14,6 +14,7 @@ SRC_URI += "\
 file://0006-make.bash-add-GOTOOLDIR_BOOTSTRAP-environment-variab.patch 
\
 file://0007-ld-add-soname-to-shareable-objects.patch \
 file://0008-make.bash-add-GOHOSTxx-indirection-for-cross-canadia.patch 
\
+file://0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch 
\
 "
 SRC_URI[main.md5sum] = "da2d44ea384076efec43ee1f8b7d45d2"
 SRC_URI[main.sha256sum] = 
"a4ab229028ed167ba1986825751463605264e44868362ca8e7accc8be057e993"
diff --git 
a/meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch
 
b/meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch
new file mode 100644
index 00..aa5fcfdd23
--- /dev/null
+++ 
b/meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch
@@ -0,0 +1,47 @@
+From aae44527c8065d54f6acaf87c82cba1ac96fae59 Mon Sep 17 00:00:00 2001
+From: Ian Lance Taylor 
+Date: Fri, 18 Aug 2017 17:46:03 -0700
+Subject: [PATCH] cmd/go: -buildmode=pie forces external linking mode on all
+ systems
+
+The go tool assumed that -buildmode=pie implied internal linking on
+linux-amd64. However, that was changed by CL 36417 for issue #18968.
+
+Fixes #21452
+
+Change-Id: I8ed13aea52959cc5c53223f4c41ba35329445545
+Reviewed-on: https://go-review.googlesource.com/57231
+Run-TryBot: Ian Lance Taylor 
+TryBot-Result: Gobot Gobot 
+Reviewed-by: Avelino 
+Reviewed-by: Rob Pike 
+---
+Upstream-Status: Backport
+Signed-off-by: Khem Raj 
+
+ src/cmd/go/internal/load/pkg.go | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+diff --git a/src/cmd/go/internal/load/pkg.go b/src/cmd/go/internal/load/pkg.go
+index 2660d3f..d40773b 100644
+--- a/src/cmd/go/internal/load/pkg.go
 b/src/cmd/go/internal/load/pkg.go
+@@ -954,11 +954,12 @@ func (p *Package) load(stk *ImportStack, bp 
*build.Package, err error) *Package
+ 
+   if cfg.BuildContext.CgoEnabled && p.Name == "main" && !p.Goroot {
+   // Currently build modes c-shared, pie (on systems that do not
+-  // support PIE with internal linking mode), plugin, and
+-  // -linkshared force external linking mode, as of course does
++  // support PIE with internal linking mode (currently all
++  // systems: issue #18968)), plugin, and -linkshared force
++  // external linking mode, as of course does
+   // -ldflags=-linkmode=external. External linking mode forces
+   // an import of runtime/cgo.
+-  pieCgo := cfg.BuildBuildmode == "pie" && (cfg.BuildContext.GOOS 
!= "linux" || cfg.BuildContext.GOARCH != "amd64")
++  pieCgo := cfg.BuildBuildmode == "pie"
+   linkmodeExternal := false
+   for i, a := range cfg.BuildLdflags {
+   if a == "-linkmode=external" {
+-- 
+2.14.1
+
-- 
2.14.1

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

[OE-core] ✗ patchtest: failure for "goarch.bbclass: fixups for Go ..." and 3 more

[Patchwork]

== Series Details ==

Series: "goarch.bbclass: fixups for Go ..." and 3 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9082/
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 A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch)



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 3/4] go_1.9: remove obsolete overrides

[Khem Raj]

From: Matt Madison 

Now that mips and security flags fixes are in place
in the bbclasses, remove the local settings in this
recipe.

Signed-off-by: Matt Madison 
Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/go/go_1.9.bb | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/recipes-devtools/go/go_1.9.bb 
b/meta/recipes-devtools/go/go_1.9.bb
index 08ab793f86..c67e2cb050 100644
--- a/meta/recipes-devtools/go/go_1.9.bb
+++ b/meta/recipes-devtools/go/go_1.9.bb
@@ -1,4 +1,2 @@
 require go-${PV}.inc
 require go-target.inc
-TUNE_CCARGS_remove = "-march=mips32r2"
-SECURITY_PIE_CFLAGS_remove = "-fPIE -pie"
-- 
2.14.1

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

[OE-core] [PATCH 4/4] go: Fix build with -buildmode=pie

[Khem Raj]

Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/go/go-1.9.inc|  1 +
 ...dmode-pie-forces-external-linking-mode-on.patch | 46 ++
 2 files changed, 47 insertions(+)
 create mode 100644 
meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch

diff --git a/meta/recipes-devtools/go/go-1.9.inc 
b/meta/recipes-devtools/go/go-1.9.inc
index 0b0aca3fbe..65adaa8d72 100644
--- a/meta/recipes-devtools/go/go-1.9.inc
+++ b/meta/recipes-devtools/go/go-1.9.inc
@@ -14,6 +14,7 @@ SRC_URI += "\
 file://0006-make.bash-add-GOTOOLDIR_BOOTSTRAP-environment-variab.patch 
\
 file://0007-ld-add-soname-to-shareable-objects.patch \
 file://0008-make.bash-add-GOHOSTxx-indirection-for-cross-canadia.patch 
\
+file://0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch 
\
 "
 SRC_URI[main.md5sum] = "da2d44ea384076efec43ee1f8b7d45d2"
 SRC_URI[main.sha256sum] = 
"a4ab229028ed167ba1986825751463605264e44868362ca8e7accc8be057e993"
diff --git 
a/meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch
 
b/meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch
new file mode 100644
index 00..7475d9338a
--- /dev/null
+++ 
b/meta/recipes-devtools/go/go-1.9/0009-cmd-go-buildmode-pie-forces-external-linking-mode-on.patch
@@ -0,0 +1,46 @@
+From aae44527c8065d54f6acaf87c82cba1ac96fae59 Mon Sep 17 00:00:00 2001
+From: Ian Lance Taylor 
+Date: Fri, 18 Aug 2017 17:46:03 -0700
+Subject: [PATCH] cmd/go: -buildmode=pie forces external linking mode on all
+ systems
+
+The go tool assumed that -buildmode=pie implied internal linking on
+linux-amd64. However, that was changed by CL 36417 for issue #18968.
+
+Fixes #21452
+
+Change-Id: I8ed13aea52959cc5c53223f4c41ba35329445545
+Reviewed-on: https://go-review.googlesource.com/57231
+Run-TryBot: Ian Lance Taylor 
+TryBot-Result: Gobot Gobot 
+Reviewed-by: Avelino 
+Reviewed-by: Rob Pike 
+---
+Upstream-Status: Backport
+
+ src/cmd/go/internal/load/pkg.go | 7 ---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+diff --git a/src/cmd/go/internal/load/pkg.go b/src/cmd/go/internal/load/pkg.go
+index 2660d3f..d40773b 100644
+--- a/src/cmd/go/internal/load/pkg.go
 b/src/cmd/go/internal/load/pkg.go
+@@ -954,11 +954,12 @@ func (p *Package) load(stk *ImportStack, bp 
*build.Package, err error) *Package
+ 
+   if cfg.BuildContext.CgoEnabled && p.Name == "main" && !p.Goroot {
+   // Currently build modes c-shared, pie (on systems that do not
+-  // support PIE with internal linking mode), plugin, and
+-  // -linkshared force external linking mode, as of course does
++  // support PIE with internal linking mode (currently all
++  // systems: issue #18968)), plugin, and -linkshared force
++  // external linking mode, as of course does
+   // -ldflags=-linkmode=external. External linking mode forces
+   // an import of runtime/cgo.
+-  pieCgo := cfg.BuildBuildmode == "pie" && (cfg.BuildContext.GOOS 
!= "linux" || cfg.BuildContext.GOARCH != "amd64")
++  pieCgo := cfg.BuildBuildmode == "pie"
+   linkmodeExternal := false
+   for i, a := range cfg.BuildLdflags {
+   if a == "-linkmode=external" {
+-- 
+2.14.1
+
-- 
2.14.1

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

[OE-core] [PATCH 2/4] go: disable PIE flags for cgo

[Khem Raj]

From: Matt Madison 

If the security_flags.inc file is included, gcc
will do PIE builds by default.  These flags need
to be disabled for go packages that use cgo.

Signed-off-by: Matt Madison 
Signed-off-by: Khem Raj 
---
 meta/classes/go.bbclass| 3 +++
 meta/recipes-devtools/go/go-target.inc | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/meta/classes/go.bbclass b/meta/classes/go.bbclass
index e167c949ec..09b01a84c3 100644
--- a/meta/classes/go.bbclass
+++ b/meta/classes/go.bbclass
@@ -50,6 +50,9 @@ GOTOOLDIR = 
"${STAGING_LIBDIR_NATIVE}/${TARGET_SYS}/go/pkg/tool/${BUILD_GOTUPLE}
 GOTOOLDIR_class-native = 
"${STAGING_LIBDIR_NATIVE}/go/pkg/tool/${BUILD_GOTUPLE}"
 export GOTOOLDIR
 
+SECURITY_CFLAGS = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_LDFLAGS = ""
+
 export CGO_ENABLED ?= "1"
 export CGO_CFLAGS ?= "${CFLAGS}"
 export CGO_CPPFLAGS ?= "${CPPFLAGS}"
diff --git a/meta/recipes-devtools/go/go-target.inc 
b/meta/recipes-devtools/go/go-target.inc
index b88d0166e5..6065c3c80d 100644
--- a/meta/recipes-devtools/go/go-target.inc
+++ b/meta/recipes-devtools/go/go-target.inc
@@ -18,6 +18,9 @@ GO_LDFLAGS = ""
 GO_LDFLAGS_class-nativesdk = "-linkmode external"
 export GO_LDFLAGS
 
+SECURITY_CFLAGS = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_LDFLAGS = ""
+
 do_configure[noexec] = "1"
 
 do_compile() {
-- 
2.14.1

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

[OE-core] [PATCH 1/4] goarch.bbclass: fixups for Go mips32 support

[Khem Raj]

From: Matt Madison 

* Fix the regular expression in the mips test

* Flag as incompatible any mips32 tunes for n32 ABI
  or soft-float, as go does not support them.

* Replace mips32r2 tune with mips32r1. Go only supports
  mips32r1, which is a strict subset of r2.  Adjusting
  this tune is not ideal, but is hopefully a temporary
  measure until more complete mips32 ISA coverage
  arrives upstream.

[YOCTO #12108]

Signed-off-by: Matt Madison 
Signed-off-by: Khem Raj 
---
 meta/classes/goarch.bbclass | 12 
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/meta/classes/goarch.bbclass b/meta/classes/goarch.bbclass
index 8b95c5fe94..9ed562d5ab 100644
--- a/meta/classes/goarch.bbclass
+++ b/meta/classes/goarch.bbclass
@@ -43,10 +43,14 @@ def go_map_arch(a, d):
 return 'mips64le'
 elif re.match('mips64*', a):
 return 'mips64'
-elif re.match('mipsel*', a):
-return 'mipsle'
-elif re.match('mips*', a):
-return 'mips'
+elif re.match('mips.*', a):
+tf = d.getVar('TUNE_FEATURES').split()
+if 'fpu-hard' in tf and 'n32' not in tf:
+if 'mips32r2' in tf:
+newtf = [t for t in tf if t != 'mips32r2']
+newtf.append('mips32')
+d.setVar('TUNE_FEATURES', ' '.join(newtf))
+return 'mips' if 'bigendian' in tf else 'mipsle'
 elif re.match('p(pc|owerpc)(64)', a):
 return 'ppc64'
 elif re.match('p(pc|owerpc)(64el)', a):
-- 
2.14.1

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

[OE-core] [PATCH] wayland-protocols: extend to native and fix dependencies

[Saul Wold]

When trying to build a newer version of Mesa, a native version of
wayland-protocols is needed to build.

Signed-off-by: Saul Wold 
---
 meta/recipes-graphics/wayland/wayland-protocols_1.10.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb 
b/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
index 4f9e9f32bfc..64044dae8d7 100644
--- a/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
+++ b/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
@@ -11,6 +11,9 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=c7b12b6702da38ca028ace54aae3d484 \
 
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
"
+
+DEPENDS = "wayland"
+
 SRC_URI[md5sum] = "84a7846c2b6a6a3e265fc9be36453e60"
 SRC_URI[sha256sum] = 
"5719c51d7354864983171c5083e93a72ac99229e2b460c4bb10513de08839c0a"
 
@@ -18,3 +21,5 @@ inherit allarch autotools pkgconfig
 
 PACKAGES = "${PN}"
 FILES_${PN} += "${datadir}/pkgconfig/wayland-protocols.pc"
+
+BBCLASSEXTEND = "native"
-- 
2.13.5

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

Re: [OE-core] [U-Boot] [PATCH] u-boot: Upgrade to 2017.09

[Marek Vasut]

On 09/23/2017 01:36 AM, Martin Jansa wrote:
> On Sat, Sep 23, 2017 at 12:19:27AM +0200, Marek Vasut wrote:
>> Agreed. So what is the conclusion here about this , are we updating to
>> 2017.09 or not ?
> 
> It was already merged couple days ago:
> http://git.openembedded.org/openembedded-core/commit/?id=340d413f678a4a64dfa060e8fe0ac721b73fed97
> 
> and the follow-up fix for u-boot-fw-utils as well:
> http://git.openembedded.org/openembedded-core/commit/?id=73afabf8e69019f08b424a06f3eafaab052b0606
> 
Super, thanks.

-- 
Best regards,
Marek Vasut
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [U-Boot] [PATCH] u-boot: Upgrade to 2017.09

[Martin Jansa]

On Sat, Sep 23, 2017 at 12:19:27AM +0200, Marek Vasut wrote:
> Agreed. So what is the conclusion here about this , are we updating to
> 2017.09 or not ?

It was already merged couple days ago:
http://git.openembedded.org/openembedded-core/commit/?id=340d413f678a4a64dfa060e8fe0ac721b73fed97

and the follow-up fix for u-boot-fw-utils as well:
http://git.openembedded.org/openembedded-core/commit/?id=73afabf8e69019f08b424a06f3eafaab052b0606

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


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

[OE-core] [PATCH] qemurunner: print tail qemu log in case bootlog is empty

[leonardo . sandoval . gonzalez]

From: Leonardo Sandoval 

There are cases where the 'while loop' waiting for login prompt fails
and the bootlog variable does not get populated, thus use the the new
qemurunner member (self.msg) which stores all output coming from the qemu
process.

[YOCTO #12113]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/utils/qemurunner.py | 7 ++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/utils/qemurunner.py 
b/meta/lib/oeqa/utils/qemurunner.py
index 427ae23b1b..6bae3882d6 100644
--- a/meta/lib/oeqa/utils/qemurunner.py
+++ b/meta/lib/oeqa/utils/qemurunner.py
@@ -51,6 +51,7 @@ class QemuRunner:
 self.logged = False
 self.thread = None
 self.use_kvm = use_kvm
+self.msg = ''
 
 self.runqemutime = 120
 self.qemu_pidfile = 'pidfile_'+str(os.getpid())
@@ -79,6 +80,7 @@ class QemuRunner:
 # because is possible to have control characters
 msg = msg.decode("utf-8", errors='ignore')
 msg = re_control_char.sub('', msg)
+self.msg += msg
 with codecs.open(self.logfile, "a", encoding="utf-8") as f:
 f.write("%s" % msg)
 
@@ -307,9 +309,12 @@ class QemuRunner:
 sock.close()
 stopread = True
 
+
 if not reachedlogin:
 self.logger.info("Target didn't reached login boot in %d seconds" 
% self.boottime)
-lines = "\n".join(bootlog.splitlines()[-25:])
+tail = lambda l: "\n".join(l.splitlines()[-25:])
+# in case bootlog is empty, use tail qemu log store at self.msg
+lines = tail(bootlog if bootlog else self.msg)
 self.logger.info("Last 25 lines of text:\n%s" % lines)
 self.logger.info("Check full boot log: %s" % self.logfile)
 self._dump_host()
-- 
2.12.3

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

Re: [OE-core] [U-Boot] [PATCH] u-boot: Upgrade to 2017.09

[Moritz Fischer]

Hi Marek,

On Fri, Sep 22, 2017 at 3:19 PM, Marek Vasut  wrote:
> On 09/21/2017 11:35 PM, Philip Balister wrote:
>> On 09/19/2017 04:15 AM, Marek Vasut wrote:
>>> On 09/18/2017 06:06 PM, Tom Rini wrote:
 On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
> On 18 September 2017 at 16:46, Otavio Salvador <
> otavio.salva...@ossystems.com.br> wrote:
>
>> What is the policy on doing u-boot version upgrades this late in the
>>
>> release cycle? SHouldn't this wait until after the release?
>>
>>
>> Why?
>>
>> It is just another recipe and we are upgrading to the final release.
>>
>> As Martin said, it was already broken.
>>
>> I'll take the responsibility to fix it. But as other packages, upgrades
>> has risk and we have more than enough time to proper fix it.
>>
>
> Why?  Because it was merged to master after the freeze.
>
> Personally I'm of the opinion that u-boot is one of those special recipes
> that if an upgrade appears just after freeze, we consider it.  If we don't
> keep it up to date BSPs won't use the recipe, and we'll be back to every
> BSP layer containing its own special copy of the u-boot recipe.

 Also please note that U-Boot has a rather regular and public release
 schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a
 good idea beforehand if you want to grab something for a release or not.

 Personally, I would like to see this in.  But the security issue that's
 been disclosed now is "resolved" just by not enabling functionality that
 no one was enabling in mainline, and will be removed in the next
 release, so don't feel you need to pull it in on those grounds.
>>>
>>> I agree that the 2017.09 upgrade is a good idea.
>>>
>>
>> OK, I just wanted to make sure everyone was on the same page about
>> timing of the update. We certainly don't want very many recipes to
>> decide they are special and take version bumps right up to release.
>
> Agreed. So what is the conclusion here about this , are we updating to
> 2017.09 or not ?

+1 for upgrade.

- morats
>
>> Philip
>>
>>
>
>
> --
> Best regards,
> Marek Vasut
> --
> ___
> 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] [U-Boot] [PATCH] u-boot: Upgrade to 2017.09

[Marek Vasut]

On 09/21/2017 11:35 PM, Philip Balister wrote:
> On 09/19/2017 04:15 AM, Marek Vasut wrote:
>> On 09/18/2017 06:06 PM, Tom Rini wrote:
>>> On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
 On 18 September 2017 at 16:46, Otavio Salvador <
 otavio.salva...@ossystems.com.br> wrote:

> What is the policy on doing u-boot version upgrades this late in the
>
> release cycle? SHouldn't this wait until after the release?
>
>
> Why?
>
> It is just another recipe and we are upgrading to the final release.
>
> As Martin said, it was already broken.
>
> I'll take the responsibility to fix it. But as other packages, upgrades
> has risk and we have more than enough time to proper fix it.
>

 Why?  Because it was merged to master after the freeze.

 Personally I'm of the opinion that u-boot is one of those special recipes
 that if an upgrade appears just after freeze, we consider it.  If we don't
 keep it up to date BSPs won't use the recipe, and we'll be back to every
 BSP layer containing its own special copy of the u-boot recipe.
>>>
>>> Also please note that U-Boot has a rather regular and public release
>>> schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a
>>> good idea beforehand if you want to grab something for a release or not.
>>>
>>> Personally, I would like to see this in.  But the security issue that's
>>> been disclosed now is "resolved" just by not enabling functionality that
>>> no one was enabling in mainline, and will be removed in the next
>>> release, so don't feel you need to pull it in on those grounds.
>>
>> I agree that the 2017.09 upgrade is a good idea.
>>
> 
> OK, I just wanted to make sure everyone was on the same page about
> timing of the update. We certainly don't want very many recipes to
> decide they are special and take version bumps right up to release.

Agreed. So what is the conclusion here about this , are we updating to
2017.09 or not ?

> Philip
> 
> 


-- 
Best regards,
Marek Vasut
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] OpenEmbedded Developer Meeting Oct 22, 2017 in Prague (before ELCE)

[Jeff Osier-Mixon]

If its relevance to YP and OE is able to be explained, it would be
welcomed. The only issue I see is the size of the booth, which is tiny.
However, we frequently spill out of our confined space, and I will locate a
second table if we end up needing one. Great to see community effort on the
demos!

On Thu, Sep 21, 2017 at 1:56 PM, Philip Balister 
wrote:

> On 09/21/2017 02:32 PM, akuster808 wrote:
> >
> >
> > On 09/21/2017 01:27 PM, Philip Balister wrote:
> >> On 09/20/2017 01:50 AM, Mike Looijmans wrote:
> >>> On 18-09-17 18:25, Trevor Woerner wrote:
>  Hi Mike,
> 
>  On Mon, Sep 18, 2017 at 8:45 AM, Mike Looijmans
>   wrote:
> > I can probably bring some work (e.g. Zynq MPSoC board) and fun
> > (settop box)
> > hardware along to demonstrate what I'm using OE for.
>  Any chance you could set something up that could be on display at the
>  Yocto booth during the conference?
> >>> Depends on what I'll be able tug along in my luggage on the airplane,
> >>> but whatever I can bring is probably suited for public display. A few
> >>> circuit boards will certainly fit, so if the stand could provide a HDMI
> >>> monitor (or TV) to connect them to that'd be awesome.
> >> I'd love to see some different things on the stand. Make sure you help
> >> explain to people why the Yocto Porject and OpenEmbedded are important
> >> to you and your product.
> > Philip,
> >
> > Since you are the OE rep to the Yocto Project, can you make sure this is
> > OK with them. There could be space  or limitations at their booth.
>
> I mentioned it to Jefro, I'm also making a guess he has something based
> on a Xilinx product, who are members.
>
> Philip
>
> >
> > Thanks,
> > - Armin
> >>
> >> Philip
> >>
> >>
> >>
> >>> M.
> >>>
> >>>
> >>> Kind regards,
> >>>
> >>> Mike Looijmans
> >>> System Expert
> >>>
> >>> TOPIC Products
> >>> Materiaalweg 4, NL-5681 RJ Best
> >>> Postbus 440, NL-5680 AK Best
> >>> Telefoon: +31 (0) 499 33 69 79
> >>> E-mail: mike.looijm...@topicproducts.com
> >>> Website: www.topicproducts.com
> >>>
> >>> Please consider the environment before printing this e-mail
> >>>
> >>>
> >>> Visit us at the Space Tech Expo Europe (Stand E-71)
> >>>
> >
> >
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
Jeff Osier-Mixon - Open Source Community Manager, Intel Corporation
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] State of bitbake world, Failed tasks 2017-09-21

[Martin Jansa]

The qemux86-64 failures (except mongodb do_patch) are caused by rpcgen
removal from HOSTTOOLs, will drop that change from next run, but it
also means that latest Gentoo glibc (drops rpc support) cannot be used
for OE builds anymore.


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

== Number of issues - stats ==
{| class='wikitable'
!|Date   !!colspan='3'|Failed tasks 
!!|Signatures   
!!colspan='15'|QA !!Comment
|-
||  ||qemuarm   ||qemux86   ||qemux86_64||all
||already-stripped  ||libdir||textrel   ||build-deps
||file-rdeps||version-going-backwards   ||host-user-contaminated
||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname   ||ldflags   ||compile-host-path 
||qa_pseudo ||
|-
||2017-09-21||1 ||1 ||8 ||0 ||0 ||0 
||1 ||0 ||0 ||18||1 
||0 ||0 ||0 ||0 ||0 
||0 ||0 ||0 ||
|}

== Failed tasks 2017-09-21 ==

INFO: jenkins-job.sh-1.8.31 Complete log available at
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20170922_101357.log

=== common (0) ===

=== common-x86 (0) ===

=== qemuarm (1) ===
* 
meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile

=== qemux86 (1) ===
* 
meta-openembedded/meta-networking/recipes-support/spice/spice_git.bb:do_compile

=== qemux86_64 (8) ===
* 
meta-openembedded/meta-networking/recipes-connectivity/samba/samba_4.6.7.bb:do_compile
* 
meta-openembedded/meta-networking/recipes-daemons/autofs/autofs_5.1.2.bb:do_compile
* 
meta-openembedded/meta-networking/recipes-daemons/ippool/ippool_1.3.bb:do_compile
* 
meta-openembedded/meta-networking/recipes-protocols/openl2tp/openl2tp_1.8.bb:do_compile
* 
meta-openembedded/meta-networking/recipes-support/ctdb/ctdb_2.5.6.bb:do_compile
* meta-openembedded/meta-oe/recipes-support/mongodb/mongodb_git.bb:do_patch
* 
meta-openembedded/meta-oe/recipes-support/open-vm-tools/open-vm-tools_10.1.5.bb:do_compile
* openembedded-core/meta/recipes-extended/quota/quota_4.03.bb:do_configure

=== Number of failed tasks (10) ===
{| class=wikitable
|-
|| qemuarm  || 1 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemuarm.20170920_111859.log/
|| http://errors.yoctoproject.org/Errors/Build/46963/
|-
|| qemux86  || 1 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemux86.20170920_134145.log/
|| http://errors.yoctoproject.org/Errors/Build/46969/
|-
|| qemux86_64   || 8 ||
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemux86-64.20170921_051533.log/
|| http://errors.yoctoproject.org/Errors/Build/47079/
|}

=== PNBLACKLISTs (1) ===

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



=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===

Complete log: 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.signatures.20170920_133416.log/

No issues detected


PNBLACKLISTs:
openembedded-core/:
meta-browser:
meta-openembedded:
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb:PNBLACKLIST[lksctp-tools]
?= "${@bb.utils.contains('DISTRO_FEATURES', 'ld-is-gold', "BROKEN:
fails to link against sctp_connectx symbol", '', d)}"
meta-qt5:
PNBLACKLIST[android-system] = "depends on lxc from
meta-virtualiazation which isn't included in my world builds"
PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[tearsofsteel-1080p] = "big and doesn't really need to be
tested so much"
PNBLACKLIST[build-appliance-image] = "tries to include whole downloads
directory in /home/builder/poky :/"


QA issues by type:
count: 0issue: already-stripped


count: 0issue: libdir


count: 1issue: textrel
corosync-2.4.2: ELF binary
'/tmp/work/core2-64-oe-linux/corosync/2.4.2-r0/packages-split/corosync/usr/sbin/corosync'
has relocations in .text [textrel]


count: 0issue: build-deps


count: 0issue: file-rdeps


count: 18   issue: 

Re: [OE-core] [PATCH 2/2] pseudo: Add fastop reply fix

[Otavio Salvador]

Richard,

On Fri, Sep 22, 2017 at 2:12 PM, Alexander Kanavin
 wrote:
> On 09/22/2017 07:52 PM, Seebs wrote:
>>>
>>> This changes the pseudo FASTOP functionality so that a reply to the
>>> operation is required. This means we then cannot lose data if a
>>> connection is closed. This in turn stops corruption if we run out of
>>> file handles and have to close connections.
>>>
>>> This tweaks the connection closure patch to update the comment there
>>> which is now outdated.
>>>
>>> Signed-off-by: Richard Purdie 
>>
>>
>> This looks reasonable to me. I did some testing with a very similar
>> patch and concluded that, while it slowed performance slightly, it
>> didn't slow it nearly as much as the pre-fastop behavior did.
>
> Also, the issue this patch is fixing is not theoretical. Setting max fd
> limit to a low value (192) is causing errors on my machine:
>
> dpkg-deb: error: maintainer script 'postinst' has bad permissions 644 (must
> be >=0555 and <=0775)
>
> and with the patch they seem to go away.

When queueing it, please make sure to add the proper patch headers.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/2] pseudo: Add fastop reply fix

[Alexander Kanavin]

On 09/22/2017 07:52 PM, Seebs wrote:

This changes the pseudo FASTOP functionality so that a reply to the
operation is required. This means we then cannot lose data if a
connection is closed. This in turn stops corruption if we run out of
file handles and have to close connections.

This tweaks the connection closure patch to update the comment there
which is now outdated.

Signed-off-by: Richard Purdie 


This looks reasonable to me. I did some testing with a very similar
patch and concluded that, while it slowed performance slightly, it
didn't slow it nearly as much as the pre-fastop behavior did.


Also, the issue this patch is fixing is not theoretical. Setting max fd 
limit to a low value (192) is causing errors on my machine:


dpkg-deb: error: maintainer script 'postinst' has bad permissions 644 
(must be >=0555 and <=0775)


and with the patch they seem to go away.

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

[OE-core] ✗ patchtest: failure for "staging: Reduce verbosity of l..." and 1 more

[Patchwork]

== Series Details ==

Series: "staging: Reduce verbosity of l..." and 1 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9077/
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-devtools/pseudo/files/fastopreply.patch (possible values: Pending, 
Submitted, Accepted, Backport, Denied, Inappropriate)

* 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 acc5036a6b)

* Issue A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-devtools/pseudo/files/fastopreply.patch)



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

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

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

Re: [OE-core] [PATCH 2/2] pseudo: Add fastop reply fix

[Seebs]

On Fri, 22 Sep 2017 17:41:17 +0100
Richard Purdie  wrote:

> This changes the pseudo FASTOP functionality so that a reply to the
> operation is required. This means we then cannot lose data if a
> connection is closed. This in turn stops corruption if we run out of
> file handles and have to close connections.
> 
> This tweaks the connection closure patch to update the comment there
> which is now outdated.
> 
> Signed-off-by: Richard Purdie 

This looks reasonable to me. I did some testing with a very similar
patch and concluded that, while it slowed performance slightly, it
didn't slow it nearly as much as the pre-fastop behavior did.

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

[OE-core] [PATCH 2/2] pseudo: Add fastop reply fix

[Richard Purdie]

This changes the pseudo FASTOP functionality so that a reply to the
operation is required. This means we then cannot lose data if a connection
is closed. This in turn stops corruption if we run out of file handles
and have to close connections.

This tweaks the connection closure patch to update the comment there which
is now outdated.

Signed-off-by: Richard Purdie 
---
 .../pseudo/files/fastopreply.patch | 74 ++
 .../pseudo/files/toomanyfiles.patch|  7 +-
 meta/recipes-devtools/pseudo/pseudo_1.8.2.bb   |  1 +
 3 files changed, 77 insertions(+), 5 deletions(-)
 create mode 100644 meta/recipes-devtools/pseudo/files/fastopreply.patch

diff --git a/meta/recipes-devtools/pseudo/files/fastopreply.patch 
b/meta/recipes-devtools/pseudo/files/fastopreply.patch
new file mode 100644
index 000..c8e7b08
--- /dev/null
+++ b/meta/recipes-devtools/pseudo/files/fastopreply.patch
@@ -0,0 +1,74 @@
+Ensure FASTOP messages get an ACK reply so that the client can be sure the 
server
+recieved them. This means if connections are terminated, data isn't lost.
+
+RP 2017/9/22
+
+Index: pseudo-1.8.2/pseudo_client.c
+===
+--- pseudo-1.8.2.orig/pseudo_client.c
 pseudo-1.8.2/pseudo_client.c
+@@ -1331,21 +1331,19 @@ pseudo_client_request(pseudo_msg_t *msg,
+* indicating a successful send.
+*/
+   pseudo_debug(PDBGF_CLIENT | PDBGF_VERBOSE, "sent!\n");
+-  if (msg->type != PSEUDO_MSG_FASTOP) {
+-  response = pseudo_msg_receive(connect_fd);
+-  if (!response) {
+-  pseudo_debug(PDBGF_CLIENT, "expected response 
did not occur; retrying\n");
++  response = pseudo_msg_receive(connect_fd);
++  if (!response) {
++  pseudo_debug(PDBGF_CLIENT, "expected response did not 
occur; retrying\n");
++  } else {
++  if (response->type != PSEUDO_MSG_ACK) {
++  pseudo_debug(PDBGF_CLIENT, "got non-ack 
response %d\n", response->type);
++  return 0;
++  } else if (msg->type != PSEUDO_MSG_FASTOP) {
++  pseudo_debug(PDBGF_CLIENT | PDBGF_VERBOSE, "got 
response type %d\n", response->type);
++  return response;
+   } else {
+-  if (response->type != PSEUDO_MSG_ACK) {
+-  pseudo_debug(PDBGF_CLIENT, "got non-ack 
response %d\n", response->type);
+-  return 0;
+-  } else {
+-  pseudo_debug(PDBGF_CLIENT | 
PDBGF_VERBOSE, "got response type %d\n", response->type);
+-  return response;
+-  }
++  return 0;
+   }
+-  } else {
+-  return 0;
+   }
+   }
+   pseudo_diag("pseudo: server connection persistently failed, 
aborting.\n");
+Index: pseudo-1.8.2/pseudo_server.c
+===
+--- pseudo-1.8.2.orig/pseudo_server.c
 pseudo-1.8.2/pseudo_server.c
+@@ -463,6 +463,11 @@ close_client(int client) {
+   --highest_client;
+ }
+ 
++static pseudo_msg_t server_fastop_reply = { 
++.type = PSEUDO_MSG_ACK,
++.op = OP_NONE,
++};
++
+ /* Actually process a request.
+  */
+ static int
+@@ -515,8 +520,14 @@ serve_client(int i) {
+* pseudo_server_response.
+*/
+   if (in->type != PSEUDO_MSG_SHUTDOWN) {
+-if (in->type == PSEUDO_MSG_FASTOP)
++if (in->type == PSEUDO_MSG_FASTOP) {
+ send_response = 0;
++/* For fastops we reply now to say we got the 
data */
++if ((rc = pseudo_msg_send(clients[i].fd, 
_fastop_reply, 0, NULL)) != 0) {
++pseudo_debug(PDBGF_SERVER, 
"failed to send fastop ack to client %d [%d]: %d (%s)\n",
++i, (int) clients[i].pid, 
rc, strerror(errno));
++}
++}
+   /* most messages don't need these, but xattr may */
+   response_path = 0;
+   response_pathlen = -1;
diff --git a/meta/recipes-devtools/pseudo/files/toomanyfiles.patch 
b/meta/recipes-devtools/pseudo/files/toomanyfiles.patch
index 7319ab2..d014ad5 100644
--- a/meta/recipes-devtools/pseudo/files/toomanyfiles.patch
+++ b/meta/recipes-devtools/pseudo/files/toomanyfiles.patch
@@ -31,15 +31,12 @@ 

[OE-core] [PATCH 1/2] staging: Reduce verbosity of log messages

[Richard Purdie]

The staging changes were very verbose in their logging and whilst this is useful
when staging issues occur, those thankfully seem rare now and we can tune down
the logging to a sane level. This improves the readability of error messages 
from
functions that fail.

The code is still verbose when its replacing things in the sysroot.

Signed-off-by: Richard Purdie 
---
 meta/classes/staging.bbclass | 12 ++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass
index 6185aef..ea831e0 100644
--- a/meta/classes/staging.bbclass
+++ b/meta/classes/staging.bbclass
@@ -373,7 +373,8 @@ python extend_recipe_sysroot() {
 msgbuf.append("Following dependency on %s" % 
setscenedeps[datadep][0])
 next = new
 
-bb.note("\n".join(msgbuf))
+# This logging is too verbose for day to day use sadly
+#bb.debug(2, "\n".join(msgbuf))
 
 depdir = recipesysrootnative + "/installeddeps"
 bb.utils.mkdirhier(depdir)
@@ -442,6 +443,8 @@ python extend_recipe_sysroot() {
 os.unlink(fl)
 os.unlink(fl + ".complete")
 
+msg_exists = []
+msg_adding = []
 for dep in configuredeps:
 c = setscenedeps[dep][0]
 if c not in installed:
@@ -452,7 +455,7 @@ python extend_recipe_sysroot() {
 if os.path.exists(depdir + "/" + c):
 lnk = os.readlink(depdir + "/" + c)
 if lnk == c + "." + taskhash and os.path.exists(depdir + "/" + c + 
".complete"):
-bb.note("%s exists in sysroot, skipping" % c)
+msg_exists.append(c)
 continue
 else:
 bb.note("%s exists in sysroot, but is stale (%s vs. %s), 
removing." % (c, lnk, c + "." + taskhash))
@@ -463,6 +466,8 @@ python extend_recipe_sysroot() {
 elif os.path.lexists(depdir + "/" + c):
 os.unlink(depdir + "/" + c)
 
+msg_adding.append(c)
+
 os.symlink(c + "." + taskhash, depdir + "/" + c)
 
 d2 = d
@@ -559,6 +564,9 @@ python extend_recipe_sysroot() {
 continue
 staging_copyfile(l, targetdir, dest, postinsts, seendirs)
 
+bb.note("Installed into sysroot: %s" % str(msg_adding))
+bb.note("Skipping as already exists in sysroot: %s" % str(msg_exists))
+
 for f in fixme:
 if f == '':
 staging_processfixme(fixme[f], recipesysroot, recipesysroot, 
recipesysrootnative, d)
-- 
2.7.4

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

[OE-core] [PATCHv3] pseudo: use epoll API on Linux

[Alexander Kanavin]

The idea came up here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11309
and here:
http://lists.openembedded.org/pipermail/openembedded-core/2017-August/141491.html

Signed-off-by: Alexander Kanavin 
---
 .../pseudo/files/0001-Use-epoll-API-on-Linux.patch | 292 +
 meta/recipes-devtools/pseudo/pseudo_1.8.2.bb   |   1 +
 2 files changed, 293 insertions(+)
 create mode 100644 
meta/recipes-devtools/pseudo/files/0001-Use-epoll-API-on-Linux.patch

diff --git 
a/meta/recipes-devtools/pseudo/files/0001-Use-epoll-API-on-Linux.patch 
b/meta/recipes-devtools/pseudo/files/0001-Use-epoll-API-on-Linux.patch
new file mode 100644
index 000..42557b17a7f
--- /dev/null
+++ b/meta/recipes-devtools/pseudo/files/0001-Use-epoll-API-on-Linux.patch
@@ -0,0 +1,292 @@
+From 9e407e0be01695e7b927f5820ade87ee9602c248 Mon Sep 17 00:00:00 2001
+From: Alexander Kanavin 
+Date: Fri, 15 Sep 2017 17:00:14 +0300
+Subject: [PATCH] Use epoll API on Linux
+
+Also a couple of other modifications due to epoll having
+a different approach to how the working set of fds is defined
+and used:
+1) open_client() returns an index into the array of clients
+2) close_client() has a protection against being called twice
+with the same client (which would mess up the active_clients
+counter)
+
+Upstream-Status: Submitted [Seebs CC'd by email]
+Signed-off-by: Alexander Kanavin 
+
+---
+ enums/exit_status.in |   3 +
+ pseudo_server.c  | 189 ++-
+ 2 files changed, 190 insertions(+), 2 deletions(-)
+
+diff --git a/enums/exit_status.in b/enums/exit_status.in
+index 6be44d3..88f94cd 100644
+--- a/enums/exit_status.in
 b/enums/exit_status.in
+@@ -18,3 +18,6 @@ listen_fd, "server loop had no valid listen fd"
+ pseudo_loaded, "server couldn't get out of pseudo environment"
+ pseudo_prefix, "couldn't get valid pseudo prefix"
+ pseudo_invocation, "invalid server command arguments"
++epoll_create, "epoll_create() failed"
++epoll_ctl, "epoll_ctl() failed"
++
+diff --git a/pseudo_server.c b/pseudo_server.c
+index ff16efd..14d34de 100644
+--- a/pseudo_server.c
 b/pseudo_server.c
+@@ -40,6 +40,12 @@
+ #include "pseudo_client.h"
+ #include "pseudo_db.h"
+ 
++// This has to come after pseudo includes, as that's where PSEUDO_PORT 
defines are
++#ifdef PSEUDO_PORT_LINUX
++#include 
++#endif
++
++
+ static int listen_fd = -1;
+ 
+ typedef struct {
+@@ -59,6 +65,7 @@ static int active_clients = 0, highest_client = 0, 
max_clients = 0;
+ 
+ #define LOOP_DELAY 2
+ #define DEFAULT_PSEUDO_SERVER_TIMEOUT 30
++#define EPOLL_MAX_EVENTS 10
+ int pseudo_server_timeout = DEFAULT_PSEUDO_SERVER_TIMEOUT;
+ static int die_peacefully = 0;
+ static int die_forcefully = 0;
+@@ -80,6 +87,9 @@ quit_now(int signal) {
+ static int messages = 0, responses = 0;
+ static struct timeval message_time = { .tv_sec = 0 };
+ 
++#ifdef PSEUDO_PORT_LINUX
++static void pseudo_server_loop_epoll(void);
++#endif
+ static void pseudo_server_loop(void);
+ 
+ /* helper function to make a directory, just like mkdir -p.
+@@ -369,12 +379,16 @@ pseudo_server_start(int daemonize) {
+   kill(ppid, SIGUSR1);
+   }
+   }
++#ifdef PSEUDO_PORT_LINUX
++  pseudo_server_loop_epoll();
++#else
+   pseudo_server_loop();
++#endif
+   return 0;
+ }
+ 
+ /* mess with internal tables as needed */
+-static void
++static unsigned int
+ open_client(int fd) {
+   pseudo_client_t *new_clients;
+   int i;
+@@ -390,7 +404,7 @@ open_client(int fd) {
+   ++active_clients;
+   if (i > highest_client)
+   highest_client = i;
+-  return;
++  return i;
+   }
+   }
+ 
+@@ -414,9 +428,11 @@ open_client(int fd) {
+ 
+   max_clients += 16;
+   ++active_clients;
++  return max_clients - 16;
+   } else {
+   pseudo_diag("error allocating new client, fd %d\n", fd);
+   close(fd);
++  return 0;
+   }
+ }
+ 
+@@ -433,6 +449,10 @@ close_client(int client) {
+   client, highest_client);
+   return;
+   }
++  if (clients[client].fd == -1) {
++  pseudo_debug(PDBGF_SERVER, "client %d already closed\n", 
client);
++  return;
++  }
+   close(clients[client].fd);
+   clients[client].fd = -1;
+   free(clients[client].tag);
+@@ -566,6 +586,171 @@ serve_client(int i) {
+   }
+ }
+ 
++#ifdef PSEUDO_PORT_LINUX
++static void pseudo_server_loop_epoll(void)
++{
++  struct sockaddr_un client;
++  socklen_t len;
++int i;
++int rc;
++int fd;
++  int timeout;
++  struct epoll_event ev, events[EPOLL_MAX_EVENTS];
++  int loop_timeout = pseudo_server_timeout;
++
++  clients = malloc(16 * sizeof(*clients));
++
++  

[OE-core] [PATCH v3] OBmesa: Upgrade to 17.2.1 release

[Otavio Salvador]

Upgrade to a new stable release and drop patches applied on upstream.

For a full release notes, please see:
https://mesa3d.org/relnotes/17.2.0.html
https://mesa3d.org/relnotes/17.2.1.html

Signed-off-by: Fabio Berton 
Signed-off-by: Otavio Salvador 
---
This patch has been tested using OE-Core current Wayland as well as v2
of Fabien patches:

 weston: Bump version to 3.0.0
 wayland-protocols: Fix installation patch issue
 wayland : Bump to version 1.14.0

The distro used for test had: opengl, wayland, x11 and vulkan enabled.

Changes in v3:
 - fix build for wayland

Changes in v2:
 - update to 17.2.1

 ...1-ac-fix-build-after-LLVM-5.0-SVN-r300718.patch | 40 --
 ...allivm-Fix-build-against-LLVM-SVN-r302589.patch | 49 --
 .../mesa/{mesa-gl_17.1.7.bb => mesa-gl_17.2.1.bb}  |  0
 meta/recipes-graphics/mesa/mesa.inc|  2 +-
 .../mesa/{mesa_17.1.7.bb => mesa_17.2.1.bb}|  7 ++--
 5 files changed, 4 insertions(+), 94 deletions(-)
 delete mode 100644 
meta/recipes-graphics/mesa/files/0001-ac-fix-build-after-LLVM-5.0-SVN-r300718.patch
 delete mode 100644 
meta/recipes-graphics/mesa/files/0002-gallivm-Fix-build-against-LLVM-SVN-r302589.patch
 rename meta/recipes-graphics/mesa/{mesa-gl_17.1.7.bb => mesa-gl_17.2.1.bb} 
(100%)
 rename meta/recipes-graphics/mesa/{mesa_17.1.7.bb => mesa_17.2.1.bb} (77%)

diff --git 
a/meta/recipes-graphics/mesa/files/0001-ac-fix-build-after-LLVM-5.0-SVN-r300718.patch
 
b/meta/recipes-graphics/mesa/files/0001-ac-fix-build-after-LLVM-5.0-SVN-r300718.patch
deleted file mode 100644
index b27a3bc8e4..00
--- 
a/meta/recipes-graphics/mesa/files/0001-ac-fix-build-after-LLVM-5.0-SVN-r300718.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From 9861437e58fdd0de01193a102608d34e5952953f Mon Sep 17 00:00:00 2001
-From: Christoph Haag 
-Date: Thu, 20 Apr 2017 10:34:18 +0200
-Subject: [PATCH 1/2] ac: fix build after LLVM 5.0 SVN r300718
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-v2: previously getWithDereferenceableBytes() exists, but addAttr() doesn't 
take that type
-
-Signed-off-by: Christoph Haag 
-Reviewed-by: Nicolai Hähnle 
-Tested-and-reviewed-by: Mike Lothian 

-Upstream-Status: Backport
-
- src/amd/common/ac_llvm_helper.cpp | 4 
- 1 file changed, 4 insertions(+)
-
-diff --git a/src/amd/common/ac_llvm_helper.cpp 
b/src/amd/common/ac_llvm_helper.cpp
-index d9ea4b1..11fa809 100644
 a/src/amd/common/ac_llvm_helper.cpp
-+++ b/src/amd/common/ac_llvm_helper.cpp
-@@ -44,9 +44,13 @@ typedef AttributeSet AttributeList;
- void ac_add_attr_dereferenceable(LLVMValueRef val, uint64_t bytes)
- {
-llvm::Argument *A = llvm::unwrap(val);
-+#if HAVE_LLVM < 0x0500
-llvm::AttrBuilder B;
-B.addDereferenceableAttr(bytes);
-A->addAttr(llvm::AttributeList::get(A->getContext(), A->getArgNo() + 1,  
B));
-+#else
-+   A->addAttr(llvm::Attribute::getWithDereferenceableBytes(A->getContext(), 
bytes));
-+#endif
- }
- 
- bool ac_is_sgpr_param(LLVMValueRef arg)
--- 
-2.13.3
-
diff --git 
a/meta/recipes-graphics/mesa/files/0002-gallivm-Fix-build-against-LLVM-SVN-r302589.patch
 
b/meta/recipes-graphics/mesa/files/0002-gallivm-Fix-build-against-LLVM-SVN-r302589.patch
deleted file mode 100644
index ac8caec74d..00
--- 
a/meta/recipes-graphics/mesa/files/0002-gallivm-Fix-build-against-LLVM-SVN-r302589.patch
+++ /dev/null
@@ -1,49 +0,0 @@
-From a02a0dfda2712d30ad62b8f0421ec7b8244ba2cb Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Michel=20D=C3=A4nzer?= 
-Date: Wed, 10 May 2017 17:26:07 +0900
-Subject: [PATCH 2/2] gallivm: Fix build against LLVM SVN >= r302589
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-deregisterEHFrames doesn't take any parameters anymore.
-
-Reviewed-by: Vedran Miletić 
-Reviewed-by: Marek Olšák 

-Upstream-Status: Backport
-
- src/gallium/auxiliary/gallivm/lp_bld_misc.cpp | 12 +---
- 1 file changed, 9 insertions(+), 3 deletions(-)
-
-diff --git a/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp 
b/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
-index 2a388cb..0e4a531 100644
 a/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
-+++ b/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp
-@@ -342,14 +342,20 @@ class DelegatingJITMemoryManager : public 
BaseMemoryManager {
-   virtual void registerEHFrames(uint8_t *Addr, uint64_t LoadAddr, size_t 
Size) {
-  mgr()->registerEHFrames(Addr, LoadAddr, Size);
-   }
--  virtual void deregisterEHFrames(uint8_t *Addr, uint64_t LoadAddr, 
size_t Size) {
-- mgr()->deregisterEHFrames(Addr, LoadAddr, Size);
--  }
- #else
-   virtual void registerEHFrames(llvm::StringRef SectionData) {
-  

[OE-core] ARM Cross-distro BoF at Linaro Connect next week

[Riku Voipio]

Hi,

We'll have the traditional cross-distribution BoF at Linaro connect
Wednesday  27.9, at 3PM US pacific time - 22.00 UTC. We don't have a
set agenda, but if anything is bugging you, replying to this mail is
great way to make it into our topics :)

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

Re: [OE-core] [PATCH 2/2] go: Remove mips32r2 from march to get cgo working

[Matt Madison]

On Thu, Sep 21, 2017 at 10:42 AM, Khem Raj  wrote:
> on mips, cgo used mips32r1 and that conflicts with mips32r2
> lets remove it for now and work go upstream to make it work
> for golang as well

There is already someone working on expanding MIPS support for go,
based on some mailing list discussions I've seen.  Doesn't look like
the changes have made it in yet, but looked like they could for 1.10.

>
> Fixes
> | # runtime/cgo
> | cc1: error: '-mips32r2' conflicts with the other architecture options, 
> which specify a mips32 processor
>
> Fixes [YOCTO #12108]
>
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/go/go-common.inc | 4 
>  meta/recipes-devtools/go/go_1.9.bb | 2 --
>  2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/go/go-common.inc 
> b/meta/recipes-devtools/go/go-common.inc
> index ce1eb86812..41f661bc4e 100644
> --- a/meta/recipes-devtools/go/go-common.inc
> +++ b/meta/recipes-devtools/go/go-common.inc
> @@ -20,3 +20,7 @@ B = "${S}"
>
>  INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
>  SSTATE_SCAN_CMD = "true"
> +
> +TUNE_CCARGS_remove = "-march=mips32r2"

The rework for this should probably go into goarch.bblcass, so it
applies to go packages as well as the toolchain.  The mips checks in
goarch.bbclass need some refinement anyway, since Go only supports o32
ABI and hard-float.  I can send along a patch that should cover what's
needed.

-Matt


> +SECURITY_CFLAGS = "${SECURITY_NOPIE_CFLAGS}"
> +SECURITY_LDFLAGS = ""
> diff --git a/meta/recipes-devtools/go/go_1.9.bb 
> b/meta/recipes-devtools/go/go_1.9.bb
> index 08ab793f86..c67e2cb050 100644
> --- a/meta/recipes-devtools/go/go_1.9.bb
> +++ b/meta/recipes-devtools/go/go_1.9.bb
> @@ -1,4 +1,2 @@
>  require go-${PV}.inc
>  require go-target.inc
> -TUNE_CCARGS_remove = "-march=mips32r2"
> -SECURITY_PIE_CFLAGS_remove = "-fPIE -pie"
>
> --
> 2.14.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2] mesa: Upgrade to 17.2.1 release

[Otavio Salvador]

Hello Richard,

On Fri, Sep 22, 2017 at 3:43 AM, Richard Purdie
 wrote:
> On Thu, 2017-09-21 at 21:43 -0300, Otavio Salvador wrote:
>> On Thu, Sep 21, 2017 at 7:34 PM, Richard Purdie
>>  wrote:
>> >
>> > On Thu, 2017-09-21 at 11:08 -0300, Otavio Salvador wrote:
>> > >
>> > > Upgrade to a new stable release and drop patches applied on
>> > > upstream.
>> > >
>> > > For a full release notes, please see:
>> > > https://mesa3d.org/relnotes/17.2.0.html
>> > > https://mesa3d.org/relnotes/17.2.1.html
>> > >
>> > > Signed-off-by: Fabio Berton 
>> > > Signed-off-by: Otavio Salvador 
>> > > ---
>> > >
>> > > Changes in v2:
>> > >  - update to 17.2.1
>> > The trouble is this isn't just a "stable release", I didn't check
>> > the
>> > patch fully enough initially but now I see this was a 17.1.X ->
>> > 17.2.X
>> > change.
>> The commit log mentions the two release notes. The 17.1 is at 17.1.9
>> release but should not receive more fixes. It is advised to move to
>> 17.2.1 as it is the current release but it is up to you if we will
>> take this one or 17.1.9.
>
> Its not clear from the commit message that we're on 17.1.7, that 17.1.9
> (and maybe .8?) exist and that in going to 17.2.X, we're actually
> changing stable series. Release notes for 17.1.X are not mentioned.

17.2.0 implies it is a major release, does not?

...
>> That's the reason for autobuilder, right? I do not spawn all
>> configurations here as I don't own such build monster ...
>
> The autobuilder is a last final sanity check so we can test the
> proposed changes, Ross and I are not here just to queue and test and
> report back on people's patches.
>
> In this case *any* poky build of mesa is failing. That is likely
> because poky has wayland in distro features and your local
> configuration does not.

Possibly.

In fact I was testing for an i.MX machine and as it mangles the
PACKAGECONFIG the test was not showing your error, even with wayland
enabled.

>> > If people want us to be more flexible about taking "point version"
>> > changes later into the release cycle, we really need to start
>> > getting
>> > better about how these things get tested and how we refer to them
>> > in
>> > the commit messages.
>> See the commit log above. You are frustrated, and I get that, but
>> commit log mentions BOTH!
>
> The commit message implies we're upgrading along a stable release path.
> Now, I agree had I thought more carefully I'd have realised that to
> mention release notes of a .0, we must not be. You do call it a stable
> update though and it really isn't.
>
>> > [and yes, the fix is trivial and included below, that isn't really
>> > the
>> > point though]
>> Do you want a v3? or a 17.1.9? Let me know what I can help.
>
> I left it building locally overnight and the first fix I mentioned
> isn't enough, it eventually fails with:
>
> | make[4]: *** No rule to make target 
> '/usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml',
>  needed by 'drivers/dri2/linux-dmabuf-unstable-v1-client-protocol.h'.  Stop.
>
> so a v3 would need to figure out and fix that. Who knows what else
> might then fail. I suspect we might have more success with 17.1.9 but
> it sounds like I'll be the one who you want to test this...

I am preparing a v3 and testing with wayland and x11 enabled. Once it
works fine I send it out.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] go-dep: Fix build with hardening flags

[Matt Madison]

On Thu, Sep 21, 2017 at 11:05 PM, Khem Raj  wrote:
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/go/go-dep_0.3.0.bb | 4 
>  1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-devtools/go/go-dep_0.3.0.bb 
> b/meta/recipes-devtools/go/go-dep_0.3.0.bb
> index abfeb48370..20ea792c52 100644
> --- a/meta/recipes-devtools/go/go-dep_0.3.0.bb
> +++ b/meta/recipes-devtools/go/go-dep_0.3.0.bb
> @@ -11,6 +11,10 @@ SRCREV = "7a91b794bbfbf1f3b8b79823799316451127801b"
>
>  inherit go
>
> +TUNE_CCARGS_remove = "-march=mips32r2"
> +SECURITY_CFLAGS = "${SECURITY_NOPIE_CFLAGS}"
> +SECURITY_LDFLAGS = ""

The SECURITY* settings should go into go.bbclass, since every go
recipe will need them.

-Matt

> +
>  GO_INSTALL = "${GO_IMPORT}/cmd/dep"
>
>  RDEPENDS_${PN}-dev += "bash"
> --
> 2.14.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 4/4] mesa: Bump to version 17.2.0

[Fabien Lahoudere]

On Fri, 2017-09-22 at 13:51 +0200, Nicolas Dechesne wrote:
> On Fri, Sep 22, 2017 at 1:02 PM, Fabien Lahoudere
>  wrote:
> > Signed-off-by: Fabien Lahoudere 
> > ---
> >  meta/recipes-graphics/mesa/mesa_17.2.0.bb | 24 
> >  1 file changed, 24 insertions(+)
> >  create mode 100644 meta/recipes-graphics/mesa/mesa_17.2.0.bb
> 
> * the diff looks suspicious. you should have renamed the existing
> recipe, not just added a new one.
> * there is already a patch being discussed on the list for 17.2.1, please 
> check.
> * we will not merge any x.y.0 release of mesa, the .0 release are not
> meant for production use, as mentioned in the release notes: "Mesa
> 17.2.0 is a new development release. People who are concerned with
> stability and reliability should stick with a previous release or wait
> for Mesa 17.2.1."
> 

Indeed you're right.
So please ignore this patch.

Thanks

> > 
> > diff --git a/meta/recipes-graphics/mesa/mesa_17.2.0.bb b/meta/recipes-
> > graphics/mesa/mesa_17.2.0.bb
> > new file mode 100644
> > index 00..e522e0bbfe
> > --- /dev/null
> > +++ b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
> > @@ -0,0 +1,24 @@
> > +require ${BPN}.inc
> > +
> > +SRC_URI = "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
> > +   file://replace_glibc_check_with_linux.patch \
> > +   file://disable-asm-on-non-gcc.patch \
> > +   file://0001-Use-wayland-scanner-in-the-path.patch \
> > +   file://0002-hardware-gloat.patch \
> > +   file://vulkan-mkdir.patch \
> > +   file://llvm-config-version.patch \
> > +   file://0001-winsys-svga-drm-Include-sys-types.h.patch \
> > +   file://0001-configure.ac-Always-check-for-expat.patch \
> > +   "
> > +SRC_URI[md5sum] = "1d8d7323d11146767a37c3cb6a6d411d"
> > +SRC_URI[sha256sum] = 
> > "3123448f770eae58bc73e15480e78909defb892f10ab777e9116c9b218094943"
> > +
> > +DEPENDS += " llvm-native wayland-protocols "
> > +
> > +#because we cannot rely on the fact that all apps will use pkgconfig,
> > +#make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
> > +do_install_append() {
> > +if ${@bb.utils.contains('PACKAGECONFIG', 'egl', 'true', 'false', d)}; 
> > then
> > +sed -i -e 's/^#if defined(MESA_EGL_NO_X11_HEADERS)$/#if
> > defined(MESA_EGL_NO_X11_HEADERS) || ${@bb.utils.contains('PACKAGECONFIG', 
> > 'x11', '0', '1', d)}/'
> > ${D}${includedir}/EGL/eglplatform.h
> > +fi
> > +}
> > --
> > 2.11.0
> > 
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH v2 4/4] mesa: Bump to version 17.2.0

[Nicolas Dechesne]

On Fri, Sep 22, 2017 at 1:02 PM, Fabien Lahoudere
 wrote:
> Signed-off-by: Fabien Lahoudere 
> ---
>  meta/recipes-graphics/mesa/mesa_17.2.0.bb | 24 
>  1 file changed, 24 insertions(+)
>  create mode 100644 meta/recipes-graphics/mesa/mesa_17.2.0.bb

* the diff looks suspicious. you should have renamed the existing
recipe, not just added a new one.
* there is already a patch being discussed on the list for 17.2.1, please check.
* we will not merge any x.y.0 release of mesa, the .0 release are not
meant for production use, as mentioned in the release notes: "Mesa
17.2.0 is a new development release. People who are concerned with
stability and reliability should stick with a previous release or wait
for Mesa 17.2.1."

>
> diff --git a/meta/recipes-graphics/mesa/mesa_17.2.0.bb 
> b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
> new file mode 100644
> index 00..e522e0bbfe
> --- /dev/null
> +++ b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
> @@ -0,0 +1,24 @@
> +require ${BPN}.inc
> +
> +SRC_URI = "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
> +   file://replace_glibc_check_with_linux.patch \
> +   file://disable-asm-on-non-gcc.patch \
> +   file://0001-Use-wayland-scanner-in-the-path.patch \
> +   file://0002-hardware-gloat.patch \
> +   file://vulkan-mkdir.patch \
> +   file://llvm-config-version.patch \
> +   file://0001-winsys-svga-drm-Include-sys-types.h.patch \
> +   file://0001-configure.ac-Always-check-for-expat.patch \
> +   "
> +SRC_URI[md5sum] = "1d8d7323d11146767a37c3cb6a6d411d"
> +SRC_URI[sha256sum] = 
> "3123448f770eae58bc73e15480e78909defb892f10ab777e9116c9b218094943"
> +
> +DEPENDS += " llvm-native wayland-protocols "
> +
> +#because we cannot rely on the fact that all apps will use pkgconfig,
> +#make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
> +do_install_append() {
> +if ${@bb.utils.contains('PACKAGECONFIG', 'egl', 'true', 'false', d)}; 
> then
> +sed -i -e 's/^#if defined(MESA_EGL_NO_X11_HEADERS)$/#if 
> defined(MESA_EGL_NO_X11_HEADERS) || ${@bb.utils.contains('PACKAGECONFIG', 
> 'x11', '0', '1', d)}/' ${D}${includedir}/EGL/eglplatform.h
> +fi
> +}
> --
> 2.11.0
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for "[v2] wayland : Bump to version..." and 3 more

[Patchwork]

== Series Details ==

Series: "[v2] wayland : Bump to version..." and 3 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9073/
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 A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch)



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

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

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

[OE-core] [PATCH v2 3/4] weston: Bump version to 3.0.0

[Fabien Lahoudere]

Signed-off-by: Fabien Lahoudere 
---
 .../wayland/{weston_2.0.0.bb => weston_3.0.0.bb} | 16 +++-
 1 file changed, 7 insertions(+), 9 deletions(-)
 rename meta/recipes-graphics/wayland/{weston_2.0.0.bb => weston_3.0.0.bb} (89%)

diff --git a/meta/recipes-graphics/wayland/weston_2.0.0.bb 
b/meta/recipes-graphics/wayland/weston_3.0.0.bb
similarity index 89%
rename from meta/recipes-graphics/wayland/weston_2.0.0.bb
rename to meta/recipes-graphics/wayland/weston_3.0.0.bb
index 54b07bd6b9..6b3fad7b83 100644
--- a/meta/recipes-graphics/wayland/weston_2.0.0.bb
+++ b/meta/recipes-graphics/wayland/weston_3.0.0.bb
@@ -9,12 +9,11 @@ SRC_URI = 
"https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
file://weston.png \
file://weston.desktop \
file://0001-make-error-portable.patch \
-   file://0001-configure.ac-Fix-wayland-protocols-path.patch \
file://xwayland.weston-start \

file://0001-weston-launch-Provide-a-default-version-that-doesn-t.patch \
 "
-SRC_URI[md5sum] = "15f38945942bf2a91fe2687145fb4c7d"
-SRC_URI[sha256sum] = 
"b4e446ac27f118196f1609dab89bb3cb3e81652d981414ad860e733b355365d8"
+SRC_URI[md5sum] = "9c42a4c51a1b9f35d040fa9d45ada36d"
+SRC_URI[sha256sum] = 
"cde1d55e8dd70c3cbb3d1ec72f60e6041579caa1d6a262bd9c35e93723a5"
 
 inherit autotools pkgconfig useradd distro_features_check
 # depends on virtual/egl
@@ -25,7 +24,6 @@ DEPENDS += "wayland wayland-protocols libinput virtual/egl 
pango wayland-native"
 
 EXTRA_OECONF = "--enable-setuid-install \
 --disable-rdp-compositor \
-WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT} \
 "
 EXTRA_OECONF_append_qemux86 = "\
WESTON_NATIVE_BACKEND=fbdev-backend.so \
@@ -77,7 +75,7 @@ PACKAGECONFIG[pam] = "--with-pam,--without-pam,libpam"
 
 do_install_append() {
# Weston doesn't need the .la files to load modules, so wipe them
-   rm -f ${D}/${libdir}/libweston-2/*.la
+   rm -f ${D}/${libdir}/libweston-3/*.la
 
# If X11, ship a desktop file to launch it
if [ "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}" ]; then
@@ -94,16 +92,16 @@ do_install_append() {
 }
 
 PACKAGES += "${@bb.utils.contains('PACKAGECONFIG', 'xwayland', 
'${PN}-xwayland', '', d)} \
- libweston-2 ${PN}-examples"
+ libweston-3 ${PN}-examples"
 
 FILES_${PN} = "${bindir}/weston ${bindir}/weston-terminal 
${bindir}/weston-info ${bindir}/weston-launch ${bindir}/wcap-decode 
${libexecdir} ${libdir}/${BPN}/*.so ${datadir}"
 
-FILES_libweston-2 = "${libdir}/lib*${SOLIBS} ${libdir}/libweston-2/*.so"
-SUMMARY_libweston-2 = "Helper library for implementing 'wayland window 
managers'."
+FILES_libweston-3 = "${libdir}/lib*${SOLIBS} ${libdir}/libweston-3/*.so"
+SUMMARY_libweston-3 = "Helper library for implementing 'wayland window 
managers'."
 
 FILES_${PN}-examples = "${bindir}/*"
 
-FILES_${PN}-xwayland = "${libdir}/libweston-2/xwayland.so"
+FILES_${PN}-xwayland = "${libdir}/libweston-3/xwayland.so"
 RDEPENDS_${PN}-xwayland += "xserver-xorg-xwayland"
 
 RDEPENDS_${PN} += "xkeyboard-config"
-- 
2.11.0

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

[OE-core] [PATCH v2 2/4] wayland-protocols: Fix installation patch issue

[Fabien Lahoudere]

This patch also remove workaround to find wayland-protocols:

WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT}

in:

- gtk+3
- libsdl2
- xserver-xorg
- gstreamer1.0-plugins-bad

Signed-off-by: Fabien Lahoudere 
---
 meta/recipes-gnome/gtk+/gtk+3.inc  |  1 -
 meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb |  2 +-
 .../usesysrootprefixforpkgdatadirvariable.patch| 27 ++
 .../wayland/wayland-protocols_1.10.bb  |  1 +
 .../recipes-graphics/xorg-xserver/xserver-xorg.inc |  1 -
 .../gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb   |  1 -
 6 files changed, 29 insertions(+), 4 deletions(-)
 create mode 100644 
meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch

diff --git a/meta/recipes-gnome/gtk+/gtk+3.inc 
b/meta/recipes-gnome/gtk+/gtk+3.inc
index 0a357db049..420ead2ca2 100644
--- a/meta/recipes-gnome/gtk+/gtk+3.inc
+++ b/meta/recipes-gnome/gtk+/gtk+3.inc
@@ -35,7 +35,6 @@ EXTRA_OECONF += " \
  --enable-modules \
  --disable-cups \
  --disable-colord \
- WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT} \
  ${@bb.utils.contains("DISTRO_FEATURES", "x11", "", 
"--disable-gtk-doc", d)} \
  "
 
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb
index 12d3aaf6f0..6bfa13200b 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb
@@ -35,7 +35,7 @@ EXTRA_OECONF = "--disable-oss --disable-esd --disable-arts \
 --enable-pthreads \
 --enable-sdl-dlopen \
 --disable-rpath \
-WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT}"
+"
 
 # opengl packageconfig factored out to make it easy for distros
 # and BSP layers to pick either (desktop) opengl, gles2, or no GL
diff --git 
a/meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
 
b/meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
new file mode 100644
index 00..0922a4d2c2
--- /dev/null
+++ 
b/meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
@@ -0,0 +1,27 @@
+From 875130ee3cbcf62266901ef4b91b9a0fb6adad43 Mon Sep 17 00:00:00 2001
+From: Tomek Bury 
+Date: Fri, 4 Aug 2017 16:16:38 +0100
+Subject: Use sysroot prefix for pkgdatadir variable
+
+The pc_sysroot is automatically added to cflags and libs but not
+to 'pkg-config --variable'
+
+Upstream-Status: Backport 
[https://cgit.freedesktop.org/wayland/wayland-protocols/commit/?id=875130ee3cbcf62266901ef4b91b9a0fb6adad43]
+
+Reviewed-by: Daniel Stone 
+
+diff --git a/wayland-protocols.pc.in b/wayland-protocols.pc.in
+index a26744c..379be06 100644
+--- a/wayland-protocols.pc.in
 b/wayland-protocols.pc.in
+@@ -1,6 +1,6 @@
+ prefix=@prefix@
+ datarootdir=@datarootdir@
+-pkgdatadir=@datadir@/@PACKAGE@
++pkgdatadir=${pc_sysrootdir}@datadir@/@PACKAGE@
+ 
+ Name: Wayland Protocols
+ Description: Wayland protocol files
+-- 
+cgit v0.10.2
+
diff --git a/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb 
b/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
index 4f9e9f32bf..1ff12c607b 100644
--- a/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
+++ b/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=c7b12b6702da38ca028ace54aae3d484 \
 
file://stable/presentation-time/presentation-time.xml;endline=26;md5=4646cd7d9edc9fa55db941f2d3a7dc53"
 
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
+  file://usesysrootprefixforpkgdatadirvariable.patch \
"
 SRC_URI[md5sum] = "84a7846c2b6a6a3e265fc9be36453e60"
 SRC_URI[sha256sum] = 
"5719c51d7354864983171c5083e93a72ac99229e2b460c4bb10513de08839c0a"
diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
index 863d80ce43..e8025de55f 100644
--- a/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
@@ -117,7 +117,6 @@ EXTRA_OECONF += "--with-fop=no \
  --sysconfdir=/etc/X11 \
  --localstatedir=/var \
  --with-xkb-output=/var/lib/xkb \
- WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT} \
 "
 
 OPENGL_PKGCONFIGS = "dri glx glamor dri3 xshmfence"
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb
index 8321da0c27..a83a5bab21 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb
@@ -22,5 +22,4 

[OE-core] [PATCH v2 4/4] mesa: Bump to version 17.2.0

[Fabien Lahoudere]

Signed-off-by: Fabien Lahoudere 
---
 meta/recipes-graphics/mesa/mesa_17.2.0.bb | 24 
 1 file changed, 24 insertions(+)
 create mode 100644 meta/recipes-graphics/mesa/mesa_17.2.0.bb

diff --git a/meta/recipes-graphics/mesa/mesa_17.2.0.bb 
b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
new file mode 100644
index 00..e522e0bbfe
--- /dev/null
+++ b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
@@ -0,0 +1,24 @@
+require ${BPN}.inc
+
+SRC_URI = "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
+   file://replace_glibc_check_with_linux.patch \
+   file://disable-asm-on-non-gcc.patch \
+   file://0001-Use-wayland-scanner-in-the-path.patch \
+   file://0002-hardware-gloat.patch \
+   file://vulkan-mkdir.patch \
+   file://llvm-config-version.patch \
+   file://0001-winsys-svga-drm-Include-sys-types.h.patch \
+   file://0001-configure.ac-Always-check-for-expat.patch \
+   "
+SRC_URI[md5sum] = "1d8d7323d11146767a37c3cb6a6d411d"
+SRC_URI[sha256sum] = 
"3123448f770eae58bc73e15480e78909defb892f10ab777e9116c9b218094943"
+
+DEPENDS += " llvm-native wayland-protocols "
+
+#because we cannot rely on the fact that all apps will use pkgconfig,
+#make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
+do_install_append() {
+if ${@bb.utils.contains('PACKAGECONFIG', 'egl', 'true', 'false', d)}; then
+sed -i -e 's/^#if defined(MESA_EGL_NO_X11_HEADERS)$/#if 
defined(MESA_EGL_NO_X11_HEADERS) || ${@bb.utils.contains('PACKAGECONFIG', 
'x11', '0', '1', d)}/' ${D}${includedir}/EGL/eglplatform.h
+fi
+}
-- 
2.11.0

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

[OE-core] [PATCH v2 1/4] wayland : Bump to version 1.14.0

[Fabien Lahoudere]

Signed-off-by: Fabien Lahoudere 
---
 .../recipes-graphics/wayland/{wayland_1.13.0.bb => wayland_1.14.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/wayland/{wayland_1.13.0.bb => wayland_1.14.0.bb} 
(92%)

diff --git a/meta/recipes-graphics/wayland/wayland_1.13.0.bb 
b/meta/recipes-graphics/wayland/wayland_1.14.0.bb
similarity index 92%
rename from meta/recipes-graphics/wayland/wayland_1.13.0.bb
rename to meta/recipes-graphics/wayland/wayland_1.14.0.bb
index b9396b6c75..2a2489d658 100644
--- a/meta/recipes-graphics/wayland/wayland_1.13.0.bb
+++ b/meta/recipes-graphics/wayland/wayland_1.14.0.bb
@@ -14,8 +14,8 @@ DEPENDS = "expat libxml2 libffi wayland-native"
 
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
"
-SRC_URI[md5sum] = "cae152ed956da6de53f9727bc1c45039"
-SRC_URI[sha256sum] = 
"69b052c031a61e89af7cc8780893d0da1e301492352aa449dee9345043e6fe51"
+SRC_URI[md5sum] = "0235f6075c32c3be61cff94fa0b9f108"
+SRC_URI[sha256sum] = 
"ed80cabc0961a759a42092e2c39aabfc1ec9a13c86c98bbe2b812f008da27ab8"
 
 inherit autotools pkgconfig
 
-- 
2.11.0

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

[OE-core] [morty][PATCH] image.bbclass: Sorted ctypes to avoid basehash error

[Gerson Fernando Budke]

When selected multiple subimages a similar error could happend:
  Variable do_image_cpio[subimages] value changed \
from 'cpio.gz.u-boot cpio.gz' to 'cpio.gz cpio.gz.u-boot'
To avoid this, 'ctypes' should be sorted at 'gen_conversion_cmds'.

This garantee that 'CONVERSION_CMD_xxx' are always written in tha same
order and consequently 'do_image_cpio' have the same hash.

(From OE-Core rev: 271f1a5f65b8685a1e3645026876251122ef3974)

Signed-off-by: Gerson Fernando Budke 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie 
---
 meta/classes/image.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ef2b38aeaf..9c9f14a99a 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -453,7 +453,7 @@ python () {

 rm_tmp_images = set()
 def gen_conversion_cmds(bt):
-for ctype in ctypes:
+for ctype in sorted(ctypes):
 if bt.endswith("." + ctype):
 type = bt[0:-len(ctype) - 1]
 if type.startswith("debugfs_"):
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 1/2] systemd: change some RRECOMMENDS to RDEPENDS

[Martin Jansa]

This doesn't seem to work correctly for MACHINEs with empty SERIAL_CONSOLE,
because with empty SERIAL_CONSOLE there is no systemd-serialgetty package
(because it's also empty) and the build fails with:

Collected errors:
 * calculate_dependencies_for: Cannot satisfy the following dependencies
for packagegroup-core-boot:
 *  systemd-serialgetty *
 * opkg_solver_install: Cannot install package packagegroup-core-boot.

If you're setting NO_RECOMMENDATIONS to "1", then you should expect that
some recommended functionality will be missing, no?

On Tue, Sep 5, 2017 at 10:07 AM, Chen Qi  wrote:

> Set NO_RECOMMENDATIONS to "1", build and start a systemd image, and we
> could not get serial getty spawned, thus causing the user not able to
> login via serial port.
>
> E.g.
> MACHINE=qemux86-64 bitbake core-image-minimal
> runqemu qemux86-64 nographic
>
> And we cannot login onto the system.
>
> Move util-linux-agetty and systemd-serialgetty (determined by
> PACKAGECONFIG)
> from RRECOMMENDS to RDEPENDS to fix the above problem.
>
> Signed-off-by: Chen Qi 
> ---
>  meta/recipes-core/systemd/systemd_234.bb | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/meta/recipes-core/systemd/systemd_234.bb
> b/meta/recipes-core/systemd/systemd_234.bb
> index 2736f38..2695e15 100644
> --- a/meta/recipes-core/systemd/systemd_234.bb
> +++ b/meta/recipes-core/systemd/systemd_234.bb
> @@ -492,13 +492,13 @@ FILES_${PN} = " ${base_bindir}/* \
>
>  FILES_${PN}-dev += "${base_libdir}/security/*.la
> ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd"
>
> -RDEPENDS_${PN} += "kmod dbus util-linux-mount udev (= ${EXTENDPKGV})"
> +RDEPENDS_${PN} += "kmod dbus util-linux-mount udev (= ${EXTENDPKGV})
> util-linux-agetty"
> +RDEPENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
> 'serial-getty-generator', '', 'systemd-serialgetty', d)}"
>  RDEPENDS_${PN} += "volatile-binds update-rc.d"
>
> -RRECOMMENDS_${PN} += "${@bb.utils.contains('PACKAGECONFIG',
> 'serial-getty-generator', '', 'systemd-serialgetty', d)} \
> -  systemd-extra-utils \
> +RRECOMMENDS_${PN} += "systemd-extra-utils \
>systemd-compat-units udev-hwdb \
> -  util-linux-agetty  util-linux-fsck e2fsprogs-e2fsck
> \
> +  util-linux-fsck e2fsprogs-e2fsck \
>kernel-module-autofs4 kernel-module-unix
> kernel-module-ipv6 \
>os-release \
>  "
> --
> 1.9.1
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for "wayland : Bump to version 1.14..." and 3 more

[Patchwork]

== Series Details ==

Series: "wayland : Bump to version 1.14..." and 3 more
Revision: 1
URL   : https://patchwork.openembedded.org/series/9070/
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-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
 (possible values: Pending, Submitted, Accepted, Backport, Denied, 
Inappropriate)

* Issue A patch file has been added, but does not have a 
Signed-off-by tag [test_signed_off_by_presence] 
  Suggested fixSign off the added patch file 
(meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch)



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 3/4] weston: Bump version to 3.0.0

[Fabien Lahoudere]

Signed-off-by: Fabien Lahoudere 
---
 .../wayland/{weston_2.0.0.bb => weston_3.0.0.bb} | 16 +++-
 1 file changed, 7 insertions(+), 9 deletions(-)
 rename meta/recipes-graphics/wayland/{weston_2.0.0.bb => weston_3.0.0.bb} (89%)

diff --git a/meta/recipes-graphics/wayland/weston_2.0.0.bb 
b/meta/recipes-graphics/wayland/weston_3.0.0.bb
similarity index 89%
rename from meta/recipes-graphics/wayland/weston_2.0.0.bb
rename to meta/recipes-graphics/wayland/weston_3.0.0.bb
index 54b07bd6b9..6b3fad7b83 100644
--- a/meta/recipes-graphics/wayland/weston_2.0.0.bb
+++ b/meta/recipes-graphics/wayland/weston_3.0.0.bb
@@ -9,12 +9,11 @@ SRC_URI = 
"https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
file://weston.png \
file://weston.desktop \
file://0001-make-error-portable.patch \
-   file://0001-configure.ac-Fix-wayland-protocols-path.patch \
file://xwayland.weston-start \

file://0001-weston-launch-Provide-a-default-version-that-doesn-t.patch \
 "
-SRC_URI[md5sum] = "15f38945942bf2a91fe2687145fb4c7d"
-SRC_URI[sha256sum] = 
"b4e446ac27f118196f1609dab89bb3cb3e81652d981414ad860e733b355365d8"
+SRC_URI[md5sum] = "9c42a4c51a1b9f35d040fa9d45ada36d"
+SRC_URI[sha256sum] = 
"cde1d55e8dd70c3cbb3d1ec72f60e6041579caa1d6a262bd9c35e93723a5"
 
 inherit autotools pkgconfig useradd distro_features_check
 # depends on virtual/egl
@@ -25,7 +24,6 @@ DEPENDS += "wayland wayland-protocols libinput virtual/egl 
pango wayland-native"
 
 EXTRA_OECONF = "--enable-setuid-install \
 --disable-rdp-compositor \
-WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT} \
 "
 EXTRA_OECONF_append_qemux86 = "\
WESTON_NATIVE_BACKEND=fbdev-backend.so \
@@ -77,7 +75,7 @@ PACKAGECONFIG[pam] = "--with-pam,--without-pam,libpam"
 
 do_install_append() {
# Weston doesn't need the .la files to load modules, so wipe them
-   rm -f ${D}/${libdir}/libweston-2/*.la
+   rm -f ${D}/${libdir}/libweston-3/*.la
 
# If X11, ship a desktop file to launch it
if [ "${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)}" ]; then
@@ -94,16 +92,16 @@ do_install_append() {
 }
 
 PACKAGES += "${@bb.utils.contains('PACKAGECONFIG', 'xwayland', 
'${PN}-xwayland', '', d)} \
- libweston-2 ${PN}-examples"
+ libweston-3 ${PN}-examples"
 
 FILES_${PN} = "${bindir}/weston ${bindir}/weston-terminal 
${bindir}/weston-info ${bindir}/weston-launch ${bindir}/wcap-decode 
${libexecdir} ${libdir}/${BPN}/*.so ${datadir}"
 
-FILES_libweston-2 = "${libdir}/lib*${SOLIBS} ${libdir}/libweston-2/*.so"
-SUMMARY_libweston-2 = "Helper library for implementing 'wayland window 
managers'."
+FILES_libweston-3 = "${libdir}/lib*${SOLIBS} ${libdir}/libweston-3/*.so"
+SUMMARY_libweston-3 = "Helper library for implementing 'wayland window 
managers'."
 
 FILES_${PN}-examples = "${bindir}/*"
 
-FILES_${PN}-xwayland = "${libdir}/libweston-2/xwayland.so"
+FILES_${PN}-xwayland = "${libdir}/libweston-3/xwayland.so"
 RDEPENDS_${PN}-xwayland += "xserver-xorg-xwayland"
 
 RDEPENDS_${PN} += "xkeyboard-config"
-- 
2.11.0

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

[OE-core] [PATCH 1/4] wayland : Bump to version 1.14.0

[Fabien Lahoudere]

Signed-off-by: Fabien Lahoudere 
---
 .../recipes-graphics/wayland/{wayland_1.13.0.bb => wayland_1.14.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-graphics/wayland/{wayland_1.13.0.bb => wayland_1.14.0.bb} 
(92%)

diff --git a/meta/recipes-graphics/wayland/wayland_1.13.0.bb 
b/meta/recipes-graphics/wayland/wayland_1.14.0.bb
similarity index 92%
rename from meta/recipes-graphics/wayland/wayland_1.13.0.bb
rename to meta/recipes-graphics/wayland/wayland_1.14.0.bb
index b9396b6c75..2a2489d658 100644
--- a/meta/recipes-graphics/wayland/wayland_1.13.0.bb
+++ b/meta/recipes-graphics/wayland/wayland_1.14.0.bb
@@ -14,8 +14,8 @@ DEPENDS = "expat libxml2 libffi wayland-native"
 
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
"
-SRC_URI[md5sum] = "cae152ed956da6de53f9727bc1c45039"
-SRC_URI[sha256sum] = 
"69b052c031a61e89af7cc8780893d0da1e301492352aa449dee9345043e6fe51"
+SRC_URI[md5sum] = "0235f6075c32c3be61cff94fa0b9f108"
+SRC_URI[sha256sum] = 
"ed80cabc0961a759a42092e2c39aabfc1ec9a13c86c98bbe2b812f008da27ab8"
 
 inherit autotools pkgconfig
 
-- 
2.11.0

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

[OE-core] [PATCH 4/4] mesa: Bump to version 17.2.0

[Fabien Lahoudere]

Signed-off-by: Fabien Lahoudere 
---
 meta/recipes-graphics/mesa/mesa_17.2.0.bb | 24 
 1 file changed, 24 insertions(+)
 create mode 100644 meta/recipes-graphics/mesa/mesa_17.2.0.bb

diff --git a/meta/recipes-graphics/mesa/mesa_17.2.0.bb 
b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
new file mode 100644
index 00..e522e0bbfe
--- /dev/null
+++ b/meta/recipes-graphics/mesa/mesa_17.2.0.bb
@@ -0,0 +1,24 @@
+require ${BPN}.inc
+
+SRC_URI = "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
+   file://replace_glibc_check_with_linux.patch \
+   file://disable-asm-on-non-gcc.patch \
+   file://0001-Use-wayland-scanner-in-the-path.patch \
+   file://0002-hardware-gloat.patch \
+   file://vulkan-mkdir.patch \
+   file://llvm-config-version.patch \
+   file://0001-winsys-svga-drm-Include-sys-types.h.patch \
+   file://0001-configure.ac-Always-check-for-expat.patch \
+   "
+SRC_URI[md5sum] = "1d8d7323d11146767a37c3cb6a6d411d"
+SRC_URI[sha256sum] = 
"3123448f770eae58bc73e15480e78909defb892f10ab777e9116c9b218094943"
+
+DEPENDS += " llvm-native wayland-protocols "
+
+#because we cannot rely on the fact that all apps will use pkgconfig,
+#make eglplatform.h independent of MESA_EGL_NO_X11_HEADER
+do_install_append() {
+if ${@bb.utils.contains('PACKAGECONFIG', 'egl', 'true', 'false', d)}; then
+sed -i -e 's/^#if defined(MESA_EGL_NO_X11_HEADERS)$/#if 
defined(MESA_EGL_NO_X11_HEADERS) || ${@bb.utils.contains('PACKAGECONFIG', 
'x11', '0', '1', d)}/' ${D}${includedir}/EGL/eglplatform.h
+fi
+}
-- 
2.11.0

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

[OE-core] [PATCH 2/4] wayland-protocols: Fix installation patch issue

[Fabien Lahoudere]

This patch also remove workaround to find wayland-protocols:

WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT}

in:

- gtk+3
- libsdl2
- xserver-xorg
- gstreamer1.0-plugins-bad

Signed-off-by: Fabien Lahoudere 
---
 meta/recipes-gnome/gtk+/gtk+3.inc  |  1 -
 meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb |  2 +-
 .../usesysrootprefixforpkgdatadirvariable.patch| 27 ++
 .../wayland/wayland-protocols_1.10.bb  |  1 +
 .../recipes-graphics/xorg-xserver/xserver-xorg.inc |  1 -
 .../gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb   |  1 -
 6 files changed, 29 insertions(+), 4 deletions(-)
 create mode 100644 
meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch

diff --git a/meta/recipes-gnome/gtk+/gtk+3.inc 
b/meta/recipes-gnome/gtk+/gtk+3.inc
index 0a357db049..420ead2ca2 100644
--- a/meta/recipes-gnome/gtk+/gtk+3.inc
+++ b/meta/recipes-gnome/gtk+/gtk+3.inc
@@ -35,7 +35,6 @@ EXTRA_OECONF += " \
  --enable-modules \
  --disable-cups \
  --disable-colord \
- WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT} \
  ${@bb.utils.contains("DISTRO_FEATURES", "x11", "", 
"--disable-gtk-doc", d)} \
  "
 
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb 
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb
index 12d3aaf6f0..6bfa13200b 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb
@@ -35,7 +35,7 @@ EXTRA_OECONF = "--disable-oss --disable-esd --disable-arts \
 --enable-pthreads \
 --enable-sdl-dlopen \
 --disable-rpath \
-WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT}"
+"
 
 # opengl packageconfig factored out to make it easy for distros
 # and BSP layers to pick either (desktop) opengl, gles2, or no GL
diff --git 
a/meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
 
b/meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
new file mode 100644
index 00..e0d63448d6
--- /dev/null
+++ 
b/meta/recipes-graphics/wayland/wayland-protocols/usesysrootprefixforpkgdatadirvariable.patch
@@ -0,0 +1,27 @@
+From 875130ee3cbcf62266901ef4b91b9a0fb6adad43 Mon Sep 17 00:00:00 2001
+From: Tomek Bury 
+Date: Fri, 4 Aug 2017 16:16:38 +0100
+Subject: Use sysroot prefix for pkgdatadir variable
+
+The pc_sysroot is automatically added to cflags and libs but not
+to 'pkg-config --variable'
+
+Reviewed-by: Daniel Stone 
+
+Upstream-status: Backport 
[https://cgit.freedesktop.org/wayland/wayland-protocols/commit/?id=875130ee3cbcf62266901ef4b91b9a0fb6adad43]
+
+diff --git a/wayland-protocols.pc.in b/wayland-protocols.pc.in
+index a26744c..379be06 100644
+--- a/wayland-protocols.pc.in
 b/wayland-protocols.pc.in
+@@ -1,6 +1,6 @@
+ prefix=@prefix@
+ datarootdir=@datarootdir@
+-pkgdatadir=@datadir@/@PACKAGE@
++pkgdatadir=${pc_sysrootdir}@datadir@/@PACKAGE@
+ 
+ Name: Wayland Protocols
+ Description: Wayland protocol files
+-- 
+cgit v0.10.2
+
diff --git a/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb 
b/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
index 4f9e9f32bf..1ff12c607b 100644
--- a/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
+++ b/meta/recipes-graphics/wayland/wayland-protocols_1.10.bb
@@ -10,6 +10,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=c7b12b6702da38ca028ace54aae3d484 \
 
file://stable/presentation-time/presentation-time.xml;endline=26;md5=4646cd7d9edc9fa55db941f2d3a7dc53"
 
 SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
+  file://usesysrootprefixforpkgdatadirvariable.patch \
"
 SRC_URI[md5sum] = "84a7846c2b6a6a3e265fc9be36453e60"
 SRC_URI[sha256sum] = 
"5719c51d7354864983171c5083e93a72ac99229e2b460c4bb10513de08839c0a"
diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
index 863d80ce43..e8025de55f 100644
--- a/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
@@ -117,7 +117,6 @@ EXTRA_OECONF += "--with-fop=no \
  --sysconfdir=/etc/X11 \
  --localstatedir=/var \
  --with-xkb-output=/var/lib/xkb \
- WAYLAND_PROTOCOLS_SYSROOT_DIR=${RECIPE_SYSROOT} \
 "
 
 OPENGL_PKGCONFIGS = "dri glx glamor dri3 xshmfence"
diff --git 
a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb
index 8321da0c27..a83a5bab21 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.2.bb
@@ -22,5 +22,4 

[OE-core] [PATCH v2] useradd-staticids: don't create username-group if gid is specified

[André Draszik]

From: André Draszik 

Adding distcc to an image, and having staticids enabled,
doesn't work as it causes a a superfluous 'distcc' group
being added using a conflicting  GID, thus failing the
build:
 | ERROR: distcc-3.2-r0 do_prepare_recipe_sysroot: distcc: groupadd command did 
not succeed.

Compared to other recipes, the distcc recipe only
specifies --gid for the primary group, and doesn't specify
--no-user-group, but when --gid is given, it doesn't make
sense to create a matching username-group in addition,
even if --no-user-group was not specified, and 'useradd'
actually complains if --gid and --user-group are given
both.

If only --gid is given, the current code in here
effectively behaves as if --user-group was specified,
taking the group-id of the username-group from the
--gid parameter. This causes the error above, as we try
to add a new group (distcc) with an existing group-id
(nogroup).

This is contrary to the comment in this file just above,
contrary to what useradd can do, contrary to behaviour
without the useradd-staticids bbclass, and non-intuitive.

Change the code such that a username-group is only created
- if a primary group using --gid was not specified, or
- if --no-user-group was not specified

To be in line with useradd, if gid is not given, and
--no-user-group is given, we add the user to the group
'users', which mimics useradd's behaviour.

Signed-off-by: André Draszik 

---
v2: bring this even more in line with useradd
---
 meta/classes/useradd-staticids.bbclass | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/meta/classes/useradd-staticids.bbclass 
b/meta/classes/useradd-staticids.bbclass
index ce4ac62ab5..eb8e59e67a 100644
--- a/meta/classes/useradd-staticids.bbclass
+++ b/meta/classes/useradd-staticids.bbclass
@@ -102,9 +102,13 @@ def update_useradd_static_config(d):
 # So if the implicit username-group creation is on, then the 
implicit groupname (LOGIN)
 # is used, and we disable the user_group option.
 #
-user_group = uaargs.user_group is None or uaargs.user_group is True
-uaargs.groupname = uaargs.LOGIN if user_group else uaargs.gid
-uaargs.groupid = field[3] or uaargs.gid or uaargs.groupname
+if uaargs.gid:
+uaargs.groupname = uaargs.gid
+elif uaargs.user_group is not False:
+uaargs.groupname = uaargs.LOGIN
+else:
+uaargs.groupname = 'users'
+uaargs.groupid = field[3] or uaargs.groupname
 
 if uaargs.groupid and uaargs.gid != uaargs.groupid:
 newgroup = None
-- 
2.14.1

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

Re: [OE-core] [PATCH V2] python2/3: Remove building host path from packages

[Dengke Du]

The libxml2 ,python3-dbus and gpgme used host include and/or library 
paths, if we


remove those host paths in the end of do_install task, those host paths 
would not


populate in sysroot, so it's better to put the removing action in 
PACKAGE_PREPROCESS_FUNCS.



On 2017年06月08日 21:36, Burton, Ross wrote:


I think the seds need to be moved earlier in the build, or that py 
file recompiled.


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

[OE-core] ✗ patchtest: failure for lame: backport patch to fix CVE-2017-13712

[Patchwork]

== Series Details ==

Series: lame: backport patch to fix CVE-2017-13712
Revision: 1
URL   : https://patchwork.openembedded.org/series/9069/
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:



* Patch[1/1] lame: fix CVE-2017-13712
 Issue Missing or incorrectly formatted CVE tag in included patch 
file [test_cve_tag_format] 
  Suggested fixCorrect or include the CVE tag on cve patch with format: 
"CVE: CVE--"



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

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

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

Re: [OE-core] [PATCH v2] mesa: Upgrade to 17.2.1 release

[Richard Purdie]

On Thu, 2017-09-21 at 21:43 -0300, Otavio Salvador wrote:
> Hello Richard,
> 
> On Thu, Sep 21, 2017 at 7:34 PM, Richard Purdie
>  wrote:
> > 
> > On Thu, 2017-09-21 at 11:08 -0300, Otavio Salvador wrote:
> > > 
> > > Upgrade to a new stable release and drop patches applied on
> > > upstream.
> > > 
> > > For a full release notes, please see:
> > > https://mesa3d.org/relnotes/17.2.0.html
> > > https://mesa3d.org/relnotes/17.2.1.html
> > > 
> > > Signed-off-by: Fabio Berton 
> > > Signed-off-by: Otavio Salvador 
> > > ---
> > > 
> > > Changes in v2:
> > >  - update to 17.2.1
> > The trouble is this isn't just a "stable release", I didn't check
> > the
> > patch fully enough initially but now I see this was a 17.1.X ->
> > 17.2.X
> > change.
> The commit log mentions the two release notes. The 17.1 is at 17.1.9
> release but should not receive more fixes. It is advised to move to
> 17.2.1 as it is the current release but it is up to you if we will
> take this one or 17.1.9.

Its not clear from the commit message that we're on 17.1.7, that 17.1.9
(and maybe .8?) exist and that in going to 17.2.X, we're actually
changing stable series. Release notes for 17.1.X are not mentioned.

Every upstream out there will advise moving to their latest version but
that doesn't mean it will work. In fact here it doesn't.

> > When I tried building it locally I get:
> > 
> > > 
> > > checking for x11 xext xdamage >= 1.1 xfixes x11-xcb xcb xcb-glx
> > > >= 1.8.1 xcb-dri2 >= 1.8 xxf86vm... yes
> > > checking for wayland-scanner...
> > > /media/build1/poky/build/tmp/work/core2-64-poky-
> > > linux/mesa/2_17.2.1-r0/recipe-sysroot-native/usr/bin/wayland-
> > > scanner
> > > checking for wayland-client >= 1.11 wayland-server >= 1.11... yes
> > > configure: error: wayland-protocols >= 1.8 is needed to compile
> > > the wayland platform
> > > NOTE: The following config.log files may provide further
> > > information.
> > and basically I just wiped out a round of autobuilder testing of a
> > larger patchset due to this.
> That's the reason for autobuilder, right? I do not spawn all
> configurations here as I don't own such build monster ...

The autobuilder is a last final sanity check so we can test the
proposed changes, Ross and I are not here just to queue and test and
report back on people's patches.

In this case *any* poky build of mesa is failing. That is likely
because poky has wayland in distro features and your local
configuration does not.

> > If people want us to be more flexible about taking "point version"
> > changes later into the release cycle, we really need to start
> > getting
> > better about how these things get tested and how we refer to them
> > in
> > the commit messages.
> See the commit log above. You are frustrated, and I get that, but
> commit log mentions BOTH!

The commit message implies we're upgrading along a stable release path.
Now, I agree had I thought more carefully I'd have realised that to
mention release notes of a .0, we must not be. You do call it a stable
update though and it really isn't.

> > [and yes, the fix is trivial and included below, that isn't really
> > the
> > point though]
> Do you want a v3? or a 17.1.9? Let me know what I can help.

I left it building locally overnight and the first fix I mentioned
isn't enough, it eventually fails with:

| make[4]: *** No rule to make target 
'/usr/share/wayland-protocols/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml',
 needed by 'drivers/dri2/linux-dmabuf-unstable-v1-client-protocol.h'.  Stop.

so a v3 would need to figure out and fix that. Who knows what else
might then fail. I suspect we might have more success with 17.1.9 but
it sounds like I'll be the one who you want to test this...

Cheers,

Richard



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

[OE-core] [PATCH 1/1] lame: fix CVE-2017-13712

[kai.kang]

From: Kai Kang 

Backport patch to fix CVE-2017-13712 for lame.

Signed-off-by: Kai Kang 
---
 .../lame/lame/CVE-2017-13712.patch | 309 +
 meta/recipes-multimedia/lame/lame_3.99.5.bb|   4 +-
 2 files changed, 312 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-multimedia/lame/lame/CVE-2017-13712.patch

diff --git a/meta/recipes-multimedia/lame/lame/CVE-2017-13712.patch 
b/meta/recipes-multimedia/lame/lame/CVE-2017-13712.patch
new file mode 100644
index 00..f9ec7665ff
--- /dev/null
+++ b/meta/recipes-multimedia/lame/lame/CVE-2017-13712.patch
@@ -0,0 +1,309 @@
+Upstream-Status: Backport 
[http://lame.cvs.sourceforge.net/viewvc/lame/lame/libmp3lame/id3tag.c?r1=1.79=1.80]
+
+Backport patch to fix CVE-2017-13712 for lame.
+
+Signed-off-by: Kai Kang 
+---
+--- a/libmp3lame/id3tag.c  2017/08/22 19:44:05 1.79
 b/libmp3lame/id3tag.c  2017/08/28 15:39:51 1.80
+@@ -194,7 +194,11 @@
+ }
+ #endif
+ 
+-
++static int
++is_lame_internal_flags_null(lame_t gfp)
++{
++return (gfp && gfp->internal_flags) ? 0 : 1;
++}
+ 
+ static int
+ id3v2_add_ucs2_lng(lame_t gfp, uint32_t frame_id, unsigned short const *desc, 
unsigned short const *text);
+@@ -238,8 +242,7 @@
+ static void
+ id3v2AddAudioDuration(lame_t gfp, double ms)
+ {
+-lame_internal_flags *gfc = gfp != 0 ? gfp->internal_flags : 0;
+-SessionConfig_t const *const cfg = >cfg;
++SessionConfig_t const *const cfg = >internal_flags->cfg; /* caller 
checked pointers */
+ charbuffer[1024];
+ double const max_ulong = MAX_U_32_NUM;
+ unsigned long playlength_ms;
+@@ -280,7 +283,12 @@
+ void
+ id3tag_init(lame_t gfp)
+ {
+-lame_internal_flags *gfc = gfp->internal_flags;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return;
++}
++gfc = gfp->internal_flags;
+ free_id3tag(gfc);
+ memset(>tag_spec, 0, sizeof gfc->tag_spec);
+ gfc->tag_spec.genre_id3v1 = GENRE_NUM_UNKNOWN;
+@@ -293,7 +301,12 @@
+ void
+ id3tag_add_v2(lame_t gfp)
+ {
+-lame_internal_flags *gfc = gfp->internal_flags;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return;
++}
++gfc = gfp->internal_flags;
+ gfc->tag_spec.flags &= ~V1_ONLY_FLAG;
+ gfc->tag_spec.flags |= ADD_V2_FLAG;
+ }
+@@ -301,7 +314,12 @@
+ void
+ id3tag_v1_only(lame_t gfp)
+ {
+-lame_internal_flags *gfc = gfp->internal_flags;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return;
++}
++gfc = gfp->internal_flags;
+ gfc->tag_spec.flags &= ~(ADD_V2_FLAG | V2_ONLY_FLAG);
+ gfc->tag_spec.flags |= V1_ONLY_FLAG;
+ }
+@@ -309,7 +327,12 @@
+ void
+ id3tag_v2_only(lame_t gfp)
+ {
+-lame_internal_flags *gfc = gfp->internal_flags;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return;
++}
++gfc = gfp->internal_flags;
+ gfc->tag_spec.flags &= ~V1_ONLY_FLAG;
+ gfc->tag_spec.flags |= V2_ONLY_FLAG;
+ }
+@@ -317,7 +340,12 @@
+ void
+ id3tag_space_v1(lame_t gfp)
+ {
+-lame_internal_flags *gfc = gfp->internal_flags;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return;
++}
++gfc = gfp->internal_flags;
+ gfc->tag_spec.flags &= ~V2_ONLY_FLAG;
+ gfc->tag_spec.flags |= SPACE_V1_FLAG;
+ }
+@@ -331,7 +359,12 @@
+ void
+ id3tag_set_pad(lame_t gfp, size_t n)
+ {
+-lame_internal_flags *gfc = gfp->internal_flags;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return;
++}
++gfc = gfp->internal_flags;
+ gfc->tag_spec.flags &= ~V1_ONLY_FLAG;
+ gfc->tag_spec.flags |= PAD_V2_FLAG;
+ gfc->tag_spec.flags |= ADD_V2_FLAG;
+@@ -583,22 +616,29 @@
+ int
+ id3tag_set_albumart(lame_t gfp, const char *image, size_t size)
+ {
+-int mimetype = 0;
+-unsigned char const *data = (unsigned char const *) image;
+-lame_internal_flags *gfc = gfp->internal_flags;
+-
+-/* determine MIME type from the actual image data */
+-if (2 < size && data[0] == 0xFF && data[1] == 0xD8) {
+-mimetype = MIMETYPE_JPEG;
+-}
+-else if (4 < size && data[0] == 0x89 && strncmp((const char *) [1], 
"PNG", 3) == 0) {
+-mimetype = MIMETYPE_PNG;
+-}
+-else if (4 < size && strncmp((const char *) data, "GIF8", 4) == 0) {
+-mimetype = MIMETYPE_GIF;
++int mimetype = MIMETYPE_NONE;
++lame_internal_flags *gfc = 0;
++
++if (is_lame_internal_flags_null(gfp)) {
++return 0;
+ }
+-else {
+-return -1;
++gfc = gfp->internal_flags;
++
++if (image != 0) {
++unsigned char const *data = (unsigned char const *) image;
++/* determine MIME type from the actual image data */
++if (2 < size && data[0] == 0xFF && data[1] 

[OE-core] [PATCH 0/1] lame: backport patch to fix CVE-2017-13712

[kai.kang]

From: Kai Kang 

The following changes since commit eac8a5cf4212feaf8baf230e9ae991939732141d:

  oe-build-perf-report-email.py: add cc and bcc options (2017-09-21 23:16:55 
+0100)

are available in the git repository at:

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

Kai Kang (1):
  lame: fix CVE-2017-13712

 .../lame/lame/CVE-2017-13712.patch | 309 +
 meta/recipes-multimedia/lame/lame_3.99.5.bb|   4 +-
 2 files changed, 312 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-multimedia/lame/lame/CVE-2017-13712.patch

-- 
2.14.1

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

Re: [OE-core] [PATCH 2/2] go: Remove mips32r2 from march to get cgo working

[Richard Purdie]

On Thu, 2017-09-21 at 10:42 -0700, Khem Raj wrote:
> on mips, cgo used mips32r1 and that conflicts with mips32r2
> lets remove it for now and work go upstream to make it work
> for golang as well
> 
> Fixes
> > 
> > # runtime/cgo
> > cc1: error: '-mips32r2' conflicts with the other architecture
> > options, which specify a mips32 processor
> Fixes [YOCTO #12108]
> 
> Signed-off-by: Khem Raj 
> ---
>  meta/recipes-devtools/go/go-common.inc | 4 
>  meta/recipes-devtools/go/go_1.9.bb | 2 --
>  2 files changed, 4 insertions(+), 2 deletions(-)

I think this causes:

https://autobuilder.yocto.io/builders/nightly-world-lsb/builds/486/steps/BuildImages/logs/stdio

| # /tmp/go-build282041009/libstd.so
| 
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/build/tmp/work/i586-poky-linux/go-runtime/1.9-r0/go/pkg/tool/linux_amd64/link:
 running i586-poky-linux-gcc failed: exit status 1
| /tmp/go-link-130351246/go.o:(.data.rel.ro+0x36bfcc): undefined reference to 
`main.init'
| /tmp/go-link-130351246/go.o:(.data.rel.ro+0x36bfd0): undefined reference to 
`main.main'
| collect2: error: ld returned 1 exit status
| 
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_compile (log file is located at 
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/build/tmp/work/i586-poky-linux/go-runtime/1.9-r0/temp/log.do_compile.29509)
NOTE: recipe go-runtime-1.9-r0: task do_compile: Failed
ERROR: Task 
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/meta/recipes-devtools/go/go-runtime_1.9.bb:do_compile)
 failed with exit code '1'

Cheers,

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

[OE-core] [PATCH] go-dep: Fix build with hardening flags

[Khem Raj]

Signed-off-by: Khem Raj 
---
 meta/recipes-devtools/go/go-dep_0.3.0.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/meta/recipes-devtools/go/go-dep_0.3.0.bb 
b/meta/recipes-devtools/go/go-dep_0.3.0.bb
index abfeb48370..20ea792c52 100644
--- a/meta/recipes-devtools/go/go-dep_0.3.0.bb
+++ b/meta/recipes-devtools/go/go-dep_0.3.0.bb
@@ -11,6 +11,10 @@ SRCREV = "7a91b794bbfbf1f3b8b79823799316451127801b"
 
 inherit go
 
+TUNE_CCARGS_remove = "-march=mips32r2"
+SECURITY_CFLAGS = "${SECURITY_NOPIE_CFLAGS}"
+SECURITY_LDFLAGS = ""
+
 GO_INSTALL = "${GO_IMPORT}/cmd/dep"
 
 RDEPENDS_${PN}-dev += "bash"
-- 
2.14.1

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