From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: pango-native build problem (and solution idea)
Date: Mon, 08 Oct 2012 09:45:00 +0200 [thread overview]
Message-ID: <5072847C.7@dresearch-fe.de> (raw)
After upgrading my build host to openSUSE 12.2 i hit a build problem with pango-native (from oe-classic).
-------------> snip <-------------
...
| x86_64-linux-libtool: link: gcc -isystem/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/include -O2 -g -Wall -Wl,-rpath-link -Wl,/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib -Wl,-rpath -Wl,/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib -Wl,-O1 -o .libs/pango-view viewer-render.o viewer-main.o pango-view.o viewer-x.o viewer-pangox.o viewer-pangoft2.o viewer-cairo.o viewer-pangocairo.o -pthread -L/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib ../pango/.libs/libpango-1.0.so ../pango/.libs/libpangox-1.0.so ../pango/.libs/libpangoft2-1.0.so ../pango/.libs/libpangocairo-1.0.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/work/x86_64-linux/pango-native-1.24.4-r1.2/pango-1.24.4/pango/.libs/libpangoft2-1.0.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/work/x86_64-linux/pango-native-1.24.4-r1.2/pango-1.24.4/pango/.libs/libpango-1.0.so
/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libgobject-2.0.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libgthread-2.0.so -lpthread /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libgmodule-2.0.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libglib-2.0.so -lrt /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libcairo.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libpixman-1.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libfontconfig.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libfreetype.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libexpat.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libpng12.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libX11.so
/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libxcb.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libpthread-stubs.so /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libXau.so -ldl /pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib/libz.so -lXrender -lm -pthread -Wl,-rpath -Wl,/pm/sledz/HydraIP/OE/tmp.6-SSZ-fensuse/sysroots/x86_64-linux/usr/lib
| /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libXrender.so: undefined reference to `_XGetRequest'
| collect2: error: ld returned 1 exit status
-------------> snip <-------------
It seems that the libXrender version at the build host now misses the _XGetRequest symbol.
Would it be an acceptable solution to add libxrender-native to DEPENDS_virtclass-native?
Regards,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next reply other threads:[~2012-10-08 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 7:45 Steffen Sledz [this message]
2012-10-08 14:01 ` pango-native build problem (and solution idea) Khem Raj
2012-10-09 8:49 ` [2011.03-maintenance 0/1] pull request 20121009 Steffen Sledz
2012-10-09 8:49 ` [2011.03-maintenance 1/1] pango-native: add libxrender-native to dependencies Steffen Sledz
2012-10-09 14:42 ` [2011.03-maintenance 0/1] pull request 20121009 Tom Rini
2012-10-10 6:41 ` Steffen Sledz
2012-10-10 14:55 ` Tom Rini
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=5072847C.7@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.