From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ulogd - rpm file generation
Date: Fri, 20 Jul 2012 01:12:14 +0100 [thread overview]
Message-ID: <5008A25E.2090108@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1207200150310.3054@frira.zrqbmnf.qr>
> No idea what you patched in the package, or otherwise did to your
> system. On a pure Centos 5.8. I did *NOT* talk about fc13.
>
I don't give two hoots what is/isn't supported on a bloody CentOS
system, quite frankly! The point I was making is that libnetfilter_acct
does *NOT* depend on glibc 2.9 as evident from my previous post.
Oh, and also:
>
>> 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).
Can you read?
next prev parent reply other threads:[~2012-07-20 0:12 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
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 [this message]
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=5008A25E.2090108@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=jengelh@inai.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.