linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Chris Frey <cdfrey@netdirect.ca>
Cc: linux-kernel@vger.kernel.org,
	Netfilter Development Mailinglist 
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [2.4.23] compile / link error in net/ipv4/netfilter
Date: Tue, 2 Dec 2003 13:53:33 +0530	[thread overview]
Message-ID: <20031202082333.GI546@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <20031201202853.A31914@netdirect.ca>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

On Mon, Dec 01, 2003 at 08:28:31PM -0500, Chris Frey wrote:
> Hi,
> 
> Using gcc 3.2.3.
> 
> When compiling 2.4.23, it stops during the compile with these errors:

how did you get the .config you have attached?

You have COMPAT_IPCHAINS activated at the same time as COMPAT_IPFWADM!

This is illegal, and 'make menuconfig' or 'make xconfig' should not
allow you to combine the two of them.  Please describe how you managed
to do that ;)

Greetings from india,
	Harald.
-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-12-02 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02  1:28 [2.4.23] compile / link error in net/ipv4/netfilter Chris Frey
2003-12-02  6:43 ` Chris Frey
2003-12-02  7:27   ` Martin Josefsson
2003-12-02  8:23 ` Harald Welte [this message]
2003-12-02 19:22   ` Chris Frey

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=20031202082333.GI546@obroa-skai.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=cdfrey@netdirect.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter-devel@lists.netfilter.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).