On Tue, Feb 21, 2012 at 2:26 PM, Steve Sakoman <[email protected]> wrote:
> On Tue, Feb 21, 2012 at 1:52 PM, Richard Purdie
> <[email protected]> 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 <[email protected]>
>>> ---
>>>  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.

FWIW, a clean build resolved the binutils dependency, so the above
patch is not required.

I suspect that the current set of PR bumps for the zlib issue still
aren't sufficient for many users, but I'm hoping the switch to
OEBasicHash will minimize further pain.

Steve

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to