All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Kinar <n.kinar@usask.ca>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 821] New: cp: illegal operation
Date: Mon, 21 Dec 2009 18:47:51 -0600	[thread overview]
Message-ID: <4B301737.5020402@usask.ca> (raw)
In-Reply-To: <bug-821-163@https.bugs.busybox.net/>

Hello Marcus--

It is good to know that you were able to get some aspects of buildroot 
up and running on Mac OS X.  How do you deal with build dependencies?  I 
have been attempting to run buildroot on 10.5 Leopard using the Fink 
binutils, but I found that I would still have to build fakeroot (and a 
few other associated utilities and libraries) from scratch.

Is fakeroot included with Mac OS X 10.6?  When building, do you still 
receive errors when stripping executables?  When I last tried to run 
buildroot on OS X, some header files particular to Linux-based systems 
could not be found.
Nicholas

bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=821
>
>               Host: MacBook Pro running Snow Leopard
>             Target: ARM SX-560
>              Build: buildroot
>            Summary: cp: illegal operation
>            Product: buildroot
>            Version: 2009.11
>           Platform: Macintosh
>         OS/Version: Mac OS
>             Status: NEW
>           Severity: normal
>           Priority: P5
>          Component: Other
>         AssignedTo: unassigned at buildroot.uclibc.org
>         ReportedBy: markus.schabel at gmail.com
>                 CC: buildroot at uclibc.org
>    Estimated Hours: 0.5
>
>
> When building the toolchain on my Mac, it always halts because of an illegal
> parameter for cp. the parameter "-d" is not supported on Mac OS X. The
> following patch should work on all systems:
>
> --- Makefile    2008-02-25 09:15:31.000000000 +0100
> +++ Makefile    2009-12-22 00:04:29.000000000 +0100
> @@ -283,11 +257,11 @@
>  $(BR2_DEPENDS_DIR): .config
>         rm -rf $@
>         mkdir -p $(@D)
> +       cp -af $(CONFIG)/buildroot-config $@
> -       cp -dpRf $(CONFIG)/buildroot-config $@
>
>  dirs: $(DL_DIR) $(TOOL_BUILD_DIR) $(BUILD_DIR) $(STAGING_DIR) $(TARGET_DIR) \
>
>
>   

  reply	other threads:[~2009-12-22  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 23:13 [Buildroot] [Bug 821] New: cp: illegal operation bugzilla at busybox.net
2009-12-22  0:47 ` Nicholas Kinar [this message]
2009-12-22  7:44 ` Peter Korsgaard
2010-01-28 22:59 ` [Buildroot] [Bug 821] " bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-02-21 18:53 ` bugzilla 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=4B301737.5020402@usask.ca \
    --to=n.kinar@usask.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.