From: Peter Seebach <peter.seebach@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] pseudo_1.6.0.bb: uprev to pseudo 1.6
Date: Mon, 14 Jul 2014 13:39:50 -0500 [thread overview]
Message-ID: <20140714133950.37e29e55@e6410-2> (raw)
In-Reply-To: <1405114369.21289.95.camel@ted>
On Fri, 11 Jul 2014 22:32:49 +0100
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> The issue is the lack of the xattr headers from what I saw, not the
> xattr support itself and we're missing what looks like a single define.
> For the complexity, I did wonder if we should ship a default...
Thinking about this more, the default alone wouldn't do it, I'd have to
either drop the header or make it conditional, which I'd sort of prefer not
to do. Checks for header availability are a pain.
So should I resubmit with the attr-native dependency? I don't know how much
build time that will impose, but I assume not very much.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2014-07-14 18:39 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
2014-07-11 21:32 ` Richard Purdie
2014-07-11 21:56 ` Peter Seebach
2014-07-14 18:39 ` Peter Seebach [this message]
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=20140714133950.37e29e55@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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