From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/mklibs
Date: Wed, 3 Jan 2007 06:11:17 -0800 (PST) [thread overview]
Message-ID: <20070103141117.C564F48641@busybox.net> (raw)
Author: aldot
Date: 2007-01-03 06:11:16 -0800 (Wed, 03 Jan 2007)
New Revision: 17144
Log:
- portable cp args
Modified:
trunk/buildroot/toolchain/mklibs/mklibs.mk
Changeset:
Modified: trunk/buildroot/toolchain/mklibs/mklibs.mk
===================================================================
--- trunk/buildroot/toolchain/mklibs/mklibs.mk 2007-01-03 13:44:01 UTC (rev 17143)
+++ trunk/buildroot/toolchain/mklibs/mklibs.mk 2007-01-03 14:11:16 UTC (rev 17144)
@@ -6,7 +6,7 @@
MKLIBS_PROGRAM:=$(STAGING_DIR)/bin/mklibs.py
$(MKLIBS_PROGRAM): toolchain/mklibs/mklibs.py
- cp -a toolchain/mklibs/mklibs.py $@
+ cp -dpf toolchain/mklibs/mklibs.py $@
mklibs-clean:
rm -f $(MKLIBS_PROGRAM)
reply other threads:[~2007-01-03 14:11 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=20070103141117.C564F48641@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