public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Romu <huruomu@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] /usr/include/linux/capability.h:70: error: expected specifier-qualifier-list before ‘__le32’
Date: Wed, 08 Aug 2012 12:27:11 +0800	[thread overview]
Message-ID: <5021EA9F.1090606@cn.fujitsu.com> (raw)
In-Reply-To: <CANoG8sX7V5VFgHdm7O2r1E4DXrfFM9jDeP2WDyD7roMXkGe-RA@mail.gmail.com>

On 07/30/2012 10:58 AM, Romu wrote:
> Hi,
> 
> I tried building LTP-20120614 on CentOS5 but it always failed (see
> error message below).  LTP-20120401 builds fine on CentOS5.
> 
> make[3]: Entering directory
> `/dev/shm/ltp-full-20120614/testcases/kernel/security'
> make[4]: Entering directory
> `/dev/shm/ltp-full-20120614/testcases/kernel/security/cap_bound'
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> -I/dev/shm/ltp-full-20120614/testcases/kernel/include
> -I../../../../include -I../../../../include   -L../../../../lib
> cap_bounds_r.c   -lltp  -o cap_bounds_r
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> -I/dev/shm/ltp-full-20120614/testcases/kernel/include
> -I../../../../include -I../../../../include   -L../../../../lib
> cap_bounds_rw.c   -lltp  -o cap_bounds_rw
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> -I/dev/shm/ltp-full-20120614/testcases/kernel/include
> -I../../../../include -I../../../../include   -L../../../../lib
> cap_bset_inh_bounds.c   -lltp  -o cap_bset_inh_bounds
> gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall
> -I/dev/shm/ltp-full-20120614/testcases/kernel/include
> -I../../../../include -I../../../../include   -L../../../../lib
> check_pe.c   -lltp  -o check_pe
> In file included from /usr/include/sys/capability.h:34,
>                  from cap_bset_inh_bounds.c:32:
> /usr/include/linux/capability.h:70: error: expected
> specifier-qualifier-list before ‘__le32’
> In file included from /usr/include/sys/capability.h:34,
>                  from cap_bounds_rw.c:29:
> /usr/include/linux/capability.h:70: error: expected
> specifier-qualifier-list before ‘__le32’
> In file included from /usr/include/sys/capability.h:34,
>                  from cap_bounds_r.c:30:
> /usr/include/linux/capability.h:70: error: expected
> specifier-qualifier-list before ‘__le32’
> In file included from /usr/include/sys/capability.h:34,
>                  from check_pe.c:33:
> /usr/include/linux/capability.h:70: error: expected
> specifier-qualifier-list before ‘__le32’
> cap_bset_inh_bounds.c:128:2: warning: no newline at end of file
> make[4]: *** [cap_bset_inh_bounds] Error 1
> make[4]: *** Waiting for unfinished jobs....
> cap_bounds_rw.c: In function ‘main’:
> cap_bounds_rw.c:82: warning: unused variable ‘i’
> cap_bounds_rw.c:81: warning: unused variable ‘ret’
> make[4]: *** [cap_bounds_rw] Error 1
> make[4]: *** [cap_bounds_r] Error 1
> check_pe.c:88:2: warning: no newline at end of file
> make[4]: *** [check_pe] Error 1
> make[4]: Leaving directory
> `/dev/shm/ltp-full-20120614/testcases/kernel/security/cap_bound'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory
> `/dev/shm/ltp-full-20120614/testcases/kernel/security'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/dev/shm/ltp-full-20120614/testcases/kernel'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/dev/shm/ltp-full-20120614/testcases'
> make: *** [testcases-all] Error 2
> 
> 
> I found:
> http://osdir.com/ml/debian-bugs-dist/2009-12/msg00664.html
> https://bugs.gentoo.org/show_bug.cgi?id=264770
> 
> But still can't figure out how to fix the issue.
> Any idea?

Can you test this patch ? 
http://marc.info/?l=ltp-list&m=134392485410819&w=2

Thanks,
Wanlong Gao

> 
> Thanks
> Romu
> 
> ------------------------------------------------------------------------------
> 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
> 


------------------------------------------------------------------------------
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-08-08  4:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30  2:58 [LTP] /usr/include/linux/capability.h:70: error: expected specifier-qualifier-list before ‘__le32’ Romu
2012-08-08  4:27 ` Wanlong Gao [this message]
2012-08-08  4:51   ` Romu
2012-08-08  5:24     ` 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=5021EA9F.1090606@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=huruomu@gmail.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