netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: netfilter-devel@vger.kernel.org
Subject: Re: ulogd - rpm file generation
Date: Thu, 19 Jul 2012 23:52:32 +0100	[thread overview]
Message-ID: <50088FB0.4020403@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1207192320100.6629@frira.zrqbmnf.qr>


> ulogd depends on libnetfilter_acct, which in turn requires glibc >= 2.9, 
> and RHEL5 is just too damn old.
>   
Nope! If libnetfilter_acct is compiled from source it does *not* require 
glibc >= 2.9 and uses the version of glibc on the host system.

It is how I managed to build (and use) ulogd on one of my FC13-based 
machines - built and installed it from source, together with its 
immediate dependencies (libnetfilter_acct-devel, libnetfilter_log-devel, 
libnfnetlink-devel & libnetfilter_conntrack_devel).

There is currently a "bug" in the main ulogd.spec file (at least for my 
Fedora distribution) as it doesn't have a BuildRequires for 
libnetfilter_acct-devel - maybe because Fedora people are too lazy and 
haven't got arround to create the libnetfilter_acct package yet.


  reply	other threads:[~2012-07-19 22:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 17:57 ulogd - rpm file generation Gomathivinayagam Muthuvinayagam
2012-07-19 19:23 ` Jan Engelhardt
2012-07-19 19:34   ` Gomathivinayagam Muthuvinayagam
2012-07-19 20:07     ` Jan Engelhardt
2012-07-19 20:14       ` Gomathivinayagam Muthuvinayagam
2012-07-19 21:13         ` Gomathivinayagam Muthuvinayagam
2012-07-19 21:21           ` Jan Engelhardt
2012-07-19 22:52             ` Mr Dash Four [this message]
2012-07-19 23:16               ` Jan Engelhardt
2012-07-19 23:29                 ` Mr Dash Four
2012-07-20  0:06                   ` Jan Engelhardt
2012-07-20  0:12                     ` Mr Dash Four
2012-07-20  0:18                       ` Jan Engelhardt
2012-07-20  0:35                         ` 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=50088FB0.4020403@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=netfilter-devel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).