From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94231] Problems compiling libdrm since glibc 2.23
Date: Mon, 22 Feb 2016 23:39:33 +0000 [thread overview]
Message-ID: <bug-94231-502-eCwRzNVeBF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94231-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1111 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94231
Mike Frysinger <vapier@gentoo.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vapier@gentoo.org
--- Comment #12 from Mike Frysinger <vapier@gentoo.org> ---
it's really not that difficult to test for & include the sys/sysmacros.h header
directly when you're using the non-standard functions they provide. this is
the API under BSD systems, and where Linux C libs have already moved/are moving
towards. *this* is the deprecation period.
upstream glibc will take a more measured approach including updating their
docs, but realistically, no one is going to read those until they see breakage.
the Gentoo changes are only in an opt-in dev-only build, so it too isn't
hitting people randomly.
as the upstream thread shows, if you used the (long time documented)
AC_HEADER_MAJOR macro in autoconf, then this wouldn't have impacted drm.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2393 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-22 23:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 12:31 [Bug 94231] Problems compiling libdrm since glibc 2.23 bugzilla-daemon
2016-02-22 8:53 ` bugzilla-daemon
2016-02-22 10:26 ` bugzilla-daemon
2016-02-22 11:03 ` bugzilla-daemon
2016-02-22 11:39 ` bugzilla-daemon
2016-02-22 12:28 ` bugzilla-daemon
2016-02-22 12:34 ` bugzilla-daemon
2016-02-22 14:03 ` bugzilla-daemon
2016-02-22 14:09 ` bugzilla-daemon
2016-02-22 14:10 ` bugzilla-daemon
2016-02-22 14:16 ` bugzilla-daemon
2016-02-22 14:47 ` bugzilla-daemon
2016-02-22 17:34 ` bugzilla-daemon
2016-02-22 23:39 ` bugzilla-daemon [this message]
2016-02-23 14:03 ` bugzilla-daemon
2016-02-23 14:24 ` bugzilla-daemon
2016-02-23 14:40 ` bugzilla-daemon
2016-02-23 17:26 ` bugzilla-daemon
2016-02-23 20:24 ` bugzilla-daemon
2016-04-21 5:10 ` bugzilla-daemon
2016-04-21 12:26 ` bugzilla-daemon
2016-04-28 19:43 ` bugzilla-daemon
2016-04-30 19:59 ` bugzilla-daemon
2016-06-21 18:12 ` bugzilla-daemon
2016-06-21 18:13 ` bugzilla-daemon
2016-07-06 16:51 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-94231-502-eCwRzNVeBF@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox