public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>, Mitani <mitani@ryobi.co.jp>
Subject: Re: [LTP] 2010-02-01 cvs make problem
Date: Tue, 02 Feb 2010 11:29:46 -0500	[thread overview]
Message-ID: <1265128186.3114.7.camel@moss-pluto.epoch.ncsc.mil> (raw)
In-Reply-To: <364299f41002011635m8985236k3b2e75c7278ae5e3@mail.gmail.com>

On Mon, 2010-02-01 at 16:35 -0800, Garrett Cooper wrote:
> On Mon, Feb 1, 2010 at 12:52 PM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > On Mon, 2010-02-01 at 12:02 -0800, Garrett Cooper wrote:
> >> On Mon, Feb 1, 2010 at 6:20 AM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> >> > On Mon, 2010-02-01 at 00:44 -0800, Garrett Cooper wrote:
> >> >> On Mon, Feb 1, 2010 at 12:09 AM, Mitani <mitani@ryobi.co.jp> wrote:
> >> >> > Hi,
> >> >> >
> >> >> > I tried to build 2010-02-01 cvs in RHEL5.4 system.
> >> >> > (Archecture : x86 and x86_64)
> >> >> >
> >> >> >
> >> >> > "make" failed with following message:
> >> >> > ------------
> >> >> > [...]
> >> >> > make[5]: Entering directory
> >> >> > `/home/LTP/ltp-2010-02-01/testcases/kernel/security/selinux-testsuite/refpol
> >> >> > icy'
> >> >> > (cd
> >> >> > "/home/LTP/ltp-2010-02-01/testcases/kernel/security/selinux-testsuite/refpol
> >> >> > icy/policy_files/generic" && cat test_global.te test_bounds.te
> >> >
> >> > Hmm...this indicates that your Makefile rewrite still isn't working
> >> > properly on RHEL5, where it is supposed to use the files under
> >> > refpolicy/policy_files/redhat-5 instead of generic.
> >> >
> >> >> > test_capable_file.te test_capable_net.te test_capable_sys.te
> >> >> > test_dyntrace.te test_dyntrans.te test_entrypoint.te test_execshare.te
> >> >> > test_exectrace.te test_execute_no_trans.te test_fdreceive.te test_file.te
> >> >> > test_inherit.te test_ioctl.te test_ipc.te test_link.te test_mkdir.te
> >> >> > test_open.te test_ptrace.te test_readlink.te test_relabel.te test_rename.te
> >> >> > test_rxdir.te test_setattr.te test_setnice.te test_sigkill.te test_stat.te
> >> >> > test_sysctl.te test_task_create.te test_task_getpgid.te
> >> >> > test_task_getsched.te test_task_getsid.te test_task_setpgid.te
> >> >> > test_task_setsched.te test_transition.te test_wait.te) > test_policy.te
> >> >> > cat: /selinux/mls: No such file or directory
> >> >
> >> > And this suggests that the tester does not have SELinux enabled in his
> >> > kernel.  You shouldn't enable the SELinux testsuite unless SELinux is
> >> > enabled in the kernel.  You can test with something akin to:
> >> > if [ -x /usr/sbin/selinuxenabled ] && selinuxenabled; then
> >> >        <run selinux testsuite>
> >> > fi
> >> >
> >> >
> >> >> > make[6]: Entering directory
> >> >> > `/home/LTP/ltp-2010-02-01/testcases/kernel/security/selinux-testsuite/refpol
> >> >> > icy'
> >> >> > Compiling targeted test_policy module
> >> >> > test_policy.te:129:ERROR 'syntax error' at token 'typebounds' on line 93991:
> >> >> > # Definition of boundary relationship
> >> >> > typebounds test_bounds_parent_t test_bounds_child_t;
> >> >> > /usr/bin/checkmodule:  error(s) encountered while parsing configuration
> >> >> > /usr/bin/checkmodule:  loading policy configuration from tmp/test_policy.tmp
> >> >
> >> > And apparently your Makefile logic to exclude test_bounds.te if
> >> > CHECKPOLICYVERS is not 24 isn't working either, although it wouldn't try
> >> > if it was using the right subdirectory.
> >>
> >> Mitani-san -- could you do the following please?
> >>
> >> 1. cat out your /etc/issue file.
> >> 2. Provide the output for $srcdir/scripts/detect_distro.sh
> >
> > Doesn't seem to be stripping the minor version.
> > $ ./scripts/detect_distro.sh
> > redhat-5.4
> > $ ./scripts/detect_distro.sh  -m
> > redhat-5.4
> 
> Ok -- what's the input (/etc/issue)?

Do you mean /etc/redhat-release?
Red Hat Enterprise Linux Client release 5.4 (Tikanga)

Maybe it would be more portable to use lsb_release(1)

# lsb_release -i
Distributor ID:	RedHatEnterpriseClient
# lsb_release -d
Description:	Red Hat Enterprise Linux Client release 5.4 (Tikanga)
# lsb_release -r
Release:	5.4

-- 
Stephen Smalley
National Security Agency


------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2010-02-02 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  8:09 [LTP] 2010-02-01 cvs make problem Mitani
2010-02-01  8:44 ` Garrett Cooper
2010-02-01 14:20   ` Stephen Smalley
2010-02-01 20:02     ` Garrett Cooper
2010-02-01 20:52       ` Stephen Smalley
2010-02-02  0:35         ` Garrett Cooper
2010-02-02 16:29           ` Stephen Smalley [this message]
2010-02-02 17:01             ` 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=1265128186.3114.7.camel@moss-pluto.epoch.ncsc.mil \
    --to=sds@tycho.nsa.gov \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=mitani@ryobi.co.jp \
    --cc=yanegomi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox