On 7/05/2015 9:59 p.m., Alex Dowad wrote:
> When included, musl libc's sys/signal.h issues a compiler warning
> stating that signal.h should be used directly instead. If gcc is
> treating all warnings as errors, this breaks the build.
>
> glibc's sys/signal.h does not contain any definitions; all
When included, musl libc's sys/signal.h issues a compiler warning
stating that signal.h should be used directly instead. If gcc is
treating all warnings as errors, this breaks the build.
glibc's sys/signal.h does not contain any definitions; all it does
is include signal.h (indirectly). So directl
