From: Seebs <seebs@seebs.net>
To: Andreas Kaufmann <andreas.kaufmann.79@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pseudo: explicitly enable xattr support
Date: Thu, 22 Mar 2018 11:08:46 -0500 [thread overview]
Message-ID: <20180322110846.25d9c2e6@seebsdell> (raw)
In-Reply-To: <1521734768-11762-1-git-send-email-andreas.kaufmann.79@gmail.com>
On Thu, 22 Mar 2018 17:06:08 +0100
Andreas Kaufmann <andreas.kaufmann.79@gmail.com> wrote:
> Pseudo is using a custom configure script that detects if it shall
> build with extended file attribute support or not. The check is done
> by simply calling 'getfattr' provided by attr-native which is not
> part of the dependency list. Due to the recent changes (recipe
> specific sysroot & cleanup of $PATH) this call fails now when the
> recipe is being build for the first time (at least when being build
> for nativesdk case). Explicitly setting up a dependency to
> attr-native just to satisfy configure would be wrong also since the
> real dependency is to attr/nativesdk-attr which are already part of
> the dependency list (see DEPENDS). Therefore bypass the test in the
> configure by explicitly enabling xattr using a configure option
> available in any case.
This seems reasonable to me. The historical rationale for the configure
test was that we encountered actual systems in the wild which did not
have the underlying xattr support, as I recall? But I think that's no
longer remotely relevant.
-s
prev parent reply other threads:[~2018-03-22 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 16:06 [PATCH] pseudo: explicitly enable xattr support Andreas Kaufmann
2018-03-22 16:08 ` Seebs [this message]
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=20180322110846.25d9c2e6@seebsdell \
--to=seebs@seebs.net \
--cc=andreas.kaufmann.79@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