From: "Kory Maincent" <kory.maincent@bootlin.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v4] ltp: add support for tirpc and fix build issue
Date: Sat, 19 Dec 2020 12:08:00 +0100 [thread overview]
Message-ID: <20201219110800.5207-1-kory.maincent@bootlin.com> (raw)
Add support to tirpc tests build.
The export of ${prefix} updates all other paths variable and
in particular PKG_CONFIG_PATH. This variable beeing updated it could
not find the pkgconfig file for tirpc.
Use immediate expansion to avoid ${prefix} export overflows on
PKG_CONFIG_PATH.
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Change since v1:
- Use PACKAGECONFIG to enable rpc tests
- Improve ${libdir} and ${incdir} export
Change since v2:
- Improve ${libdir} and ${incdir} export
Change since v3:
- Use PKG_CONFIG_PATH in place of the ${libdir} ${incdir} variable export
meta/recipes-extended/ltp/ltp_20200930.bb | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-extended/ltp/ltp_20200930.bb b/meta/recipes-extended/ltp/ltp_20200930.bb
index 7acf15b360..1a9c05a7e4 100644
--- a/meta/recipes-extended/ltp/ltp_20200930.bb
+++ b/meta/recipes-extended/ltp/ltp_20200930.bb
@@ -42,14 +42,13 @@ inherit autotools-brokensep pkgconfig
TARGET_CC_ARCH += "${LDFLAGS}"
+PKG_CONFIG_PATH := "${PKG_CONFIG_PATH}"
export prefix = "/opt/${PN}"
-export exec_prefix = "/opt/${PN}"
PACKAGECONFIG[numa] = "--with-numa, --without-numa, numactl,"
+PACKAGECONFIG[rpc] = "--with-tirpc, --without-tirpc, virtual/librpc,"
EXTRA_AUTORECONF += "-I ${S}/testcases/realtime/m4"
EXTRA_OECONF = " --with-realtime-testsuite --with-open-posix-testsuite "
-# ltp network/rpc test cases ftbfs when libtirpc is found
-EXTRA_OECONF += " --without-tirpc "
do_install(){
install -d ${D}${prefix}/
--
2.17.1
next reply other threads:[~2020-12-19 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 11:08 Kory Maincent [this message]
2020-12-19 15:42 ` [OE-core] [PATCH v4] ltp: add support for tirpc and fix build issue 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=20201219110800.5207-1-kory.maincent@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox