From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Joshua Lock <joshua.g.lock@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] oe.path: preserve xattr in copytree() and copyhardlinktree()
Date: Tue, 06 Sep 2016 16:26:05 +0100 [thread overview]
Message-ID: <1473175565.20226.54.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP71WjwZ8Py3To_t+oEVuKNXEagshT2HBiZLL_FtgtCbgD9zBA@mail.gmail.com>
On Tue, 2016-09-06 at 17:22 +0200, Nicolas Dechesne wrote:
> What happens is that I am installing coreutils in my images, and i
> have a copy of 'cp' in my sysroot *and* I don't have xattrs in
> DISTRO_FEATURES. As a consequence the 'cp' command which is invoked
> does not have xattrs support, while my host 'cp' command has it...
>
> e.g.
>
> ~/work/oe-rpb-master/build-rpb$
> tmp-rpb-glibc/sysroots/x86_64-linux/usr/bin/cp -afl --preserve=xattr
> foo bar
> tmp-rpb-glibc/sysroots/x86_64-linux/usr/bin/cp: cannot preserve
> extended attributes, cp is built without xattr support
>
> while this one works fine:
>
> ~/work/oe-rpb-master/build-rpb$ cp -afl --preserve=xattr foo bar
>
> Should we revert these patches or am I missing anything?
Did you have:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=92fc3ef9738165300a4daed4c90526dbbad43149
Cheers,
Richard
next prev parent reply other threads:[~2016-09-06 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 15:43 [PATCH 0/2] Preserve extended attributes in sstate objects Joshua Lock
2016-08-26 15:43 ` [PATCH 1/2] buildtools-tarball: add tar Joshua Lock
2016-08-30 12:24 ` Paul Eggleton
2016-08-26 15:43 ` [PATCH 2/2] oe.path: preserve xattr in copytree() and copyhardlinktree() Joshua Lock
2016-08-26 15:48 ` Mark Hatle
2016-08-30 12:00 ` Joshua Lock
2016-08-30 12:19 ` Richard Purdie
2016-09-06 15:22 ` Nicolas Dechesne
2016-09-06 15:26 ` Richard Purdie [this message]
2016-09-06 15:34 ` Nicolas Dechesne
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=1473175565.20226.54.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joshua.g.lock@intel.com \
--cc=nicolas.dechesne@linaro.org \
--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 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.