From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] cp -dpR fails on BSD systems -- advice on resolving?
Date: Sat, 07 Jul 2007 21:31:17 +0300 [thread overview]
Message-ID: <468FDBF5.6060807@cs.helsinki.fi> (raw)
In-Reply-To: <37c712e0707071110x127595c1nb77f020c16a98a40@mail.gmail.com>
Allan Clark kirjoitti:
> Hi everyone;
>
> I ran into a problem when I moved from uclibc-snapshot to
> uclibc-0.9.28 or 0.9.29: the "cp" command is a non-Unix option: "cp
> -a" or "cp -dpR", or "cp --no-dereference"
>
> I assume it's on Linux, and works, so those of us doing something
> funky (like BSD or MacOSX) invite a few problems.
>
> I'm wondering if the fix should be:
> 1) submit compatible patches to the group, using an older
> syntax/options for all hosts, or
> 2) detect, and download/build/use a replacement (same way I did for
> gmake, as was done for sed)
OT: Any particular reason you're using a Chinese charset? Anyway, issues
of cp have been discussed before on this list. And there are bug reports
about it in the tracker. I suppose nothing conclusive was ever reached.
In the case of uClibc, one could imagine replacing the cp with the tar
trick that's used in the SVN trunk, but the problem, as you surely know
by now, has much wider manifestation over buildroot, and should be dealt
with some uniform, generally agreed upon, way everywhere.
-- Heikki Lindholm
next prev parent reply other threads:[~2007-07-07 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 18:10 [Buildroot] cp -dpR fails on BSD systems -- advice on resolving? Allan Clark
2007-07-07 18:31 ` Heikki Lindholm [this message]
2007-07-07 18:42 ` Bernhard Fischer
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=468FDBF5.6060807@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