Date   

[meta-security][PATCH] softhsm: drop pkg as meta-oe has it

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-security/softHSM/softhsm_2.6.1.bb | 30 -----------------------
1 file changed, 30 deletions(-)
delete mode 100644 recipes-security/softHSM/softhsm_2.6.1.bb

diff --git a/recipes-security/softHSM/softhsm_2.6.1.bb b/recipes-security/softHSM/softhsm_2.6.1.bb
deleted file mode 100644
index 74e837a..0000000
--- a/recipes-security/softHSM/softhsm_2.6.1.bb
+++ /dev/null
@@ -1,30 +0,0 @@
-SUMMARY = "SoftHSM is an implementation of a cryptographic store accessible through a PKCS #11 interface."
-HOMEPAGE = "www.opendnssec.org"
-
-LICENSE = "BSD"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ef3f77a3507c3d91e75b9f2bdaee4210"
-
-DEPENDS = "sqlite3"
-
-SRC_URI = "https://dist.opendnssec.org/source/softhsm-2.6.1.tar.gz"
-SRC_URI[sha256sum] = "61249473054bcd1811519ef9a989a880a7bdcc36d317c9c25457fc614df475f2"
-
-inherit autotools pkgconfig siteinfo
-
-EXTRA_OECONF += " --with-sqlite3=${STAGING_DIR_HOST}/usr"
-EXTRA_OECONF += "${@oe.utils.conditional('SITEINFO_BITS', '64', ' --enable-64bit', '', d)}"
-
-PACKAGECONFIG ?= "pk11 openssl"
-
-PACKAGECONFIG[npm] = ",--disable-non-paged-memory"
-PACKAGECONFIG[ecc] = "--enable-ecc,--disable-ecc"
-PACKAGECONFIG[gost] = "--enable-gost,--disable-gost"
-PACKAGECONFIG[eddsa] = "--enable-eddsa, --disable-eddsa"
-PACKAGECONFIG[fips] = "--enable-fips, --disable-fips"
-PACKAGECONFIG[notvisable] = "--disable-visibility"
-PACKAGECONFIG[openssl] = "--with-openssl=${STAGING_DIR_HOST}/usr --with-crypto-backend=openssl, --without-openssl, openssl, openssl"
-PACKAGECONFIG[botan] = "--with-botan=${STAGING_DIR_HOST}/usr --with-crypto-backend=botan, --without-botan, botan"
-PACKAGECONFIG[migrate] = "--with-migrate"
-PACKAGECONFIG[pk11] = "--enable-p11-kit --with-p11-kit==${STAGING_DIR_HOST}/usr, --without-p11-kit, p11-kit, p11-kit"
-
-RDEPENDS_${PN} = "sqlite3"
--
2.17.1


[meta-security] [PATCH V2 8/8] ima-evm-rootfs.bbclass: avoid generating /etc/fstab for wic

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

Or else wic will fail without "--no-fstab-update" option.

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
meta-integrity/classes/ima-evm-rootfs.bbclass | 3 +++
1 file changed, 3 insertions(+)

diff --git a/meta-integrity/classes/ima-evm-rootfs.bbclass b/meta-integri=
ty/classes/ima-evm-rootfs.bbclass
index 4359af0..0acd6e7 100644
--- a/meta-integrity/classes/ima-evm-rootfs.bbclass
+++ b/meta-integrity/classes/ima-evm-rootfs.bbclass
@@ -28,6 +28,9 @@ IMA_EVM_ROOTFS_HASHED ?=3D ". -depth 0 -false"
# the iversion flags (needed by IMA when allowing writing).
IMA_EVM_ROOTFS_IVERSION ?=3D ""
=20
+# Avoid re-generating fstab when ima is enabled.
+WIC_CREATE_EXTRA_ARGS_append =3D "${@bb.utils.contains('DISTRO_FEATURES'=
, 'ima', ' --no-fstab-update', '', d)}"
+
ima_evm_sign_rootfs () {
cd ${IMAGE_ROOTFS}
=20
--=20
2.29.0


[meta-security] [PATCH V2 7/8] initramfs-framework-ima: let ima_enabled return 0

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

Otherwise, ima script would not run as intended.

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
.../recipes-core/initrdscripts/initramfs-framework-ima/ima | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-integrity/recipes-core/initrdscripts/initramfs-framewor=
k-ima/ima b/meta-integrity/recipes-core/initrdscripts/initramfs-framework=
-ima/ima
index 16ed53f..cff26a3 100644
--- a/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima/i=
ma
+++ b/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima/i=
ma
@@ -6,6 +6,7 @@ ima_enabled() {
if [ "$bootparam_no_ima" =3D "true" ]; then
return 1
fi
+ return 0
}
=20
ima_run() {
--=20
2.29.0


[meta-security] [PATCH V2 6/8] README.md: update according to the refactoring in ima-evm-rootfs.bbclass

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
meta-integrity/README.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta-integrity/README.md b/meta-integrity/README.md
index 4607948..5048fba 100644
--- a/meta-integrity/README.md
+++ b/meta-integrity/README.md
@@ -73,8 +73,10 @@ Adding the layer only enables IMA (see below regarding=
EVM) during
compilation of the Linux kernel. To also activate it when building
the image, enable image signing in the local.conf like this:
=20
- INHERIT +=3D "ima-evm-rootfs"
+ IMAGE_CLASSES +=3D "ima-evm-rootfs"
IMA_EVM_KEY_DIR =3D "${INTEGRITY_BASE}/data/debug-keys"
+ IMA_EVM_PRIVKEY =3D "${IMA_EVM_KEY_DIR}/privkey_ima.pem"
+ IMA_EVM_X509 =3D "${IMA_EVM_KEY_DIR}/x509_ima.der"
=20
This uses the default keys provided in the "data" directory of the layer=
.
Because everyone has access to these private keys, such an image
--=20
2.29.0


[meta-security] [PATCH V2 5/8] meta: refactor IMA/EVM sign rootfs

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

The current logic in ima-evm-rootfs.bbclass does not guarantee
ima_evm_sign_rootfs is the last function in IMAGE_PREPROCESS_COMMAND
by appending to it, for instance, if there are other "_append" being
used as it's the case in openembedded-core/meta/classes/image.bbclass:

| IMAGE_PREPROCESS_COMMAND_append =3D " ${@ 'systemd_preset_all;' \
| if bb.utils.contains('DISTRO_FEATURES', 'systemd', True, False, d) \
| and not bb.utils.contains('IMAGE_FEATURES', 'stateless-rootfs', True,
| False, d) else ''} reproducible_final_image_task; "

and ima-evm-rootfs should be in IMAGE_CLASSES instead of in INHERIT
since that would impact all recipes but not only image recipes.

To fix the above issues, we introduce a ima_evm_sign_handler setting
IMA/EVM rootfs signing requirements/dependencies in event
bb.event.RecipePreFinalise, it checks 'ima' distro feature to decide if
IMA/EVM rootfs signing logic should be applied or not.

Also add ima-evm-keys to IMAGE_INSTALL.

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
meta-integrity/classes/ima-evm-rootfs.bbclass | 30 ++++++++-----------
1 file changed, 12 insertions(+), 18 deletions(-)

diff --git a/meta-integrity/classes/ima-evm-rootfs.bbclass b/meta-integri=
ty/classes/ima-evm-rootfs.bbclass
index d6ade3b..4359af0 100644
--- a/meta-integrity/classes/ima-evm-rootfs.bbclass
+++ b/meta-integrity/classes/ima-evm-rootfs.bbclass
@@ -37,15 +37,6 @@ ima_evm_sign_rootfs () {
# reasons (including a change of the signing keys) without also
# re-running do_rootfs.
=20
- # Copy file(s) which must be on the device. Note that
- # evmctl uses x509_evm.der also for "ima_verify", which is probably
- # a bug (should default to x509_ima.der). Does not matter for us
- # because we use the same key for both.
- install -d ./${sysconfdir}/keys
- rm -f ./${sysconfdir}/keys/x509_evm.der
- install "${IMA_EVM_X509}" ./${sysconfdir}/keys/x509_evm.der
- ln -sf x509_evm.der ./${sysconfdir}/keys/x509_ima.der
-
# Fix /etc/fstab: it must include the "i_version" mount option for
# those file systems where writing files is allowed, otherwise
# these changes will not get detected at runtime.
@@ -80,13 +71,16 @@ ima_evm_sign_rootfs () {
}
=20
# Signing must run as late as possible in the do_rootfs task.
-# IMAGE_PREPROCESS_COMMAND runs after ROOTFS_POSTPROCESS_COMMAND, so
-# append (not prepend!) to IMAGE_PREPROCESS_COMMAND, and do it with
-# _append instead of +=3D because _append gets evaluated later. In
-# particular, we must run after prelink_image in
-# IMAGE_PREPROCESS_COMMAND, because prelinking changes executables.
-
-IMAGE_PREPROCESS_COMMAND_append =3D " ima_evm_sign_rootfs ; "
+# To guarantee that, we append it to IMAGE_PREPROCESS_COMMAND in
+# RecipePreFinalise event handler, this ensures it's the last
+# function in IMAGE_PREPROCESS_COMMAND.
+python ima_evm_sign_handler () {
+ if not e.data or 'ima' not in e.data.getVar('DISTRO_FEATURES').split=
():
+ return
=20
-# evmctl must have been installed first.
-do_rootfs[depends] +=3D "ima-evm-utils-native:do_populate_sysroot"
+ e.data.appendVar('IMAGE_PREPROCESS_COMMAND', ' ima_evm_sign_rootfs; =
')
+ e.data.appendVar('IMAGE_INSTALL', ' ima-evm-keys')
+ e.data.appendVarFlag('do_rootfs', 'depends', ' ima-evm-utils-native:=
do_populate_sysroot')
+}
+addhandler ima_evm_sign_handler
+ima_evm_sign_handler[eventmask] =3D "bb.event.RecipePreFinalise"
--=20
2.29.0


[meta-security] [PATCH V2 4/8] initramfs-framework-ima: RDEPENDS on ima-evm-keys

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
.../recipes-core/initrdscripts/initramfs-framework-ima.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-integrity/recipes-core/initrdscripts/initramfs-framewor=
k-ima.bb b/meta-integrity/recipes-core/initrdscripts/initramfs-framework-=
ima.bb
index dacdc8b..77f6f7c 100644
--- a/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima.b=
b
+++ b/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima.b=
b
@@ -27,5 +27,5 @@ do_install () {
=20
FILES_${PN} =3D "/init.d ${sysconfdir}"
=20
-RDEPENDS_${PN} =3D "keyutils ${IMA_POLICY}"
+RDEPENDS_${PN} =3D "keyutils ima-evm-keys ${IMA_POLICY}"
RDEPENDS_${PN} +=3D "initramfs-framework-base"
--=20
2.29.0


[meta-security] [PATCH V2 3/8] ima-evm-keys: add recipe

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

Create a recipe to package IMA/EMV public keys.

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
.../ima-evm-keys/ima-evm-keys_1.0.bb | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
create mode 100644 meta-integrity/recipes-security/ima-evm-keys/ima-evm-=
keys_1.0.bb

diff --git a/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.=
0.bb b/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb
new file mode 100644
index 0000000..62685bb
--- /dev/null
+++ b/meta-integrity/recipes-security/ima-evm-keys/ima-evm-keys_1.0.bb
@@ -0,0 +1,16 @@
+SUMMARY =3D "IMA/EMV public keys"
+LICENSE =3D "MIT"
+LIC_FILES_CHKSUM =3D "file://${COREBASE}/meta/COPYING.MIT;md5=3D3da9cfbc=
b788c80a0384361b4de20420"
+
+inherit features_check
+REQUIRED_DISTRO_FEATURES =3D "ima"
+
+ALLOW_EMPTY_${PN} =3D "1"
+
+do_install () {
+ if [ -e "${IMA_EVM_X509}" ]; then
+ install -d ${D}/${sysconfdir}/keys
+ install "${IMA_EVM_X509}" ${D}${sysconfdir}/keys/x509_evm.der
+ lnr ${D}${sysconfdir}/keys/x509_evm.der ${D}${sysconfdir}/keys/x=
509_ima.der
+ fi
+}
--=20
2.29.0


[meta-security] [PATCH V2 2/8] initramfs-framework-ima: fix a wrong path

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

/etc/ima-policy > /etc/ima/ima-policy.

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
.../recipes-core/initrdscripts/initramfs-framework-ima/ima | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-integrity/recipes-core/initrdscripts/initramfs-framewor=
k-ima/ima b/meta-integrity/recipes-core/initrdscripts/initramfs-framework=
-ima/ima
index 8616f99..16ed53f 100644
--- a/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima/i=
ma
+++ b/meta-integrity/recipes-core/initrdscripts/initramfs-framework-ima/i=
ma
@@ -46,7 +46,7 @@ ima_run() {
# ("[Linux-ima-user] IMA policy loading via cat") and we get better =
error reporting when
# checking the write of each line. To minimize the risk of policy lo=
ading going wrong we
# also remove comments and blank lines ourselves.
- if ! (set -e; while read i; do if echo "$i" | grep -q -e '^#' -e '^ =
*$'; then debug "Skipping IMA policy: $i"; else debug "Writing IMA policy=
: $i"; if echo $i; then sleep ${bootparam_ima_delay:-0}; else fatal "Inva=
lid line in IMA policy: $i"; exit 1; fi; fi; done) </etc/ima-policy >/sys=
/kernel/security/ima/policy; then
+ if ! (set -e; while read i; do if echo "$i" | grep -q -e '^#' -e '^ =
*$'; then debug "Skipping IMA policy: $i"; else debug "Writing IMA policy=
: $i"; if echo $i; then sleep ${bootparam_ima_delay:-0}; else fatal "Inva=
lid line in IMA policy: $i"; exit 1; fi; fi; done) </etc/ima/ima-policy >=
/sys/kernel/security/ima/policy; then
fatal "Could not load IMA policy."
fi
}
--=20
2.29.0


[meta-security] [PATCH V2 1/8] ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

'ima' does not have to be in native DISTRO_FEATURES, unset it to avoid
sanity check for ima-evm-utils-native.

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
---
.../recipes-security/ima-evm-utils/ima-evm-utils_git.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-integrity/recipes-security/ima-evm-utils/ima-evm-utils_=
git.bb b/meta-integrity/recipes-security/ima-evm-utils/ima-evm-utils_git.=
bb
index 7f649c2..bd85583 100644
--- a/meta-integrity/recipes-security/ima-evm-utils/ima-evm-utils_git.bb
+++ b/meta-integrity/recipes-security/ima-evm-utils/ima-evm-utils_git.bb
@@ -26,6 +26,7 @@ S =3D "${WORKDIR}/git"
inherit pkgconfig autotools features_check
=20
REQUIRED_DISTRO_FEATURES =3D "ima"
+REQUIRED_DISTRO_FEATURES_class-native =3D ""
=20
EXTRA_OECONF_append_class-target =3D " --with-kernel-headers=3D${STAGING=
_KERNEL_BUILDDIR}"
=20
--=20
2.29.0


[meta-security] [PATCH V2 0/8] Some fixes for IMA/EVM

Ming Liu <liu.ming50@...>
 

From: Ming Liu <liu.ming50@gmail.com>

Changes in patch set V2:

1 Split patches as suggested by Dmitry Baryshkov.

Ming Liu (8):
ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty
initramfs-framework-ima: fix a wrong path
ima-evm-keys: add recipe
initramfs-framework-ima: RDEPENDS on ima-evm-keys
meta: refactor IMA/EVM sign rootfs
README.md: update according to the refactoring in
ima-evm-rootfs.bbclass
initramfs-framework-ima: let ima_enabled return 0
ima-evm-rootfs.bbclass: avoid generating /etc/fstab for wic

meta-integrity/README.md | 4 ++-
meta-integrity/classes/ima-evm-rootfs.bbclass | 33 +++++++++----------
.../initrdscripts/initramfs-framework-ima.bb | 2 +-
.../initrdscripts/initramfs-framework-ima/ima | 3 +-
.../ima-evm-keys/ima-evm-keys_1.0.bb | 16 +++++++++
.../ima-evm-utils/ima-evm-utils_git.bb | 1 +
6 files changed, 38 insertions(+), 21 deletions(-)
create mode 100644 meta-integrity/recipes-security/ima-evm-keys/ima-evm-=
keys_1.0.bb

--=20
2.29.0


Re: [ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Randy MacLeod
 

On 2021-02-19 12:25 p.m., Richard Purdie wrote:
On Fri, 2021-02-19 at 10:18 -0500, Randy MacLeod wrote:
On 2021-02-19 1:44 a.m., Chen Qi wrote:
Hi Anibal,

The ptest-runner repo seems to be messed up.
This patch is no longer there, yet the SRCREV in ptest-runner recipe
refers to this commit.

$ git show 834670317bd3f6e427e1ac461c07ada6b8936dfd
fatal: bad object 834670317bd3f6e427e1ac461c07ada6b8936dfd

Regards,
Chen Qi
This was making our automated builds fail but I've added
the fall-back tarball and that should suffice for now.

We should probably do something to prevent that but
could someone take a look soon and perhaps restore the repo
from another location?
I talked with Anibal and its fixed now.
Thanks everyone.
../Randy

Cheers,
Richard

--
# Randy MacLeod
# Wind River Linux


Re: [ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Richard Purdie
 

On Fri, 2021-02-19 at 10:18 -0500, Randy MacLeod wrote:
On 2021-02-19 1:44 a.m., Chen Qi wrote:
Hi Anibal,

The ptest-runner repo seems to be messed up.
This patch is no longer there, yet the SRCREV in ptest-runner recipe
refers to this commit.

$ git show 834670317bd3f6e427e1ac461c07ada6b8936dfd
fatal: bad object 834670317bd3f6e427e1ac461c07ada6b8936dfd

Regards,
Chen Qi
This was making our automated builds fail but I've added
the fall-back tarball and that should suffice for now.

We should probably do something to prevent that but
could someone take a look soon and perhaps restore the repo
from another location?
I talked with Anibal and its fixed now.

Cheers,

Richard


Re: [ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Anibal Limon
 



On Fri, 19 Feb 2021 at 09:18, Randy MacLeod <randy.macleod@...> wrote:
On 2021-02-19 1:44 a.m., Chen Qi wrote:
> Hi Anibal,
>
> The ptest-runner repo seems to be messed up.
> This patch is no longer there, yet the SRCREV in ptest-runner recipe
> refers to this commit.
>
> $ git show 834670317bd3f6e427e1ac461c07ada6b8936dfd
> fatal: bad object 834670317bd3f6e427e1ac461c07ada6b8936dfd
>
> Regards,
> Chen Qi

This was making our automated builds fail but I've added
the fall-back tarball and that should suffice for now.

We should probably do something to prevent that but
could someone take a look soon and perhaps restore the repo
from another location?

My local clone has:
$ git log --oneline -3
8346703 (HEAD -> master) Fix inappropriate ioctl when detaching tty
1e9a845 (tag: v2.4)
            Add support to specify multiple folder for ptest-runner
287ba30 Makefile: Fix TEST_LDFLAGS gcc cmdline position


fyi:

$ cd .../ptest-runner2.git
$ git pull
remote: Enumerating objects: 7, done.
remote: Counting objects: 100% (7/7), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 0 (delta 0)
Unpacking objects: 100% (4/4), 526 bytes | 65.00 KiB/s, done.
 From git://git.yoctoproject.org/ptest-runner2
  + 8346703...87f6a6e master     -> origin/master  (forced update)
fatal: Not possible to fast-forward, aborting.

$ cd .../oe-core.git
$ git status
$ cd ../build
$ . ../oe-core.git/oe-init-build-env foo
$ bitbake -c fetch ptest-runner
...
WARNING: ptest-runner-2.4.0+gitAUTOINC+834670317b-r0 do_fetch: Failed to
fetch URL git://git.yoctoproject.org/ptest-runner2, attempting MIRRORS
if available

but the fetch works since it falls back to the downloads tarball:

Hi Randy,

I pushed the rev, my mistake, sorry for the trouble.

Regards,
Anibal
 


--2021-02-19 14:36:24--
http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.ptest-runner2.tar.gz
Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)...
198.145.29.63
Connecting to downloads.yoctoproject.org
(downloads.yoctoproject.org)|198.145.29.63|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 185994 (182K) [application/octet-stream]
Saving to:
‘/ala-lpggp31/rmacleod/src/distro/yocto/b/foo/downloads/git2_git.yoctoproject.org.ptest-runner2.tar.gz’

../Randy
>
> On 07/14/2020 03:29 AM, Anibal Limon wrote:
>> Applied, Thanks!.
>>
>> Anibal
>>
>> On Fri, 10 Jul 2020 at 00:44, Tero Kinnunen <tero.kinnunen@...
>> <mailto:tero.kinnunen@...>> wrote:
>>
>>     Fixes error
>>
>>         ERROR: Unable to detach from controlling tty, Inappropriate
>>     ioctl for device
>>
>>     when running multiple ptests
>>
>>         ptest-runner a b
>>
>>     or when invoked over ssh single command, like
>>
>>         $ ssh localhost ptest-runner
>>
>>     For ssh case, fd 0 is not a tty. (isatty(0) is false).
>>     When running multiple ptests, deattach for parent needs to be
>>     done only once.
>>
>>     Signed-off-by: Tero Kinnunen <tero.kinnunen@...
>>     <mailto:tero.kinnunen@...>>
>>     ---
>>      utils.c | 6 +++---
>>      1 file changed, 3 insertions(+), 3 deletions(-)
>>
>>     diff --git a/utils.c b/utils.c
>>     index a8ba190..a4e190e 100644
>>     --- a/utils.c
>>     +++ b/utils.c
>>     @@ -437,6 +437,9 @@ run_ptests(struct ptest_list *head, const
>>     struct ptest_options opts,
>>                             break;
>>                     }
>>                     fprintf(fp, "START: %s\n", progname);
>>     +               if (isatty(0) && ioctl(0, TIOCNOTTY) == -1) {
>>     +                       fprintf(fp, "ERROR: Unable to detach from
>>     controlling tty, %s\n", strerror(errno));
>>     +               }
>>                     PTEST_LIST_ITERATE_START(head, p)
>>                             char *ptest_dir = strdup(p->run_ptest);
>>                             if (ptest_dir == NULL) {
>>     @@ -444,9 +447,6 @@ run_ptests(struct ptest_list *head, const
>>     struct ptest_options opts,
>>                                     break;
>>                             }
>>                             dirname(ptest_dir);
>>     -                       if (ioctl(0, TIOCNOTTY) == -1) {
>>     -                               fprintf(fp, "ERROR: Unable to
>>     detach from controlling tty, %s\n", strerror(errno));
>>     -                       }
>>
>>                             if ((pgid = getpgid(0)) == -1) {
>>                                     fprintf(fp, "ERROR: getpgid()
>>     failed, %s\n", strerror(errno));
>>     --
>>     2.25.1
>>
>>
>>
>
>
>
>
>


--
# Randy MacLeod
# Wind River Linux


Re: Run aarch64 binaries using bitbake recipe

Khem Raj
 

use MACHINE="qemuarm64" or some such machine which is based on arm64

On Fri, Feb 19, 2021 at 2:54 AM William Jacob via
lists.yoctoproject.org
<william.jacob=sama.com.sg@lists.yoctoproject.org> wrote:


Hi, I have a yocto build system which currently cross compiles for armv7 (32bit) .

I have a requirement of building 64 bit software .How do I modify my yocto build such that I am able to run create binaries aarch64



Thanks

William




Re: [ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Randy MacLeod
 

On 2021-02-19 1:44 a.m., Chen Qi wrote:
Hi Anibal,
The ptest-runner repo seems to be messed up.
This patch is no longer there, yet the SRCREV in ptest-runner recipe refers to this commit.
$ git show 834670317bd3f6e427e1ac461c07ada6b8936dfd
fatal: bad object 834670317bd3f6e427e1ac461c07ada6b8936dfd
Regards,
Chen Qi
This was making our automated builds fail but I've added
the fall-back tarball and that should suffice for now.

We should probably do something to prevent that but
could someone take a look soon and perhaps restore the repo
from another location?

My local clone has:
$ git log --oneline -3
8346703 (HEAD -> master) Fix inappropriate ioctl when detaching tty
1e9a845 (tag: v2.4)
Add support to specify multiple folder for ptest-runner
287ba30 Makefile: Fix TEST_LDFLAGS gcc cmdline position


fyi:

$ cd .../ptest-runner2.git
$ git pull
remote: Enumerating objects: 7, done.
remote: Counting objects: 100% (7/7), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 0 (delta 0)
Unpacking objects: 100% (4/4), 526 bytes | 65.00 KiB/s, done.
From git://git.yoctoproject.org/ptest-runner2
+ 8346703...87f6a6e master -> origin/master (forced update)
fatal: Not possible to fast-forward, aborting.

$ cd .../oe-core.git
$ git status
$ cd ../build
$ . ../oe-core.git/oe-init-build-env foo
$ bitbake -c fetch ptest-runner
...
WARNING: ptest-runner-2.4.0+gitAUTOINC+834670317b-r0 do_fetch: Failed to fetch URL git://git.yoctoproject.org/ptest-runner2, attempting MIRRORS if available

but the fetch works since it falls back to the downloads tarball:


--2021-02-19 14:36:24--
http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.ptest-runner2.tar.gz
Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.29.63
Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 185994 (182K) [application/octet-stream]
Saving to: ‘/ala-lpggp31/rmacleod/src/distro/yocto/b/foo/downloads/git2_git.yoctoproject.org.ptest-runner2.tar.gz’

../Randy
On 07/14/2020 03:29 AM, Anibal Limon wrote:
Applied, Thanks!.

Anibal

On Fri, 10 Jul 2020 at 00:44, Tero Kinnunen <tero.kinnunen@vaisala.com <mailto:tero.kinnunen@vaisala.com>> wrote:

Fixes error

    ERROR: Unable to detach from controlling tty, Inappropriate
ioctl for device

when running multiple ptests

    ptest-runner a b

or when invoked over ssh single command, like

    $ ssh localhost ptest-runner

For ssh case, fd 0 is not a tty. (isatty(0) is false).
When running multiple ptests, deattach for parent needs to be
done only once.

Signed-off-by: Tero Kinnunen <tero.kinnunen@vaisala.com
<mailto:tero.kinnunen@vaisala.com>>
---
 utils.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/utils.c b/utils.c
index a8ba190..a4e190e 100644
--- a/utils.c
+++ b/utils.c
@@ -437,6 +437,9 @@ run_ptests(struct ptest_list *head, const
struct ptest_options opts,
                        break;
                }
                fprintf(fp, "START: %s\n", progname);
+               if (isatty(0) && ioctl(0, TIOCNOTTY) == -1) {
+                       fprintf(fp, "ERROR: Unable to detach from
controlling tty, %s\n", strerror(errno));
+               }
                PTEST_LIST_ITERATE_START(head, p)
                        char *ptest_dir = strdup(p->run_ptest);
                        if (ptest_dir == NULL) {
@@ -444,9 +447,6 @@ run_ptests(struct ptest_list *head, const
struct ptest_options opts,
                                break;
                        }
                        dirname(ptest_dir);
-                       if (ioctl(0, TIOCNOTTY) == -1) {
-                               fprintf(fp, "ERROR: Unable to
detach from controlling tty, %s\n", strerror(errno));
-                       }

                        if ((pgid = getpgid(0)) == -1) {
                                fprintf(fp, "ERROR: getpgid()
failed, %s\n", strerror(errno));
--
2.25.1



--
# Randy MacLeod
# Wind River Linux


Run aarch64 binaries using bitbake recipe

William Jacob
 

Hi, I have a yocto build system which currently cross compiles for armv7 (32bit) .

I have a requirement of building 64 bit software .How do I modify my yocto build such that I am able to run create binaries aarch64

 

Thanks

William


Re: [ptest-runner][PATCH v2] Fix inappropriate ioctl when detaching tty

Chen Qi
 

Hi Anibal,

The ptest-runner repo seems to be messed up.
This patch is no longer there, yet the SRCREV in ptest-runner recipe refers to this commit.

$ git show 834670317bd3f6e427e1ac461c07ada6b8936dfd
fatal: bad object 834670317bd3f6e427e1ac461c07ada6b8936dfd

Regards,
Chen Qi

On 07/14/2020 03:29 AM, Anibal Limon wrote:
Applied, Thanks!.

Anibal

On Fri, 10 Jul 2020 at 00:44, Tero Kinnunen <tero.kinnunen@...> wrote:
Fixes error

    ERROR: Unable to detach from controlling tty, Inappropriate ioctl for device

when running multiple ptests

    ptest-runner a b

or when invoked over ssh single command, like

    $ ssh localhost ptest-runner

For ssh case, fd 0 is not a tty. (isatty(0) is false).
When running multiple ptests, deattach for parent needs to be
done only once.

Signed-off-by: Tero Kinnunen <tero.kinnunen@...>
---
 utils.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/utils.c b/utils.c
index a8ba190..a4e190e 100644
--- a/utils.c
+++ b/utils.c
@@ -437,6 +437,9 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
                        break;
                }
                fprintf(fp, "START: %s\n", progname);
+               if (isatty(0) && ioctl(0, TIOCNOTTY) == -1) {
+                       fprintf(fp, "ERROR: Unable to detach from controlling tty, %s\n", strerror(errno));
+               }
                PTEST_LIST_ITERATE_START(head, p)
                        char *ptest_dir = strdup(p->run_ptest);
                        if (ptest_dir == NULL) {
@@ -444,9 +447,6 @@ run_ptests(struct ptest_list *head, const struct ptest_options opts,
                                break;
                        }
                        dirname(ptest_dir);
-                       if (ioctl(0, TIOCNOTTY) == -1) {
-                               fprintf(fp, "ERROR: Unable to detach from controlling tty, %s\n", strerror(errno));
-                       }

                        if ((pgid = getpgid(0)) == -1) {
                                fprintf(fp, "ERROR: getpgid() failed, %s\n", strerror(errno));
--
2.25.1




    



Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

safouane maaloul
 

Yeah it works. I have yet to test the image on my raspberry pi Monday in the office. But I finished the build.  I will tested Monday and i will tell you. I have a warning : 
image-1.0-r0 do_rootfs: The license listed AOM-Patent-1.0 was not in the licenses collected for recipe aom 

I think because the name of the license in meta-openembedded/meta-multimedia/licenses/ is AOM-Patent-License-1.0 and not AOM-Patent-1.0 like mentioned in the recipe. I think it must be changed. Thanks I will tell you Monday what happened when I try the image on my raspberry Pi zero W.

Best regards,

Safouane

Le ven. 19 févr. 2021 à 00:00, Khem Raj <raj.khem@...> a écrit :
Please try applying below patch to aom recipe in meta-openembedded repo

https://lists.openembedded.org/g/openembedded-devel/topic/meta_multimedia_patch_aom/80743335?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80743335

let me know how it goes.

On Thu, Feb 18, 2021 at 12:22 PM safouane maaloul
<maaloulsafouane@...> wrote:
>
> Sorry to annoying you with my question but how do i find where HAVE_NEON is set ?
>
> Best regards,
>
> Safouane
>
> Le jeu. 18 févr. 2021 à 21:16, Khem Raj <raj.khem@...> a écrit :
>>
>> Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly
>>
>> On Thu, Feb 18, 2021 at 12:12 PM safouane maaloul <maaloulsafouane@...> wrote:
>>>
>>> I have an erreur:
>>> | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
>>> |   525 |   const int32x4_t v0 = vld1q_s32(buf);
>>> |       |                        ^~~~~~~~~~~~~~
>>> | ninja: build stopped: subcommand failed.
>>> | WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
>>> | WARNING: Backtrace (BB generated script):
>>> |       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
>>> |       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
>>> |       #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
>>> |       #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
>>> |
>>> | Backtrace (metadata-relative locations):
>>> |       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
>>> |       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
>>> |       #3: do_compile, autogenerated, line 2
>>> ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.
>>>
>>> Summary: 1 task failed:
>>>   /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
>>> Summary: There was 1 WARNING message shown.
>>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>>
>>> Do you have any idea why it didn't work ?
>>>
>>> Best regards,
>>>
>>> Safouane
>>>
>>> Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@...> a écrit :
>>>>
>>>> can you try adding
>>>>
>>>> EXTRA_OECMAKE += "-DHAVE_NEON=0"
>>>>
>>>> and see if that helps ? for whatever reason set_aom_detect_var is
>>>> enabling it where as default should be 0
>>>>
>>>> On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
>>>> <maaloulsafouane@...> wrote:
>>>> >
>>>> > I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this     TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
>>>> > | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
>>>> > |   528 |   const int16x4_t s1 = vmovn_s32(v1);
>>>> > |       |                        ^~~~~~~~~~~~~
>>>> > | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
>>>> > | /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
>>>> > |  7556 | vmovn_s32 (int32x4_t __a)
>>>> > |       | ^~~~~~~~~
>>>> >
>>>> > So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.
>>>> >
>>>> > Best regards,
>>>> >
>>>> > Safouane
>>>> >
>>>> > Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>>> >>
>>>> >> https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm
>>>> >>
>>>> >> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
>>>> >> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES
>>>> >>
>>>> >> Zee
>>>> >> _______
>>>> >>
>>>> >> On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
>>>> >> <maaloulsafouane@...> wrote:
>>>> >> >
>>>> >> > Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?
>>>> >> >
>>>> >> > Best regards,
>>>> >> >
>>>> >> > Safouane
>>>> >> >
>>>> >> > Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>>> >> >>
>>>> >> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>>>> >> >>
>>>> >> >> Here is an interesting reading for you, for me also:
>>>> >> >> https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html
>>>> >> >>
>>>> >> >> What I am getting from this reading is that you need to try with the
>>>> >> >> following line:
>>>> >> >> TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs"
>>>> >> >>
>>>> >> >> I guess, YOCTO people have not too much experience with armv6, nor me,
>>>> >> >> but this should be (I hope) generic.
>>>> >> >>
>>>> >> >> Hope this helps.
>>>> >> >> Zoran
>>>> >> >> _______
>>>> >> >>
>>>> >> >> On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
>>>> >> >> <maaloulsafouane@...> wrote:
>>>> >> >> >
>>>> >> >> > This is my build configuration :
>>>> >> >> > Build Configuration:
>>>> >> >> > BB_VERSION           = "1.46.0"
>>>> >> >> > BUILD_SYS            = "x86_64-linux"
>>>> >> >> > NATIVELSBSTRING      = "universal"
>>>> >> >> > TARGET_SYS           = "arm-poky-linux-gnueabi"
>>>> >> >> > MACHINE              = "raspberrypi0-wifi"
>>>> >> >> > DISTRO               = "poky"
>>>> >> >> > DISTRO_VERSION       = "3.1.5"
>>>> >> >> > TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
>>>> >> >> > TARGET_FPU           = "hard"
>>>> >> >> > meta
>>>> >> >> > meta-poky
>>>> >> >> > meta-yocto-bsp       = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
>>>> >> >> > meta-oe
>>>> >> >> > meta-multimedia
>>>> >> >> > meta-networking
>>>> >> >> > meta-python          = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
>>>> >> >> > meta-raspberrypi     = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
>>>> >> >> > meta-gstreamer1.0    = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"
>>>> >> >> >
>>>> >> >> > Best regards,
>>>> >> >> >
>>>> >> >> > Safouane
>>>> >> >> >
>>>> >> >> > Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@...> a écrit :
>>>> >> >> >>
>>>> >> >> >> So, what is your MACHINE variable set to?
>>>> >> >> >>
>>>> >> >> >> Maybe knowing that, somebody can help.
>>>> >> >> >>
>>>> >> >> >> Zee
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > --
>>>> >> >> > SAFOUANE MAALOUL
>>>> >> >> > maaloulsafouane@...
>>>> >> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > --
>>>> >> > SAFOUANE MAALOUL
>>>> >> > maaloulsafouane@...
>>>> >> >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > SAFOUANE MAALOUL
>>>> > maaloulsafouane@...
>>>> >
>>>> >
>>>> >
>>>> >
>>>
>>>
>>>
>>> --
>>> SAFOUANE MAALOUL
>>> maaloulsafouane@...
>>>
> --
> SAFOUANE MAALOUL
> maaloulsafouane@...
>


--
SAFOUANE MAALOUL


[meta-gplv2] [PATCH] disable-gplv3.inc: Update pattern match to what we really mean

Richard Purdie
 

This code wants to disable GPLv3 and GPLv3+ however the pattern
didnt specify that and with recent changes in OE-Core, it needs
to be specific. Update the pattern to be specific.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
conf/distro/include/disable-gplv3.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include/disable-gplv3.inc
index 761be7d..bded378 100644
--- a/conf/distro/include/disable-gplv3.inc
+++ b/conf/distro/include/disable-gplv3.inc
@@ -1,3 +1,3 @@
-INCOMPATIBLE_LICENSE = '*GPLv3'
+INCOMPATIBLE_LICENSE = '*GPLv3*'
WARN_QA_remove = 'incompatible-license'
RDEPENDS_${PN}-ptest_remove_pn-glib-2.0 = "python3-dbusmock"
--
2.27.0


Re: #av1 #armv6 #raspberrypi #neon #av1 #armv6 #raspberrypi #neon

Khem Raj
 

Please try applying below patch to aom recipe in meta-openembedded repo

https://lists.openembedded.org/g/openembedded-devel/topic/meta_multimedia_patch_aom/80743335?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,80743335

let me know how it goes.

On Thu, Feb 18, 2021 at 12:22 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

Sorry to annoying you with my question but how do i find where HAVE_NEON is set ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 21:16, Khem Raj <raj.khem@gmail.com> a écrit :

Well we do not enable neon for this tune but aom still seems to want it so I would suggest to look at the build and see if it’s disabling neon and have HAVE_NEON is not set properly

On Thu, Feb 18, 2021 at 12:12 PM safouane maaloul <maaloulsafouane@gmail.com> wrote:

I have an erreur:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
| 525 | const int32x4_t v0 = vld1q_s32(buf);
| | ^~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
| WARNING: Backtrace (BB generated script):
| #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 155
| #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 149
| #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 144
| #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.24037, line 168
|
| Backtrace (metadata-relative locations):
| #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
| #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
| #3: do_compile, autogenerated, line 2
ERROR: Task (/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3538 tasks of which 3326 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../meta-openembedded/meta-multimedia/recipes-multimedia/aom/aom_2.0.0.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Do you have any idea why it didn't work ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 20:54, Khem Raj <raj.khem@gmail.com> a écrit :

can you try adding

EXTRA_OECMAKE += "-DHAVE_NEON=0"

and see if that helps ? for whatever reason set_aom_detect_var is
enabling it where as default should be 0

On Thu, Feb 18, 2021 at 10:42 AM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

I succed in removing callconvention-hard from TUNE_FEATURES ? But i have the same problem. I am pretty sure that i get get it working if i add neon to the TUNE_FEATURES. Something like this TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard neon". But I can't do it with armv6. I have to use raspberrypi zero w so i have to make it work with armv6. I know that i can make it work with armv7 and armv8. I have error like this : | In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:528:24: note: called from here
| 528 | const int16x4_t s1 = vmovn_s32(v1);
| | ^~~~~~~~~~~~~
| In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:7556:1: error: inlining failed in call to 'always_inline' 'vmovn_s32': target specific option mismatch
| 7556 | vmovn_s32 (int32x4_t __a)
| | ^~~~~~~~~

So i am sure i have to add the neon feature so i appreciate it if someone can help me. I didn't find a workaround this problem on the internet.

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 18:00, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

https://yocto.yoctoproject.narkive.com/Wle40I09/gcc-on-arm

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-TUNE_FEATURES
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-AVAILTUNES

Zee
_______

On Thu, Feb 18, 2021 at 3:28 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

Yes I will check it. Do you know how to remove callconvention-hard from TUNE_FEATURES ?

Best regards,

Safouane

Le jeu. 18 févr. 2021 à 14:52, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
Here is an interesting reading for you, for me also:
https://www.yoctoproject.org/pipermail/meta-xilinx/2015-July/001060.html

What I am getting from this reading is that you need to try with the
following line:
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs"

I guess, YOCTO people have not too much experience with armv6, nor me,
but this should be (I hope) generic.

Hope this helps.
Zoran
_______

On Thu, Feb 18, 2021 at 12:44 PM safouane maaloul
<maaloulsafouane@gmail.com> wrote:

This is my build configuration :
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi0-wifi"
DISTRO = "poky"
DISTRO_VERSION = "3.1.5"
TUNE_FEATURES = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "dunfell:7ea41de13774675828239b7738d3f5d70be8b1af"
meta-oe
meta-multimedia
meta-networking
meta-python = "dunfell:5bba79488b7d393d2258d6e917f7bf7b0d7c4073"
meta-raspberrypi = "dunfell:987993209716302eb8f314f69a2a3340555f94d8"
meta-gstreamer1.0 = "dunfell:b489b1ba084544d9c4c08f7c3b3d1c37ffa53c51"

Best regards,

Safouane

Le mer. 17 févr. 2021 à 13:24, Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com> a écrit :

So, what is your MACHINE variable set to?

Maybe knowing that, somebody can help.

Zee


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com


--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com





--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com
--
SAFOUANE MAALOUL
maaloulsafouane@gmail.com

1501 - 1520 of 53882