From: Marcus Sundberg <marcus@ingate.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: netfilter-devel@lists.samba.org
Subject: Re: [PATCH] Compile fixes
Date: 04 Jun 2002 13:10:17 +0200 [thread overview]
Message-ID: <ve660zwb8m.fsf@inigo.ingate.se> (raw)
In-Reply-To: <20020604094437.B13631@sunbeam.de.gnumonks.org>
Harald Welte <laforge@gnumonks.org> writes:
> On Sun, Jun 02, 2002 at 04:01:04PM +0200, Marcus Sundberg wrote:
> > Hi,
> >
> > some fixes to make current CVS compile properly.
>
> thanks, applied.
Seems I forgot to include the patch for the POOL target in the first
mail, so here it comes:
Index: userspace/extensions/libipt_POOL.c
===================================================================
RCS file: /cvsroot/netfilter/userspace/extensions/libipt_POOL.c,v
retrieving revision 1.3
diff -u -r1.3 libipt_POOL.c
--- userspace/extensions/libipt_POOL.c 29 May 2002 13:08:16 -0000
+++ userspace/extensions/libipt_POOL.c 2 Jun 2002 13:48:14 -0000
@@ -15,6 +15,9 @@
#include <libippool/ip_pool_support.h>
/* FIXME --RR */
+#define ip_pool_init ip_POOL_init
+#define ip_pool_get_index ip_POOL_get_index
+#define ip_pool_get_name ip_POOL_get_name
#include "../ippool/libippool.c"
/* Function which prints out usage message. */
//Marcus
--
---------------------------------------+--------------------------
Marcus Sundberg <marcus@ingate.com> | Firewalls with SIP & NAT
Firewall Developer, Ingate Systems AB | http://www.ingate.com/
next prev parent reply other threads:[~2002-06-04 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 14:01 [PATCH] Compile fixes Marcus Sundberg
2002-06-04 7:44 ` Harald Welte
2002-06-04 11:10 ` Marcus Sundberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 9:19 [patch] compile fixes Andrew Morton
2002-02-13 14:56 ` David Woodhouse
2002-02-14 9:47 ` Adrian Bunk
2002-02-14 10:01 ` Andrew Morton
2002-02-14 14:12 ` Adrian Bunk
2002-02-14 13:58 ` Adrian Bunk
2002-02-15 3:51 ` Andrew Morton
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=ve660zwb8m.fsf@inigo.ingate.se \
--to=marcus@ingate.com \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@lists.samba.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.