public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Vinson Lee <vlee@twitter.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] filecaps: Fix build.
Date: Mon, 11 Jun 2012 18:27:25 -0700	[thread overview]
Message-ID: <1339464445-21694-1-git-send-email-vlee@twitter.com> (raw)

Fix build error that was introduced at commit
66ad27e08d774c572e99e97cc9b885295ec0aa55.

gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
-I/tmp/ltp/testcases/kernel/include -D_GNU_SOURCE -I../../../../include
-I../../../../include -L../../../../lib c.c -lltp -o c c.c:22:28: fatal
error: sys/capability.h: No such file or directory

Signed-off-by: Vinson Lee <vlee@twitter.com>
---
 testcases/kernel/security/filecaps/c.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/testcases/kernel/security/filecaps/c.c b/testcases/kernel/security/filecaps/c.c
index 38c1516..fbd0365 100644
--- a/testcases/kernel/security/filecaps/c.c
+++ b/testcases/kernel/security/filecaps/c.c
@@ -19,7 +19,9 @@
 /******************************************************************************/
 
 #include <stdio.h>
+#if HAVE_SYS_CAPABILITY_H
 #include <sys/capability.h>
+#endif
 
 int main()
 {
-- 
1.7.9.5


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2012-06-12  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12  1:27 Vinson Lee [this message]
2012-06-12  8:25 ` [LTP] [PATCH] filecaps: Fix build Wanlong Gao

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=1339464445-21694-1-git-send-email-vlee@twitter.com \
    --to=vlee@twitter.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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