From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Debugging u-boot
Date: Thu, 07 Jul 2011 22:18:33 -0700 [thread overview]
Message-ID: <4E169329.3050702@gmail.com> (raw)
In-Reply-To: <F7C0AA5DD1508F4789E10B6CC9BB75DB04A78FCB@nzc-ap-xch-02.ap.trimblecorp.net>
On 07/07/2011 12:25 PM, Bernard Mentink wrote:
> Hi Charles,
>
> Tried that but got the following linker error:
>
> ---------------------------------------------------------- error ---------------------------------------
> | /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: failed to merge target specific data of file emutls_s.o
> | /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: error: /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o uses VFP register arguments, ./libgcc_s.so.1.tmp does not
> | /home/bernie/Stuff/build/tmp/sysroots/i686-linux/usr/armv6/arm-angstrom-linux-gnueabi/bin/ld: failed to merge target specific data of file /home/bernie/Stuff/build/tmp/work/i686-armv6-sdk-angstrom-linux-gnueabi/gcc-cross-sdk-4.5-r36.2+svnr170880/gcc-4_5-branch/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/crtendS.o
> | collect2: ld returned 1 exit status
> | make[2]: *** [libgcc_s.so] Error 1
this means there is fp ABI gotcha is it on latest oe.dev ? I remember
fixing the hard FP build on oe.dev see commit
888c1f3a2e103793bc03488d2051ee4683f7516a
I dont know if that was picked for 2011.03 release branch
next prev parent reply other threads:[~2011-07-08 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 23:25 Debugging u-boot Bernard Mentink
2011-07-07 0:37 ` Charles Manning
2011-07-07 1:13 ` Bernard Mentink
2011-07-07 1:51 ` Charles Manning
2011-07-07 19:25 ` Bernard Mentink
2011-07-08 5:18 ` Khem Raj [this message]
[not found] ` <201107121016.47983.manningc2@actrix.gen.nz>
2011-07-12 19:35 ` Bernard Mentink
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=4E169329.3050702@gmail.com \
--to=raj.khem@gmail.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.