How to fail an ARMv5T u-boot build when libgcc is ARMv7T2?
wookey at wookware.org
Fri Nov 11 00:01:25 UTC 2011
+++ Loïc Minier [2011-11-10 17:44 +0100]:
> On Thu, Nov 10, 2011, Chung-Lin Tang wrote:
> > I'd assume the Ubuntu-packaged toolchain probably doesn't have a ARMv5
> > multilib? You could either expand the toolchain configuration and
> > rebuild, or more simply, use a CodeSourcery toolchain. Our default
> > multilib is ARMv5TE.
> Sorry, I didn't make my goal very clear: I'd like to prevent other
> people from hitting this problem. I know what the problem is about
> now, but I'd have preferred for the build to fail at some stage rather
> than for the build to succeed and for me to run an ARMv7 binary on an
> ARMv5 (virtual) board. (It wasn't easy to spot that the problem came
> from libgcc.)
Steve Magoun said at UDS that they (canonical OEM team I think?) had a
tool to spot binaries built for the wrong ARMvX flavour. That might be
useful in this case?
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
More information about the linaro-toolchain