From: Patrick Ohly <patrick.ohly@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] mtd-utils: keep xattr support enabled
Date: Wed, 12 Aug 2015 11:33:56 +0200 [thread overview]
Message-ID: <1439372036.28153.29.camel@intel.com> (raw)
In-Reply-To: <CAJTo0LbMmZ9rf-Jq_XoGJzTCj_0E=1qene_ooyf_T_nWsH60Jw@mail.gmail.com>
On Tue, 2015-08-11 at 15:33 +0100, Burton, Ross wrote:
>
> On 11 August 2015 at 09:45, Patrick Ohly <patrick.ohly@intel.com>
> wrote:
> -EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}'
> 'CFLAGS=${CFLAGS} -I${S}/include -DWITHOUT_XATTR' 'BUILDDIR=
> ${S}'"
> +EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}'
> 'CFLAGS=${CFLAGS} -I${S}/include' 'BUILDDIR=${S}'"
>
>
> There's a "xattr" DISTRO_FEATURE that should be respected here for
> target builds (and explicitly enabled for native I guess).
I can add that check, if you want.
> Does enabling xattr mean adding build dependencies?
No, the conditional code uses lgetxattr and llistxattr, which are in
glibc.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2015-08-12 9:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 8:44 [PATCH 0/3] preserve xattrs in images Patrick Ohly
2015-08-11 8:44 ` [PATCH 1/3] tar-replacement-native: avoid race condition with host tar Patrick Ohly
2015-08-14 10:47 ` Burton, Ross
2015-08-14 11:01 ` Paul Eggleton
2015-08-14 11:03 ` Burton, Ross
2015-08-14 14:52 ` Patrick Ohly
2015-08-14 14:56 ` Paul Eggleton
2015-08-14 15:38 ` Patrick Ohly
2015-08-14 16:29 ` Paul Eggleton
2015-08-14 14:59 ` [PATCH v2 0/2] xattr + tar Patrick Ohly
2015-08-14 14:59 ` [PATCH v2 1/2] tar-replacement-native: relocate via NATIVE_PACKAGE_PATH_SUFFIX Patrick Ohly
2015-08-14 15:07 ` Burton, Ross
2015-08-14 16:01 ` [PATCH v3 0/2] xattr + tar Patrick Ohly
2015-08-14 16:01 ` [PATCH v3 1/2] tar-replacement-native: relocate via NATIVE_PACKAGE_PATH_SUFFIX Patrick Ohly
2015-08-14 16:01 ` [PATCH v3 2/2] image_types.bbclass: allow replacing tar command Patrick Ohly
2015-08-14 14:59 ` [PATCH v2 " Patrick Ohly
2015-08-11 8:44 ` [PATCH 2/3] " Patrick Ohly
2015-08-11 8:45 ` [PATCH 3/3] mtd-utils: keep xattr support enabled Patrick Ohly
2015-08-11 14:33 ` Burton, Ross
2015-08-12 9:33 ` Patrick Ohly [this message]
2015-08-14 10:51 ` Burton, Ross
2015-08-25 11:46 ` Patrick Ohly
2015-08-25 13:26 ` Mark Hatle
2015-08-25 13:46 ` Andrea Adami
2015-08-25 15:27 ` Patrick Ohly
2015-08-25 19:49 ` Mark Hatle
2015-08-11 14:29 ` [PATCH 0/3] preserve xattrs in images Burton, Ross
2015-08-12 9:28 ` Patrick Ohly
2015-08-12 14:34 ` Mark Hatle
2015-08-12 14:44 ` Patrick Ohly
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=1439372036.28153.29.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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