From: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Don't require libcap when building libsystemd-shared
Date: Thu, 31 May 2012 06:10:01 +0000 [thread overview]
Message-ID: <4FC70B39.9060902@kadzban.is-a-geek.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
src/shared/util.c includes <sys/capability.h> but doesn't use anything
defined there. Since <sys/capability.h> is part of libcap, not libc,
don't require it.
Allows systemd-without-udevd to require fewer external libraries.
Signed-Off-By: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
-----
Tested by building just systemd-udevd, as the previous patch.
Patch generated against current git again, as well.
[-- Attachment #2: remove-libcap-from-libsystemd-shared.patch --]
[-- Type: text/plain, Size: 302 bytes --]
diff --git a/src/shared/util.c b/src/shared/util.c
index 9db2a6b..67ec5ae 100644
--- a/src/shared/util.c
+++ b/src/shared/util.c
@@ -50,7 +50,6 @@
#include <linux/kd.h>
#include <dlfcn.h>
#include <sys/wait.h>
-#include <sys/capability.h>
#include <sys/time.h>
#include <glob.h>
#include <grp.h>
next reply other threads:[~2012-05-31 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 6:10 Bryan Kadzban [this message]
2012-05-31 9:59 ` [PATCH] Don't require libcap when building libsystemd-shared Kay Sievers
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=4FC70B39.9060902@kadzban.is-a-geek.net \
--to=bryan@kadzban.is-a-geek.net \
--cc=linux-hotplug@vger.kernel.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).