public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix nscd HAVE_LIBCAP
Date: Fri, 23 Mar 2007 16:10:00 -0000	[thread overview]
Message-ID: <20070323161435.GB1826@sunsite.mff.cuni.cz> (raw)
In-Reply-To: <20070322164224.GA1826@sunsite.mff.cuni.cz>

On Thu, Mar 22, 2007 at 05:42:25PM +0100, Jakub Jelinek wrote:
> 2007-03-22  Jakub Jelinek  <jakub@redhat.com>
> 
> 	* config.h.in (HAVE_LIBCAP): Add.
> 	* nscd/selinux.h: Include sys/capability.h rather than non-existent
> 	sys/capabilities.h.
> 	* nscd/selinux.c (preserve_capabilities): Use cap_free instead of
> 	free_caps.  Cast away const from 4th cap_set_flag argument.

When this is applied, check-local-headers complains about sys/capability.h,
which isn't a glibc header.

Fixed thusly:

2007-03-23  Jakub Jelinek  <jakub@redhat.com>

	* scripts/check-local-headers.sh: Filter out sys/capability.h.

--- libc/scripts/check-local-headers.sh.jj	2007-01-15 23:25:30.000000000 +0100
+++ libc/scripts/check-local-headers.sh	2007-03-23 17:05:08.000000000 +0100
@@ -30,6 +30,7 @@ if fgrep "$includedir" */*.{o,os,oS}.d |
 fgrep -v "$includedir/asm" |
 fgrep -v "$includedir/linux" |
 fgrep -v "$includedir/selinux" |
+fgrep -v "$includedir/sys/capability.h" |
 fgrep -v "$includedir/gd"; then
   # If we found a match something is wrong.
   exit 1

	Jakub

      reply	other threads:[~2007-03-23 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 16:38 Jakub Jelinek
2007-03-23 16:10 ` Jakub Jelinek [this message]

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=20070323161435.GB1826@sunsite.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    /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).