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
2016-04-08 18:23:18 +02:00
2016-04-08 13:43:57 +02:00
2016-04-04 11:05:49 +02:00
2016-03-22 18:39:59 +01:00
2015-09-21 10:37:55 +02:00
2016-04-08 13:43:55 +02:00
2016-04-07 15:51:16 +02:00
2015-09-17 12:18:53 +02:00
2015-05-02 13:25:27 +02:00
wip
2016-04-01 15:04:41 +02:00
2016-03-18 14:33:53 +01:00
2016-03-22 18:39:59 +01:00
2015-05-02 13:25:27 +02:00
2015-05-08 21:06:09 +02:00
Description
No description provided
44 MiB
Languages
C++ 60.3%
C 31.1%
Python 3.4%
Java 1.9%
Makefile 1.6%
Other 1.5%