Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001251]: Buildroot uses lots of cp commands that assume GNU cp
Date: Fri, 2 Mar 2007 13:26:20 -0800	[thread overview]
Message-ID: <c5366a2a98b31a23483fabf295e85bce@busybox.net> (raw)


The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1251 
====================================================================== 
Reported By:                holin
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1251
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             03-02-2007 13:26 PST
Last Modified:              03-02-2007 13:26 PST
====================================================================== 
Summary:                    Buildroot uses lots of cp commands that assume GNU
cp
Description: 
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. The ugly part is that -R, which is also recursive, has to be used
to get real as-is copying of symbolic links. Attached a patch for some of
the cp commands, but there are many more. Maybe, patches could be appended
to this report.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-02-07 13:26  holin          New Issue                                    
03-02-07 13:26  holin          Status                   new => assigned     
03-02-07 13:26  holin          Assigned To               => buildroot       
03-02-07 13:26  holin          File Added: buildroot-070302-cp-01.patch         
          
======================================================================

             reply	other threads:[~2007-03-02 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 21:26 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-07 18:46 [Buildroot] [buildroot 0001251]: Buildroot uses lots of cp commands that assume GNU cp bugs at busybox.net

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=c5366a2a98b31a23483fabf295e85bce@busybox.net \
    --to=bugs@busybox.net \
    --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