Not all operating systems name the GNU Make `make`. FreeBSD e.g. uses a
different dialect of Make, that seems to be incompatible with GNU make.
(I wasn't able to get `make` run, but `gmake` works).
This allows our test scripts to be configured via the environment
variable `MAKE` to point to a different make command.
This adds a small wrapper script to configure and start radvd on a
tun interface.
This allows the use of router advertisements and global adresses with
the `native` target.
Usage:
- first create the tap interface as usual
sudo dist/tools/tapsetup/tapsetup
- now run radvd on the new tapbr0 interface
sudo dist/tools/radvd/radvd.sh -c tapbr0 2001:db8::/64
- Now run the `gnrc_networking` example on native:
make -C examples/gnrc_networking all term
You should now see that the `native` node has received a global address
in `ifconfig`.
You should be able to reach this address from your host computer.
It may take very long for the native node to obtain the address.
If you are observing this, try turning off router advertisements of the
native node on the upstream interface by running
ifconfig 6 -rtr_adv
Alternatively change `USEMODULE += gnrc_ipv6_router_default` to
`USEMODULE += gnrc_ipv6_default` in the project's `Makefile`.
When building with make -j, flatbuffers is cloned by both the flatc build and the regular package build and from time to time a concurrency issue make the build to fail. Keeping regular flatbuffer package and flatc tool sources separate avoid this issue
Previously, uncrustify.sh would fail (report uncrustifying necessary) if
there was any output of uncrustify. Turns out uncrustify sometimes
outputs something.
This commit changes the logic to use uncrustify's output value as
indicator.
Also, adds printing which file causes the check to fail.
This adds a new subdirectory called `fuzzing/` which will contain
applications for fuzzing various RIOT network modules in the future.
This subdirectory is heavily inspired by the `examples/` subdirectory.
The fuzzing applications use AFL as a fuzzer. Each application contains
Makefiles, source code, and an input corpus used by AFL to generate
input for fuzzing.
