<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Problems compiling libdrm since glibc 2.23" href="https://bugs.freedesktop.org/show_bug.cgi?id=94231#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Problems compiling libdrm since glibc 2.23" href="https://bugs.freedesktop.org/show_bug.cgi?id=94231">bug 94231</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>Thanks for the links Mike. Not sure about others, but I'm not a happy bunny. So there's a issue/bug in stdlib.h (or was it g++), that leads to the inclusion of sys/types.h. To 'fix' this lets break the documented behaviour (for those of us that read the manpages). Hmm ... wait what ? Sorry but this sounds backwards. If we cannot squash the issue, it should be documented properly with list of workarounds (as pointed in the redhat bugzilla). Yes it sucks, big time. Yet we shouldn't break one thing, in order to workaround another issue, should we ? If this workaround is needed/applicable with other libc providers like musl (on Linux at least), then there should be a documentation update alongside the deprecation. Followed by a lengthy period _before_ removing things ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>