Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wade Berrier <wberrier@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tar: avoid ccache chicken and egg problem when bootstrapping tar
Date: Wed, 3 Jul 2013 14:57:35 -0600	[thread overview]
Message-ID: <20130703205733.GA11235@berrier.lan> (raw)

Signed-off-by: Wade Berrier <wberrier@gmail.com>
---
 package/tar/tar.mk |    5 +++++
 1 file changed, 5 insertions(+)

diff --git a/package/tar/tar.mk b/package/tar/tar.mk
index 3ffeaf0..56443a8 100644
--- a/package/tar/tar.mk
+++ b/package/tar/tar.mk
@@ -20,6 +20,11 @@ $(eval $(autotools-package))
 # host-tar: use cpio.gz instead of tar.gz to prevent chicken-egg problem
 # of needing tar to build tar.
 HOST_TAR_SOURCE = tar-$(TAR_VERSION).cpio.gz
+
+# ccache isn't available yet when building for the host
+HOST_TAR_CONF_ENV = \
+	CC="$(HOSTCC_NOCCACHE)"
+
 define HOST_TAR_EXTRACT_CMDS
 	mkdir -p $(@D)
 	cd $(@D) && \
-- 
1.7.9.5

             reply	other threads:[~2013-07-03 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 20:57 Wade Berrier [this message]
2013-08-10 19:32 ` [Buildroot] [PATCH] tar: avoid ccache chicken and egg problem when bootstrapping tar Thomas Petazzoni

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=20130703205733.GA11235@berrier.lan \
    --to=wberrier@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