Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Lindholm <holindho@cs.helsinki.fi>
To: buildroot@busybox.net
Subject: [Buildroot] target busybox skeleton.
Date: Thu, 08 Mar 2007 14:23:09 +0200	[thread overview]
Message-ID: <45F0002D.7020203@cs.helsinki.fi> (raw)
In-Reply-To: <20070308114948.GE31261@aon.at>

Bernhard Fischer kirjoitti:
> On Thu, Mar 08, 2007 at 01:14:40PM +0200, Heikki Lindholm wrote:
> 
>>Bernhard Fischer kirjoitti:
>>
>>>On Sun, Feb 18, 2007 at 06:32:11PM +0100, Thomas Lundquist wrote:
>>>
>>>
>>>>Maybe it's a bit too tiny?
>>>>
>>>>I'd suggest that /usr/lib is added.
>>>
>>>
>>>hmz. And what if i don't have anything in /usr/lib? Wasted dentry.
>>>
>>>What about switching to "install -D" instead, where appropriate?
>>
>>If doing major changes, please consider taking portability issues into 
>>account. In this case, "-D" isn't supported on OS X.
> 
> 
> It shouldn't be too hard to ship our own working install source an
> compile and use that for the host, but thanks for the hint anyway.
> 
> MacOS-BSD already has trouble due to the use of "cp -a", IIRC and i was
> gradually switching those over to cp -dpf like suggested in one
> bug-report.

Getting a bit off-topic here maybe, but I have to comment that your 
effort has not been that useful, because such bug report has been wrong: 
Mac OS X doesn't support the -d option for cp and thus every cp -dfp is 
as dysfunctional as cp -a. Proper way would be cp -RPfp, which, as an 
unavoidable side-effect, is also recursive. I also filed a bug report on 
this a while ago.

-- Heikki Lindholm

  reply	other threads:[~2007-03-08 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 17:32 [Buildroot] target busybox skeleton Thomas Lundquist
2007-03-08 10:36 ` Bernhard Fischer
2007-03-08 11:14   ` Heikki Lindholm
2007-03-08 11:49     ` Bernhard Fischer
2007-03-08 12:23       ` Heikki Lindholm [this message]
2007-03-08 15:53         ` Bernhard Fischer
2007-03-10 13:41   ` Thomas Lundquist

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=45F0002D.7020203@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