From: Peter Seebach <peter.seebach@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] pseudo_1.6.0.bb: uprev to pseudo 1.6
Date: Fri, 11 Jul 2014 15:24:49 -0500 [thread overview]
Message-ID: <20140711152449.08d84fdc@e6410-2> (raw)
In-Reply-To: <CAJTo0Lay1CB_BumWQDDLHrS2i2XkiE99TamO3bwMH86_=P8gFg@mail.gmail.com>
On Fri, 11 Jul 2014 21:21:06 +0100
"Burton, Ross" <ross.burton@intel.com> wrote:
> The extended attributes code means adding build-dependency on attr.
>
> Which leads onto the discussion as to whether we add attr-native to
> the build for pseudo-native, or use ASSUME_PROVIDED and document that
> the host needs to provide it.
Well, since my builds worked without adding the dependency, I guess I would
go with ASSUME_PROVIDED since that was what I did, apparently.
I admit to not having been aware that it was possible to lack xattr
support in a modernish Linux.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2014-07-11 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 20:22 [PATCH 0/1] pseudo 1.6.0 Peter Seebach
2014-07-11 20:22 ` [PATCH 1/1] pseudo_1.6.0.bb: uprev to pseudo 1.6 Peter Seebach
2014-07-11 20:21 ` Burton, Ross
2014-07-11 20:24 ` Peter Seebach [this message]
2014-07-11 21:32 ` Richard Purdie
2014-07-11 21:56 ` Peter Seebach
2014-07-14 18:39 ` Peter Seebach
2014-07-14 18:55 ` Burton, Ross
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 19:12 [PATCH 0/1] " Peter Seebach
2014-07-14 19:12 ` [PATCH 1/1] pseudo_1.6.0.bb: uprev to " Peter Seebach
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=20140711152449.08d84fdc@e6410-2 \
--to=peter.seebach@windriver.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