From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Jeremy Drake <jeremyd@apptechsys.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Building cvs 2.4.18
Date: Mon, 25 Mar 2002 23:32:17 -0700 [thread overview]
Message-ID: <20020326063217.50AB1482C@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Jeremy Drake <jeremyd@apptechsys.com> of "Mon, 25 Mar 2002 14:06:47 PST." <Pine.LNX.4.33L2.0203251403190.13376-100000@eiger.apptechsys.com>
Jeremy Drake wrote:
> config and went on. Everything build successfully, but the depmod died.
> Here's the output
>
> depmod: *** Unresolved symbols in
> /usr/src/linux/debian/tmp-image/lib/modules/2.4.18-pa8/kernel/net/ipv4/netfil
> ter/ip_tables.o
> depmod: smp_num_cpus
> depmod: __cpu_number_map
hmm...this must have recently broke since I've built plenty
of SMP kernels with iptables enabled. I've stopped building SMP
for 2.4.18 since SMP is b0rken at the moment. But i don't think
we changed anything related to this since I've stopped...can you
run "make clean;make dep; make vmlinux;make modules" again?
> depmod: *** Unresolved symbols in
> /usr/src/linux/debian/tmp-image/lib/modules/2.4.18-pa8/kernel/net/ipv4/netfil
> ter/ipchains.o
> depmod: smp_num_cpus
> depmod: __cpu_number_map
If you can, ditch ipchains. If you need examples on how to
use iptables look at ftp.p-l.o:patches/a500/firewall.
grant
next prev parent reply other threads:[~2002-03-26 6:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 22:06 [parisc-linux] Building cvs 2.4.18 Jeremy Drake
2002-03-26 6:32 ` Grant Grundler [this message]
2002-03-26 6:45 ` Grant Grundler
2002-03-26 16:16 ` Jeremy Drake
2002-03-27 14:09 ` Andrew Shugg
2002-03-28 7:02 ` Grant Grundler
2002-03-28 10:13 ` Andrew Shugg
2002-03-28 17:17 ` Grant Grundler
2002-03-29 1:08 ` Andrew Shugg
2002-03-29 17:56 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2002-07-21 15:06 [parisc-linux] PARISC Linux machines? Michael Madden
2002-07-21 17:04 ` Juergen Braukmann
2002-07-26 5:29 ` Andrew Shugg
2002-07-27 8:53 ` Juergen Braukmann
2002-07-29 18:06 ` Grant Grundler
[not found] <20020327151405.2397A482F@dsl2.external.hp.com>
2002-03-28 4:27 ` [parisc-linux] Mozilla, etc David Dougall
2002-03-28 5:44 ` Christian Suder
2002-03-28 9:31 ` Thomas Bogendoerfer
2002-03-28 16:13 ` Tilo Jandt
2002-03-28 22:59 ` Thomas Bogendoerfer
2002-03-29 18:45 ` Christian Suder
2002-03-28 8:20 ` Tilo Jandt
2002-03-28 12:18 ` Andrew Shugg
2002-03-28 17:41 ` Grant Grundler
2001-05-26 0:10 [parisc-linux] List of packages for hppa ISO release Matt Taggart
2001-05-26 16:45 ` Grant Grundler
2001-05-29 20:16 ` Matt Taggart
2001-05-29 20:48 ` Matthew Wilcox
2001-05-29 21:18 ` John Galt
2001-05-29 21:53 ` Alan Cox
2001-05-29 21:30 ` Andrew Shugg
2001-05-29 22:50 ` Matt Taggart
[not found] ` <grundler@puffin.external.hp.com>
2002-08-30 18:20 ` [parisc-linux] A WinXP patch grundler
2002-08-30 19:04 ` Grant Grundler
2000-11-15 9:05 [parisc-linux] Palinux on a 712/60 Arnaud.ATOCH
2000-11-15 10:10 ` Andrew Shugg
2000-11-15 20:49 ` Matt Taggart
2000-11-08 20:14 [parisc-linux] webshite Matthew Wilcox
2000-11-08 20:31 ` Grant Grundler
2000-11-09 10:06 ` Matthew Wilcox
2000-11-08 21:13 ` Andrew Shugg
2000-11-08 21:22 ` Matt Taggart
2000-11-09 9:59 ` Matthew Wilcox
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=20020326063217.50AB1482C@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=jeremyd@apptechsys.com \
--cc=parisc-linux@parisc-linux.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