From: Ed Nelson <enelson1000@comcast.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: shared-mime-info-native-0.51 do_compile failure
Date: Fri, 26 Feb 2010 12:12:05 -0800 [thread overview]
Message-ID: <4B882B15.60902@comcast.net> (raw)
In-Reply-To: <20100226195002.GC25079@gmail.com>
Khem Raj wrote:
> On (14/02/10 11:41), ed wrote:
>
>> Trying to build image for mini2440 and get the following error.
>>
> ==============================
>
>> Says it has undefined gzopen64
>> But gzopen64 is apparently there.
>> ed ~/mini2440/OE/build/tmp/staging/i686-linux/usr/lib:$: strings
>> libxml2.so |grep gzopen64
>> gzopen64
>> ed ~/mini2440/OE/build/tmp/staging/i686-linux/usr/lib:$: objdump -T
>> libxml2.so |grep gzopen64
>> 00000000 DF *UND* 00000000 gzopen64
>>
>>
>> Any ideas?
>>
>
> It must be using libxml from host and libz from your native staging.
> So either use both from host or both from staging. Mixing can cause this
> problem.
>
> Do you have any of zlib-native or libxml2-native in your local.conf as
> ASSUME_PROVIDED ?
>
>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
I ended up modifying libxml12-native.inc file and added
--with-zlib=${STAGING_INCDIR}/zlib.h to EXTRA_OECONF.
Looked at your email response to Cliff Brake "gettext native failure" on
2/23/2010.
Not sure if this was the correct way to fix it but it solved my problem.
Thanks
Ed
prev parent reply other threads:[~2010-02-26 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 19:41 shared-mime-info-native-0.51 do_compile failure ed
2010-02-15 20:35 ` Denys Dmytriyenko
2010-02-26 19:50 ` Khem Raj
2010-02-26 20:12 ` Ed Nelson [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=4B882B15.60902@comcast.net \
--to=enelson1000@comcast.net \
--cc=openembedded-devel@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