All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ti-c6accel-1_01_00_01: link error
Date: Thu, 30 Dec 2010 21:27:11 +0100	[thread overview]
Message-ID: <ifipuv$nbt$1@dough.gmane.org> (raw)
In-Reply-To: <4D1CD8F2.6000209@eukrea.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30-12-10 20:09, Eric Bénard wrote:
> Hi Koen,
> 
> same problems exists with ti-dmai (which also shows another one as a
> bonus ;-)
> 
> oe master + angstrom-2010.x + beagleboard leads to :
> 
> .../... /usr/include -Dxdc_target_name__=arm/GCArmv5T -g -Wall -Werror
> -c -o obj/linux/Capture.omap3530.o470MV linux/Capture.c
> cc1: warnings being treated as errors
> In file included from
> /home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/sysroots/beagleboard-angstrom-linux-gnueabi/kernel/include/linux/videodev2.h:66:0,
> 
>                  from linux/Capture.c:43:
> /home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/sysroots/beagleboard-angstrom-linux-gnueabi/kernel/include/linux/types.h:13:2:
> error: #warning "Attempt to use kernel headers from user space, see
> http://kernelnewbies.org/KernelHeaders"
> make[1]: *** [obj/linux/Capture.omap3530.o470MV] Error 1
> 
> this can be "fixed" by removing -Werror in the makefile but then I meet
> the same problem as with ti-c6accel :
> 
> Linking linux/audio_decode1_omap3530.x470MV from appMain.omap3530.o470MV
> linux/main.omap3530.o470MV linux/audio_decode1_omap3530_config/linker.cmd..
> /home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/sysroots/i686-linux/usr/armv7a/bin/arm-angstrom-linux-gnueabi-gcc
>  -lpthread -lm
> -L/home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib
> -lasound -Wl,-Map,linux/audio_decode1_omap3530.x470MV.map -o
> linux/audio_decode1_omap3530.x470MV appMain.omap3530.o470MV
> linux/main.omap3530.o470MV linux/audio_decode1_omap3530_config/linker.cmd
> /home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.5.3/../../../../arm-angstrom-linux-gnueabi/bin/ld:
> warning: linux/audio_decode1_omap3530_config/linker.cmd contains output
> sections; did you forget -T?
> /home/ebenard/OMAP/2010/angstrom-setup-scripts/build/tmp-angstrom_2010_x/sysroots/i686-linux/usr/armv7a/lib/gcc/arm-angstrom-linux-gnueabi/4.5.3/../../../../arm-angstrom-linux-gnueabi/bin/ld:
> .gnu.attributes not found for insert
> collect2: ld returned 1 exit status

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.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNHOseMkyGM64RGpERAvFLAKCRUN2pJozNFVUR5Z/dR4vcut6sqQCfTXFR
W+ztBNtzo3I2C70qMexOVV8=
=U6CK
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-12-30 20:27 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 [this message]
2010-12-30 20:53         ` Eric Bénard

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='ifipuv$nbt$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.