From: Jan Engelhardt <jengelh@medozas.de>
To: kaber@trash.net
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 3/7] libxt_string: define _GNU_SOURCE for strnlen
Date: Mon, 8 Aug 2011 02:42:19 +0200 [thread overview]
Message-ID: <1312764144-23849-4-git-send-email-jengelh@medozas.de> (raw)
In-Reply-To: <1312764144-23849-1-git-send-email-jengelh@medozas.de>
On RHEL-5.6 and clones with its gcc-4.1.2 and glibc-2.5:
libxt_string.c: In function "parse_string":
libxt_string.c:84: warning: implicit declaration of function "strnlen"
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
---
extensions/libxt_string.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/extensions/libxt_string.c b/extensions/libxt_string.c
index eef0b08..8cee335 100644
--- a/extensions/libxt_string.c
+++ b/extensions/libxt_string.c
@@ -20,6 +20,7 @@
* updated to work with slightly modified
* ipt_string_info.
*/
+#define _GNU_SOURCE 1 /* strnlen for older glibcs */
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
--
1.7.3.4
next prev parent reply other threads:[~2011-08-08 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 0:42 iptables build fixes Jan Engelhardt
2011-08-08 0:42 ` [PATCH 1/7] extensions: use multi-target registration Jan Engelhardt
2011-08-08 0:42 ` [PATCH 2/7] libxt_TCPMSS: restore build with IPv6-less libcs Jan Engelhardt
2011-08-08 0:42 ` Jan Engelhardt [this message]
2011-08-08 0:42 ` [PATCH 4/7] build: workaround broken linux-headers on RHEL-5 Jan Engelhardt
2011-08-08 0:42 ` [PATCH 5/7] build: strengthen check for overlong lladdr components Jan Engelhardt
2011-08-08 0:42 ` [PATCH 6/7] build: abort autogen on subcommand failure Jan Engelhardt
2011-08-08 0:42 ` [PATCH 7/7] libipq: add pkgconfig file Jan Engelhardt
2011-08-09 11:23 ` iptables build fixes Patrick McHardy
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=1312764144-23849-4-git-send-email-jengelh@medozas.de \
--to=jengelh@medozas.de \
--cc=kaber@trash.net \
--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).