From: Darcy L. Watkins <dwatkins@tranzeo.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.02 "echo foo"
Date: Fri, 26 Feb 2010 13:35:20 -0800 [thread overview]
Message-ID: <1267220120.28886.99.camel@localhost.localdomain> (raw)
In-Reply-To: <D61182AC8012EA4EBC531B3AF23BE10992A96A@tranzeo-mail2.12stewart.tranzeo.com>
I think this should fix it ....
--- buildroot-2010.02_arm/package/dosfstools/dosfstools.mk.theorig 2010-02-26 06:52:48.000000000 -0800
+++ buildroot-2010.02_arm/package/dosfstools/dosfstools.mk 2010-02-26 11:12:54.000000000 -0800
@@ -32,8 +32,7 @@ $(DOSFSTOOLS_DIR)/.built : $(DOSFSTOOLS_
$(STRIPCMD) $(DOSFSTOOLS_DIR)/$(DOSFSLABEL_BINARY)
touch $@
-$(TARGET_DIR)/$(MKDOSFS_TARGET_BINARY): # $(DOSFSTOOLS_DIR)/.built
- echo foo
+$(TARGET_DIR)/$(MKDOSFS_TARGET_BINARY): $(DOSFSTOOLS_DIR)/.built
cp -a $(DOSFSTOOLS_DIR)/$(MKDOSFS_BINARY) $@
touch -c $@
... and don't revert any of the other changes.
On Fri, 2010-02-26 at 11:11 -0800, Darcy Watkins wrote:
> I see ?echo foo? in output of make just before it breaks because it
> wants to copy mkdosfs from dosfstools before having built the package.
>
> I see the ?echo foo? and make dependency commented out in recent patch
> and commit wrt dosfstools package (in dosfstools.mk).
>
>
>
> Was this debug intended to be removed before the release?
next prev parent reply other threads:[~2010-02-26 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 19:11 [Buildroot] Buildroot 2010.02 "echo foo" Darcy Watkins
2010-02-26 21:35 ` Darcy L. Watkins [this message]
2010-03-01 19:54 ` [Buildroot] Patch to allow iproute2 without IPv6 requirement Darcy L. Watkins
2010-03-06 21:51 ` Peter Korsgaard
2010-03-08 14:49 ` Darcy Watkins
2010-03-08 19:29 ` Peter Korsgaard
2010-03-06 23:19 ` [Buildroot] Buildroot 2010.02 "echo foo" Peter Korsgaard
2010-02-26 22:53 ` 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=1267220120.28886.99.camel@localhost.localdomain \
--to=dwatkins@tranzeo.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.