[oe] libxml2-native build against host zlib.h

[Tom Rini]

On Tue, Apr 07, 2009 at 04:01:58PM -0300, Jader H. Silva wrote:
> Tom Rini escreveu:
>> On Tue, Apr 07, 2009 at 02:54:35PM -0300, Jader H. Silva wrote:
>>   
>>> Koen Kooi escreveu:
>>>     
>>>> On 23-03-09 20:10, Jader H. Silva wrote:
>>>>       
>>>>>     It seems libxml2-native is built using host zlib.h.
>>>>>     My host have a symbol redefinition in zlib.h (gzopen ->    
>>>>> gzopen64), but
>>>>>     that symbol does not exists in OE compiled library.
>>>>>     Setting --with-zlib=${STAGING_INCIR}/zlib.h in libxml2-native.inc
>>>>>     solved it. There's a patch attached.
>>>>>         
>>>> The patch seems to solve the problem, could you resend a version 
>>>> that  bumps the PR as well? Once this in .dev we should apply it to 
>>>>  stable/2008 as well.
>>>>
>>>> regards,
>>>>
>>>> Koen
>>>>       
>>> Patch with compilation fix and PR update is attached.
>>>     
>>
>> As Khem pointed out previously, this is not correct, NACK.  From the
>> configure script --help:
>>   --with-zlib[=DIR]       use libz in DIR
>> So this should be adding '--with-zlib=${STAGING_INCIR}'
>>
>>   
> --with-zlib=${STAGING_INCDIR} don't fix it.

That's odd.  Reading libxml2-native-2.7.2-r2/libxml2-2.7.2/configure I
don't see how that value being a file and not a dir could work.  In
fact, moving my system zlib.h out of the way and reading config.log I
see things like:
configure:12246: checking zlib.h usability
configure:12263: gcc -c
-isystem/home/trini/work/OE-upstream/tmp.4.3.3/staging/x86_64-linux/usr/include
-O2
-isystem/home/trini/work/OE-upstream/tmp.4.3.3/staging/x86_64-linux/usr/include
conftest.c >&5
configure:12269: $? = 0
configure:12283: result: yes
configure:12287: checking zlib.h presence
configure:12302: gcc -E
-isystem/home/trini/work/OE-upstream/tmp.4.3.3/staging/x86_64-linux/usr/include
conftest.c
configure:12308: $? = 0
configure:12322: result: yes
configure:12350: checking for zlib.h
configure:12358: result: yes

Can you tell us more about what host system you're using and possibly
just as importantly what config.log looks like when you use your patch?
I'm not saying you don't have a failure, I'm just saying it's puzzling
that your patch works.

Also, trying to figure out when zlib-native gets pulled in and I see
it's coming from file-native, so perhaps we should, while we're in here
anyhow, add zlib-native to the dep list for libxml2-native?

-- 
Tom Rini