Re: How to fail an ARMv5T u-boot build when libgcc is ARMv7T2?

On Thu, Nov 10, 2011, Richard Earnshaw wrote:

The build attributes were never intended to be used in executables; the format is too expensive to decode in most situations. Instead the ABI specification included an optional PHEADER that had a highly simplified indication of the executable compatibility of an image (essentially the architecture). Unfortunately this has never been added to GNU Binutils.

See PT_ARM_ARCHEXT in the ARM ELF specification (available from infocenter).

As a poor man's test, would it be reliable to test Tag_CPU_name on the resulting u-boot ELF binary at the end of the build? If I read you correctly, you seem to suggest that it would be too fragile?