Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Konrad Witaszczyk <def@freebsd.org>
Subject: Re: How can I install the latest version of Linux Audit on CentOS 6.8?
Date: Fri, 15 Jul 2016 09:17:00 -0400	[thread overview]
Message-ID: <2326978.VhGrlLPiTR@x2> (raw)
In-Reply-To: <DA0F677D-1DB2-44D8-9E58-76DA8667EFFA@FreeBSD.org>

On Friday, July 15, 2016 2:52:02 PM EDT Mateusz Piotrowski wrote:
> I’m trying to update the 2013 version of auditd on a just installed CentOS
> 6.8-i386.
>
> So far I’ve downloaded audit-userspace from GitHub[1] and I’ve faced a
> couple of problems:
> 
> 1. README says that I should consult the README-install file. I cannot see
> this file. Where is it? 2. I consulted the INSTALL.tmp and since I’ve not
> got any ./configure file inside my clone I deducted I’ve got to run
> ./autogen.sh. I was missing some dependencies so I ran `yum install
> autoconf automake libtool`.
> 
>  Then I ran `./configure --sbindir=/sbin --with-python=yes --with-libwrap
> --enable-gssapi-krb5=yes --with-libcap-ng=yes` but the command failed at
> this is a part of the log I got (the full log file is available here[2]):
> 
>     configure: WARNING: unrecognized options: --with-libcap-ng
>     ...
>     Checking for programs
>     ...
>     ./configure: line 13130: AX_PROG_CC_FOR_BUILD: command not found
>     ...
>     Checking for header files
>     ...
>     checking for python... /usr/bin/python
>     checking for python version... 2.6
>     checking for python platform... linux2
>     checking for python script directory...
> ${prefix}/lib/python2.6/site-packages checking for python extension module
> directory... ${exec_prefix}/lib/python2.6/site-packages configure: error:
> Python explicitly requested and python headers were not found
> 
>  Have you got any idea what the problem is?

Probably missing dependencies that would have been detected by building from a 
spec file.
 
> Is there an easier way to get the latest Linux Audit version on my system?

Why wouldn't you start with the distribution tar file?

http://people.redhat.com/sgrubb/audit/audit-2.6.5.tar.gz

If you are creating a distributable tar file for compilation, that would assume 
that you already had all dependencies solved on your system. The distributable 
tar file above was created on a system with all dependencies solved and the 
latest auto tools so that platforms are correctly detected.

If you want it packaged, then start with the Centos 6.8 spec file and adjust 
accordingly. The spec file shipped is aimed at future systems that are systemd 
based. So, you'd want to start with a spec file that was intended for the OS 
that you are using.

-Steve


--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2016-07-15 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 12:52 How can I install the latest version of Linux Audit on CentOS 6.8? Mateusz Piotrowski
2016-07-15 13:17 ` Steve Grubb [this message]
2016-07-18 15:39   ` Mateusz Piotrowski
2016-08-02 14:21     ` How can I install the latest version of Linux Audit on CentOS 6.8? (Update on CentOS 7) Mateusz Piotrowski

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=2326978.VhGrlLPiTR@x2 \
    --to=sgrubb@redhat.com \
    --cc=def@freebsd.org \
    --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