From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Mitani <mitani@ryobi.co.jp>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] cap_bounds_r.c build failure
Date: Thu, 1 Apr 2010 10:26:47 -0500 [thread overview]
Message-ID: <20100401152647.GH22648@us.ibm.com> (raw)
In-Reply-To: <000001cad18d$ea091c60$be1b5520$@co.jp>
Quoting Mitani (mitani@ryobi.co.jp):
> Hi Rishi,
>
> I installed "libcap-devel", but after configure, build failed, too.
>
> ------------
> [root@RHEL4-8 mitani]# rpm -qa | grep libcap
> libcap-devel-1.10-20
> libcap-1.10-20
> [root@RHEL4-8 mitani]#
> ------------
>
> "libcap-1.10-20" version is normal version in my system (RHEL4.8
> 2.6.9-89.ELsmp).
> In this version, capability.h doesn't have CAP_LAST_CAP definition.
> I try to upgrade version "2.11".
Yeah, you need libcap2 for these tests. I guess we could stand
to add a rule to m4/ltp-cap.m4 to check for the existance of
libcap.so.2.X, X > oh say 12.
-serge
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-04-01 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 8:13 [LTP] cap_bounds_r.c build failure Mitani
2010-04-01 8:35 ` Rishikesh K Rajak
2010-04-01 9:23 ` Mitani
2010-04-01 9:35 ` Rishikesh K Rajak
2010-04-01 11:24 ` Mitani
2010-04-01 15:26 ` Serge E. Hallyn [this message]
2010-04-02 2:20 ` Mitani
2010-04-05 13:20 ` Serge E. Hallyn
2010-04-09 7:49 ` Mitani
2010-04-16 18:39 ` Garrett Cooper
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=20100401152647.GH22648@us.ibm.com \
--to=serue@us.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mitani@ryobi.co.jp \
/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