[yocto] wrong distro name in toolchain

2017-12-18 Thread Marek Słomiany
Hi, I'm having problem while building Qt application inside of yocto and
using generated SDK.
I have bypassed it when using generated SDK, which I describe here.

My setup in short:
I'm using for Qt this layer git://github.com/meta-qt5/meta-qt5.git in rocko
branch
beside Qt, other layers that might be important:
meta-poky (rocko)
meta-oe (morty)
meta-python (morty)
meta-networking (morty)
meta-ti (morty)

The platform is am335x
distro name is "etos"

I had some problems with sdk (at first I added Qt to my build but
applications were developped and build by my coleagues using external
toolchains).
Recently I've added recipes for those apps to my layer.
To test if code I got from my team is building fine, I have generated SDK
using "bitbake  -c populate_sdk" and deployed it in default
path which is /opt/etos/1.0/. When I have sourced it and tried to configure
I got:

  CMake Error at
/opt/etos/1.0/sysroots/armv7ahf-neon-etos-linux-gnueabi/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:32
(message):
  The imported target "Qt5::Core" references the file

 
"/opt/etos/1.0/sysroots/armv7ahf-neon-etos-linux-gnueabi/../x86_64-oesdk-linux/usr/bin/qt5/qmake"
  but this file does not exist.  Possible reasons include:
  * The file was deleted, renamed, or moved to another location.
  * An install or uninstall procedure did not complete successfully.
  * The installation package was faulty and contained

 
"/opt/etos/1.0/sysroots/armv7ahf-neon-etos-linux-gnueabi/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake"
  but not all the files it references.

To solve that problem I coppied the
/opt/etos/1.0/sysroots/x86_64-etossdk-linux/ to
/opt/etos/1.0/sysroots/x86_64-oesdk-linux/ with all its content.
Even if that's not the right solution, it worked.
But now I wat to add the recipe to my image. I get something similar:

Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| CMake Error at
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:20
(message):
|   The imported target "Qt5::Core" references the file
|  "/../x86_64-oesdk-linux/usr/bin/qt5/qmake"
|   but this file does not exist.  Possible reasons include:
|   * The file was deleted, renamed, or moved to another location.
|   * An install or uninstall procedure did not complete successfully.
|   * The installation package was faulty and contained
|
 
"/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake"
|   but not all the files it references.
|
| Call Stack (most recent call first):
|
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake:6
(_qt5_Core_check_file_exists)
|
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:177
(include)
|
/home/mslomiany/linux-dev/poky/build/tmp/sysroots/x86_64-linux/usr/lib/cmake/Qt5/Qt5Config.cmake:33
(find_package)
|   deps/CMake/Qt.cmake:23 (find_package)
|   deps/GuiCore/src/CMakeLists.txt:3 (include)
|
| -- Configuring incomplete, errors occurred!
| See also
"/home/mslomiany/linux-dev/poky/build/tmp/work/armv7ahf-neon-etos-linux-gnueabi/Gui/0.1-r0/build/CMakeFiles/CMakeOutput.log".
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/home/mslomiany/linux-dev/poky/build/tmp/work/armv7ahf-neon-etos-linux-gnueabi/Gui/0.1-r0/temp/log.do_configure.11780)

It seems like my aproach is not making any difference. I might be trying to
copy wrong directories in ./build/tmp subdirectories.
Can you tell me if all those problems are caused by my mistake or is it
something wrong in yocto/openembedded scripts?

Kind Regards,
Marek
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] replace hciattach with a compiled binary

2017-12-18 Thread Sherif Omran
hello guys,

i am working with Bluetooth, and thus installed Bluez5.
But the installed hciattach file has size of 108760 and does not work,
where as the one from raspbian has size of 120636 and is working.

is there a way to replace it?

thanks
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] replace hciattach with a compiled binary

2017-12-18 Thread Alan Martinovic
Hi,
with the risk of being off topic,
the hciattach has been deprecated by btattach.
I'm successfully using it with bluez5.

On Mon, Dec 18, 2017 at 1:08 PM, Sherif Omran  wrote:
> hello guys,
>
> i am working with Bluetooth, and thus installed Bluez5.
> But the installed hciattach file has size of 108760 and does not work, where
> as the one from raspbian has size of 120636 and is working.
>
> is there a way to replace it?
>
> thanks
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] CROPS status?

2017-12-18 Thread Joshua Lock

Hi Martin,

On 14/12/17 20:52, Martin Kelly wrote:

On 12/13/2017 12:44 PM, Avery, Brian wrote:

+ joshua.

I am no longer working on the YP, but Joshua is looking after CROPS. 
It is actually a family of containers, so some parts have been updated 
more recently.


-brian



Thanks Brian. Joshua, do you know the code status? Is the project still 
actively being worked on? Are there any related repositories I should be 
looking at?


We have relatively little time for feature development, but we are 
attempting to keep the container images up-to-date with new distro 
releases. There are Fedora 27 and Ubuntu 17.10 versions of the 
containers available on Docker Hub[1].


Thanks,
Joshua

1. https://hub.docker.com/r/crops/
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Yocto Project Status WW51’17

2017-12-18 Thread Jolley, Stephen K
Current Dev Position: YP 2.5 M2 development

Next Deadline: YP 2.5 M2 cut off of 1/15/18


SWAT team rotation: Stephano -> Maxin on Dec. 15, 2017.

SWAT team rotation: Maxin -> Cal on Dec. 22, 2017.

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


Key Status/Updates:

·The QA of YP 2.5 M1 rc1 is just starting.  See: 
https://wiki.yoctoproject.org/wiki/2.5_QA_Status

·The QA of YP 2.4.1 rc1 is about 80% complete.  See: 
https://wiki.yoctoproject.org/wiki/2.4_QA_Status. We are having some issues 
with the eclipse plugin testing.

·The QA of YP 2.3.3 rc1 is about 3% complete. See: 
https://wiki.yoctoproject.org/wiki/2.3_QA_Status

·YP 2.2.3 rc1 has been built and is queued to begin QA when the QA team 
has bandwidth.

·We have finally tracked down the qemux86-64 kvm apic hang to an issue 
in the host kernel. We have a mitigation plan in mind but that is blocked on 
finding another separate bug causing selftest failures when upgrading the guest 
kernel.

·We have identified further intermittent bugs in various releases which 
we’re continuing to look into (including gpg memory allocation issues on pyro, 
sstate writing races in morty, further occurrences of the inode count issues 
with our NAS on the autobuilder).


Planned upcoming dot releases:

YP 2.4.1 (Rocko) rc1 is in QA.  See 
https://wiki.yoctoproject.org/wiki/2.4_QA_Status.

YP 2.2.3 (Morty) rc1 is in QA.  See 
https://wiki.yoctoproject.org/wiki/2.3_QA_Status.

YP 2.3.3 (Pyro) is built and pending QA.  When work begins see 
https://wiki.yoctoproject.org/wiki/2.2_QA_Status


Key YP 2.5 Dates are:

YP 2.5 M1 release of 12/15/17 (Will be later this month.)

YP 2.5 M2 cut off of 1/15/18

YP 2.5 M2 release of 1/26/18

YP 2.5 M3 cut off of 2/19/18

YP 2.5 M3 release of 3/2/18

YP 2.5 M4 cut off of 4/2/18

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

WDD 2719 (last week 2690)

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


Key Status Links for YP:

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

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

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

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

Thanks,

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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] CROPS status?

2017-12-18 Thread Martin Kelly

On 12/18/2017 07:05 AM, Joshua Lock wrote:

Hi Martin,

On 14/12/17 20:52, Martin Kelly wrote:

On 12/13/2017 12:44 PM, Avery, Brian wrote:

+ joshua.

I am no longer working on the YP, but Joshua is looking after CROPS. 
It is actually a family of containers, so some parts have been 
updated more recently.


-brian



Thanks Brian. Joshua, do you know the code status? Is the project 
still actively being worked on? Are there any related repositories I 
should be looking at?


We have relatively little time for feature development, but we are 
attempting to keep the container images up-to-date with new distro 
releases. There are Fedora 27 and Ubuntu 17.10 versions of the 
containers available on Docker Hub[1].


Thanks,
Joshua

1. https://hub.docker.com/r/crops/


OK, thanks for the information!
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Layer documentation for meta-raspberrypi

2017-12-18 Thread Paul Barker
On Mon, Dec 11, 2017 at 12:20 PM, Paul Barker  wrote:
> On Mon, Dec 11, 2017 at 12:08 PM, Mirza Krak  wrote:
>> 2017-12-11 12:55 GMT+01:00 Paul Barker :
>>> Hi all,
>>>
>>> As a quick announcement, the layer documentation for meta-raspberrypi
>>> is now available on Read the Docs:
>>> http://meta-raspberrypi.readthedocs.io/en/latest/
>>>

>>
>> One little thing though, the current "theme" used which I assume is
>> the default Sphinx theme is not optimal IMO.
>>

>
> Thanks for the feedback. The conf.py file we're using is just what was
> generated by sphinx-quickstart with minimal tweaks. It sets html_theme
> which is obviously overriding the default for read the docs.
>
> I think I should be able to get the right behaviour by commenting out
> the html_theme setting completely. I'll give that a go and see what
> happens.
>

That worked. Looks much better!
http://meta-raspberrypi.readthedocs.io/en/latest/index.html

I'll backport that little change to pyro/rocko when I have some spare time.

-- 
Paul Barker
Togán Labs Ltd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Layer documentation for meta-raspberrypi

2017-12-18 Thread Mirza Krak
On Dec 18, 2017 20:50, "Paul Barker"  wrote:

On Mon, Dec 11, 2017 at 12:20 PM, Paul Barker  wrote:
> On Mon, Dec 11, 2017 at 12:08 PM, Mirza Krak  wrote:
>> 2017-12-11 12:55 GMT+01:00 Paul Barker :
>>> Hi all,
>>>
>>> As a quick announcement, the layer documentation for meta-raspberrypi
>>> is now available on Read the Docs:
>>> http://meta-raspberrypi.readthedocs.io/en/latest/
>>>

>>
>> One little thing though, the current "theme" used which I assume is
>> the default Sphinx theme is not optimal IMO.
>>

>
> Thanks for the feedback. The conf.py file we're using is just what was
> generated by sphinx-quickstart with minimal tweaks. It sets html_theme
> which is obviously overriding the default for read the docs.
>
> I think I should be able to get the right behaviour by commenting out
> the html_theme setting completely. I'll give that a go and see what
> happens.
>

That worked. Looks much better!
http://meta-raspberrypi.readthedocs.io/en/latest/index.html


Great job. Agree that it looks much better.

Best Regards
Mirza
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-gplv2][PATCH 0/3] Consolidated re-send of previously submitted patches

2017-12-18 Thread Andre McCurdy
Andre McCurdy (2):
  gnutls: update 3.3.27 -> 3.3.28
  elfutils_0.148: musl build fixes

Phong Tran (1):
  gettext: fix compilation with securityflags enabled

 ...grep-fix-compile-error-Werror-format-secu.patch |  88 ++
 recipes-core/gettext/gettext_0.16.1.bb |   1 +
 .../musl-support-for-elfutils-0.148.patch  | 133 +
 recipes-devtools/elfutils/elfutils_0.148.bb|   9 +-
 recipes-support/gnutls/gnutls.inc  |   9 +-
 recipes-support/gnutls/gnutls_3.3.27.bb|  17 ---
 recipes-support/gnutls/gnutls_3.3.28.bb|   8 ++
 7 files changed, 241 insertions(+), 24 deletions(-)
 create mode 100644 
recipes-core/gettext/gettext-0.16.1/0001-gettext-libgrep-fix-compile-error-Werror-format-secu.patch
 create mode 100644 
recipes-devtools/elfutils/elfutils-0.148/musl-support-for-elfutils-0.148.patch
 delete mode 100644 recipes-support/gnutls/gnutls_3.3.27.bb
 create mode 100644 recipes-support/gnutls/gnutls_3.3.28.bb

-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-gplv2][PATCH 1/3] gnutls: update 3.3.27 -> 3.3.28

2017-12-18 Thread Andre McCurdy
* Version 3.3.28 (released 2017-07-04)

** libgnutls: Fixed issue when rehandshaking without a client certificate in
   a session which initially used one. Reported by Frantisek Sumsal.

** libgnutls: fix issue in RSA-PSK client callback which resulted in no username
   being sent to the peer. Patch by Nicolas Dufresne.

** libgnutls: no longer parse the ResponseID field of the status response
   TLS extension. The field is not used by GnuTLS nor is made available to
   calling applications. That addresses a null pointer dereference on server
   side caused by packets containing the ResponseID field. Reported
   by Hubert Kario. [GNUTLS-SA-2017-4]

** libgnutls: Handle specially HSMs which request explicit authentication.
   There are HSMs which return CKR_USER_NOT_LOGGED_IN on the first private key
   operation. Detect that state and try to login.

** libgnutls: the GNUTLS_PKCS11_OBJ_FLAG_LOGIN will force a login on HSMs.
   That is, even in tokens which do not have a CKF_LOGIN_REQUIRED flag
   a login will be forced. This improves operation on certain Safenet HSMs.

** libgnutls: do not set leading zeros when copying integers on HSMs.
   PKCS#11 defines integers as unsigned having most significant byte
   first, e.g., 32768 = 0x80 0x00. This is interpreted literraly by
   some HSMs which do not accept an integer with a leading zero. This
   improves operation with certain Atos HSMs.

** libgnutls: Backported PKCS#11 key generation functionality for DSA keys.

** libgnutls: Improve check for /dev/urandom uniqueness. Ensure that when
   gnutls_global_init() is called for a second time that /dev/urandom is
   re-opened when the inode or device ID has changed.

** API and ABI modifications:
No changes since last version.

Signed-off-by: Andre McCurdy 
---
 recipes-support/gnutls/gnutls.inc   |  9 -
 recipes-support/gnutls/gnutls_3.3.27.bb | 17 -
 recipes-support/gnutls/gnutls_3.3.28.bb |  8 
 3 files changed, 12 insertions(+), 22 deletions(-)
 delete mode 100644 recipes-support/gnutls/gnutls_3.3.27.bb
 create mode 100644 recipes-support/gnutls/gnutls_3.3.28.bb

diff --git a/recipes-support/gnutls/gnutls.inc 
b/recipes-support/gnutls/gnutls.inc
index 4a5c3df..4cf375f 100644
--- a/recipes-support/gnutls/gnutls.inc
+++ b/recipes-support/gnutls/gnutls.inc
@@ -8,9 +8,8 @@ LICENSE_${PN}-xx = "LGPLv2.1+"
 LICENSE_${PN}-bin = "GPLv3+"
 LICENSE_${PN}-openssl = "GPLv3+"
 
-LIC_FILES_CHKSUM = "file://LICENSE;md5=71391c8e0c1cfe68077e7fce3b586283 \
-file://doc/COPYING;md5=d32239bcb673463ab874e80d47fae504 \
-
file://doc/COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
+file://COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
 
 DEPENDS = "nettle gmp virtual/libiconv"
 DEPENDS_append_libc-musl = " argp-standalone"
@@ -21,9 +20,8 @@ SRC_URI = 
"ftp://ftp.gnutls.org/gcrypt/gnutls/v${SHRT_VER}/gnutls-${PV}.tar.xz";
 
 inherit autotools texinfo binconfig pkgconfig gettext lib_package gtk-doc
 
-PACKAGECONFIG ??= "libidn zlib"
+PACKAGECONFIG ??= "zlib"
 
-PACKAGECONFIG[libidn] = "--with-idn,--without-idn,libidn"
 PACKAGECONFIG[libtasn1] = 
"--with-included-libtasn1=no,--with-included-libtasn1,libtasn1"
 PACKAGECONFIG[p11-kit] = "--with-p11-kit,--without-p11-kit,p11-kit"
 PACKAGECONFIG[tpm] = "--with-tpm,--without-tpm,trousers"
@@ -31,6 +29,7 @@ PACKAGECONFIG[zlib] = "--with-zlib,--without-zlib,zlib"
 
 EXTRA_OECONF = " \
 --enable-doc \
+--disable-crywrap \
 --disable-libdane \
 --disable-guile \
 --disable-rpath \
diff --git a/recipes-support/gnutls/gnutls_3.3.27.bb 
b/recipes-support/gnutls/gnutls_3.3.27.bb
deleted file mode 100644
index a1dcdb5..000
--- a/recipes-support/gnutls/gnutls_3.3.27.bb
+++ /dev/null
@@ -1,17 +0,0 @@
-require gnutls.inc
-
-LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504 \
-file://COPYING.LESSER;md5=a6f89e2100d9b6cdffcea4f398e37343"
-
-SRC_URI += " \
-file://configure.ac-fix-sed-command.patch \
-file://use-pkg-config-to-locate-zlib.patch \
-"
-SRC_URI[md5sum] = "8ee8cebd7f7575b11f232766a21c31d3"
-SRC_URI[sha256sum] = 
"8dfda16c158ef5c134010d51d1a91d02aa5d43b8cb711b1572650a7ffb56b17f"
-
-# This version doesn't support this option added in newer gnutls
-# ERROR: gnutls-3.3.27-r0 do_configure: QA Issue: gnutls: configure was passed 
unrecognised options: --with-idn [unknown-configure-option]
-PACKAGECONFIG[libidn] = ""
-# but it still has the libidn dependency, without this option
-EXTRA_OECONF += "--disable-crywrap"
diff --git a/recipes-support/gnutls/gnutls_3.3.28.bb 
b/recipes-support/gnutls/gnutls_3.3.28.bb
new file mode 100644
index 000..1b23369
--- /dev/null
+++ b/recipes-support/gnutls/gnutls_3.3.28.bb
@@ -0,0 +1,8 @@
+require gnutls.inc
+
+SRC_URI += " \
+file://configure.ac-fix-sed-command.patch \
+file://use-pkg-config-to-locate-zlib

[yocto] [meta-gplv2][PATCH 2/3] elfutils_0.148: musl build fixes

2017-12-18 Thread Andre McCurdy
Signed-off-by: Andre McCurdy 
---
 .../musl-support-for-elfutils-0.148.patch  | 133 +
 recipes-devtools/elfutils/elfutils_0.148.bb|   9 +-
 2 files changed, 140 insertions(+), 2 deletions(-)
 create mode 100644 
recipes-devtools/elfutils/elfutils-0.148/musl-support-for-elfutils-0.148.patch

diff --git 
a/recipes-devtools/elfutils/elfutils-0.148/musl-support-for-elfutils-0.148.patch
 
b/recipes-devtools/elfutils/elfutils-0.148/musl-support-for-elfutils-0.148.patch
new file mode 100644
index 000..5a52d6d
--- /dev/null
+++ 
b/recipes-devtools/elfutils/elfutils-0.148/musl-support-for-elfutils-0.148.patch
@@ -0,0 +1,133 @@
+From 8a6cefcd35fb0ba6e12afc6611cfeb600865ca17 Mon Sep 17 00:00:00 2001
+From: Andre McCurdy 
+Date: Wed, 27 Sep 2017 21:32:27 -0700
+Subject: [PATCH] musl build fixes
+
+Upstream-Status: Inappropriate [legacy version]
+
+Signed-off-by: Andre McCurdy 
+---
+ lib/fixedsizehash.h   |  4 ++--
+ lib/system.h  | 11 +++
+ libelf/elf.h  |  8 ++--
+ libelf/elf_begin.c|  4 ++--
+ libelf/elf_getarsym.c |  2 +-
+ libelf/libelf.h   |  1 +
+ 6 files changed, 23 insertions(+), 7 deletions(-)
+
+diff --git a/lib/fixedsizehash.h b/lib/fixedsizehash.h
+index a686051..3118954 100644
+--- a/lib/fixedsizehash.h
 b/lib/fixedsizehash.h
+@@ -51,12 +51,12 @@
+ #include 
+ #include 
+ #include 
+-#include 
+ #include 
+ 
+ #include 
+ 
+-#define CONCAT(t1,t2) __CONCAT (t1,t2)
++#define CONCAT1(x,y) x##y
++#define CONCAT(x,y) CONCAT1(x,y)
+ 
+ /* Before including this file the following macros must be defined:
+ 
+diff --git a/lib/system.h b/lib/system.h
+index 10b4734..a9cb35e 100644
+--- a/lib/system.h
 b/lib/system.h
+@@ -52,6 +52,17 @@
+ #include 
+ #include 
+ 
++#ifndef TEMP_FAILURE_RETRY
++#define TEMP_FAILURE_RETRY(expression)\
++  (__extension__  \
++({ long int __result; \
++   do __result = (long int) (expression); \
++   while (__result == -1L && errno == EINTR); \
++   __result; }))
++#endif
++
++#define error(status, errno, ...) err(status, __VA_ARGS__)
++
+ extern void *xmalloc (size_t) __attribute__ ((__malloc__));
+ extern void *xcalloc (size_t, size_t) __attribute__ ((__malloc__));
+ extern void *xrealloc (void *, size_t) __attribute__ ((__malloc__));
+diff --git a/libelf/elf.h b/libelf/elf.h
+index 4158764..6d9af96 100644
+--- a/libelf/elf.h
 b/libelf/elf.h
+@@ -23,7 +23,9 @@
+ 
+ #include 
+ 
+-__BEGIN_DECLS
++#ifdef __cplusplus
++extern "C" {
++#endif
+ 
+ /* Standard ELF types.  */
+ 
+@@ -2909,6 +2911,8 @@ typedef Elf32_Addr Elf32_Conflict;
+ #define R_M32R_NUM256 /* Keep this the last entry. */
+ 
+ 
+-__END_DECLS
++#ifdef __cplusplus
++}
++#endif
+ 
+ #endif/* elf.h */
+diff --git a/libelf/elf_begin.c b/libelf/elf_begin.c
+index 0b38991..9083736 100644
+--- a/libelf/elf_begin.c
 b/libelf/elf_begin.c
+@@ -819,7 +819,7 @@ __libelf_next_arhdr_wrlock (elf)
+ }
+ 
+   /* Copy the raw name over to a NUL terminated buffer.  */
+-  *((char *) __mempcpy (elf->state.ar.raw_name, ar_hdr->ar_name, 16)) = '\0';
++  *((char *) mempcpy (elf->state.ar.raw_name, ar_hdr->ar_name, 16)) = '\0';
+ 
+   elf_ar_hdr = &elf->state.ar.elf_ar_hdr;
+ 
+@@ -911,7 +911,7 @@ __libelf_next_arhdr_wrlock (elf)
+   const char *string = ar_hdr->FIELD;   \
+   if (ar_hdr->FIELD[sizeof (ar_hdr->FIELD) - 1] != ' ') \
+   { \
+-*((char *) __mempcpy (buf, ar_hdr->FIELD, sizeof (ar_hdr->FIELD)))  \
++*((char *) mempcpy (buf, ar_hdr->FIELD, sizeof (ar_hdr->FIELD)))\
+   = '\0';   \
+ string = buf;   \
+   } \
+diff --git a/libelf/elf_getarsym.c b/libelf/elf_getarsym.c
+index 9ff7f29..74339ce 100644
+--- a/libelf/elf_getarsym.c
 b/libelf/elf_getarsym.c
+@@ -257,7 +257,7 @@ elf_getarsym (elf, ptr)
+ else
+   arsym[cnt].as_off = file_data[cnt];
+ arsym[cnt].as_hash = _dl_elf_hash (str_data);
+-str_data = rawmemchr (str_data, '\0') + 1;
++str_data = memchr (str_data, '\0', SIZE_MAX) + 1;
+   }
+ /* At the end a special entry.  */
+ arsym[n].as_name = NULL;
+diff --git a/libelf/libelf.h b/libelf/libelf.h
+index b0b3a8d..ec15c43 100644
+--- a/libelf/libelf.h
 b/libelf/libelf.h
+@@ -50,6 +50,7 @@
+ #ifndef _LIBELF_H
+ #define _LIBELF_H 1
+ 
++#include 
+ #include 
+ 
+ /* Get the ELF types.  */
+-- 
+1.9.1
+
diff --git a/recipes-devtools/elfutils/elfutils_0.148.bb 
b/recipes-devtools/elfutils/elfutils_0.148.bb
index 892a523..a03b74e 100644
--- a/recipes-devtools/elfutils/elfutils_0.1

[yocto] [meta-gplv2][PATCH 3/3] gettext: fix compilation with securityflags enabled

2017-12-18 Thread Andre McCurdy
From: Phong Tran 

Signed-off-by: Phong Tran 
---
 ...grep-fix-compile-error-Werror-format-secu.patch | 88 ++
 recipes-core/gettext/gettext_0.16.1.bb |  1 +
 2 files changed, 89 insertions(+)
 create mode 100644 
recipes-core/gettext/gettext-0.16.1/0001-gettext-libgrep-fix-compile-error-Werror-format-secu.patch

diff --git 
a/recipes-core/gettext/gettext-0.16.1/0001-gettext-libgrep-fix-compile-error-Werror-format-secu.patch
 
b/recipes-core/gettext/gettext-0.16.1/0001-gettext-libgrep-fix-compile-error-Werror-format-secu.patch
new file mode 100644
index 000..d51513d
--- /dev/null
+++ 
b/recipes-core/gettext/gettext-0.16.1/0001-gettext-libgrep-fix-compile-error-Werror-format-secu.patch
@@ -0,0 +1,88 @@
+From b0e57fc44ee102c668f13a324360fb2f27ee7538 Mon Sep 17 00:00:00 2001
+From: Phong Tran 
+Date: Fri, 8 Dec 2017 07:56:58 +0700
+Subject: [PATCH] gettext libgrep fix compile error -Werror=format-security
+
+---
+ gettext-tools/libgrep/m-fgrep.c |  4 ++--
+ gettext-tools/libgrep/m-regex.c | 12 ++--
+ 2 files changed, 8 insertions(+), 8 deletions(-)
+
+diff --git a/gettext-tools/libgrep/m-fgrep.c b/gettext-tools/libgrep/m-fgrep.c
+index 28f900c..2e49a74 100644
+--- a/gettext-tools/libgrep/m-fgrep.c
 b/gettext-tools/libgrep/m-fgrep.c
+@@ -55,7 +55,7 @@ Fcompile (const char *pattern, size_t pattern_size,
+   for (lim = beg; lim < pattern + pattern_size && *lim != '\n'; ++lim)
+   ;
+   if ((err = kwsincr (ckwset->kwset, beg, lim - beg)) != NULL)
+-  error (exit_failure, 0, err);
++  error (exit_failure, 0, "%s", err);
+   if (lim < pattern + pattern_size)
+   ++lim;
+   beg = lim;
+@@ -63,7 +63,7 @@ Fcompile (const char *pattern, size_t pattern_size,
+   while (beg < pattern + pattern_size);
+ 
+   if ((err = kwsprep (ckwset->kwset)) != NULL)
+-error (exit_failure, 0, err);
++error (exit_failure, 0, "%s", err);
+   return ckwset;
+ }
+ 
+diff --git a/gettext-tools/libgrep/m-regex.c b/gettext-tools/libgrep/m-regex.c
+index 6f7aae3..70f04b3 100644
+--- a/gettext-tools/libgrep/m-regex.c
 b/gettext-tools/libgrep/m-regex.c
+@@ -73,7 +73,7 @@ struct compiled_regex {
+ void
+ dfaerror (const char *mesg)
+ {
+-  error (exit_failure, 0, mesg);
++  error (exit_failure, 0, "%s", mesg);
+ }
+ 
+ /* If the DFA turns out to have some set of fixed strings one of
+@@ -99,7 +99,7 @@ kwsmusts (struct compiled_regex *cregex,
+   continue;
+ cregex->kwset_exact_matches++;
+ if ((err = kwsincr (cregex->ckwset.kwset, dm->must, strlen 
(dm->must))) != NULL)
+-  error (exit_failure, 0, err);
++  error (exit_failure, 0, "%s", err);
+   }
+   /* Now, we compile the substrings that will require
+the use of the regexp matcher.  */
+@@ -108,10 +108,10 @@ kwsmusts (struct compiled_regex *cregex,
+ if (dm->exact)
+   continue;
+ if ((err = kwsincr (cregex->ckwset.kwset, dm->must, strlen 
(dm->must))) != NULL)
+-  error (exit_failure, 0, err);
++  error (exit_failure, 0, "%s", err);
+   }
+   if ((err = kwsprep (cregex->ckwset.kwset)) != NULL)
+-  error (exit_failure, 0, err);
++  error (exit_failure, 0, "%s", err);
+ }
+ }
+ 
+@@ -161,7 +161,7 @@ Gcompile (const char *pattern, size_t pattern_size,
+ 
+   if ((err = re_compile_pattern (motif, len,
+
&(cregex->patterns[cregex->pcount].regexbuf))) != NULL)
+-  error (exit_failure, 0, err);
++  error (exit_failure, 0, "%s", err);
+   cregex->pcount++;
+ 
+   motif = sep;
+@@ -247,7 +247,7 @@ compile (const char *pattern, size_t pattern_size,
+ 
+   if ((err = re_compile_pattern (motif, len,
+
&(cregex->patterns[cregex->pcount].regexbuf))) != NULL)
+-  error (exit_failure, 0, err);
++  error (exit_failure, 0, "%s", err);
+   cregex->pcount++;
+ 
+   motif = sep;
+-- 
+2.7.4
+
diff --git a/recipes-core/gettext/gettext_0.16.1.bb 
b/recipes-core/gettext/gettext_0.16.1.bb
index e79f4da..dacdfd3 100644
--- a/recipes-core/gettext/gettext_0.16.1.bb
+++ b/recipes-core/gettext/gettext_0.16.1.bb
@@ -19,6 +19,7 @@ SRC_URI = "${GNU_MIRROR}/gettext/gettext-${PV}.tar.gz \
file://fix_aclocal_version.patch \
file://fix_gnu_source_circular.patch \
file://hardcode_macro_version.patch \
+   
file://0001-gettext-libgrep-fix-compile-error-Werror-format-secu.patch \
   "
 
 SRC_URI[md5sum] = "3d9ad24301c6d6b17ec30704a13fe127"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] How to disable a linux virtual terminal...

2017-12-18 Thread Mirza Krak
2017-12-14 22:51 GMT+01:00 Greer, Charles (ext) :
> Hi all,
>
>
>
> Would anyone know how to disable the virtual terminals in linux?  I am using
> Yocto, Morty version on an i.MX6 processor.  Even though our base
> distribution is Yocto, unfortunately we have diverged from building it with
> recipes, so this is more of a straight linux question than Yocto…
>
>
>
> To give some detail as to my problem:  It is for an embedded device that has
> an HDMI port - when I attach a terminal to the HDMI port it shows the Linux
> Penguin logo, a getty service and blanks out after 600 seconds.  I just want
> to use the hdmi port as an output with nothing displayed on the output and I
> want it to stay on all the time.
>
>
>
> I have found that the hdmi port maps to /dev/tty1 – when I type:  echo
> “asdfasdf” > /dev/tty1 I see the characters output to the monitor.
>
>
>
> Here are a few things I have tried to no avail – a lot of these are not
> needed if I can figure out how to disable it as a virtual terminal…
>
>
>
> · I figured out how to disable the getty service but a cursor still
> blinks.   I don’t even want a cursor to show

Normally you disable the cursor with a kernel argument:

vt.global_cursor_default=0

You probably also need to remove "console=tty1" from kernel arguments
to avoid to getting "boot prints"

< snip >

> Disabling the logo or console blanking would not be necessary if I could
> just figure out how to disable that port as a terminal…
>
>
>
> So does anyone have pointers or things I could try?  I am relatively new
> (returning after 10 years - I worked with DNX 10 years ago v2.6 and it seems
> everything I knew about init is fairly obsolete lol) to linux so I am sure I
> am missing a lot…

Well it sounds to me that you would like to disable the framebuffer
console completely.

Removing (=n) the

CONFIG_FRAMEBUFFER_CONSOLE

config should definitely get rid of most of the things that you
mentioned. But normally you would not disable it completely if you
would like to display a "boot screen" / splashscreen but if you do not
want it you can safely remove that option.

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] How to use iconv natively in do_compile?

2017-12-18 Thread Aaron_Wright
I'm on pyro, and I have a do_compile step that converts some files to 
UTF8. I use iconv to do this.

According to `oe-pkgdata-util find-path /usr/bin/iconv`, iconv is provided 
by the glibc-utils package. So I tried adding glibc-native or glibc to my 
DEPENDS, but that didn't work. 

I also tried virtual/libiconv-native without any luck. virtual/libiconv is 
listed in ASSUME_PROVIDED but iconv isn't in HOSTTOOLS. I'm not 100% sure 
how those variables are supposed to work.

What do I put in my DEPENDS so that iconv is natively available during 
do_compile?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] wrong distro name in toolchain

2017-12-18 Thread Mirza Krak
2017-12-18 12:11 GMT+01:00 Marek Słomiany :
> Hi, I'm having problem while building Qt application inside of yocto and
> using generated SDK.
> I have bypassed it when using generated SDK, which I describe here.
>
> My setup in short:
> I'm using for Qt this layer git://github.com/meta-qt5/meta-qt5.git in rocko
> branch
> beside Qt, other layers that might be important:
> meta-poky (rocko)
> meta-oe (morty)
> meta-python (morty)
> meta-networking (morty)
> meta-ti (morty)

First of, why are you mixing branches here? You should use the same
branch on all the layer for better chances for it to work
out-of-the-box. There have been a lot of changes to the "core" from
morty to rocko and trying to mix them probably raises some "extra"
problems that you would not normally get.

>
> The platform is am335x
> distro name is "etos"
>
> I had some problems with sdk (at first I added Qt to my build but
> applications were developped and build by my coleagues using external
> toolchains).
> Recently I've added recipes for those apps to my layer.
> To test if code I got from my team is building fine, I have generated SDK
> using "bitbake  -c populate_sdk" and deployed it in default path
> which is /opt/etos/1.0/. When I have sourced it and tried to configure I
> got:

What image did you build when you generated the SDK?

meta-qt5 seems to provide a recipe for a toolchain containing all the
Qt stuff including qmake [1].  Try that out if you haven't already by
simply running:

   bitbake meta-toolchain-qt5

[1]. 
https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/meta/meta-toolchain-qt5.bb

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

2017-12-18 Thread Robert Yang

Hi Alexander,

Thank you very much, I will try it later:-).

// Robert

On 12/15/2017 09:35 PM, Alexander Kanavin wrote:

On 12/14/2017 06:38 PM, Alexander Kanavin wrote:


Got it, thanks.


I just sent the patches to yocto@ ML and published them on github - please do 
try them out, and rebase your patchset on top (some of it may no longer be 
relevant).


I did the rebase myself, and pushed the result here - please check and feel free 
to add anything else that you deem useful:


http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/log/?h=devel

Alex


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto