From: Matt Johnson <johnso87@crhc.illinois.edu>
To: angstrom-distro-devel@linuxtogo.org,
openembedded-devel@lists.openembedded.org
Subject: Re: Can't build gstreamer-ti
Date: Tue, 09 Nov 2010 09:06:44 -0600 [thread overview]
Message-ID: <4CD96384.70100@crhc.illinois.edu> (raw)
In-Reply-To: <mailman.0.1289314919.16967.angstrom-distro-devel@linuxtogo.org>
On 08/10/2010 04:58 AM, Gary Thomas wrote:
On 08/09/2010 04:37 PM, Chethan Pandarinath wrote:
This seems to be the same error:
http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/42905.aspx
With the problem being that the cl6x compiler isn't bundled with the
rest of
the toolchain, and has to be downloaded separately.
But I've downloaded those tools and was able to build this recipe just
a few weeks ago. I think something in the staged packaging has broken it.
I worked past this problem by installing a symlink by hand to my DVSDK
installed tools.
Next problem :-(
|
/local/Angstrom_BeagleBoard/tmp/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/../../../../arm-angstrom-linux-gnueabi/bin/ld:
warning: package/cfg/bin/ti_platforms_evm3530/app_remote_xv5T.xdl
contains output sections; did you forget -T? |
/local/Angstrom_BeagleBoard/tmp/work/beagleboard-angstrom-linux-gnueabi/ti-codec-engine-2_25_01_06-r5/codec_engine_2_25_01_06/packages/ti/sdo/ce/lib/release/ce.av5T(Engine.ov5T):
In function `Engine_deleteNode':
| Engine.c:(.text+0x19d4): undefined reference to `__aeabi_uidiv'
|
/local/Angstrom_BeagleBoard/tmp/work/beagleboard-angstrom-linux-gnueabi/ti-codec-engine-2_25_01_06-r5/codec_engine_2_25_01_06/packages/ti/sdo/ce/osal/linux/lib/release/osal_linux_470.av5T(Global_noOS.ov5T):
In function `Global_atexit':
| Global_noOS.c:(.text+0x238): undefined reference to `atexit'
|
/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/share/ti/ti-dsplink-tree/packages/dsplink/gpp/export/BIN/Linux/OMAP3530/RELEASE/dsplink.lib:
In function `_RingIO_writerAcquire':
| ringio.c:(.text+0x24e4): undefined reference to `__aeabi_uidivmod'
| ringio.c:(.text+0x261c): undefined reference to `__aeabi_uidivmod'
| ringio.c:(.text+0x2654): undefined reference to `__aeabi_uidivmod'
|
/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/share/ti/ti-dsplink-tree/packages/dsplink/gpp/export/BIN/Linux/OMAP3530/RELEASE/dsplink.lib:
In function `_RingIO_readerAcquire':
| ringio.c:(.text+0x28ac): undefined reference to `__aeabi_uidivmod'
| ringio.c:(.text+0x2bd4): undefined reference to `__aeabi_uidivmod'
|
/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/share/ti/ti-dsplink-tree/packages/dsplink/gpp/export/BIN/Linux/OMAP3530/RELEASE/dsplink.lib:ringio.c:(.text+0x2eb4):
more undefined references to `__aeabi_uidivmod' follow |
/local/Angstrom_BeagleBoard/tmp/sysroots/beagleboard-angstrom-linux-gnueabi/usr/share/ti/ti-dsplink-tree/packages/dsplink/gpp/export/BIN/Linux/OMAP3530/RELEASE/dsplink.lib:
In function `DRV_installCleanupRoutines':
| ringio.c:(.text+0x9354): undefined reference to `atexit'
| collect2: ld returned 1 exit status
| make[1]: *** [bin/ti_platforms_evm3530/app_remote.xv5T] Error 1
| gmake: ***
[/local/Angstrom_BeagleBoard/tmp/work/beagleboard-angstrom-linux-gnueabi/ti-codec-engine-2_25_01_06-r5/codec_engine_2_25_01_06/examples/ti/sdo/ce/examples/apps/speech,.executables]
Error 2
| make[1]: *** [all] Error 2
| make[1]: Leaving directory
`/local/Angstrom_BeagleBoard/tmp/work/beagleboard-angstrom-linux-gnueabi/ti-codec-engine-2_25_01_06-r5/codec_engine_2_25_01_06/examples/ti/sdo/ce/examples/apps/speech'|
make: *** [all] Error 2 NOTE: package ti-codec-engine-2_25_01_06-r5:
task do_compile: Failed ERROR: TaskFailed event exception, aborting
ERROR: Build of
/local/Angstrom_BeagleBoard/openembedded/recipes/ti/ti-codec-engine_2.25.01.06.bb
do_compile failed
I wasn't subscribed to the Angstrom-devel list when this was posted, so please excuse the improper quoting.
I ran into this problem as well attempting to build ti-codec-engine with binutils 2.20 (Angstrom 2010).
It turns out that the problem is a linker script generated by TI XDCTools. The issue, and a workaround, is documented here:http://www.eclipse.org/forums/index.php?t=tree&th=197704&S=bf2c36fb547f9973f300fdf573c34d81#page_top <http://www.eclipse.org/forums/index.php?t=tree&th=197704&S=bf2c36fb547f9973f300fdf573c34d81#page_top>
I tested the workaround in my OE tree and it worked fine. Thought I'd post that in case others were still having trouble.
We can either make a patch in ti-xdctools to remove the offending lines from the linker script generators, wait for XDCTools 3.21 to be released and quickly get a recipe going for that, or both.
XDCTools 3.21 should be available here (http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/index.html ) when it's released.
Best,
-Matt
next parent reply other threads:[~2010-11-09 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1289314919.16967.angstrom-distro-devel@linuxtogo.org>
2010-11-09 15:06 ` Matt Johnson [this message]
2010-11-09 18:14 ` Can't build gstreamer-ti Gary Thomas
2010-11-09 18:28 ` Matt Johnson
2010-11-09 21:55 ` Henning Heinold
2011-03-07 23:42 Gary Thomas
2011-03-08 7:19 ` Maksym Parkachov
2011-03-09 6:41 ` Khem Raj
2011-03-09 16:55 ` Gary Thomas
2011-04-19 22:39 ` Tim Harvey
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=4CD96384.70100@crhc.illinois.edu \
--to=johnso87@crhc.illinois.edu \
--cc=angstrom-distro-devel@linuxtogo.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 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.