public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arjun.is at lostca dot se" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nss/26233] matchpathcon and security_context_t are deprecated by libselinux API Date: Thu, 23 Jul 2020 10:39:58 +0000 [thread overview] Message-ID: <bug-26233-131-D8RJrX7mvK@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26233-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26233 --- Comment #3 from Arjun Shankar <arjun.is at lostca dot se> --- The warnings due to these deprecated symbols have been suppressed leading up to 2.32: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=04726be814c6 This doesn't fix the actual bug but will let us build glibc-2.32 with -Werror on systems with libselinux >= 3.1. We should port to the new API before 2.33. There should be some ideas in this selinux development mailing list tread: https://lore.kernel.org/selinux/39f23208-c9df-c16d-6513-49b3fd234fc7@redhat.com/T/#t -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-23 10:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-13 13:09 [Bug nss/26233] New: " arjun.is at lostca dot se 2020-07-13 13:10 ` [Bug nss/26233] " arjun.is at lostca dot se 2020-07-16 15:25 ` jsegitz at suse dot de 2020-07-21 11:20 ` fweimer at redhat dot com 2020-07-21 11:43 ` glaubitz at physik dot fu-berlin.de 2020-07-21 11:48 ` glaubitz at physik dot fu-berlin.de 2020-07-21 11:52 ` schwab@linux-m68k.org 2020-07-22 21:18 ` arjun.is at lostca dot se 2020-07-23 10:39 ` arjun.is at lostca dot se [this message] 2022-09-12 22:28 ` cvs-commit at gcc dot gnu.org 2022-09-12 22:30 ` carlos at redhat dot com
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-26233-131-D8RJrX7mvK@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).