Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-12-10
Date: Fri, 24 Dec 2010 18:28:20 +0100	[thread overview]
Message-ID: <if2l7k$6v8$1@dough.gmane.org> (raw)
In-Reply-To: <4D14B770.3000601@eukrea.com>

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

On 24-12-10 16:08, Eric Bénard wrote:
> Hi Khem,
> 
> On 16/12/2010 16:48, Khem Raj wrote:
>> On (16/12/10 08:55), Cliff Brake wrote:
>>> beagleboard beagleboard-linuxtag2010-demo-image is failing with:
>>>
>>> http://tinderbox.openembedded.net/packages/1321155/
>>>
>>> ti-c6accel
>>>
>>> Linking c6accel_app from appMain.o c6accel_testfxns.o
>>> ../c6accelw/lib/c6accelw_omap3530.a470MV
>>> c6accel_app_config/linker.cmd..
>>> /lib/libgcc_s.so.1: file not recognized: File format not recognized
>>
>>
>> Have you tried with latest .dev ? It might work with latest .dev
>> I have fixed libgcc install locations
>>
> I tested beagleboard-linuxtag2010-demo-image for machine beagleboard
> with today's master and it still fails with the following messages :
> 
> Linking c6accel_app from appMain.o c6accel_testfxns.o
> ../c6accelw/lib/c6accelw_omap3530.a470MV c6accel_app_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: c6accel_app_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:
> skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
> /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:
> skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
> /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
> make[2]: *** [c6accel_app] Error 1
> 
> Do you have any idea on how to fix this ?

That looks like the xdctools linkerscript problem we had before. Maybe
an xdc .clean and xdc .make would help.

regards,

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

iD8DBQFNFNg0MkyGM64RGpERAttfAJ4w1FuLClSrBfa0rUq8wSbUaBXJBACgnQhk
FtZ4xrzyf8LsMfP/Y7FC4pw=
=zMd/
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-12-24 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 16:05 testing branch 2010-12-10 Cliff Brake
2010-12-16 13:55 ` Cliff Brake
2010-12-16 15:48   ` Khem Raj
2010-12-24 15:08     ` Eric Bénard
2010-12-24 15:25       ` Khem Raj
2010-12-24 17:28       ` Koen Kooi [this message]
2010-12-25 18:31         ` Eric Bénard
2010-12-25 18:43           ` Eric Bénard
2010-12-25 19:59             ` Khem Raj
2010-12-25 21:15               ` 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='if2l7k$6v8$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox