From: pgowda <pgowda.cve@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: rwmacleod@gmail.com, pgowda <pgowda.cve@gmail.com>
Subject: [PATCH] glibc: ptest: Add lib32-glibc-tests PROVIDES
Date: Mon, 2 May 2022 01:08:51 -0700 [thread overview]
Message-ID: <20220502080851.40753-1-pgowda.cve@gmail.com> (raw)
While running lib32-glibc-tests, it fails with the following error
as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests
and is not able to recognize the multilibs.
ERROR: Nothing PROVIDES 'lib32-glibc-tests'
Signed-off-by: pgowda <pgowda.cve@gmail.com>
---
meta/recipes-core/glibc/glibc-tests_2.35.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/glibc/glibc-tests_2.35.bb b/meta/recipes-core/glibc/glibc-tests_2.35.bb
index 414f8660de..2515e98bb3 100644
--- a/meta/recipes-core/glibc/glibc-tests_2.35.bb
+++ b/meta/recipes-core/glibc/glibc-tests_2.35.bb
@@ -18,7 +18,7 @@ python __anonymous() {
d.setVar("PROVIDES", "${PN} ${PN}-ptest")
d.setVar("RPROVIDES", "${PN} ${PN}-ptest")
- d.setVar("BBCLASSEXTEND", "")
+# d.setVar("BBCLASSEXTEND", "")
d.setVar("RRECOMMENDS", "")
d.setVar("SYSTEMD_SERVICE:nscd", "")
d.setVar("SYSTEMD_PACKAGES", "")
--
2.35.1
next reply other threads:[~2022-05-02 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 8:08 pgowda [this message]
2022-05-02 9:13 ` [OE-core] [PATCH] glibc: ptest: Add lib32-glibc-tests PROVIDES Jose Quaresma
2022-05-02 20:30 ` Luca Ceresoli
2022-05-05 10:25 ` pgowda cve
2022-05-13 12:28 ` pgowda cve
2022-05-13 12:45 ` richard.purdie
2022-05-13 12:56 ` pgowda cve
2022-05-13 13:06 ` Randy MacLeod
2022-05-13 13:11 ` richard.purdie
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=20220502080851.40753-1-pgowda.cve@gmail.com \
--to=pgowda.cve@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rwmacleod@gmail.com \
/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.