[OE-core] [PATCH] libxml2: add missing dependency on binutils

Martin Jansa martin.jansa at gmail.com
Tue Feb 21 22:48:11 UTC 2012


On Tue, Feb 21, 2012 at 02:26:49PM -0800, Steve Sakoman wrote:
> On Tue, Feb 21, 2012 at 1:52 PM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
> > 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 at 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?
> 
> For some reason the libxml2 configure phase decides that ansidecl.h
> from binutils is present, but then at compile time it finds that it
> actually isn't there!  I saw the same issue on both my desktop and
> autobuilder setups.
> 
> I'll try a clean build to see if the problem persists.  The libz
> change from last week seems to have put my builds in a bad state, and
> the PR bumps intended to fix things really don't seem to be fixing
> things, at least on my build machines.  I suspect it might be faster
> to do a clean build than to track down where the corruption is.

The list of PR bumped recipes probably wasn't complete for you. It was
for me, but later I've noticed that ie subversion-1.6 wasn't bumped,
because I'm using only 1.7.

So it was complete for my default build (when those PR bumps were
applied to all included layers at once, which is not the case for most
people) and if you build different recipes or different versions you
have to add your own PR bumps in those recipes (see khem's script).

Clean build could be faster but doesn't fix installed -dev packages on
target..

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120221/2055a1d3/attachment-0002.sig>


More information about the Openembedded-core mailing list