From: Saul Wold <sgw@linux.intel.com>
To: Koen Kooi <koen.kooi@linaro.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libarchive: add missing e2fsprogs dependency
Date: Mon, 05 May 2014 14:54:08 -0700 [thread overview]
Message-ID: <53680880.30402@linux.intel.com> (raw)
In-Reply-To: <1399289179-5662-1-git-send-email-koen.kooi@linaro.org>
On 05/05/2014 04:26 AM, Koen Kooi wrote:
> This fixes the following build error:
> | libarchive/archive_entry.c:59:55: fatal error: ext2fs/ext2_fs.h: No such file or directory
>
> There is no configure options to avoid this dependency.
>
> Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
> ---
> meta/recipes-extended/libarchive/libarchive_3.1.2.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-extended/libarchive/libarchive_3.1.2.bb b/meta/recipes-extended/libarchive/libarchive_3.1.2.bb
> index eedbaa7..277d8c8 100644
> --- a/meta/recipes-extended/libarchive/libarchive_3.1.2.bb
> +++ b/meta/recipes-extended/libarchive/libarchive_3.1.2.bb
> @@ -5,6 +5,8 @@ SECTION = "devel"
> LICENSE = "BSD"
> LIC_FILES_CHKSUM = "file://COPYING;md5=b4e3ffd607d6686c6cb2f63394370841"
>
> +DEPENDS = "e2fsprogs"
> +
By doing this we also have to extend e2fprogs to be a nativesdk target.
Is there not a way to make this optional by editing the configure.ac and
adding a switch? What functionality to we gain or loose with / without
the ext2fs extensions?
Sau!
> PACKAGECONFIG ?= "libxml2 zlib bz2"
>
> PACKAGECONFIG_append_class-target = "\
>
next prev parent reply other threads:[~2014-05-05 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 11:26 [PATCH] libarchive: add missing e2fsprogs dependency Koen Kooi
2014-05-05 21:54 ` Saul Wold [this message]
2014-05-06 5:52 ` Koen Kooi
2014-05-06 9:17 ` Paul Eggleton
2014-05-06 9:18 ` Paul Eggleton
2014-05-06 10:33 ` Paul Barker
2014-05-06 10:39 ` Paul Eggleton
2014-05-06 18:25 ` Khem Raj
2014-05-06 22:57 ` Paul Barker
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=53680880.30402@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen.kooi@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.