From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Steve Sakoman <steve@sakoman.com>
Subject: Re: [PATCH] libxml2: add missing dependency on binutils
Date: Tue, 21 Feb 2012 21:52:58 +0000 [thread overview]
Message-ID: <1329861178.20261.62.camel@ted> (raw)
In-Reply-To: <1329851229-31625-1-git-send-email-steve@sakoman.com>
On Tue, 2012-02-21 at 11:07 -0800, Steve Sakoman wrote:
> Otherwise build fails with following error:
>
> | In file included from libxml.h:36:0,
> | from xmlmemory.c:8:
> | ./include/libxml/xmlversion.h:396:22: fatal error: ansidecl.h: No such file or directory
>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
> meta/recipes-core/libxml/libxml2.inc | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-core/libxml/libxml2.inc b/meta/recipes-core/libxml/libxml2.inc
> index 0979acd..6230f60 100644
> --- a/meta/recipes-core/libxml/libxml2.inc
> +++ b/meta/recipes-core/libxml/libxml2.inc
> @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://Copyright;md5=bb90c48926316d9af6e2d70ca7013ade \
> file://trio.c;beginline=5;endline=14;md5=6c025753c86d958722ec76e94cae932e"
>
> DEPENDS_virtclass-native = "python-native"
> -DEPENDS =+ "zlib"
> +DEPENDS =+ "zlib binutils"
>
> SRC_URI = "ftp://xmlsoft.org/libxml2/libxml2-${PV}.tar.gz \
> file://libxml-64bit.patch"
This sounds very wrong. It would have implications for libxml2-native
I'd imagine. What is it doing that needs binutils?
Its going to add considerable time to the build too.
Cheers,
Richard
next prev parent reply other threads:[~2012-02-21 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 19:07 [PATCH] libxml2: add missing dependency on binutils Steve Sakoman
2012-02-21 21:52 ` Richard Purdie [this message]
2012-02-21 22:26 ` Steve Sakoman
2012-02-21 22:48 ` Martin Jansa
2012-02-21 23:02 ` Phil Blundell
2012-02-22 15:09 ` Steve Sakoman
2012-02-21 22:58 ` Khem Raj
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=1329861178.20261.62.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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