strcmp-armv4.S: Error: invalid constant (ff) after fixup

[Claudio Destro]

Hi guys,

Maybe a silly (or old) question… 

I am trying to cross compile newlib 2.2.0 for ARM under OS X El Capitan, but compilation fails with this errors:

../../../../../../../../newlib-2.2.0.20151023/newlib/libc/machine/arm/strcmp-armv4.S:108: Error: invalid constant (ff) after fixup
../../../../../../../../newlib-2.2.0.20151023/newlib/libc/machine/arm/strcmp-armv4.S:281: Error: invalid constant (ff) after fixup
../../../../../../../../newlib-2.2.0.20151023/newlib/libc/machine/arm/strcmp-armv4.S:330: Error: invalid constant (ff) after fixup
../../../../../../../../newlib-2.2.0.20151023/newlib/libc/machine/arm/strcmp-armv4.S:349: Error: invalid constant (ff) after fixup
../../../../../../../../newlib-2.2.0.20151023/newlib/libc/machine/arm/strcmp-armv4.S:367: Error: invalid constant (ff) after fixup
../../../../../../../../newlib-2.2.0.20151023/newlib/libc/machine/arm/strcmp-armv4.S:368: Error: invalid constant (ff) after fixup

How can I fix these???

Is there something wrong in my compilation process???

It seems arm-none-eabi-gcc accepts signed integer constants instead of unsigned ones. I mean, if I change #255 with #-1, the error disappears… Can it be?

What I did:

1- I compiled gcc-5.2.0 natively using clang
2- then built binutils 2.25 for arm-none-eabi using clang
3- recompiled gcc-5.2.0 (gcc only) for arm-elf-eabi using gcc-5.2.0 native (from step 1)
4- finally tried to compile newlib using gcc-5.2.0 (both native and arm-elf-eabi)

Thanks in advance!

{ "greetings": "Kind regards",
  “firstName": "Claudio”
  “lastName": "Destro” }