All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: GeunSik Lim <leemgs1@gmail.com>
Cc: ltp-list@lists.sourceforge.net, Steve Grubb <sgrubb@redhat.com>,
	Andrew Morgan <morgan@kernel.org>
Subject: Re: [LTP] Report - make error of ltp-full-20090531.tgz
Date: Tue, 16 Jun 2009 11:19:49 -0500	[thread overview]
Message-ID: <20090616161949.GA32566@us.ibm.com> (raw)
In-Reply-To: <49b7c2350906152243p4c970b1di74cc62badc85a2e7@mail.gmail.com>

Quoting GeunSik Lim (leemgs1@gmail.com):
> On Tue, Jun 16, 2009 at 1:24 PM, Serge E. Hallyn<serue@us.ibm.com> wrote:
> > Quoting GeunSik Lim (leemgs1@gmail.com):
> >> I made patch file to solve below problem.
> >
> > well, NAK to the patch, but this is a real problem that needs to
> > be fixed.  I'll take a look in the morning, but Andrew do you know
> > offhand what the problem is with capability.h (in F11 I gather) that
> > would cause:
> Serge E. Hallyn,
> 
> Thanks for your opinion about  this report that I posted.
> Yes.  My below patch is private patch to solve  make error on Fedora 11
> distribution ( fedora11 2.6.29.4-167.fc11.i686).
> This means that my patch is not official patch file as you think.
> 
> For reference,
>  I used libcap 2.16 version
> at the  http://ftp.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.6/  .

Are you sure?

With the libcap-2.16 from kernel.org, /usr/include/sys/capability.h
#includes <sys/types.h>.  The version that comes with Fedora 11's
libcap-devel-2.16-2.fc11.i586 #includes <linux/types.h> instead.
When I just fix that, my F11 system compiles cap_bound.c just fine.

Steve, do you know why that change is made?

It then moves on to the next F11-specific compile failure, namely
LTP's <test.h> ends up #including /usr/include/asm/sigcontext.h
causing the compile errors bc of undefined __u64 and __u32,
which I can fix by adding:

#define __u64 u_int64_t
#define __u32 u_int32_t

to <sys/types.h>.  So perhaps it would be prudent to add them
to the top of LTP's test.h?

It woudl be better to figure out why that's happening in the
first place...

thanks,
-serge

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-06-16 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  1:13 [LTP] Report - make error of ltp-full-20090531.tgz GeunSik Lim
2009-06-16  1:57 ` GeunSik Lim
2009-06-16  4:24   ` Serge E. Hallyn
2009-06-16  5:43     ` GeunSik Lim
2009-06-16 16:19       ` Serge E. Hallyn [this message]
2009-06-16 16:45         ` Steve Grubb
2009-06-16 17:02           ` Serge E. Hallyn
2009-06-16 18:41           ` Serge E. Hallyn
2009-06-16 23:42             ` GeunSik Lim
2009-06-17 12:22               ` Steve Grubb
2009-06-17 13:10                 ` GeunSik Lim
2009-06-17 13:31                   ` Steve Grubb
2009-06-17 13:31                   ` Serge E. Hallyn

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=20090616161949.GA32566@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=leemgs1@gmail.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=morgan@kernel.org \
    --cc=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.