Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] svgtiny: create BUILDDIR before $(BUILDDIR)/src_colors.c
Date: Wed, 18 Jun 2014 10:57:12 +0400	[thread overview]
Message-ID: <1403074632-28224-1-git-send-email-jcmvbkbc@gmail.com> (raw)

Fixes:
  http://autobuild.buildroot.net/results/5fe/5feca450d70a8de48fa2463e55c9e84db5d755b0/

Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
 .../libsvgtiny-100-create-builddir.patch           |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)
 create mode 100644 package/libsvgtiny/libsvgtiny-100-create-builddir.patch

diff --git a/package/libsvgtiny/libsvgtiny-100-create-builddir.patch b/package/libsvgtiny/libsvgtiny-100-create-builddir.patch
new file mode 100644
index 0000000..a404d86
--- /dev/null
+++ b/package/libsvgtiny/libsvgtiny-100-create-builddir.patch
@@ -0,0 +1,15 @@
+svgtiny: create BUILDDIR before $(BUILDDIR)/src_colors.c
+
+Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
+---
+--- libsvgtiny-12121/src/Makefile.orig	2014-06-17 15:30:21.765311434 +0400
++++ libsvgtiny-12121/src/Makefile	2014-06-17 15:29:56.569909931 +0400
+@@ -3,7 +3,7 @@
+ 
+ SOURCES := $(SOURCES) $(BUILDDIR)/src_colors.c
+ 
+-$(BUILDDIR)/src_colors.c: src/colors.gperf
++$(BUILDDIR)/src_colors.c: src/colors.gperf $(BUILDDIR)/stamp
+ 	$(VQ)$(ECHO) "   GPERF: $<"
+ 	$(Q)gperf --output-file=$@.tmp $<
+ # Hack for GCC 4.2 compatibility (gperf 3.0.4 solves this properly)
-- 
1.7.7.6

             reply	other threads:[~2014-06-18  6:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  6:57 Max Filippov [this message]
2014-06-18 11:52 ` [Buildroot] [PATCH] svgtiny: create BUILDDIR before $(BUILDDIR)/src_colors.c Peter Korsgaard

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=1403074632-28224-1-git-send-email-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox