Felix Raimundo 33226cc3a9 Dirty fix device build. ...

It seems that gcc generates instructions it cannot use which is weird.
The offending line was:
char input[255] = {0};

It was trying tp use __eabi_memclr for that which it did not have.

We need to find out why it generates instruction it cannot use (probably some
wrong flags somewhere).

Change-Id: I6a05280ce8876aa50e2cd6d5a112d18d266581c4

2016-04-08 18:23:18 +02:00

4.5 KiB

Raw Blame History

View Raw