From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] cp command incompatibility
Date: Fri, 23 Feb 2007 19:15:29 +0200 [thread overview]
Message-ID: <45DF2131.2020404@cs.helsinki.fi> (raw)
Hi,
there's some incompatilibity between GNU cp and Mac OS X (probably BSD,
too) cp commands. GNU cp arguments -d and -a do not exist on OS X. -a
can be written -pPR on OS X. -d is partly covered by -P and partly by
-R. -P is the --no-dereference part of -d and -R does what
--preserve=links does AFAICT.
Doing a quick grep -r "cp " `find . -iname "*.mk"` reveals that there is
quite a bit of work to fix all the incompatible cp occurences, so, I'm
asking here what might be the best way to do it:
(1) hand-edit all incompatible cp occurences to something that works on
both systems ("POSIXify")
(2) introduce some menuconfig options for common cp "use cases" and use
shell variables to pass these configurable options to cp, for example,
.mk scripts might have "cp $ARCHIVE foo bar", where $ARCHIVE would, for
instance, be "-a" on Linux and "-pPR" on OS X.
(3) give up and build a local copy of GNU fileutils, instead
-- Heikki Lindholm
next reply other threads:[~2007-02-23 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 17:15 Heikki Lindholm [this message]
2007-03-08 13:56 ` [Buildroot] cp command incompatibility Bernhard Fischer
2007-03-10 7:36 ` Heikki Lindholm
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=45DF2131.2020404@cs.helsinki.fi \
--to=holindho@cs.helsinki.fi \
--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