unittests: Force execution of $(UNITTEST_LIBS) build target
core:debug: documentation for `DEBUG_PRINT` was confusing and wrong
native: fix coding style
native: set optional path with unix socket option

fixes #1045
Merge pull request #1214 from LudwigOrtmann/issue-1045

native: unix socket path enhancement
Merge pull request #1238 from authmillenon/makefile-unittests

unittests: Force execution of $(UNITTEST_LIBS) build target
x86: fix download script for OSX

Mac OSX does not have `wget`, but `curl`.
It does not understand `tar xJ`, but `tar xj`.
Merge pull request #1250 from Kijewski/x86-osx-fix-download

x86: fix download script for OSX
Merge pull request #1248 from thomaseichinger/debug_h_doc_fix

core:debug: documentation for `DEBUG_PRINT` was confusing and wrong
destiny: segfault due to dereferencing nullpointer
get_socket(i) returns NULL, when no specific socket is found.
Without an appropriate check for NULL, the current state
of the code leads to a segfault.

destiny: added parens

destiny: continuing the loop makes more sense than returning at first sight of NULL
Merge pull request #1269 from cgundogan/fix_get_waiting_connection_socket_null_check

destiny: segfault due to dereferencing nullpointer
core: fix variable name for sched_pidlist
Merge pull request #1272 from OlegHahm/sched_pidlist_fix

core: fix variable name for sched_pidlist
wireshark: fix dissector plugin and expand documentation

The wireshark dissector plugin currently fails with a "Lua Error" when
trying to parse nativenet packets. This patch restores working behaviour
by commenting the offending line introduced in 1258675, which intention
was to account for padding in small packets. It further adds a comment
on how to edit the plugin for the case padding information is required.

The README.md now contains a usage note for configuration on fedora
which might also be helpful for users of other distributions.
destiny: wireshark compliant tcp flags
This enum is also used to set the tcp flags within a tcp header.
With the current values in this enum, wireshark is not able to
recognize the tcp segments as their actual tcp type,
and thus odd messages in wireshark appear.

destiny: reusing tcp flags for combinations
core/cortex-m: add missing NORETURNs to thread_arch
Merge pull request #1274 from sgso/wireshark_dissector

wireshark: fix dissector plugin and expand documentation
native: add id option
Merge pull request #1192 from LudwigOrtmann/native_override_pid

native: add id option
destiny: change byte order of ipv6_header->length
When accessing the length field of an ipv6_header a byte order switch (host -> network) is necessary.
Otherwise, it breaks calculations or the checksum and other tcp related computations.
Furthermore, when writing to ipv6_header->length it is important to switch this
from host byte order to network byte order.