All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ross Burton" <ross@burtonini.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH] arm/optee-test: don't attempt to build with musl
Date: Mon,  2 Nov 2020 16:09:55 +0000	[thread overview]
Message-ID: <20201102160955.2845447-1-ross.burton@arm.com> (raw)

optee-test doesn't build on musl (or bionic) because libstdc++.a under musl
depends on libc providing the pthread functions, but TAs are built without
a libc.

Until this is fixed upstream (see https://github.com/OP-TEE/optee_test/issues/458)
simply refuse to build optee-test with musl.

Change-Id: If73fd43683e19e2943bf54f4027806786fb1dc7d
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 meta-arm/recipes-security/optee/optee-test.inc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta-arm/recipes-security/optee/optee-test.inc b/meta-arm/recipes-security/optee/optee-test.inc
index 467e687..eb11a12 100644
--- a/meta-arm/recipes-security/optee/optee-test.inc
+++ b/meta-arm/recipes-security/optee/optee-test.inc
@@ -8,6 +8,10 @@ LIC_FILES_CHKSUM = "file://${S}/LICENSE.md;md5=daa2bcccc666345ab8940aab1315a4fa"
 inherit python3native
 require optee.inc
 
+# Linking fails on musl due to C++/threads
+# https://github.com/OP-TEE/optee_test/issues/458#issuecomment-720540834
+COMPATIBLE_HOST_libc-musl = 'null'
+
 DEPENDS = "optee-client optee-os python3-pycryptodomex-native"
 
 SRC_URI = "git://github.com/OP-TEE/optee_test.git \
-- 
2.25.1


             reply	other threads:[~2020-11-02 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 16:09 Ross Burton [this message]
2020-11-03  2:12 ` [meta-arm] [PATCH] arm/optee-test: don't attempt to build with musl Jon Mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201102160955.2845447-1-ross.burton@arm.com \
    --to=ross@burtonini.com \
    --cc=meta-arm@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.