mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Matthew Schumacher <schu@schu.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: 2.4.0 Kernel Fails to compile when CONFIG_IP_NF_FTP is selected
Date: Sat, 6 Jan 2001 12:12:44 +1100 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.31.0101061156360.15856-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <3A56653C.BF55B6E0@schu.net>

On Fri, 5 Jan 2001, Matthew Schumacher wrote:

>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.0/include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
> -march=i686 -DMODULE -DMODVERSIONS -include
> /usr/src/linux-2.4.0/include/linux/modversions.h   -c -o ip_nat_ftp.o
> ip_nat_ftp.c
> ip_nat_ftp.c: In function `help':
> ip_nat_ftp.c:315: structure has no member named `nat'
> make[2]: *** [ip_nat_ftp.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.4.0/net/ipv4/netfilter'
> make[1]: *** [_modsubdir_ipv4/netfilter] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.0/net'
> make: *** [_mod_net] Error 2
>
> This is the error I get if I try to compile in the kernel or as a
> module.
>

Did you configure the kernel with 'Full NAT'?

(CONFIG_IP_NF_NAT in the .config file).

- James
--
James Morris
<jmorris@intercode.com.au>



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-06  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06  0:22 Matthew Schumacher
2001-01-06  0:59 ` David S. Miller
2001-01-06  2:40   ` Rusty Russell
2001-01-06 23:47     ` David S. Miller
2001-01-06  1:12 ` James Morris [this message]

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=Pine.LNX.4.31.0101061156360.15856-100000@blackbird.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schu@schu.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

all inboxes | Powered by JetHome®