From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/2019.08.x] package/libsvgtiny: disable parallel build
Date: Mon, 18 Nov 2019 13:54:06 +0100 [thread overview]
Message-ID: <20191118124638.2425C8F16D@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=cb232691210b92a0c1081f73a8952c065787b7ea
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/2019.08.x
Build can sometimes fails on:
src/svgtiny.c:21:10: fatal error: autogenerated_colors.c: No such file or directory
#include "autogenerated_colors.c"
^~~~~~~~~~~~~~~~~~~~~~~~
because svgtiny.c does not properly depends on autogenerated_colors.c
that is built by gperf. So, just disable parallel build instead of
trying to fix this issue especially because libsvgtiny uses the netsurf
buildsystem
Fixes:
- http://autobuild.buildroot.org/results/48e7a7f7c72634d59cca817778d31661bfe8e72f
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
(cherry picked from commit 26d67a2599d6c88facd5178de853fa355244e7c2)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
package/libsvgtiny/libsvgtiny.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/libsvgtiny/libsvgtiny.mk b/package/libsvgtiny/libsvgtiny.mk
index febd3fcec8..fe7dc0a6d2 100644
--- a/package/libsvgtiny/libsvgtiny.mk
+++ b/package/libsvgtiny/libsvgtiny.mk
@@ -12,6 +12,8 @@ LIBSVGTINY_DEPENDENCIES = \
libxml2 host-gperf host-pkgconf host-netsurf-buildsystem
LIBSVGTINY_LICENSE = MIT
LIBSVGTINY_LICENSE_FILES = README
+# Package does not build in parallel due to improper make rules
+LIBSVGTINY_MAKE = $(MAKE1)
# The libsvgtiny build system cannot build both the shared and static
# libraries. So when the Buildroot configuration requests to build
reply other threads:[~2019-11-18 12:54 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=20191118124638.2425C8F16D@busybox.osuosl.org \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.