[oe] xbmc: task `compile` fails with `/tools/TexturePacker/XBMCTex.cpp:394: undefined reference to `__lzo_init2'`
Khem Raj
raj.khem at gmail.com
Mon Nov 29 20:28:26 UTC 2010
On Mon, Nov 29, 2010 at 12:23 PM, Paul Menzel
<paulepanter at users.sourceforge.net> wrote:
> Am Montag, den 29.11.2010, 11:43 -0800 schrieb Khem Raj:
>> On Fri, Nov 26, 2010 at 4:15 AM, Paul Menzel
>> <paulepanter at users.sourceforge.net> wrote:
>> > arm-angstrom-linux-gnueabi-g++ -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb -isystem/oe/build/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb2 -fpermissive -fvisibility-inlines-hidden -fPIC -DPIC -D_REENTRANT -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -g -D_DEBUG -Wall -O2 -mfloat-abi=softfp -mno-apcs-stack-check -Wa,-march=armv7a -mcpu=cortex-a8 -mfpu=neon -mvectorize-with-neon-quad -isystem/oe/build/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb2 -fpermissive -fvisibility-inlines-hidden -fPIC -DPIC -D_REENTRANT -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -g -D_DEBUG -Wall -O2 -mfloat-abi=softfp -mno-apcs-stack-check -Wa,-march=armv7a -mcpu=cortex-a8 -mfpu=neon -mvectorize-with-neon-quad -isystem/oe/build/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/include -fexpensive-optimizations -frename-registers -fomit-frame-pointer -O2 -ggdb2 -fpermissive -fvisibility-inlines-hidden -fPIC -DPIC -D_REENTRANT -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -g -D_DEBUG -Wall -O2 -mfloat-abi=softfp -mno-apcs-stack-check -Wa,-march=armv7a -mcpu=cortex-a8 -mfpu=neon -mvectorize-with-neon-quad SDL_anigif.o XBTFWriter.o XBMCTex.o ../../guilib/XBTF.o -L/oe/build/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib -Wl,-rpath-link,/oe/build/angstrom-dev/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib -Wl,-O1 -Wl,--hash-style=gnu ../../xbmc/lib/libsquish/libsquish-arm.a -lSDL_image -lSDL -llzo2 -o TexturePacker
>> > XBMCTex.o: In function `main':
>> > /oe/build/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xbmc-10.05-r8+gitr0+e2ab481ebe964321c358ab9d6402088c714adcbe/git/tools/TexturePacker/XBMCTex.cpp:394: undefined reference to `__lzo_init2'
>> > collect2: ld returned 1 exit status
>> > make[1]: *** [TexturePacker] Error 1
>> > make[1]: Leaving directory `/oe/build/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/xbmc-10.05-r8+gitr0+e2ab481ebe964321c358ab9d6402088c714adcbe/git/tools/TexturePacker'
>> > make: *** [tools/TexturePacker/TexturePacker] Error 2
>>
>> It seems link line has -llzo2 and liblzo2 should contain this
>> function, you could investigate.
>> 1. If liblzo2 exists in the staging area
>
> /oe/build/angstrom-dev$ find sysroots/ -iname *liblzo*
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo.so.1
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo.a
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo2.a
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo2.so.2
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo2.la
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo.la
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo2.so.2.0.0
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo.so.1.0.0
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo.so
> sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo2.so
>
>> 2. If it does then dump the symbols it has exported as globals
>
> /oe/build/angstrom-dev$ objdump -t sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo.so | grep lzo_init
> 00000000 l df *ABS* 00000000 lzo_init.c
> 0000274c g F .text 000000c8 __lzo_init2
> 00024ba8 g O .bss 00000004 __lzo_init_done
> 00002814 g F .text 00000054 __lzo_init
> /oe/build/angstrom-dev$ objdump -t sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/liblzo2.so | grep lzo_init
> 00000000 l df *ABS* 00000000 lzo_init.c
> 000021fc g F .text 000000c8 __lzo_init_v2
> 000247a0 g O .bss 00000004 __lzo_init_done
>
>> 3. If the symbol __lzo_init2 is not exported then find out if
>> something is wrong with liblzo2 builds that can result in this
>> exlusion
>
> Sorry, I do not know how to do that.
>
>
ok so it seems it needs to link with liblzo probably and not with liblzo2
> Thanks,
>
> Paul
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>
More information about the Openembedded-devel
mailing list