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: Wed, 22 Jul 2020 21:18:40 +0000	[thread overview]
Message-ID: <bug-26233-131-F5paQTks4d@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 #2 from Arjun Shankar <arjun.is at lostca dot se> ---
> This actually makes the build fail on m68k when building with -Werror:

Right. It already failed when building glibc for Fedora rawhide as well. There
is one additional problem area: nscd/selinux.c also uses some deprecated
symbols.

As of now, it appears that for 2.32, we will end up disabling these via a
compiler pragma to disable the warning, and work on porting to newer API once
2.32 is released.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-07-22 21:18 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 [this message]
2020-07-23 10:39 ` arjun.is at lostca dot se
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-F5paQTks4d@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).