mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Andersen <kernel-list@majorstua.net>
To: "Marius Müller" <m.mueller@freakmail.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.24 from kernel.org
Date: Mon, 26 Jan 2004 01:26:35 +0100	[thread overview]
Message-ID: <40145EBB.20805@majorstua.net> (raw)
In-Reply-To: <DF6611C8-4F87-11D8-B999-000393DC9DA0@freakmail.de>



>
> I just tried to compile linux-2.4.24.tar.bz2 from 
> http://www.kernel.org/pub/linux/kernel/v2.4/
> The date of the archive I downloaded was 05-Jan-2004 5:54. After 
> configuring the options for compiling I started the process by "make 
> dep" and then "make bzImage". After a few minutes I got the following 
> error message:
>
> ipt_ECN.c:16: linux/netfilter_ipv4/ipt_ECN.h: No such file or directory
> ipt_ECN.c:26: warning: `struct ipt_ECN_info' declared inside parameter 
> list
> ipt_ECN.c:26: warning: its scope is only this definition or 
> declaration, which is probably not what you want.
> (...)
> ipt_ECN.c:156: dereferencing pointer to incomplete type
> ipt_ECN.c:156: `IPT_ECN_OP_SET_ECE' undeclared (first use in this 
> function)
> ipt_ECN.c:156: `IPT_ECN_OP_SET_CWR' undeclared (first use in this 
> function)
> make[3]: *** [ipt_ECN.o] Error 1
> make[3]: Leaving directory `/WorX/linux-2.4.24/net/ipv4/netfilter'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/WorX/linux-2.4.24/net/ipv4/netfilter'
> make[1]: *** [_subdir_ipv4/netfilter] Error 2
> make[1]: Leaving directory `/WorX/linux-2.4.24/net'
> make: *** [_dir_net] Error 2
>
> I then discovered that the file linux/netfilter_ipv4/ipt_ECN.h that 
> could not be found and caused the following errors really doesn't 
> exist but there is a file ipt_ECN.1.h in linux/netfilter_ipv4/. I 
> searched for more of the .1.h files and found the following:
>
> .//include/linux/netfilter_ipv4/ipt_DSCP.1.h
> .//include/linux/netfilter_ipv4/ipt_ECN.1.h
> .//include/linux/netfilter_ipv4/ipt_mark.1.h
> .//include/linux/netfilter_ipv4/ipt_tcpmss.1.h
> .//include/linux/netfilter_ipv4/ipt_tos.1.h
> .//include/linux/netfilter_ipv6/ip6t_mark.1.h
> .//net/ipv4/netfilter/ipt_DSCP.1.c
> .//net/ipv4/netfilter/ipt_ecn.1.c
> .//net/ipv4/netfilter/ipt_mark.1.c
> .//net/ipv4/netfilter/ipt_tcpmss.1.c
> .//net/ipv4/netfilter/ipt_tos.1.c
> .//net/ipv6/netfilter/ip6t_mark.1.c
>
> I searched contents of the sources with grep for any occurrences of 
> the above header-files but the only occurrences found were for the 
> exact same files but without the .1.h but with .h only. I renamed all 
> the above files from .1.h to .h and finally succeeded in compiling 
> without any problems.
> I don't know if get something very wrong here but it looked like some 
> sort wrong file names for me.
> Hopefully I haven't wasted your time with "fake" problems.
>
> Marius
>
This is not a problem with the source from kernel.org but rather a 
problem with case-sensitivity on your system. It looks like only files 
with the same name (not being case-sensitive) are renamed to the .1 ending.

Daniel Andersen


      reply	other threads:[~2004-01-26  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25 22:43 Marius Müller
2004-01-26  0:26 ` Daniel Andersen [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=40145EBB.20805@majorstua.net \
    --to=kernel-list@majorstua.net \
    --cc=daniel@majorstua.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.mueller@freakmail.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

Powered by JetHome