From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: shared-mime-info-native-0.51 do_compile failure
Date: Mon, 15 Feb 2010 15:35:01 -0500 [thread overview]
Message-ID: <20100215203501.GC14442@denix.org> (raw)
In-Reply-To: <1266176499.12424.6.camel@ed-hp-laptop>
On Sun, Feb 14, 2010 at 11:41:39AM -0800, ed wrote:
> Trying to build image for mini2440 and get the following error.
>
> NOTE: Running task 694 of 2862 (ID:
> 1434, /home/ed/mini2440/OE/openembedded/recipes/shared-mime-info/shared-mime-info-native_0.51.bb, do_compile)
> ERROR: function do_compile failed
> ERROR: log data follows
> (/home/ed/mini2440/OE/build/tmp/work/i686-linux/shared-mime-info-native-0.51-r0/temp/log.do_compile.11554)
> | NOTE: make
> | Making check in po
> | make[1]: Entering directory
> `/home/ed/mini2440/OE/build/tmp/work/i686-linux/shared-mime-info-native-0.51-r0/shared-mime-info-0.51/po'
> | rm -f missing notexist
> |
> srcdir=. /home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/bin/intltool-update -m
> | if [ -r missing -o -r notexist ]; then \
> | exit 1; \
> | fi
> | make[1]: Leaving directory
> `/home/ed/mini2440/OE/build/tmp/work/i686-linux/shared-mime-info-native-0.51-r0/shared-mime-info-0.51/po'
> | make[1]: Entering directory
> `/home/ed/mini2440/OE/build/tmp/work/i686-linux/shared-mime-info-native-0.51-r0/shared-mime-info-0.51'
> | ccache gcc
> -I/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/include/libxml2
> -I/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/include/glib-2.0
> -I/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/lib/glib-2.0/include -isystem/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/include -O2 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -L/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/lib -Wl,-rpath-link,/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/lib -Wl,-rpath,/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/lib -Wl,-O1 -o update-mime-database update_mime_database-update-mime-database.o -L/home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/lib -lxml2 -lglib-2.0
> | /home/ed/mini2440/OE/build/tmp/staging/i686-linux/usr/lib/libxml2.so:
> undefined reference to `gzopen64'
> | collect2: ld returned 1 exit status
> | make[1]: *** [update-mime-database] Error 1
> | make[1]: Leaving directory
> `/home/ed/mini2440/OE/build/tmp/work/i686-linux/shared-mime-info-native-0.51-r0/shared-mime-info-0.51'
> | make: *** [check-recursive] Error 1
> | FATAL: oe_runmake failed
> NOTE: Task
> failed: /home/ed/mini2440/OE/build/tmp/work/i686-linux/shared-mime-info-native-0.51-r0/temp/log.do_compile.11554
> ERROR: TaskFailed event exception, aborting
> ERROR: Build
> of /home/ed/mini2440/OE/openembedded/recipes/shared-mime-info/shared-mime-info-native_0.51.bb do_compile failed
> ERROR: Task 1434
> (/home/ed/mini2440/OE/openembedded/recipes/shared-mime-info/shared-mime-info-native_0.51.bb, do_compile) failed
> NOTE: Tasks Summary: Attempted 693 tasks of which 674 didn't need to be
> rerun and 1 failed.
> ERROR:
> '/home/ed/mini2440/OE/openembedded/recipes/shared-mime-info/shared-mime-info-native_0.51.bb' failed
>
> ==============================
> 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
Actually, it clearly says it's *UND*efined in this context... :) As gzopen*()
is provided by libz - looks like it may be trying to link against your host
lib...
--
Denys
next prev parent reply other threads:[~2010-02-15 20:37 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 [this message]
2010-02-26 19:50 ` Khem Raj
2010-02-26 20:12 ` Ed Nelson
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=20100215203501.GC14442@denix.org \
--to=denis@denix.org \
--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