From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Khem Raj <kraj@juniper.net>
Subject: Re: [PATCH 1/3] cmake-native: Fix build on ubuntu
Date: Fri, 20 Jul 2012 08:42:48 +0100 [thread overview]
Message-ID: <1342770168.21788.5.camel@ted> (raw)
In-Reply-To: <1342761780-20215-1-git-send-email-raj.khem@gmail.com>
On Thu, 2012-07-19 at 22:22 -0700, Khem Raj wrote:
> From: Khem Raj <kraj@juniper.net>
>
> Fixes errors like
>
> /yocto/poky/build/tmp/work/x86_64-linux/cmake-native-2.8.5-r2.1/cmake-2.8.5/Utilities/cmlibarchive/libarchive/archive_entry.c:56:55:
> fatal error: ext2fs/ext2_fs.h: No such file or directory
>
> Signed-off-by: Khem Raj <kraj@juniper.net>
> ---
> meta/recipes-devtools/cmake/cmake-native_2.8.5.bb | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/cmake/cmake-native_2.8.5.bb b/meta/recipes-devtools/cmake/cmake-native_2.8.5.bb
> index 3fe0c2e..98ae300 100644
> --- a/meta/recipes-devtools/cmake/cmake-native_2.8.5.bb
> +++ b/meta/recipes-devtools/cmake/cmake-native_2.8.5.bb
> @@ -1,7 +1,9 @@
> require cmake.inc
> inherit native
>
> -PR = "${INC_PR}.1"
> +DEPENDS += "e2fsprogs-native"
> +
> +PR = "${INC_PR}.2"
>
> SRC_URI[md5sum] = "3c5d32cec0f4c2dc45f4c2e84f4a20c5"
> SRC_URI[sha256sum] = "5e18bff75f01656c64f553412a8905527e1b85efaf3163c6fb81ea5aaced0b91"
Does cmake really need e2fsprogs? Can we disable that dependency
instead? What would we lose?
Cheers,
Richard
prev parent reply other threads:[~2012-07-20 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 5:22 [PATCH 1/3] cmake-native: Fix build on ubuntu Khem Raj
2012-07-20 5:22 ` [PATCH 2/3] binutils: Add missing target package dependencies Khem Raj
2012-07-21 0:26 ` Saul Wold
2012-07-20 5:23 ` [PATCH 3/3] puzzles, mkelfimage: Use svn protocol instead of http Khem Raj
2012-07-20 7:42 ` Richard Purdie [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=1342770168.21788.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=kraj@juniper.net \
--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