[oe] [oe-core] gstreamer-ti, questions

[Joel A Fernandes]

On Thu, Aug 4, 2011 at 8:04 PM, Joel A Fernandes <agnel.joel at gmail.com> wrote:
> On Thu, Aug 4, 2011 at 2:44 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>
>> Op 3 aug. 2011, om 18:28 heeft Enrico Butera het volgende geschreven:
>>
>>> I've started importing bb files from oe classic into
>>> meta-texasinstruments, i still not have a clean build of everything
>>> but here are some "basic" questions:
>>>
>>> - cross compiler binaries:
>>>
>>> in classic oe there were
>>> "sysroots/i686-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-[gcc,ld...]"
>>> and "sysroots/i686-linux/usr/armv7a/arm-angstrom-linux-gnueabi/bin/[gcc,ld...]",
>>> some ti tools use one, some the other. Now there is only
>>> usr/bin/armv7a..... and this "confuses" some ti tools.
>>>
>>> The question is: what is the proper way to handle this? patch gcc
>>> install to have a similar layout to classic oe? patch ti tools to
>>> "fix" them?
>>
>>
>> Joel was running into similar problems with https://github.com/joelagnel/meta-texasinstruments/commits/master can you guys have a look at it together?
>>
>
> I think its cleaner to have the toolchain to define symlinks in /bin
>
> I've done this in the gcc-cross recipe in do_install (which is
> hopefully the right place to do it)
>
> http://www.hackerbliss.org/joel/cgit/cgit.cgi/oe-core/commit/?id=2878a712aabf839cb4c6e84961b6e8deafacf824
>
> Now ti-codec-engine codecs, extensions and server builds but the
> 'apps' fails to build with a linker error.
>
> Here's the compiler log:
> [..]
> #
> # lnkv5T bin/ti_platforms_evm3530/app_remote.xv5T ...
> /home/joel/angstrom-oe/setup-scripts-core/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-gcc
>   -o bin/ti_platforms_evm3530/app_remote.xv5T
> package/cfg/bin/ti_platforms_evm3530/app_remote/main_native.ov5T
> package/cfg/bin/ti_platforms_evm3530/app_remote_xv5T.ov5T
> package/cfg/bin/ti_platforms_evm3530/app_remote/app.ov5T
> package/cfg/bin/ti_platforms_evm3530/app_remote_xv5T.xdl
> -L/home/joel/angstrom-oe/setup-scripts-core/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/lib
> -lpthread


Interestingly the path:
/home/joel/angstrom-oe/setup-scripts-core/build/tmp-angstrom_2010_x-eglibc/sysroots/i686-linux/usr/bin/armv7a-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/lib

doesn't exist, which explains the symbol errors.

libgcc contains the symbol `__aeabi_uidivmod'

Does this point to another problem with the toolchain? How would we fix this?

thanks,
Joel