From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Robby Workman <rw@rlworkman.net>
Cc: Jan Engelhardt <jengelh@medozas.de>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] conntrack-tools 0.9.11 released
Date: Mon, 23 Feb 2009 10:19:58 +0100 [thread overview]
Message-ID: <49A26A3E.5020707@netfilter.org> (raw)
In-Reply-To: <alpine.LSU.2.00.0902230815570.20446@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Monday 2009-02-23 06:34, Robby Workman wrote:
>> On Sat, 21 Feb 2009 18:40:03 +0100
>> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>>
>>> The netfilter project presents another development release of the
>>> conntrack-tools...
>> I thought I recalled seeing discussion about this already, but I don't
>> see it in my archives, so maybe not. With glibc-2.7, this release
>> builds fine; however, with glibc-2.9, both src/mcast.c and
>> src/sync-mode.c need limits.h included, or else INT_MAX is undefined.
>
> This builds fine for me - and I am on glibc 2.9.
> Just *what* is it in (which distro? Debian/Ubuntu again?)
> again to constantly fail on INT_MAX?
Indeed. This also compiles fine for me in debian. I have committed a
patch for this [1]. This issue is unfortunate. Gentoo bugzilla on
conntrack-tools had a patch but nobody has sent it to me. I notice it
after the release.
[1]
http://git.netfilter.org/cgi-bin/gitweb.cgi?p=conntrack-tools.git;a=commit;h=9bf002ff7935e7dff625683787fc3a06ac2ef2cb
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2009-02-23 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 17:40 [ANNOUNCE] conntrack-tools 0.9.11 released Pablo Neira Ayuso
2009-02-23 5:34 ` Robby Workman
2009-02-23 7:17 ` Jan Engelhardt
2009-02-23 9:19 ` Pablo Neira Ayuso [this message]
2009-02-23 15:34 ` Robby Workman
2009-02-23 16:55 ` Jan Engelhardt
2009-02-24 3:02 ` Robby Workman
2009-02-24 9:59 ` Jan Engelhardt
2009-02-24 9:55 ` Pablo Neira Ayuso
2009-02-24 14:10 ` Robby Workman
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=49A26A3E.5020707@netfilter.org \
--to=pablo@netfilter.org \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=rw@rlworkman.net \
/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).