Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Weidner <klaus@atsec.com>
To: "Williams, P. Lane" <Lane.Williams@jhuapl.edu>
Cc: linux-audit@redhat.com
Subject: Re: auditctl question
Date: Thu, 3 Aug 2006 15:29:20 -0500	[thread overview]
Message-ID: <20060803202920.GD5964@w-m-p.com> (raw)
In-Reply-To: <17B584B5C0638745ADF6002331331FDFA7D6F1@aplesliberty.dom1.jhuapl.edu>

On Thu, Aug 03, 2006 at 04:02:56PM -0400, Williams, P. Lane wrote:
> I installed the 2.6.17.7 kernel and then tried to build audit-1.2.5 and received the following...
> 
> make[2]: Entering directory `/tmp/audit/audit-1.2.5/src'
> gcc -D_REENTRANT -D_GNU_SOURCE -g -O2 -o auditd -pie -Wl,-z -Wl,relro auditd-auditd.o auditd-auditd-event.o auditd-auditd-config.o auditd-auditd-reconfig.o auditd-auditd-sendmail.o auditd-auditd-dispatch.o  -lpthread -L/tmp/audit/audit-1.2.5/src/mt -lauditmt
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../lib   -D_REENTRANT -D_GNU_SOURCE -g -O2 -c auditctl.c
> auditctl.c: In function ‘audit_print_reply’:
> auditctl.c:1046: error: ‘AUDIT_SE_USER’ undeclared (first use in this function)
> auditctl.c:1046: error: (Each undeclared identifier is reported only once
> auditctl.c:1046: error: for each function it appears in.)
> auditctl.c:1047: error: ‘AUDIT_SE_CLR’ undeclared (first use in this function)
> 
> I also received the same error with the other kernel.  I did not build the SE-Linux stuff into the kernel, should I have?

Audit should not require SELinux, but I don't think it currently gets
much testing with SELinux turned off which can cause such build issues.
Steve, do you have a fix for this?

-Klaus

  reply	other threads:[~2006-08-03 20:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 17:14 New List Member: Intro & comments Clif Flynt
2006-07-31 17:54 ` Steve Grubb
2006-08-07  9:37   ` Marcus Meissner
2006-07-31 20:05 ` SQLite Clarification Clif Flynt
2006-07-31 21:13   ` Steve Grubb
2006-08-02 20:49     ` auditctl question Lane Williams
2006-08-02 22:03       ` Steve Grubb
2006-08-02 22:15         ` Linda Knippers
2006-08-02 22:29           ` Steve Grubb
2006-08-03  0:22       ` Klaus Weidner
2006-08-03 13:00         ` Williams, P. Lane
2006-08-03 15:18           ` Klaus Weidner
2006-08-03 20:02             ` Williams, P. Lane
2006-08-03 20:29               ` Klaus Weidner [this message]
2006-08-03 21:06               ` Steve Grubb
2006-08-04  1:50                 ` Williams, P. Lane
2006-08-04 10:28                   ` Steve Grubb
2006-08-04 12:48                     ` Lane Williams
2006-07-31 22:05   ` SQLite Clarification Clif Flynt
  -- strict thread matches above, loose matches on Subject: below --
2007-03-21 17:03 auditctl Question Khoa V. Nguyen
2007-03-22 13:57 ` Steve Grubb

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=20060803202920.GD5964@w-m-p.com \
    --to=klaus@atsec.com \
    --cc=Lane.Williams@jhuapl.edu \
    --cc=linux-audit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox