Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

On dimanche 29 janvier 2017 23:31:49 CET Bruce Ashfield wrote: > On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield > wrote: > > I spent Friday looking into this in more detail, and to keep things > consistent > with how the path and config queues are handled, with all the tree > manipulations > pul

[yocto] [meta-security][PATCH v2 0/9] tpm: virtual TPM for qemu

I recently started using swtpm-native in combination with the qemu-tpm patches to simulate a virtual TPM chip in qemu. The qemu-tpm patches should go into OE-core, but currently usage is a bit cumbersome (requires root privileges and manually starting swtpm before each runqemu invocation), so at th

[yocto] [meta-security][PATCH v2 1/9] trousers: missing libtspi.so.1 in libtspi package

The soname of libtspi.so is "libtspi.so.1" and therefore apps linked against that library depend on the libtspi.so.1 symlink to find the library. Signed-off-by: Patrick Ohly --- recipes-tpm/trousers/trousers_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-tpm/t

[yocto] [meta-security][PATCH v2 2/9] trousers: recommend tcsd

Installing tpm-tools for tools like tpm_takeown pull in the libtspi package, but the resulting system is not functional unless the tcsd (from the main "trousers" package) also gets installed. A RRECOMMENDS entry for that takes care of that automatically. Signed-off-by: Patrick Ohly --- recipes-t

[yocto] [meta-security][PATCH v2 3/9] trousers: tcsd.conf must be owned tss:tss

The upstream dist/Makefile.am ensures that /etc/tcsd.conf is owned by tss:tss, and that must not be changed because otherwise tcsd refuses to start. In addition, tss group and user should be added as special system group resp. user, because they are not normal users. This also avoids the host-use

[yocto] [meta-security][PATCH v2 5/9] swtpm: depends on tpm-tools

The configure script checks for tpm_nvdefine from tpm-tools and fails when it is not present. Signed-off-by: Patrick Ohly --- recipes-tpm/swtpm/swtpm_1.0.bb | 5 + 1 file changed, 5 insertions(+) diff --git a/recipes-tpm/swtpm/swtpm_1.0.bb b/recipes-tpm/swtpm/swtpm_1.0.bb index d5a2a58..528

[yocto] [meta-security][PATCH v2 4/9] swtpm: enable native and nativesdk flavors

For use with qemu-tpm as described in the swtpm main README, swtpm must be compiled natively. nativesdk is added just in case that someone wants to add this to an SDK. The fix_lib_search_path.patch was recently removed during the version update, but it is still needed when building natively. Here'

[yocto] [meta-security][PATCH v2 6/9] swtpm: fix compiler format warning

When building for x86-64, gcc complains: tpm_ioctl.c:866:9: error: format ‘%llx’ expects argument of type ‘long long unsigned int’, but argument 2 has type ‘long unsigned int’ [-Werror=format=] | printf("ptm capability is 0x%llx\n", (uint64_t)devtoh64(is_chardev, cap)); | ^ | c

[yocto] [meta-security][PATCH v2 7/9] swtpm: cuse packageconfig

The CUSE support in swtpm does not depend on selinux. It is needed for simulating a virtual TPM, one of the use cases for swtpm-native, so enable it by default. Signed-off-by: Patrick Ohly --- recipes-tpm/swtpm/swtpm_1.0.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/

[yocto] [meta-security][PATCH v2 8/9] swtpm-wrappers: simplify using swtpm-native

Native tools exist in recipe specific sysroots and are normally not meant to be called from outside a build. But that's what we need to do when using swtpm-native together with qemu, so these wrappers make that possible by setting up the necessary environment and hiding the internal paths. Invokin

[yocto] [meta-security][PATCH v2 9/9] swtpm: update to latest tip

Brings in instructions for setting the log level. Setting the log level with --log file=...,level=1 is necessary at the moment before anything gets written to the log. Even errors are suppressed by default. Signed-off-by: Patrick Ohly --- recipes-tpm/swtpm/swtpm_1.0.bb | 2 +- 1 file changed, 1

[yocto] how to support multi arch?

I am using image that to compiled for arm. I would like to build it for x86 ARCH both, what part should I add? Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] [bitbake][question] Is metadata-revs file content correct?

Hi all, Recently I wanted to use buildhistory a bit more, but I've noticed that content of metadata-revs file is a bit strange. I thought that it should be like "${LAYER_NAME} = ${LAYER_REVISION}" but I get a lots of blank spaces and then "= ${LAYER_REVISION}". Can you tell me whether it i

[yocto] Repeteability in image compilation. How to achieve it? How to measure it?

Hi everybody, How can I be sure that the same image built by distinct building hosts are trully identical?? Is it possible to measure that? Regards! -- "Do or do not. There is no try" Yoda Master -- ___ yocto mailing list yocto@yoctoproject.org htt

Re: [yocto] Repeteability in image compilation. How to achieve it? How to measure it?

Hi, > On 3 Feb 2017, at 14:11, Daniel. wrote: > > Hi everybody, > > How can I be sure that the same image built by distinct building hosts > are trully identical?? Is it possible to measure that? I can recommend tooling offered by the reproducible builds project. Especially diffoscope can be

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

On 2017-02-03 03:42 AM, David Vincent wrote: On dimanche 29 janvier 2017 23:31:49 CET Bruce Ashfield wrote: On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield wrote: I spent Friday looking into this in more detail, and to keep things consistent with how the path and config queues are handled, wit

[yocto] [meta-java]: how add nativesdk-openjdk-8

Hi, I would like to have openjdk-8 in the built SDK. Because there is not yet a nativesdk- package, I have tried in the usual way, but I am facing some issues I do not understand. I have added a .bbappend for openjdk-8-native with : BBCLASSEXTEND_append = " nativesdk" (meta-java: master

[yocto] [meta-selinux][PATCH 3/3] removed ustr package as it is unused

Signed-off-by: Doug Goldstein --- recipes-extended/ustr/ustr/ustr-c99-inline.patch | 30 - .../ustr/ustr/ustr-fix__va_copy-not-defined.patch | 26 - recipes-extended/ustr/ustr/ustr-gnu-inline.diff| 871 - recipes-extended/ustr/ustr/ustr-makefile-fix.patch | 215 -

[yocto] QA Test Report for Yocto Project 2.3 M2 rc1

Hi Here is the report for full QA Cycle on 2.3 M2 rc1 Full Report : https://wiki.yoctoproject.org/wiki/WW05_-_2017-01-24_-_Full_Test_Cycle_2.3_M2_rc1 Summary The QA cycle for 2.3 M2 rc1 was completed, 6 new issues were found, the most important was 10964 that is currently blocking all the au

[yocto] [meta-selinux][PATCH 2/3] removed ustr as a required RDEPEND

Signed-off-by: Doug Goldstein --- recipes-security/packagegroups/packagegroup-core-selinux.bb | 1 - 1 file changed, 1 deletion(-) diff --git a/recipes-security/packagegroups/packagegroup-core-selinux.bb b/recipes-security/packagegroups/packagegroup-core-selinux.bb index 9c74458..128dfba 100644

[yocto] optimize rootfs using strip

Hi, I want to remove unwanted packages but most of them are dependent. So not able to remove easily. can i strip all binary and library before creating rootfs, if possible tell me where to add flags? Can you help me to remove packages like kbd shadow dbus? -- Regards, Prashant -- This mes

[yocto] [meta-selinux][PATCH 1/3] libsemanage: remove dependency on ustr

Use the upstream patches to remove the dependency on ustr which no longer builds with new versions of GCC and the author is unresponsive and the site hosting the code is down. Signed-off-by: Doug Goldstein --- recipes-security/selinux/libsemanage.inc | 2 +- ...anage-simplify-string-

Re: [yocto] Repeteability in image compilation. How to achieve it? How to measure it?

Thank you so mutch Clemens I'll take a look!! Regards, 2017-02-03 11:31 GMT-02:00 Clemens Lang : > Hi, > > > On 3 Feb 2017, at 14:11, Daniel. wrote: > > > > Hi everybody, > > > > How can I be sure that the same image built by distinct building hosts > > are trully identical?? Is it possible

Re: [yocto] Repeteability in image compilation. How to achieve it? How to measure it?

much* 2017-02-03 13:36 GMT-02:00 Daniel. : > Thank you so mutch Clemens I'll take a look!! > > Regards, > > 2017-02-03 11:31 GMT-02:00 Clemens Lang : > >> Hi, >> >> > On 3 Feb 2017, at 14:11, Daniel. wrote: >> > >> > Hi everybody, >> > >> > How can I be sure that the same image built by dist

Re: [yocto] [meta-rockchip][PATCH 2/7] machine: Add machine file for the rk3288 linux Boards

Hi all, Thanks for reviewing, I will looking at comments and suggestions after the other work finished. : ) 在 2017年01月27日 22:37, Romain Perier 写道: Hey, Could you: - Make one patch per new machine file and not one patch for all new added machine - Add a clear @DESCRIPTION for each board,

Re: [yocto] [meta-security][PATCH v2 0/9] tpm: virtual TPM for qemu

On 2/3/17 12:46 AM, Patrick Ohly wrote: > I recently started using swtpm-native in combination with the qemu-tpm > patches to simulate a virtual TPM chip in qemu. The qemu-tpm patches > should go into OE-core, but currently usage is a bit cumbersome > (requires root privileges and manually starting

Re: [yocto] [yocto-kernel-tools][PATCH 0/1] Rework merge of feature branches

On 2017-02-03 03:42 AM, David Vincent wrote: On dimanche 29 janvier 2017 23:31:49 CET Bruce Ashfield wrote: On Wed, Jan 25, 2017 at 1:05 PM, Bruce Ashfield wrote: I spent Friday looking into this in more detail, and to keep things consistent with how the path and config queues are handled, wit

[yocto] Problem building glibc-locale

Hi all, I'm trying to build glibc-locale (actually I'm trying to build core-image-base, but that fails building glibc-locale) and encountering the following error: WARNING: Host distribution "Ubuntu-16.04" has not been validated with this version of the build system; you may possibly ex

Re: [yocto] Problem building glibc-locale

So you did: echo "DISTRO_FEATURES += \"usbhost\"" >> conf/local.conf But poky.conf does: DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC} ${POKY_DEFAULT_DISTRO_FEATURES}" Which means that the final value of DISTRO_FEATURES is "usbhost", so none of the locale support is ena

[yocto] genericx86 vs qemux86

Hello, Yocto. Sorry, I am still a bit confused with genericx86 and qemux86 targets. What is their difference and which one to choose. Both are x86 target and maybe genericx86 has more support for PC hardware? qemux86 has v86d? genericx86 is from poky and qemux86 is from openembeded? I am maki

Re: [yocto] genericx86 vs qemux86

On 3 February 2017 at 23:16, Takashi Matsuzawa wrote: > Sorry, I am still a bit confused with genericx86 and qemux86 targets. > What is their difference and which one to choose. > Both are x86 target and maybe genericx86 has more support for PC hardware? > qemux86 has v86d? > genericx86 is from

[yocto] [meta-security][PATCH] libseccomp: update to tip

adds support for 4.9 and 4.10-rc1 kernels adds support for python 3.x Signed-off-by: Armin Kuster --- recipes-security/libseccomp/libseccomp.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-security/libseccomp/libseccomp.bb b/recipes-security/libseccomp/libsecc

[yocto] [meta-selinux][PATCH] audit: fix build failure

From: Armin Kuster ERROR: oe_runmake failed | /bin/bash: swig: command not found | Makefile:776: recipe for target 'audit_wrap.c' failed | make[4]: *** [audit_wrap.c] Error 127 add swig-native to depends Signed-off-by: Armin Kuster --- recipes-security/audit/audit_2.7.bb | 2 +- 1 file change

Re: [yocto] Problem building glibc-locale

Thank you very much! This solved my problems!! Andras On 2/3/2017 3:14 PM, Burton, Ross wrote: So you did: echo "DISTRO_FEATURES += \"usbhost\"" >> conf/local.conf But poky.conf does: DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC} ${POKY_DEFAULT_DISTRO_FEATURES}" W

Re: [yocto] genericx86 vs qemux86

Hello, thank you for your reply. I wondered vmware or virtuaobox, etc. are doing something already so that the environment looks like a real PC. You can run commercial OS like Windows on it and they are no particularly built for the emulation environment. On the other hand, qemux86* builds a