From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Build fixes for old Linuxes
Date: Fri, 18 Jan 2013 01:44:55 +0100 [thread overview]
Message-ID: <20130118004455.GA20537@1984> (raw)
In-Reply-To: <1358274002-6042-1-git-send-email-jengelh@inai.de>
On Tue, Jan 15, 2013 at 07:20:00PM +0100, Jan Engelhardt wrote:
>
> With this, iptables-1.4.17a (current git state) is tested to compile
> and, to the degree covered by this patchset, to function under
> Linux 2.4.27/glibc-2.3.2/Debian-3.1.
>
> ===
> The following changes since commit 983196ceb4d3bb7b6d3cf6da18bb6d5a5eafb347:
>
> doc: document the -4 and -6 options (2013-01-07 02:26:16 +0100)
>
> are available in the git repository at:
>
> git://git.inai.de/iptables old-linux
>
> for you to fetch changes up to 1071ec54e6d7af406fe34afea1ce2c3e49ee1914:
>
> parser: workaround glibc-2.3.2 bug 358 (2013-01-15 19:16:55 +0100)
>
> ----------------------------------------------------------------
> Jan Engelhardt (2):
> build: fix libiptc build failure on old linux-glibc-devel headers
> parser: workaround glibc-2.3.2 bug 358
Helping users is a noble thing from your side. However, that glibc
branch [1] and that debian release [2] are not maintained anymore.
[1] http://sourceware.org/glibc/wiki/Release
[2] http://www.debian.org/releases/sarge/
Sorry, I'm not taking this.
next prev parent reply other threads:[~2013-01-18 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 18:20 Build fixes for old Linuxes Jan Engelhardt
2013-01-15 18:20 ` [PATCH 1/2] build: fix libiptc build failure on old linux-glibc-devel headers Jan Engelhardt
2013-01-15 18:20 ` [PATCH 2/2] parser: workaround glibc-2.3.2 bug 358 Jan Engelhardt
2013-01-18 0:44 ` Pablo Neira Ayuso [this message]
2013-01-18 1:29 ` Build fixes for old Linuxes Jan Engelhardt
2013-01-18 2:06 ` Pablo Neira Ayuso
2013-01-21 16:29 ` Jan Engelhardt
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=20130118004455.GA20537@1984 \
--to=pablo@netfilter.org \
--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 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).