Skip to content
Snippets Groups Projects
Commit 7277cf8d authored by Oleg Hahm's avatar Oleg Hahm
Browse files

README: added note about GCCv6 problem

parent a701262c
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 7 additions and 0 deletions
README.md
+ 7
− 0
View file @ 7277cf8d
...@@ -63,6 +63,13 @@ RIOT is based on a microkernel architecture, and provides features including, bu ...@@ -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) * 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. * 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 ### 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` 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`
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment