mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Matthias Andree <matthias.andree@gmx.de>,
	Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.4-pre7 build failure w/ IP NAT and ipchains
Date: Fri, 27 Apr 2001 14:31:02 -0700 (PDT)	[thread overview]
Message-ID: <15081.58646.799622.9357@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0104272012410.1256-100000@vaio>
In-Reply-To: <Pine.LNX.4.33.0104272012410.1256-100000@vaio>


Kai Germaschewski writes:
 > Anyway, the appended patch fixed the problem for me, vmlinux links okay
 > now - didn't try if it works, though.

This may work, but it is evidently the wrong change.

The helpers list desired by net/ipv4/netfilter/ip_nat_*.c is
in net/ipv4/netfilter/ip_nat_helper.c and it is not static there.

My analysis on your config being illegal, as pointed out by others, is
wrong technically.  But, something else is awry since
net/ipv4/netfilter/ip_nat_core.o should not be built without
net/ipv4/netfilter/ip_nat_helper.o being built as well.

I'll hopefully solve this by the end of the day.

Later,
David S. Miller
davem@redhat.com

  reply	other threads:[~2001-04-27 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27 18:14 Kai Germaschewski
2001-04-27 21:31 ` David S. Miller [this message]
2001-04-27 22:54 ` David S. Miller
2001-04-27 23:43   ` Kai Germaschewski
2001-04-27 23:43   ` David S. Miller
2001-04-28 19:53   ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2001-04-27  0:53 Matthias Andree
2001-04-27  8:02 ` David S. Miller
2001-04-27  9:55   ` Matthias Andree
2001-04-27 17:42     ` Andrzej Krzysztofowicz

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=15081.58646.799622.9357@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    /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

all inboxes | Powered by JetHome®