From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: excluding auditd events
Date: Thu, 26 May 2011 16:22:51 +0100 [thread overview]
Message-ID: <4DDE704B.1070906@googlemail.com> (raw)
In-Reply-To: <201105261033.11536.sgrubb@redhat.com>
> The audit package has no dependency on perl.
>
Oops, sorry, I meant python! My bad!
[rant]
The other dependency I can't overcome (which I could not remember the
other day when the same issue popped up during our discussion Steve) was
the libprelude-devel package, simply because in the way the current
libprelude-devel package is configured, there is no way on gods green
Earth I could install both i686 and x86_64 versions of the tool to
enable cross-compilation.
There are hardcoded lib paths in "/usr/bin/libprelude-config"
("libdirs=-L/usr/lib" in the i686 version, while "libdirs=-L/usr/lib64"
in the x86_64 version) which are obviously arch-dependent.
Not to mention this little gem in prelude-intttypes.h - "#define
__PRELUDE_HAVE_64BIT_LONG", which is commented out in the i686 version,
instead of using a much-more sensible approach and either 1) define
these variables depending on the current arch used for compilation -
i.e. the "--target" value used in rpmbuild for example; or 2) use two
completely separate versions of these files (say
libprelude-config-<arch> and prelude-inttypes-<arch>.h) and integrate
those in the pkgconfig files.
All this is a classic example of careless programming in my view!
[/rant]
Without libprelude-devel I can't compile/build audispd-plugins, without
audispd-plugins I can't have remote logging in auditd (you get the
picture!).
next prev parent reply other threads:[~2011-05-26 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 0:22 excluding auditd events Mr Dash Four
[not found] ` <201105260802.21606.sgrubb@redhat.com>
2011-05-26 13:16 ` Mr Dash Four
2011-05-26 13:50 ` Steve Grubb
2011-05-26 14:07 ` Mr Dash Four
2011-05-26 14:16 ` Steve Grubb
2011-05-26 14:23 ` Mr Dash Four
2011-05-26 14:33 ` Steve Grubb
2011-05-26 15:22 ` Mr Dash Four [this message]
2011-05-26 15:51 ` LC Bruzenak
2011-05-26 16:10 ` Mr Dash Four
2011-06-01 12:54 ` Mr Dash Four
2011-06-01 14:08 ` LC Bruzenak
2011-06-01 14:47 ` Mr Dash Four
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=4DDE704B.1070906@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=linux-audit@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox