Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel: Use hardlinks for do_populate_sysroot for speed
Date: Mon, 11 Nov 2013 09:35:51 +0000	[thread overview]
Message-ID: <1384162551.22454.9.camel@ted> (raw)
In-Reply-To: <CAFyqS9q_HMp+WDgcxQ9QeoDtDP3JCmpWwLSu5NVH+unqyCQ4GA@mail.gmail.com>

On Mon, 2013-11-11 at 09:06 +0100, Hans Beckérus wrote:
> I am having some trouble with these patches :( The new approach is
> using the '-n' flag to the 'cp' command.
> That is not supported on our SuSE11 based system. To be honest, I do
> not know how portable '-n' is?
> Some system have it, others seems to provide '-u' instead. I guess by
> removing '-n' part of the performance gain is lost?
> Would it be possible to test for error from the 'cp' command and if it
> fails try '-u' instead (and cache the result)? Or maybe
> even better, make this configurable in local.conf (or the distro) for
> the build platforms that does not support  '-n' but can
> instead fall-back to using '-u'. From what I can tell most systems
> support  one or the other, but never both.

Hmm, its been in coreutils since 2009 which I guess isn't that long in
the scheme of things:
http://git.savannah.gnu.org/cgit/coreutils.git/commit/src/cp.c?id=d01338eb3d30e5634f1b4d4179c229f54eea0b44

Just to double check, is cp on your system provided by coreutils or
something else?

Cheers,

Richard




  reply	other threads:[~2013-11-11  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 15:18 [PATCH] kernel: Use hardlinks for do_populate_sysroot for speed Richard Purdie
2013-11-08 15:41 ` Bruce Ashfield
2013-11-08 15:54   ` Hans Beckérus
2013-11-08 15:55   ` Richard Purdie
2013-11-08 15:59     ` Bruce Ashfield
2013-11-08 16:50       ` Richard Purdie
2013-11-08 17:23         ` Hart, Darren
2013-11-09 20:38           ` Andrea Adami
2013-11-09 22:58             ` Richard Purdie
2013-11-11  8:06               ` Hans Beckérus
2013-11-11  9:35                 ` Richard Purdie [this message]
2013-11-11  9:45                 ` Richard Purdie
2013-11-11  9:47                   ` Hans Beckérus

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=1384162551.22454.9.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=darren.hart@intel.com \
    --cc=hans.beckerus@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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