[oe] gcc-4.4.1 assembler error: offset out of range

Khem Raj raj.khem at gmail.com
Sun Apr 29 17:15:23 UTC 2012


On Sun, Apr 29, 2012 at 9:56 AM, Elvis Dowson <elvis.dowson at gmail.com> wrote:
> | /tmp/ccC0NmMi.s: Assembler messages:
> | /tmp/ccC0NmMi.s:36309: Error: offset out of range
> | /tmp/ccC0NmMi.s:36310: Error: offset out of range
> | /tmp/ccC0NmMi.s:36345: Error: offset out of range
> | /tmp/ccC0NmMi.s:36346: Error: offset out of range
> | /tmp/ccC0NmMi.s:36381: Error: offset out of range
> | /tmp/ccC0NmMi.s:36382: Error: offset out of range
> | /tmp/ccC0NmMi.s:36416: Error: offset out of range
> | /tmp/ccC0NmMi.s:36417: Error: offset out of range
> | make[2]: *** [insn-output.o] Error 1
> | make[2]: *** Waiting for unfinished jobs....
> | make[2]: Leaving directory `/tool/overo-oe/tmp/work/armv7a-angstrom-linux-gnueabi/gcc-4.4.1-r13.1/gcc-4.4.1/build.arm-angstrom-linux-gnueabi.arm-angstrom-linux-gnueabi/gcc'
> | make[1]: *** [all-gcc] Error 2

There could be that gcc is generating long branched which then
assembler catches. Usually these errors I remember dealing with was if
you compiled in thumb mode. But you seem to be not using thumb mode so
thats non issue here.

Another possibility is that the binutils/gas you have has bug in it.

You have to post the assembly output that assembler is rejecting here
for further details

Anyhow, when you are changing from 4.3.3 why to 4.4.1 and not 4.5 that
has been in OE for long and is default compiler for many OE based
distributions out there




More information about the Openembedded-devel mailing list