From: "Don Hughes" <dhughes@sannotes.org>
To: netfilter@lists.netfilter.org
Subject: Failure to build modules with 1.2.7a and kernel 2.4.19
Date: Sun, 27 Oct 2002 12:59:21 -0500 [thread overview]
Message-ID: <3DBBE329.29822.5E9E1C5@localhost> (raw)
I did my normal compile of the 2.4.19 kernal but not of the netfiler
modules were created. Any help would be appreciated. I have
included some messages for the compile log.
make[2]: Circular /usr/src/linux-make -C ipv4 modules
make[2]: Entering directory `/usr/src/linux-2.4.19.SuSE/net/ipv4'
LD_BASENAME=ip_gre -DEXPORT_SYMTAB -c ip_gre.c
make[2]: Leaving directory `/usr/src/linux-2.4.19.SuSE/net/ipv4'
make -C ipv4/netfilter modules
make[2]: Entering directory `/usr/src/linux-
2.4.19.SuSE/net/ipv4/netfilter'
LD_BASENAME=ip_conntrack_standalone -DEXPORT_SYMTAB -
c ip_conntrack_standalone.c
LD_BASENAME=ip_conntrack_core -c -o ip_conntrack_core.o
ip_conntrack_core.c
LD_BASENAME=ip_conntrack_proto_generic -c -o
ip_conntrack_proto_generic.o ip_conntrack_proto_generic.c
LD_BASENAME=ip_conntrack_proto_tcp -c -o
ip_conntrack_proto_tcp.o ip_conntrack_proto_tcp.c
LD_BASENAME=ip_conntrack_proto_udp -c -o
ip_conntrack_proto_udp.o ip_conntrack_proto_udp.c
LD_BASENAME=ip_conntrack_proto_icmp -c -o
ip_conntrack_proto_icmp.o ip_conntrack_proto_icmp.c
ld -m elf_i386 -r -o ip_conntrack.o ip_conntrack_standalone.o
ip_conntrack_core.o ip_conntrack_proto_generic.o
ip_conntrack_proto_tcp.o ip_conntrack_proto_udp.o
ip_conntrack_proto_icmp.o
LD_BASENAME=ip_conntrack_ftp -DEXPORT_SYMTAB -c
ip_conntrack_ftp.c
LD_BASENAME=ip_nat_ftp -c -o ip_nat_ftp.o ip_nat_ftp.c
LD_BASENAME=iptable_filter -c -o iptable_filter.o iptable_filter.c
LD_BASENAME=iptable_mangle -c -o iptable_mangle.o
iptable_mangle.c
LD_BASENAME=ip_nat_standalone -DEXPORT_SYMTAB -c
ip_nat_standalone.c
LD_BASENAME=ip_nat_rule -c -o ip_nat_rule.o ip_nat_rule.c
LD_BASENAME=ip_nat_helper -c -o ip_nat_helper.o
ip_nat_helper.c
LD_BASENAME=ip_nat_core -c -o ip_nat_core.o ip_nat_core.c
LD_BASENAME=ip_nat_proto_unknown -c -o
ip_nat_proto_unknown.o ip_nat_proto_unknown.c
LD_BASENAME=ip_nat_proto_tcp -c -o ip_nat_proto_tcp.o
ip_nat_proto_tcp.c
LD_BASENAME=ip_nat_proto_udp -c -o ip_nat_proto_udp.o
ip_nat_proto_udp.c
LD_BASENAME=ip_nat_proto_icmp -c -o ip_nat_proto_icmp.o
ip_nat_proto_icmp.c
ld -m elf_i386 -r -o iptable_nat.o ip_nat_standalone.o ip_nat_rule.o
ip_nat_helper.o ip_nat_core.o ip_nat_proto_unknown.o
ip_nat_proto_tcp.o ip_nat_proto_udp.o ip_nat_proto_icmp.o
LD_BASENAME=ipt_helper -c -o ipt_helper.o ipt_helper.c
make[2]: Leaving directory `/usr/src/linux-
2.4.19.SuSE/net/ipv4/netfilter'
make[1]: Leaving directory `/usr/src/linux-2.4.19.SuSE/net'
cp: cannot stat `ipt_LOG.o': No such file or directory
cp: cannot stat `ipt_MARK.o': No such file or directory
cp: cannot stat `ipt_MASQUERADE.o': No such file or directory
cp: cannot stat `ipt_REDIRECT.o': No such file or directory
cp: cannot stat `ipt_REJECT.o': No such file or directory
cp: cannot stat `ipt_ah.o': No such file or directory
cp: cannot stat `ipt_esp.o': No such file or directory
cp: cannot stat `ipt_helper.o': No such file or directory
cp: cannot stat `ipt_iplimit.o': No such file or directory
cp: cannot stat `ipt_limit.o': No such file or directory
cp: cannot stat `ipt_mark.o': No such file or directory
cp: cannot stat `ipt_multiport.o': No such file or directory
cp: cannot stat `ipt_psd.o': No such file or directory
cp: cannot stat `ipt_state.o': No such file or directory
cp: cannot stat `ipt_string.o': No such file or directory
cp: cannot stat `ipt_time.o': No such file or directory
cp: cannot stat `ipt_unclean.o': No such file or directory
make[2]: *** [_modinst__] Error 1
make[1]: *** [_modinst_ipv4/netfilter] Error 2
make: *** [_modinst_net] Error 2
...don
dhughes@microtechniques.com
White Plains, NY
reply other threads:[~2002-10-27 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DBBE329.29822.5E9E1C5@localhost \
--to=dhughes@sannotes.org \
--cc=netfilter@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