From 7277cf8d467d201bd676a3aa84ba35efe786dfd0 Mon Sep 17 00:00:00 2001 From: Oleg Hahm Date: Mon, 13 Jun 2016 12:01:16 +0200 Subject: [PATCH] README: added note about GCCv6 problem --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 5fad55ed03..46ff77398e 100644 --- a/README.md +++ b/README.md @@ -63,6 +63,13 @@ RIOT is based on a microkernel architecture, and provides features including, bu * You want to start the RIOT? Just follow our [Getting started documentation](https://github.com/RIOT-OS/RIOT/wiki/Introduction) * The RIOT API itself can be built from the code using doxygen. The latest version is uploaded daily to http://riot-os.org/api. +## KNOWN ISSUES +* With latest GCC version (>= 6) platforms based on some ARM platforms will + raise some warnings, leading to a failing build + (see https://github.com/RIOT-OS/RIOT/issues/5519). + As a workaround, you can compile with warnings not being treated as errors: + `WERROR=0 make` + ### USING THE NATIVE PORT WITH NETWORKING If you compile RIOT for the native cpu and include the `netdev2_tap` module, you can specify a network interface like this: `PORT=tap0 make term`