From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target
Date: Wed, 6 Jun 2007 12:59:02 -0700 (PDT) [thread overview]
Message-ID: <20070606195902.B57F148580@busybox.net> (raw)
Author: aldot
Date: 2007-06-06 12:59:01 -0700 (Wed, 06 Jun 2007)
New Revision: 18762
Log:
- fix typo which led to a superfluous cp invocation
Modified:
trunk/buildroot/target/linux26.mk
Changeset:
Modified: trunk/buildroot/target/linux26.mk
===================================================================
--- trunk/buildroot/target/linux26.mk 2007-06-06 19:50:05 UTC (rev 18761)
+++ trunk/buildroot/target/linux26.mk 2007-06-06 19:59:01 UTC (rev 18762)
@@ -103,7 +103,7 @@
cp -dpf $(LINUX26_DIR)/$(LINUX26_BINLOC) $(LINUX26_KERNEL)
touch -c $@
-$(TARGET_DIR)/boot/$(LINUX26_BINLOC): $(LINUX26_KERNEL)
+$(TARGET_DIR)/boot/$(LINUX26_FORMAT): $(LINUX26_KERNEL)
[ -d $(TARGET_DIR)/boot/ ] || mkdir $(TARGET_DIR)/boot
cp -a $(LINUX26_DIR)/$(LINUX26_BINLOC) $(LINUX26_DIR)/System.map $(TARGET_DIR)/boot/
touch -c $@
@@ -122,7 +122,7 @@
$(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) menuconfig
-[ -f $(LINUX26_DIR)/.config ] && touch $(LINUX26_DIR)/.configured
-linux26: cross-depmod26 $(TARGET_DIR)/lib/modules/$(LINUX26_VERSION)/modules.dep $(TARGET_DIR)/boot/$(LINUX26_BINLOC)
+linux26: cross-depmod26 $(TARGET_DIR)/lib/modules/$(LINUX26_VERSION)/modules.dep $(TARGET_DIR)/boot/$(LINUX26_FORMAT)
linux26-source: $(DL_DIR)/$(LINUX26_SOURCE)
next reply other threads:[~2007-06-06 19:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 19:59 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-30 11:35 [Buildroot] svn commit: trunk/buildroot/target jacmet at uclibc.org
2009-01-13 15:14 jacmet at uclibc.org
2009-01-12 20:58 jacmet at uclibc.org
2009-01-01 17:48 nkukard at uclibc.org
2008-12-17 9:28 ulf at uclibc.org
2008-11-04 19:58 jacmet at uclibc.org
2008-05-12 12:43 jacmet at uclibc.org
2008-04-04 7:24 jacmet at uclibc.org
2008-03-11 19:28 ninevoltz at uclibc.org
2008-03-11 8:49 jacmet at uclibc.org
2008-03-06 19:00 ninevoltz at uclibc.org
2007-10-05 11:03 aldot at uclibc.org
2007-09-30 12:42 aldot at uclibc.org
2007-09-29 19:47 aldot at uclibc.org
2007-09-23 22:08 ulf at uclibc.org
2007-07-20 12:03 ulf at uclibc.org
2007-07-08 19:23 aldot at uclibc.org
2007-06-26 16:36 aldot at uclibc.org
2007-04-17 17:30 aldot at uclibc.org
2007-03-22 18:14 aldot at uclibc.org
2007-03-19 10:49 aldot at uclibc.org
2007-02-04 16:30 aldot at uclibc.org
2007-01-30 17:38 aldot at uclibc.org
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=20070606195902.B57F148580@busybox.net \
--to=aldot@uclibc.org \
--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