From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH] redis: Fix ocasional parallel build failure
Date: Sat, 6 Apr 2019 17:06:33 -0700 [thread overview]
Message-ID: <20190407000633.38920-1-raj.khem@gmail.com> (raw)
Sometimes with high parallel build we see compile errors e.g.
clang-8: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [Makefile:52: lua] Error 1
Therefore try to build dependencies before main build
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta-oe/recipes-extended/redis/redis_4.0.12.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta-oe/recipes-extended/redis/redis_4.0.12.bb b/meta-oe/recipes-extended/redis/redis_4.0.12.bb
index af99537f52..2e54f665d2 100644
--- a/meta-oe/recipes-extended/redis/redis_4.0.12.bb
+++ b/meta-oe/recipes-extended/redis/redis_4.0.12.bb
@@ -31,6 +31,10 @@ GROUPADD_PARAM_${PN} = "--system redis"
REDIS_ON_SYSTEMD = "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', d)}"
+do_compiler_prepend() {
+ (cd deps && oe_runmake hiredis lua jemalloc linenoise)
+}
+
do_install() {
export PREFIX=${D}/${prefix}
oe_runmake install
--
2.21.0
reply other threads:[~2019-04-07 0:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190407000633.38920-1-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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