Messages in this thread | | | Date | Wed, 26 Nov 2008 14:54:41 +0100 | From | Sam Ravnborg <> | Subject | Re: Detecting endianness in scripts/recordmcount.pl? |
| |
On Wed, Nov 26, 2008 at 05:39:05PM +0900, Paul Mundt wrote: > Presently there doesn't seem to be any way to determine whether the > target is big or little endian, and it is assumed that the compiler will > do the right thing by default. Unfortunately this can not be assumed, > and mismatches ensue, resulting in the linker bailing out. > > The only obvious solution I saw was to pass in KBUILD_CFLAGS and ld_flags > along with $(CC) and $(LD) to the script, and killing off the hardcoded > flags. This at least gets things building, but that still leaves objcopy > and objdump as the odd ones out. On the other hand, the format can be figured > out by objdumping the object and reading in the file format line, but people > obviously do not have consistent naming for these, and a double-pass would > be needed -- once for establishing little or big, followed by figuring out > which set of regexes to use. > > The CONFIG_64BIT test could likewise be adopted for testing endianness, but > not all architectures have config options for endian selections. But we could add this - no? Much better than executing objdump one thousand times.
Sam
| |