From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ti-c6accel-1_01_00_01: link error
Date: Thu, 30 Dec 2010 21:53:50 +0100 [thread overview]
Message-ID: <4D1CF15E.4020003@eukrea.com> (raw)
In-Reply-To: <ifipuv$nbt$1@dough.gmane.org>
On 30/12/2010 21:27, Koen Kooi wrote:
>
> If you build the new xdctools with the linker hack (
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=7993e4ca7746a4ca9e7116cc76e6c1da32a76690
> ) then you only need a few changes to make it all build:
>
> 1) edit
> conf/distro/include/angstrom-codec-engine-latest-preferred-versions.inc:
>
> - -PREFERRED_VERSION_ti-linuxutils = "2_25_05_11"
> +PREFERRED_VERSION_ti-linuxutils = "2_26_01_02"
>
> - -PREFERRED_VERSION_ti-xdctools = "3_20_05_76"
> +PREFERRED_VERSION_ti-xdctools = "3_20_06_81"
>
> 2) Add -fPIC to C_FLAGS in the c6accel soc/ Makefiles (plural)
>
> 3) remove -Werror from DMAI makefiles
>
> 4) remove -Werror from gstreamer-ti makefiles
>
> That will get you a succesfull build, but you will have some runtime
> problems. My current goal is to get c6accel working on my USRP E100 so
> gnuradio can use that, so gst-ti is out of scope for that.
>
thanks, I'll try that.
In order to finish the image build, I removed gstreamer-ti from
beagleboard-linuxtag2010-demo-image which also "fixed" the problem as I don't
need gst-ti for my tests ;-)
Eric
prev parent reply other threads:[~2010-12-30 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 9:18 ti-c6accel-1_01_00_01: link error Eric Bénard
2010-12-30 11:48 ` Koen Kooi
2010-12-30 18:35 ` Koen Kooi
2010-12-30 18:55 ` Eric Bénard
2010-12-30 19:09 ` Eric Bénard
2010-12-30 20:27 ` Koen Kooi
2010-12-30 20:53 ` Eric Bénard [this message]
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=4D1CF15E.4020003@eukrea.com \
--to=eric@eukrea.com \
--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.