[OE-core] [PATCH] libacpi: update libacpi_fix_for_x32.patch to use libdir

2018-02-02 Thread Ricardo Salveti 
Prefix plus base_libdir generates an invalid path when building with
usrmerge, so change libacpi_fix_for_x32.patch to use libdir instead as
it provides the right path in both cases.

Signed-off-by: Ricardo Salveti 
---
 .../libacpi/files/libacpi_fix_for_x32.patch| 30 --
 meta/recipes-bsp/libacpi/libacpi_0.2.bb|  2 +-
 2 files changed, 11 insertions(+), 21 deletions(-)

diff --git a/meta/recipes-bsp/libacpi/files/libacpi_fix_for_x32.patch 
b/meta/recipes-bsp/libacpi/files/libacpi_fix_for_x32.patch
index 86a16c2..06f20e5 100644
--- a/meta/recipes-bsp/libacpi/files/libacpi_fix_for_x32.patch
+++ b/meta/recipes-bsp/libacpi/files/libacpi_fix_for_x32.patch
@@ -3,9 +3,10 @@ Upstream-Status: Pending
 Fix libacpi for x32
 
 libacpi doesn't use base_libdir for install.  This patch adds
-base_libdir support so that x32 libraries are installed properly.
+libdir support so that x32 libraries are installed properly.
 
 Patch Received from:  H.J. Lu 
+Updated by: Ricardo Salveti  2018/02/03
 
 Signed-off-by: Nitin A Kamble  2011/12/05
 
@@ -13,18 +14,7 @@ Index: libacpi-0.2/Makefile
 ===
 --- libacpi-0.2.orig/Makefile
 +++ libacpi-0.2/Makefile
-@@ -8,6 +8,10 @@ SRC_test = test-libacpi.c libacpi.c list
- OBJ = ${SRC:.c=.o}
- OBJ_test = ${SRC_test:.c=.o}
- 
-+ifndef base_libdir
-+base_libdir=/lib
-+endif
-+
- all: options libacpi.a libacpi.so test-libacpi
- 
- options:
-@@ -42,13 +46,13 @@ install: all
+@@ -42,13 +42,13 @@ install: all
@mkdir -p ${DESTDIR}${PREFIX}/include
@cp -f libacpi.h ${DESTDIR}${PREFIX}/include
@chmod 644 ${DESTDIR}${PREFIX}/include/libacpi.h
@@ -35,13 +25,13 @@ Index: libacpi-0.2/Makefile
 -  @cp -f ${SONAME} ${DESTDIR}${PREFIX}/lib/
 -  @chmod 644 ${DESTDIR}${PREFIX}/lib/${SONAME}
 -  @ln -s ${SONAME} ${DESTDIR}${PREFIX}/lib/libacpi.so
-+  @echo installing library to ${DESTDIR}${PREFIX}${base_libdir}
-+  @mkdir -p ${DESTDIR}${PREFIX}${base_libdir}
-+  @cp -f libacpi.a ${DESTDIR}${PREFIX}${base_libdir}
-+  @chmod 644 ${DESTDIR}${PREFIX}${base_libdir}/libacpi.a
-+  @cp -f ${SONAME} ${DESTDIR}${PREFIX}${base_libdir}/
-+  @chmod 644 ${DESTDIR}${PREFIX}${base_libdir}/${SONAME}
-+  @ln -s ${SONAME} ${DESTDIR}${PREFIX}${base_libdir}/libacpi.so
++  @echo installing library to ${DESTDIR}${LIBDIR}
++  @mkdir -p ${DESTDIR}${LIBDIR}
++  @cp -f libacpi.a ${DESTDIR}${LIBDIR}
++  @chmod 644 ${DESTDIR}${LIBDIR}/libacpi.a
++  @cp -f ${SONAME} ${DESTDIR}${LIBDIR}/
++  @chmod 644 ${DESTDIR}${LIBDIR}/${SONAME}
++  @ln -s ${SONAME} ${DESTDIR}${LIBDIR}/libacpi.so
@echo installing test-libacpi to ${DESTDIR}${PREFIX}/bin
@mkdir -p ${DESTDIR}${PREFIX}/bin
@cp -f test-libacpi ${DESTDIR}${PREFIX}/bin
diff --git a/meta/recipes-bsp/libacpi/libacpi_0.2.bb 
b/meta/recipes-bsp/libacpi/libacpi_0.2.bb
index 6dc66ea..5e7f7fa 100644
--- a/meta/recipes-bsp/libacpi/libacpi_0.2.bb
+++ b/meta/recipes-bsp/libacpi/libacpi_0.2.bb
@@ -28,5 +28,5 @@ EXTRA_OEMAKE = '-e MAKEFLAGS= STRIP="echo"'
 TARGET_CC_ARCH += "${LDFLAGS}"
 
 do_install() {
-   oe_runmake install DESTDIR=${D} PREFIX=${exec_prefix}
+   oe_runmake install DESTDIR=${D} PREFIX=${exec_prefix} LIBDIR=${libdir}
 }
-- 
2.7.4

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

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

2018-02-02 Thread Alejandro Enedino Hernandez Samaniego 
Cool, thanks!

Alejandro

From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Friday, February 2, 2018 1:35 PM
To: Alejandro Enedino Hernandez Samaniego 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to 
major release 1.8.2 (rev2)

So I'm 99% sure this is Exchange tramping the mail and git not handling that, 
as the patch is quoted-printable encoded.I'll pick from the branch :)

Ross

On 2 February 2018 at 21:28, Alejandro Enedino Hernandez Samaniego 
>
 wrote:

I might be wrong but you can check it here as well:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=aehs29/ninja


On 02/02/2018 01:22 PM, Alejandro Enedino Hernandez Samaniego wrote:

This is what I got:



$ git remote show origin
* remote origin
  Fetch URL: git://git.yoctoproject.org/poky
  Push  URL: git://git.yoctoproject.org/poky
  HEAD branch: master

latest commit:

bca260ef4dca87c11fc9d30b2b8a17664dc2d879 ninja: Upgrade from 1.7.2 to major 
release 1.8.2
385944254d0ef88bd6450a221a54cbcb40020b42 tcmode-default.inc: drop preferred 
version of gzip-native



On 02/02/2018 12:58 PM, Burton, Ross wrote:
On 2 February 2018 at 19:06, Alejandro Enedino Hernandez Samaniego 
> wrote:
This makes no sense to me, I rebased to master just before sending it.

Are you sure that the master you're rebasing is the actual upstream master?

Applying: ninja: Upgrade from 1.7.2 to major release 1.8.2
Using index info to reconstruct a base tree...
error: patch failed: 
meta/recipes-devtools/ninja/ninja_1.7.2.bb:1
error: meta/recipes-devtools/ninja/ninja_1.7.2.bb: patch 
does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Patch failed at 0001 ninja: Upgrade from 1.7.2 to major release 1.8.2





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

[OE-core] [PATCH] gcc: enable build-id in gcc-cross-initial

2018-02-02 Thread Taras Kondratiuk 
Normal gcc-cross has build-id feature enabled by default, so most of
target binaries has build-id. But libc (glibc, musl) doesn't have
build-id, because it is built with gcc-cross-initial.

Build-id is a useful feature, so enable it for gcc-cross-initial too.

Signed-off-by: Taras Kondratiuk 
---
 meta/recipes-devtools/gcc/gcc-7.3.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc 
b/meta/recipes-devtools/gcc/gcc-7.3.inc
index 724f9c32a06e..3a840a919cb0 100644
--- a/meta/recipes-devtools/gcc/gcc-7.3.inc
+++ b/meta/recipes-devtools/gcc/gcc-7.3.inc
@@ -116,6 +116,7 @@ EXTRA_OECONF_INITIAL = "\
 --with-system-zlib \
 --disable-lto \
 --disable-plugin \
+--enable-linker-build-id \
 --enable-decimal-float=no \
 --without-isl \
 gcc_cv_libc_provides_ssp=yes \
-- 
2.7.4

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

Re: [OE-core] [PATCH v2] ninja: Upgrade from 1.7.2 to major release 1.8.2

2018-02-02 Thread Alejandro Enedino Hernandez Samaniego 
Hey Cal,

On 02/01/2018 02:10 PM, Alejandro Enedino Hernandez Samaniego wrote:
> Signed-off-by: Alejandro Enedino Hernandez Samaniego 
> 
> ---
>   meta/recipes-devtools/ninja/ninja_1.7.2.bb | 30 
> --
>   meta/recipes-devtools/ninja/ninja_1.8.2.bb | 30 
> ++
>   2 files changed, 30 insertions(+), 30 deletions(-)
>   delete mode 100644 meta/recipes-devtools/ninja/ninja_1.7.2.bb
>   create mode 100644 meta/recipes-devtools/ninja/ninja_1.8.2.bb
Adding the following to your .gitconfig will give you more readable patches for 
package upgrades:
[diff]
     renames = copies

It simplifies the delete -> creation to a rename, then shows what changed in 
the renamed file (SRC_URI and SRCREV).

Thanks,
Cal

Good to hear from you!, I thought git mv automatically did that, I was actually 
surprised it didnt but I didn’t spend too much time on that either.
Thanks!

Alejandro

>
> diff --git a/meta/recipes-devtools/ninja/ninja_1.7.2.bb 
> b/meta/recipes-devtools/ninja/ninja_1.7.2.bb
> deleted file mode 100644
> index 4d3b272..000
> --- a/meta/recipes-devtools/ninja/ninja_1.7.2.bb
> +++ /dev/null
> @@ -1,30 +0,0 @@
> -SUMMARY = "Ninja is a small build system with a focus on speed."
> -HOMEPAGE = "http://martine.github.com/ninja/;
> -LICENSE = "Apache-2.0"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e"
> -
> -DEPENDS = "re2c-native ninja-native"
> -
> -SRCREV = "717b7b4a31db6027207588c0fb89c3ead384747b"
> -
> -SRC_URI = "git://github.com/martine/ninja.git;branch=release"
> -UPSTREAM_CHECK_GITTAGREGEX = "v(?P.*)"
> -
> -S = "${WORKDIR}/git"
> -
> -do_configure[noexec] = "1"
> -
> -do_compile_class-native() {
> -   ./configure.py --bootstrap
> -}
> -
> -do_compile() {
> -   ./configure.py
> -   ninja
> -}
> -
> -do_install() {
> -   install -D -m 0755  ${S}/ninja ${D}${bindir}/ninja
> -}
> -
> -BBCLASSEXTEND = "native nativesdk"
> diff --git a/meta/recipes-devtools/ninja/ninja_1.8.2.bb 
> b/meta/recipes-devtools/ninja/ninja_1.8.2.bb
> new file mode 100644
> index 000..c6fcfef
> --- /dev/null
> +++ b/meta/recipes-devtools/ninja/ninja_1.8.2.bb
> @@ -0,0 +1,30 @@
> +SUMMARY = "Ninja is a small build system with a focus on speed."
> +HOMEPAGE = "http://martine.github.com/ninja/;
> +LICENSE = "Apache-2.0"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e"
> +
> +DEPENDS = "re2c-native ninja-native"
> +
> +SRCREV = "253e94c1fa511704baeb61cf69995bbf09ba435e"
> +
> +SRC_URI = "git://github.com/ninja-build/ninja.git;branch=release"
> +UPSTREAM_CHECK_GITTAGREGEX = "v(?P.*)"
> +
> +S = "${WORKDIR}/git"
> +
> +do_configure[noexec] = "1"
> +
> +do_compile_class-native() {
> +   ./configure.py --bootstrap
> +}
> +
> +do_compile() {
> +   ./configure.py
> +   ninja
> +}
> +
> +do_install() {
> +   install -D -m 0755  ${S}/ninja ${D}${bindir}/ninja }
> +
> +BBCLASSEXTEND = "native nativesdk"
> --
> 2.7.4
>
> This email and any attachments are intended for the sole use of the named 
> recipient(s) and contain(s) confidential information that may be proprietary, 
> privileged or copyrighted under applicable law. If you are not the intended 
> recipient, do not read, copy, or forward this email message or any 
> attachments. Delete this email message and any attachments immediately.

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

[OE-core] [PATCH] apt-native: Add libapt-pkg headers

2018-02-02 Thread Jan Siegmund 
From: Jan Siegmund 

Native tools were not able to use the headers of apt-pkg. This patch
adds the feature.
The headers were added from apt-pkg and apt-inst to the native recipe.
The shipped headers match the ones in the Ubuntu package libapt-pkg-dev.

Signed-off-by: Jan Siegmund 
---
 meta/recipes-devtools/apt/apt-native.inc | 8 
 1 file changed, 8 insertions(+)

diff --git a/meta/recipes-devtools/apt/apt-native.inc 
b/meta/recipes-devtools/apt/apt-native.inc
index 68f1b3ce2c..8859fef797 100644
--- a/meta/recipes-devtools/apt/apt-native.inc
+++ b/meta/recipes-devtools/apt/apt-native.inc
@@ -35,6 +35,8 @@ python do_install_config () {
 outfile.close()
 }
 
+FILES_${PN} = "${includedir}"
+
 do_install_base () {
install -d ${D}${bindir}
install -m 0755 bin/apt-cdrom ${D}${bindir}/
@@ -67,4 +69,10 @@ do_install_base () {
install -d ${D}${localstatedir}/cache/apt/archives/partial
 
install -d ${D}${localstatedir}/log/apt/
+
+   install -d ${D}${includedir}/apt-pkg
+   for h in `find ${S}/apt-pkg ${S}/apt-inst -name '*.h'`
+   do
+   install -m 0644 $h ${D}${includedir}/apt-pkg
+   done
 }
-- 
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] ninja: Upgrade from 1.7.2 to major release 1.8.2

2018-02-02 Thread Cal Sullivan 



On 02/01/2018 02:10 PM, Alejandro Enedino Hernandez Samaniego wrote:

Signed-off-by: Alejandro Enedino Hernandez Samaniego 
---
  meta/recipes-devtools/ninja/ninja_1.7.2.bb | 30 --
  meta/recipes-devtools/ninja/ninja_1.8.2.bb | 30 ++
  2 files changed, 30 insertions(+), 30 deletions(-)
  delete mode 100644 meta/recipes-devtools/ninja/ninja_1.7.2.bb
  create mode 100644 meta/recipes-devtools/ninja/ninja_1.8.2.bb
Adding the following to your .gitconfig will give you more readable 
patches for package upgrades:

[diff]
    renames = copies

It simplifies the delete -> creation to a rename, then shows what 
changed in the renamed file (SRC_URI and SRCREV).


Thanks,
Cal



diff --git a/meta/recipes-devtools/ninja/ninja_1.7.2.bb 
b/meta/recipes-devtools/ninja/ninja_1.7.2.bb
deleted file mode 100644
index 4d3b272..000
--- a/meta/recipes-devtools/ninja/ninja_1.7.2.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "Ninja is a small build system with a focus on speed."
-HOMEPAGE = "http://martine.github.com/ninja/;
-LICENSE = "Apache-2.0"
-LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e"
-
-DEPENDS = "re2c-native ninja-native"
-
-SRCREV = "717b7b4a31db6027207588c0fb89c3ead384747b"
-
-SRC_URI = "git://github.com/martine/ninja.git;branch=release"
-UPSTREAM_CHECK_GITTAGREGEX = "v(?P.*)"
-
-S = "${WORKDIR}/git"
-
-do_configure[noexec] = "1"
-
-do_compile_class-native() {
-   ./configure.py --bootstrap
-}
-
-do_compile() {
-   ./configure.py
-   ninja
-}
-
-do_install() {
-   install -D -m 0755  ${S}/ninja ${D}${bindir}/ninja
-}
-
-BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/ninja/ninja_1.8.2.bb 
b/meta/recipes-devtools/ninja/ninja_1.8.2.bb
new file mode 100644
index 000..c6fcfef
--- /dev/null
+++ b/meta/recipes-devtools/ninja/ninja_1.8.2.bb
@@ -0,0 +1,30 @@
+SUMMARY = "Ninja is a small build system with a focus on speed."
+HOMEPAGE = "http://martine.github.com/ninja/;
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e"
+
+DEPENDS = "re2c-native ninja-native"
+
+SRCREV = "253e94c1fa511704baeb61cf69995bbf09ba435e"
+
+SRC_URI = "git://github.com/ninja-build/ninja.git;branch=release"
+UPSTREAM_CHECK_GITTAGREGEX = "v(?P.*)"
+
+S = "${WORKDIR}/git"
+
+do_configure[noexec] = "1"
+
+do_compile_class-native() {
+   ./configure.py --bootstrap
+}
+
+do_compile() {
+   ./configure.py
+   ninja
+}
+
+do_install() {
+   install -D -m 0755  ${S}/ninja ${D}${bindir}/ninja
+}
+
+BBCLASSEXTEND = "native nativesdk"
--
2.7.4

This email and any attachments are intended for the sole use of the named 
recipient(s) and contain(s) confidential information that may be proprietary, 
privileged or copyrighted under applicable law. If you are not the intended 
recipient, do not read, copy, or forward this email message or any attachments. 
Delete this email message and any attachments immediately.


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

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

2018-02-02 Thread Alejandro Enedino Hernandez Samaniego 

I might be wrong but you can check it here as well:

https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=aehs29/ninja


On 02/02/2018 01:22 PM, Alejandro Enedino Hernandez Samaniego wrote:


This is what I got:


$ git remote show origin
* remote origin
  Fetch URL: git://git.yoctoproject.org/poky
  Push  URL: git://git.yoctoproject.org/poky
  HEAD branch: master

latest commit:

bca260ef4dca87c11fc9d30b2b8a17664dc2d879 ninja: Upgrade from 1.7.2 to 
major release 1.8.2
385944254d0ef88bd6450a221a54cbcb40020b42 tcmode-default.inc: drop 
preferred version of gzip-native




On 02/02/2018 12:58 PM, Burton, Ross wrote:
On 2 February 2018 at 19:06, Alejandro Enedino Hernandez Samaniego 
> wrote:


This makes no sense to me, I rebased to master just before
sending it.


Are you sure that the master you're rebasing is the actual upstream 
master?


Applying: ninja: Upgrade from 1.7.2 to major release 1.8.2
Using index info to reconstruct a base tree...
error: patch failed: meta/recipes-devtools/ninja/ninja_1.7.2.bb:1 

error: meta/recipes-devtools/ninja/ninja_1.7.2.bb 
: patch does not apply

error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Patch failed at 0001 ninja: Upgrade from 1.7.2 to major release 1.8.2





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

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

2018-02-02 Thread Alejandro Enedino Hernandez Samaniego 

This is what I got:


$ git remote show origin
* remote origin
  Fetch URL: git://git.yoctoproject.org/poky
  Push  URL: git://git.yoctoproject.org/poky
  HEAD branch: master

latest commit:

bca260ef4dca87c11fc9d30b2b8a17664dc2d879 ninja: Upgrade from 1.7.2 to 
major release 1.8.2
385944254d0ef88bd6450a221a54cbcb40020b42 tcmode-default.inc: drop 
preferred version of gzip-native




On 02/02/2018 12:58 PM, Burton, Ross wrote:
On 2 February 2018 at 19:06, Alejandro Enedino Hernandez Samaniego 
> wrote:


This makes no sense to me, I rebased to master just before sending it.


Are you sure that the master you're rebasing is the actual upstream 
master?


Applying: ninja: Upgrade from 1.7.2 to major release 1.8.2
Using index info to reconstruct a base tree...
error: patch failed: meta/recipes-devtools/ninja/ninja_1.7.2.bb:1 

error: meta/recipes-devtools/ninja/ninja_1.7.2.bb 
: patch does not apply

error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Patch failed at 0001 ninja: Upgrade from 1.7.2 to major release 1.8.2



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

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

2018-02-02 Thread Burton, Ross 
So I'm 99% sure this is Exchange tramping the mail and git not handling
that, as the patch is quoted-printable encoded.I'll pick from the
branch :)

Ross

On 2 February 2018 at 21:28, Alejandro Enedino Hernandez Samaniego <
alejandro.enedino.hernandez-samani...@xilinx.com> wrote:

> I might be wrong but you can check it here as well:
> https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/
> log/?h=aehs29/ninja
>
>
>
> On 02/02/2018 01:22 PM, Alejandro Enedino Hernandez Samaniego wrote:
>
> This is what I got:
>
>
> $ git remote show origin
> * remote origin
>   Fetch URL: git://git.yoctoproject.org/poky
>   Push  URL: git://git.yoctoproject.org/poky
>   HEAD branch: master
>
> latest commit:
>
> bca260ef4dca87c11fc9d30b2b8a17664dc2d879 ninja: Upgrade from 1.7.2 to
> major release 1.8.2
> 385944254d0ef88bd6450a221a54cbcb40020b42 tcmode-default.inc: drop
> preferred version of gzip-native
>
>
>
> On 02/02/2018 12:58 PM, Burton, Ross wrote:
>
> On 2 February 2018 at 19:06, Alejandro Enedino Hernandez Samaniego <
> aleja...@xilinx.com> wrote:
>
>> This makes no sense to me, I rebased to master just before sending it.
>>
>
> Are you sure that the master you're rebasing is the actual upstream master?
>
> Applying: ninja: Upgrade from 1.7.2 to major release 1.8.2
> Using index info to reconstruct a base tree...
> error: patch failed: meta/recipes-devtools/ninja/ninja_1.7.2.bb:1
> error: meta/recipes-devtools/ninja/ninja_1.7.2.bb: patch does not apply
> error: Did you hand edit your patch?
> It does not apply to blobs recorded in its index.
> Patch failed at 0001 ninja: Upgrade from 1.7.2 to major release 1.8.2
>
>
>
>
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

2018-02-02 Thread Burton, Ross 
On 2 February 2018 at 19:06, Alejandro Enedino Hernandez Samaniego <
aleja...@xilinx.com> wrote:

> This makes no sense to me, I rebased to master just before sending it.
>

Are you sure that the master you're rebasing is the actual upstream master?

Applying: ninja: Upgrade from 1.7.2 to major release 1.8.2
Using index info to reconstruct a base tree...
error: patch failed: meta/recipes-devtools/ninja/ninja_1.7.2.bb:1
error: meta/recipes-devtools/ninja/ninja_1.7.2.bb: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
Patch failed at 0001 ninja: Upgrade from 1.7.2 to major release 1.8.2
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] packagegroup-core-tools-profile: disable valgrind on armeb

2018-02-02 Thread Mariia Movchan 
Valgrind supports only little endian ARM.

Signed-off-by: Mariia Movchan 
---
 meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb 
b/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb
index 51335e232d..a8e47da40c 100644
--- a/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb
+++ b/meta/recipes-core/packagegroups/packagegroup-core-tools-profile.bb
@@ -58,6 +58,7 @@ VALGRIND_nios2 = ""
 VALGRIND_armv4 = ""
 VALGRIND_armv5 = ""
 VALGRIND_armv6 = ""
+VALGRIND_armeb = ""
 VALGRIND_aarch64 = ""
 VALGRIND_linux-gnux32 = ""
 
-- 
2.15.1
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)

2018-02-02 Thread Alejandro Enedino Hernandez Samaniego 
This makes no sense to me, I rebased to master just before sending it.

-Original Message-
From: Patchwork [mailto:patchw...@patchwork.openembedded.org] 
Sent: Thursday, February 1, 2018 2:33 PM
To: Alejandro Enedino Hernandez Samaniego 
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for ninja: Upgrade from 1.7.2 to major release 
1.8.2 (rev2)

== Series Details ==

Series: ninja: Upgrade from 1.7.2 to major release 1.8.2 (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/10780/
State : failure

== Summary ==


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



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



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] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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 2/2] libfm: add a patch to fix build errors with recent versions of gtk-doc

2018-02-02 Thread Alexander Kanavin 
Signed-off-by: Alexander Kanavin 
---
 ...Enclose-text-in-programlisting-into-CDATA.patch | 76 ++
 meta/recipes-support/libfm/libfm_1.2.5.bb  |  4 +-
 2 files changed, 79 insertions(+), 1 deletion(-)
 create mode 100644 
meta/recipes-support/libfm/libfm/0001-Enclose-text-in-programlisting-into-CDATA.patch

diff --git 
a/meta/recipes-support/libfm/libfm/0001-Enclose-text-in-programlisting-into-CDATA.patch
 
b/meta/recipes-support/libfm/libfm/0001-Enclose-text-in-programlisting-into-CDATA.patch
new file mode 100644
index 000..40e53291e1c
--- /dev/null
+++ 
b/meta/recipes-support/libfm/libfm/0001-Enclose-text-in-programlisting-into-CDATA.patch
@@ -0,0 +1,76 @@
+From ed4ca8c0b17ff5d3c768b92409c1787e3f3f1841 Mon Sep 17 00:00:00 2001
+From: Andriy Grytsenko 
+Date: Sun, 26 Nov 2017 22:30:15 +0200
+Subject: [PATCH 2/2] Enclose text in  into 
+  * 
+  * The FM_MODULE_dummy_VERSION is a number which should be increased each
+  * time something in FmDummyInit structure is changed. The FmDummyInit
+@@ -65,7 +65,7 @@
+  * module handling in your code:
+  * 
+  * Sample of fm-dummy-widget.c
+- * 
++ * 
+  * 
+  *
+  * Third thing application should do is to register module type on the
+@@ -108,7 +108,7 @@
+  * interface (see the fm-dummy.h header example above):
+  * 
+  * Sample of module dummy/test
+- * 
++ * 
+  * 
+  * The fm_module_init_dummy should be exactly the same structure that is
+  * defined in the header file above.
+-- 
+2.15.1
+
diff --git a/meta/recipes-support/libfm/libfm_1.2.5.bb 
b/meta/recipes-support/libfm/libfm_1.2.5.bb
index 6844243c1e3..c1deea68531 100644
--- a/meta/recipes-support/libfm/libfm_1.2.5.bb
+++ b/meta/recipes-support/libfm/libfm_1.2.5.bb
@@ -12,7 +12,9 @@ SECTION = "x11/libs"
 DEPENDS = "glib-2.0 pango gtk+3 menu-cache intltool-native libexif libfm-extra 
gettext-native"
 
 SRC_URI = "${SOURCEFORGE_MIRROR}/pcmanfm/libfm-${PV}.tar.xz \
-   
file://0001-Correctly-check-the-stamp-file-that-indicates-if-we-.patch"
+   
file://0001-Correctly-check-the-stamp-file-that-indicates-if-we-.patch \
+   file://0001-Enclose-text-in-programlisting-into-CDATA.patch \
+   "
 
 SRC_URI[md5sum] = "a1ba9ae5e920f38b647dd511edd6c807"
 SRC_URI[sha256sum] = 
"c706bb1020cf5f2d6f5a9226f692ce1985947134dcf2bde64278bd0420779b5a"
-- 
2.15.1

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

[OE-core] [PATCH 1/2] gtk-doc: update to 1.27

2018-02-02 Thread Alexander Kanavin 
Gtk-doc has been rewritten in Python, so drop perl dependencies (good 
riddance!),
and adjust patches to reflect that.

Signed-off-by: Alexander Kanavin 
---
 ...r-out-if-perl-is-not-found-or-its-version.patch |  40 --
 ...hardocode-paths-to-perl-python-in-scripts.patch | 155 +++--
 .../gtk-doc/files/conditionaltests.patch   |  26 +++-
 .../gtk-doc/files/pkg-config-native.patch  |  22 ++-
 .../gtk-doc/{gtk-doc_1.25.bb => gtk-doc_1.27.bb}   |  15 +-
 5 files changed, 119 insertions(+), 139 deletions(-)
 delete mode 100644 
meta/recipes-gnome/gtk-doc/files/0001-Do-not-error-out-if-perl-is-not-found-or-its-version.patch
 rename meta/recipes-gnome/gtk-doc/{gtk-doc_1.25.bb => gtk-doc_1.27.bb} (81%)

diff --git 
a/meta/recipes-gnome/gtk-doc/files/0001-Do-not-error-out-if-perl-is-not-found-or-its-version.patch
 
b/meta/recipes-gnome/gtk-doc/files/0001-Do-not-error-out-if-perl-is-not-found-or-its-version.patch
deleted file mode 100644
index 4a9028742ca..000
--- 
a/meta/recipes-gnome/gtk-doc/files/0001-Do-not-error-out-if-perl-is-not-found-or-its-version.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From e733241fb580f032efbbe684ec35d4c9d27f1595 Mon Sep 17 00:00:00 2001
-From: Alexander Kanavin 
-Date: Thu, 8 Sep 2016 13:38:39 +0300
-Subject: [PATCH] Do not error out if perl is not found or its version is too
- old.
-
-This allows use to avoid depending on perl-native if we're not going
-to use it (when api-docs are disabled).
-
-Upstream-Status: Inappropriate [oe-core specific]
-Signed-off-by: Alexander Kanavin 

- configure.ac | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/configure.ac b/configure.ac
-index 2a61d6e..29415bd 100644
 a/configure.ac
-+++ b/configure.ac
-@@ -36,7 +36,7 @@ dnl Check for Perl.
- dnl
- AC_PATH_PROG([PERL], [perl])
- if test -z "$PERL"; then
--  AC_MSG_ERROR([perl not found])
-+  AC_MSG_WARN([perl not found])
- fi
- 
- AC_MSG_CHECKING([if Perl version >= 5.18.0])
-@@ -44,7 +44,7 @@ if "$PERL" -e "require v5.18.0"; then
-   AC_MSG_RESULT([yes])
- else
-   AC_MSG_RESULT([no])
--  AC_MSG_ERROR([perl >= 5.18.0 is required for gtk-doc])
-+  AC_MSG_WARN([perl >= 5.18.0 is required for gtk-doc])
- fi
- 
- dnl
--- 
-2.9.3
-
diff --git 
a/meta/recipes-gnome/gtk-doc/files/0001-Do-not-hardocode-paths-to-perl-python-in-scripts.patch
 
b/meta/recipes-gnome/gtk-doc/files/0001-Do-not-hardocode-paths-to-perl-python-in-scripts.patch
index 477fc9ae8c1..2fe3ab9221f 100644
--- 
a/meta/recipes-gnome/gtk-doc/files/0001-Do-not-hardocode-paths-to-perl-python-in-scripts.patch
+++ 
b/meta/recipes-gnome/gtk-doc/files/0001-Do-not-hardocode-paths-to-perl-python-in-scripts.patch
@@ -1,7 +1,7 @@
-From 6fab82b93c7bd301eb42448515b02f7cb3306897 Mon Sep 17 00:00:00 2001
+From 928102874bc2339a1d57c6b178877e0c6002cb3a Mon Sep 17 00:00:00 2001
 From: Alexander Kanavin 
 Date: Wed, 31 Aug 2016 16:44:46 +0300
-Subject: [PATCH] Do not hardocode paths to perl/python in scripts.
+Subject: [PATCH 1/3] Do not hardocode paths to perl/python in scripts.
 
 Doing so when the interpreters are somewhere deep in a sysroot directory
 can reach the shebang line limit, and resulting scripts wouldn't work
@@ -9,131 +9,134 @@ on targets either.
 
 Upstream-Status: Inappropriate [oe-core specific]
 Signed-off-by: Alexander Kanavin 
+
 ---
- gtkdoc-check.in | 2 +-
- gtkdoc-common.pl.in | 2 +-
- gtkdoc-depscan.in   | 2 +-
- gtkdoc-fixxref.in   | 2 +-
- gtkdoc-mkdb.in  | 2 +-
- gtkdoc-mktmpl.in| 2 +-
- gtkdoc-rebase.in| 2 +-
- gtkdoc-scan.in  | 2 +-
- gtkdoc-scangobj.in  | 2 +-
- tests/tools.sh.in   | 4 ++--
- 10 files changed, 11 insertions(+), 11 deletions(-)
+ gtkdoc-check.in| 2 +-
+ gtkdoc-depscan.in  | 2 +-
+ gtkdoc-fixxref.in  | 2 +-
+ gtkdoc-mkdb.in | 2 +-
+ gtkdoc-mkhtml.in   | 2 +-
+ gtkdoc-mkman.in| 2 +-
+ gtkdoc-mkpdf.in| 2 +-
+ gtkdoc-rebase.in   | 2 +-
+ gtkdoc-scan.in | 2 +-
+ gtkdoc-scangobj.in | 2 +-
+ tests/tools.sh.in  | 2 +-
+ 11 files changed, 11 insertions(+), 11 deletions(-)
 
 diff --git a/gtkdoc-check.in b/gtkdoc-check.in
-index 560d69b..b60857f 100755
+index 8c8e917..f6a25f6 100755
 --- a/gtkdoc-check.in
 +++ b/gtkdoc-check.in
 @@ -1,4 +1,4 @@
--#!@PERL@ -w
-+#!/usr/bin/env perl
- # -*- cperl -*-
- #
- # gtk-doc - GTK DocBook documentation generator.
-diff --git a/gtkdoc-common.pl.in b/gtkdoc-common.pl.in
-index 4747396..cfadb78 100644
 a/gtkdoc-common.pl.in
-+++ b/gtkdoc-common.pl.in
-@@ -1,4 +1,4 @@
--#!@PERL@ -w
-+#!/usr/bin/env perl
- # -*- cperl -*-
+-#!@PYTHON@
++#!/usr/bin/env python3
+ # -*- python; coding: utf-8 -*-
  #
  # gtk-doc - GTK DocBook documentation generator.
 diff --git a/gtkdoc-depscan.in b/gtkdoc-depscan.in
-index 83af01b..917e247 100644
+index 9bfaf30..aadc952 100644
 --- a/gtkdoc-depscan.in
 +++ b/gtkdoc-depscan.in
 @@ -1,4 +1,4 @@

Re: [OE-core] [PATCH 3/4] runqemu: check for qemuboot.conf and raise error

2018-02-02 Thread Randy MacLeod 

On 2018-02-01 10:23 PM, Robert Yang wrote:

[YOCTO #12503]

Signed-off-by: Robert Yang 
---
  scripts/runqemu | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/scripts/runqemu b/scripts/runqemu
index 0ca62f4..d50c6d1 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -417,6 +417,9 @@ class BaseConfig(object):
  
  unknown_arg = ""

  for arg in sys.argv[1:]:
+if arg.endswith('.qemuboot.conf'):
+raise RunQemuError("qemuboot.conf is not supported any more, use 
qemuboot.json to instead of it")
+

better wording:
 qemuboot.conf format is no longer supported, use a qemuboot.json file 
instead.




../Randy


  if arg in self.fstypes + self.vmtypes:
  self.check_arg_fstype(arg)
  elif arg == 'nographic':




--
# Randy MacLeod.  WR Linux
# Wind River an Intel Company
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] ✗ patchtest: failure for e2fsprogs: fixes for ptest

2018-02-02 Thread Burton, Ross 
Yes, this clearly isn't right.

On 2 February 2018 at 07:52, Huang, Jie (Jackie)  wrote:

>
>
> > -Original Message-
> > From: Patchwork [mailto:patchw...@do.openembedded.org]
> > Sent: Friday, February 02, 2018 15:33
> > To: Huang, Jie (Jackie)
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: ✗ patchtest: failure for e2fsprogs: fixes for ptest
> >
> > == Series Details ==
> >
> > Series: e2fsprogs: fixes for ptest
> > Revision: 1
> > URL   : https://patchwork.openembedded.org/series/10824/
> > 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 Patches not removed from tree
> [test_src_uri_left_files]
> >   Suggested fixAmend the patch containing the software patch file
> removal
> >   Patchquiet-debugfs.patch
>
> What I did is moving the "quiet-debugfs.patch" from SRC_URI to
> SRC_URI_append_class-native,
> the patch file is not meant to be removed.
>
> I think the test_src_uri_left_files needs to consider such changes.
>
> Thanks,
> Jackie
>
> >
> >
> >
> > 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] -> ...).
> >
> > ---
> > Guidelines:
> > https://www.openembedded.org/wiki/Commit_Patch_Message_Guideline
> > s
> > 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
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH V2] apr: 1.6.2 -> 1.6.3

2018-02-02 Thread Burton, Ross 
Yes, that.  Thanks very much!

Ross

On 2 February 2018 at 09:06, Hongxu Jia  wrote:

> 1. Improve inappropriate patches:
> - Drop inappropriate configure_fixes.patch
>   Use setting variable ac_cv_file__dev_zero and
>   ac_cv_sizeof_struct_iovec to replace
>
> - Drop cleanup.patch
>   Aassign variable libtool at ./buildconf executing and
>   use 0001-build-buildcheck.sh-improve-libtool-detection.patch
>   to replace. Submitted it to upstream.
>
> - Rename configfix.patch to
>   0002-apr-Remove-workdir-path-references-from-installed-ap.patch
>   Add its original comments and author, explain why it is inappropriate
>
> - Drop upgrade-and-fix-1.5.1.patch
>   Use 0003-Makefile.in-configure.in-support-cross-compiling.patch
>   to replace. And submitted it to upstream.
>
> 2. Fix build path issue to improve reproducibility
>
> Signed-off-by: Hongxu Jia 
> ---
>  ...d-buildcheck.sh-improve-libtool-detection.patch | 32 ++
>  ...orkdir-path-references-from-installed-ap.patch} | 33 +--
>  in-configure.in-support-cross-compiling.patch} | 52 +++--
>  ...> 0004-Fix-packet-discards-HTTP-redirect.patch} | 15 +++--
>  ...-fix-LTFLAGS-to-make-it-work-with-ccache.patch} | 12 ++--
>  ...t-size-doesn-t-match-in-glibc-when-cross.patch} | 16 ++---
>  ...ink-libapr-against-phtread-to-make-gold-.patch} | 12 ++--
>  meta/recipes-support/apr/apr/cleanup.patch | 43 --
>  meta/recipes-support/apr/apr/configure_fixes.patch | 68
> --
>  .../apr/{apr_1.6.2.bb => apr_1.6.3.bb} | 27 +
>  10 files changed, 140 insertions(+), 170 deletions(-)
>  create mode 100644 meta/recipes-support/apr/apr/0001-build-buildcheck.sh-
> improve-libtool-detection.patch
>  rename meta/recipes-support/apr/apr/{configfix.patch =>
> 0002-apr-Remove-workdir-path-references-from-installed-ap.patch} (67%)
>  rename meta/recipes-support/apr/apr/{upgrade-and-fix-1.5.1.patch =>
> 0003-Makefile.in-configure.in-support-cross-compiling.patch} (40%)
>  rename meta/recipes-support/apr/apr/{Fix-packet-discards-HTTP-redirect.patch
> => 0004-Fix-packet-discards-HTTP-redirect.patch} (71%)
>  rename 
> meta/recipes-support/apr/apr/{configure.in-fix-LTFLAGS-to-make-it-work-with-ccache.patch
> => 0005-configure.in-fix-LTFLAGS-to-make-it-work-with-ccache.patch} (78%)
>  rename meta/recipes-support/apr/apr/{0001-apr-fix-off_t-size-doesn-
> t-match-in-glibc-when-cross.patch => 0006-apr-fix-off_t-size-doesn-
> t-match-in-glibc-when-cross.patch} (85%)
>  rename meta/recipes-support/apr/apr/{0002-explicitly-link-libapr-
> against-phtread-to-make-gold-.patch => 0007-explicitly-link-libapr-
> against-phtread-to-make-gold-.patch} (90%)
>  delete mode 100644 meta/recipes-support/apr/apr/cleanup.patch
>  delete mode 100644 meta/recipes-support/apr/apr/configure_fixes.patch
>  rename meta/recipes-support/apr/{apr_1.6.2.bb => apr_1.6.3.bb} (77%)
>
> diff --git a/meta/recipes-support/apr/apr/0001-build-buildcheck.sh-
> improve-libtool-detection.patch b/meta/recipes-support/apr/
> apr/0001-build-buildcheck.sh-improve-libtool-detection.patch
> new file mode 100644
> index 000..097c195
> --- /dev/null
> +++ b/meta/recipes-support/apr/apr/0001-build-buildcheck.sh-
> improve-libtool-detection.patch
> @@ -0,0 +1,32 @@
> +From 4efdc06fb17b8a00a9eca923caa176be741d1e04 Mon Sep 17 00:00:00 2001
> +From: Hongxu Jia 
> +Date: Thu, 1 Feb 2018 14:56:13 +0800
> +Subject: [PATCH 1/7] build/buildcheck.sh: improve libtool detection
> +
> +Support customize libtool by variable assigning, it is helpful
> +for cross compileing (such as libtool=aarch64-linux-libtool)
> +
> +Upstream-Status: Submitted [https://github.com/apache/apr/pull/8]
> +Signed-off-by: Hongxu Jia 
> +---
> + build/buildcheck.sh | 4 +++-
> + 1 file changed, 3 insertions(+), 1 deletion(-)
> +
> +diff --git a/build/buildcheck.sh b/build/buildcheck.sh
> +index ab5df44..f191a41 100755
> +--- a/build/buildcheck.sh
>  b/build/buildcheck.sh
> +@@ -40,7 +40,9 @@ fi
> + # output is multiline from 1.5 onwards
> +
> + # Require libtool 1.4 or newer
> +-libtool=`build/PrintPath glibtool1 glibtool libtool libtool15 libtool14`
> ++if test -z "$libtool"; then
> ++  libtool=`build/PrintPath glibtool1 glibtool libtool libtool15
> libtool14`
> ++fi
> + lt_pversion=`$libtool --version 2>/dev/null|sed -e
> 's/([^)]*)//g;s/^[^0-9]*//;s/[- ].*//g;q'`
> + if test -z "$lt_pversion"; then
> +   echo "buildconf: libtool not found."
> +--
> +1.8.3.1
> +
> diff --git a/meta/recipes-support/apr/apr/configfix.patch
> b/meta/recipes-support/apr/apr/0002-apr-Remove-workdir-
> path-references-from-installed-ap.patch
> similarity index 67%
> rename from meta/recipes-support/apr/apr/configfix.patch
> rename to meta/recipes-support/apr/apr/0002-apr-Remove-workdir-path-
> references-from-installed-ap.patch
> index 605c4f6..72e706f 100644
> ---

[OE-core] [PATCH 2/2] x264: upgrade to latest revision

2018-02-02 Thread Maxin B. John 
Change dependency from yasm to nasm following this change:

commit d2b5f4873e2147452a723b61b14f030b2ee760a5
Author: Henrik Gramner 
Date:   Sat Mar 18 18:50:36 2017 +0100

x86: Change assembler from yasm to nasm

Refreshed the following patch:
don-t-default-to-cortex-a9-with-neon.patch

Signed-off-by: Maxin B. John 
---
 .../don-t-default-to-cortex-a9-with-neon.patch | 29 --
 meta/recipes-multimedia/x264/x264_git.bb   |  6 ++---
 2 files changed, 24 insertions(+), 11 deletions(-)

diff --git 
a/meta/recipes-multimedia/x264/x264/don-t-default-to-cortex-a9-with-neon.patch 
b/meta/recipes-multimedia/x264/x264/don-t-default-to-cortex-a9-with-neon.patch
index 73f2aac..065e3b3 100644
--- 
a/meta/recipes-multimedia/x264/x264/don-t-default-to-cortex-a9-with-neon.patch
+++ 
b/meta/recipes-multimedia/x264/x264/don-t-default-to-cortex-a9-with-neon.patch
@@ -1,20 +1,33 @@
--march flag is not in CFLAGS so this will always default to -mcpu=cortex-a8
--mfpu=neon.
+From a72bf499a0674fc75eedf15008b424e28f67e4bd Mon Sep 17 00:00:00 2001
+From: Andrei Gherzan 
+Date: Fri, 2 Feb 2018 15:10:08 +0200
+Subject: [PATCH] dont default to cortex-a9 with neon
+
+-march flag is not in CFLAGS so this will always default to
+ -mcpu=cortex-a8 -mfpu=neon.
 
 Upstream-Status: Pending
+
 Signed-off-by: Andrei Gherzan 
+Signed-off-by: Maxin B. John 
+---
+ configure | 3 ---
+ 1 file changed, 3 deletions(-)
 
 diff --git a/configure b/configure
-index 9d1586c..3109ec4 100755
+index 0e3ef23..955b993 100755
 --- a/configure
 +++ b/configure
-@@ -874,9 +874,6 @@ if [ $asm = auto -a \( $ARCH = X86 -o $ARCH = X86_64 \) ] 
; then
+@@ -911,9 +911,6 @@ if [ $asm = auto -a \( $ARCH = X86 -o $ARCH = X86_64 \) ] 
; then
  fi
  
  if [ $asm = auto -a $ARCH = ARM ] ; then
 -# set flags so neon is built by default
--echo $CFLAGS | grep -Eq '(-mcpu|-march|-mfpu)' || CFLAGS="$CFLAGS 
-mcpu=cortex-a8 -mfpu=neon"
+-[ $compiler == CL ] || echo $CFLAGS | grep -Eq '(-mcpu|-march|-mfpu)' || 
CFLAGS="$CFLAGS -mcpu=cortex-a8 -mfpu=neon"
 -
- if  cc_check '' '' '__asm__("rev ip, ip");' ; then  define HAVE_ARMV6
- cc_check '' '' '__asm__("movt r0, #0");' && define 
HAVE_ARMV6T2
- cc_check '' '' '__asm__("vadd.i16 q0, q0, q0");' && define HAVE_NEON
+ cc_check '' '' '__asm__("add r0, r1, r2");' && define HAVE_ARM_INLINE_ASM
+ if [ $compiler = CL ] && cpp_check '' '' 'defined(_M_ARM) && _M_ARM >= 7' 
; then
+ define HAVE_ARMV6
+-- 
+2.4.0
+
diff --git a/meta/recipes-multimedia/x264/x264_git.bb 
b/meta/recipes-multimedia/x264/x264_git.bb
index bc9775a..a669295 100644
--- a/meta/recipes-multimedia/x264/x264_git.bb
+++ b/meta/recipes-multimedia/x264/x264_git.bb
@@ -6,7 +6,7 @@ LICENSE = "GPLv2"
 LICENSE_FLAGS = "commercial"
 LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f"
 
-DEPENDS = "yasm-native"
+DEPENDS = "nasm-native"
 
 SRC_URI = "git://github.com/mirror/x264;branch=stable \
file://don-t-default-to-cortex-a9-with-neon.patch \
@@ -14,9 +14,9 @@ SRC_URI = "git://github.com/mirror/x264;branch=stable \
"
 UPSTREAM_CHECK_COMMITS = "1"
 
-SRCREV = "2b741f81e51f92d053d87a49f59ff1026553a0f6"
+SRCREV = "e9a5903edf8ca59ef20e6f4894c196f135af735e"
 
-PV = "r2731+git${SRCPV}"
+PV = "r2854+git${SRCPV}"
 
 S = "${WORKDIR}/git"
 
-- 
2.4.0

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

[OE-core] [PATCH 1/2] libsolv: upgrade to version 0.6.31

2018-02-02 Thread Maxin B. John 
Remove upstreamed patch:
0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch

Signed-off-by: Maxin B. John 
---
 c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch | 35 --
 .../{libsolv_0.6.29.bb => libsolv_0.6.31.bb}   |  3 +-
 2 files changed, 1 insertion(+), 37 deletions(-)
 delete mode 100644 
meta/recipes-extended/libsolv/libsolv/0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch
 rename meta/recipes-extended/libsolv/{libsolv_0.6.29.bb => libsolv_0.6.31.bb} 
(87%)

diff --git 
a/meta/recipes-extended/libsolv/libsolv/0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch
 
b/meta/recipes-extended/libsolv/libsolv/0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch
deleted file mode 100644
index 4a4e5cb..000
--- 
a/meta/recipes-extended/libsolv/libsolv/0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 1c4c935cb73ac1ccb9693df1a51ba218a22e8ca8 Mon Sep 17 00:00:00 2001
-From: Ming Liu 
-Date: Sat, 30 Sep 2017 11:15:16 +0800
-Subject: [PATCH] repo_rpmdb.c: increase MAX_HDR_CNT and MAX_HDR_DSIZE
-
-Upstream-Status: Submitted [https://github.com/openSUSE/libsolv/pull/230]
-
-We encountered 'corrupt rpm' issues when installing extreme big RPM
-packages like the kernel-devsrc package of Yocto project.
-
-It can be fixed by increasing MAX_HDR_CNT and MAX_HDR_DSIZE per test.
-
-Signed-off-by: Ming Liu 

- ext/repo_rpmdb.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/ext/repo_rpmdb.c b/ext/repo_rpmdb.c
-index c7000a9..7000835 100644
 a/ext/repo_rpmdb.c
-+++ b/ext/repo_rpmdb.c
-@@ -170,8 +170,8 @@
- #define MAX_SIG_CNT   0x10
- #define MAX_SIG_DSIZE 0x10
- 
--#define MAX_HDR_CNT   0x10
--#define MAX_HDR_DSIZE 0x200
-+#define MAX_HDR_CNT   0x20
-+#define MAX_HDR_DSIZE 0x400
- 
- typedef struct rpmhead {
-   int cnt;
--- 
-2.7.4
-
diff --git a/meta/recipes-extended/libsolv/libsolv_0.6.29.bb 
b/meta/recipes-extended/libsolv/libsolv_0.6.31.bb
similarity index 87%
rename from meta/recipes-extended/libsolv/libsolv_0.6.29.bb
rename to meta/recipes-extended/libsolv/libsolv_0.6.31.bb
index 78972e5..96c366b 100644
--- a/meta/recipes-extended/libsolv/libsolv_0.6.29.bb
+++ b/meta/recipes-extended/libsolv/libsolv_0.6.31.bb
@@ -8,13 +8,12 @@ LIC_FILES_CHKSUM = 
"file://LICENSE.BSD;md5=62272bd11c97396d4aaf1c41bc11f7d8"
 DEPENDS = "expat zlib rpm"
 
 SRC_URI = "git://github.com/openSUSE/libsolv.git \
-   
file://0001-repo_rpmdb.c-increase-MAX_HDR_CNT-and-MAX_HDR_DSIZE.patch \
   "
 SRC_URI_append_libc-musl = " 
file://0001-Add-fallback-fopencookie-implementation.patch \
  
file://0002-Fixes-to-internal-fopencookie-implementation.patch \
"
 
-SRCREV = "765be095eaeaef1b1d2a84f6a0e00d5abf677ae9"
+SRCREV = "bef46d75f6d2537060114eea0f3a892e958ad5e0"
 UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+(\.\d+)+)"
 
 S = "${WORKDIR}/git"
-- 
2.4.0

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

Re: [OE-core] Adding a "tiny" DISTRO_FEATURE and having packages build smaller

2018-02-02 Thread Otavio Salvador 
On Fri, Feb 2, 2018 at 3:21 AM, Daniel F. Dickinson
 wrote:
> On 01/02/18 09:19 AM, Burton, Ross wrote:
>>
>> On 1 February 2018 at 14:17, Daniel F. Dickinson > > wrote:
>>
>> On 01/02/18 09:12 AM, Burton, Ross wrote:
>>
>> On 1 February 2018 at 14:10, Daniel F. Dickinson
>> 
>> >>
>> wrote:
>>
>>  On 01/02/18 08:54 AM, Burton, Ross wrote:
>>
>>  On 1 February 2018 at 13:44, Daniel F. Dickinson
>>
>>  wrote:
>>
>> A distribution can set other recipe's PACKAGECONFIGs directly:
>>
>> PACKAGECONFIG_pn-recipename = "foo bar"
>>
>> And distributions are welcome to bundle groups of those into inc
>> files for the user to pull in as required at the distro level.
>>
>> I wonder if it'd be useful to have some .inc's of this variety added
>> and included (commented out) in the poky-tiny distro default
>> local.conf?
>>
>>
>> Included and enabled if they make sense, sure.  poky-tiny is, like
>> everything poky-specific, just an example.
>>
>> It already has one:
>>
>> PACKAGECONFIG_remove_pn-opkg-utils = "python"
>>
> Sorry, apparently I wasn't clear.  What I meant was having (either in poky
> or in a more appropriate place) .inc or classes that do PACKAGECONFIG for
> common sets of packages for various "tiny" use cases (e.g. router, nas
> firmware (v.s os on data disks), ap, small iot devices , etc), which may
> involve a lot of partitioning of existing packages to allow for smaller
> (tiny) builds that include only the relevant functionality.  I'm not sure
> what the situation is for oe-core, but when I look at meta-openwrt it is
> much less partitioned than say actual openwrt base system, and makes a
> number of 'bigger' choices than openwrt.  What I'd like to work on is making
> it easier to build pared down OE systems (whether poky-tiny reference design
> 'flavours', meta-openwrt/oe hybrids, or (basically) openwrt build with
> oe/meta-openwrt).
>
> In the case of the .inc's etc I'm thinking of this as 'pre-cooked'
> references designs like poky-tiny itself;  Perhaps a better place for this
> is as comments in poky-tiny's distro .conf? (Or as proof-of-concept distro
> layers based on poky-tiny and and listed in the layers index?)

I'd say it could be a layer with those. Like meta-tiny-common or
similar which other distros could include and use. This does not seem
to belong to poky.

-- 
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 01/20] oe-selftest: add a test for recipes without maintainers

2018-02-02 Thread Alexander Kanavin 

On 02/01/2018 10:41 PM, Paul Eggleton wrote:

I understand the intention, but I don't think oe-selftest is the right place to 
be
doing this. It's going to fail for sure if you have any non-OE-Core layers in
your configuration.

One thing I have continued to campaign for (and I'm aware that not everyone
completely agrees) is that oe-selftest should be able to be run with people's
own configurations, we shouldn't necessarily assume that it's only our default
being tested - that way we maximise oe-selftest's utility and audience. Of
course there's a limit to that, if someone's esoteric configuration breaks it
they get to keep the pieces - but this will definitely break with anyone's
custom configuration, esoteric or otherwise.


I do agree with this. We've had this exact conversation with Ross a few 
weeks back, and he promised to fix the test so that it's limited to 
recipes in oe-core. Take me re-sending the patch as a gentle reminder 
for that. :)



By all means let's have a script that does this - it's even trivial to write one
with tinfoil.


No manual scripts (that no one except me even knows about) please. I 
really do want to automate this, and have it run regularly on the 
autobuilder. Otherwise, one can just issue:


bitbake -c checkpkg world && grep -v @ tmp/log/checkpkg.csv


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

[OE-core] ✗ patchtest: failure for improve reproducibility of 6 recipes (rev2)

2018-02-02 Thread Patchwork 
== Series Details ==

Series: improve reproducibility of 6 recipes (rev2)
Revision: 2
URL   : https://patchwork.openembedded.org/series/10508/
State : failure

== Summary ==


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



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



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] -> ...).

---
Guidelines: 
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
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] apr: 1.6.2 -> 1.6.3

2018-02-02 Thread Hongxu Jia 

Sorry for the wrong thread,

Hi Ross,

I also updated the remote repo for it.

git://git.pokylinux.org/poky-contrib hongxu/upgrade-20180131
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/upgrade-20180131

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

[OE-core] [PATCH V2] apr: 1.6.2 -> 1.6.3

2018-02-02 Thread Hongxu Jia 
1. Improve inappropriate patches:
- Drop inappropriate configure_fixes.patch
  Use setting variable ac_cv_file__dev_zero and
  ac_cv_sizeof_struct_iovec to replace

- Drop cleanup.patch
  Aassign variable libtool at ./buildconf executing and
  use 0001-build-buildcheck.sh-improve-libtool-detection.patch
  to replace. Submitted it to upstream.

- Rename configfix.patch to
  0002-apr-Remove-workdir-path-references-from-installed-ap.patch
  Add its original comments and author, explain why it is inappropriate

- Drop upgrade-and-fix-1.5.1.patch
  Use 0003-Makefile.in-configure.in-support-cross-compiling.patch
  to replace. And submitted it to upstream.

2. Fix build path issue to improve reproducibility

Signed-off-by: Hongxu Jia 
---
 ...d-buildcheck.sh-improve-libtool-detection.patch | 32 ++
 ...orkdir-path-references-from-installed-ap.patch} | 33 +--
 in-configure.in-support-cross-compiling.patch} | 52 +++--
 ...> 0004-Fix-packet-discards-HTTP-redirect.patch} | 15 +++--
 ...-fix-LTFLAGS-to-make-it-work-with-ccache.patch} | 12 ++--
 ...t-size-doesn-t-match-in-glibc-when-cross.patch} | 16 ++---
 ...ink-libapr-against-phtread-to-make-gold-.patch} | 12 ++--
 meta/recipes-support/apr/apr/cleanup.patch | 43 --
 meta/recipes-support/apr/apr/configure_fixes.patch | 68 --
 .../apr/{apr_1.6.2.bb => apr_1.6.3.bb} | 27 +
 10 files changed, 140 insertions(+), 170 deletions(-)
 create mode 100644 
meta/recipes-support/apr/apr/0001-build-buildcheck.sh-improve-libtool-detection.patch
 rename meta/recipes-support/apr/apr/{configfix.patch => 
0002-apr-Remove-workdir-path-references-from-installed-ap.patch} (67%)
 rename meta/recipes-support/apr/apr/{upgrade-and-fix-1.5.1.patch => 
0003-Makefile.in-configure.in-support-cross-compiling.patch} (40%)
 rename meta/recipes-support/apr/apr/{Fix-packet-discards-HTTP-redirect.patch 
=> 0004-Fix-packet-discards-HTTP-redirect.patch} (71%)
 rename 
meta/recipes-support/apr/apr/{configure.in-fix-LTFLAGS-to-make-it-work-with-ccache.patch
 => 0005-configure.in-fix-LTFLAGS-to-make-it-work-with-ccache.patch} (78%)
 rename 
meta/recipes-support/apr/apr/{0001-apr-fix-off_t-size-doesn-t-match-in-glibc-when-cross.patch
 => 0006-apr-fix-off_t-size-doesn-t-match-in-glibc-when-cross.patch} (85%)
 rename 
meta/recipes-support/apr/apr/{0002-explicitly-link-libapr-against-phtread-to-make-gold-.patch
 => 0007-explicitly-link-libapr-against-phtread-to-make-gold-.patch} (90%)
 delete mode 100644 meta/recipes-support/apr/apr/cleanup.patch
 delete mode 100644 meta/recipes-support/apr/apr/configure_fixes.patch
 rename meta/recipes-support/apr/{apr_1.6.2.bb => apr_1.6.3.bb} (77%)

diff --git 
a/meta/recipes-support/apr/apr/0001-build-buildcheck.sh-improve-libtool-detection.patch
 
b/meta/recipes-support/apr/apr/0001-build-buildcheck.sh-improve-libtool-detection.patch
new file mode 100644
index 000..097c195
--- /dev/null
+++ 
b/meta/recipes-support/apr/apr/0001-build-buildcheck.sh-improve-libtool-detection.patch
@@ -0,0 +1,32 @@
+From 4efdc06fb17b8a00a9eca923caa176be741d1e04 Mon Sep 17 00:00:00 2001
+From: Hongxu Jia 
+Date: Thu, 1 Feb 2018 14:56:13 +0800
+Subject: [PATCH 1/7] build/buildcheck.sh: improve libtool detection
+
+Support customize libtool by variable assigning, it is helpful
+for cross compileing (such as libtool=aarch64-linux-libtool)
+
+Upstream-Status: Submitted [https://github.com/apache/apr/pull/8]
+Signed-off-by: Hongxu Jia 
+---
+ build/buildcheck.sh | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/build/buildcheck.sh b/build/buildcheck.sh
+index ab5df44..f191a41 100755
+--- a/build/buildcheck.sh
 b/build/buildcheck.sh
+@@ -40,7 +40,9 @@ fi
+ # output is multiline from 1.5 onwards
+ 
+ # Require libtool 1.4 or newer
+-libtool=`build/PrintPath glibtool1 glibtool libtool libtool15 libtool14`
++if test -z "$libtool"; then
++  libtool=`build/PrintPath glibtool1 glibtool libtool libtool15 libtool14`
++fi
+ lt_pversion=`$libtool --version 2>/dev/null|sed -e 
's/([^)]*)//g;s/^[^0-9]*//;s/[- ].*//g;q'`
+ if test -z "$lt_pversion"; then
+   echo "buildconf: libtool not found."
+-- 
+1.8.3.1
+
diff --git a/meta/recipes-support/apr/apr/configfix.patch 
b/meta/recipes-support/apr/apr/0002-apr-Remove-workdir-path-references-from-installed-ap.patch
similarity index 67%
rename from meta/recipes-support/apr/apr/configfix.patch
rename to 
meta/recipes-support/apr/apr/0002-apr-Remove-workdir-path-references-from-installed-ap.patch
index 605c4f6..72e706f 100644
--- a/meta/recipes-support/apr/apr/configfix.patch
+++ 
b/meta/recipes-support/apr/apr/0002-apr-Remove-workdir-path-references-from-installed-ap.patch
@@ -1,10 +1,28 @@
+From 5925b20da8bbc34d9bf5a5dca123ef38864d43c6 Mon Sep 17 00:00:00 2001
+From: Hongxu Jia 
+Date: Tue, 30 Jan 2018 09:39:06 +0800
+Subject: [PATCH 2/7] apr: