Date: Fri, 20 Aug 2004 15:51:43 -0500 From: "P.D. Seniura" <pdseniura@techie.com> To: "Andre Oppermann" <andre@freebsd.org> Cc: ru@freebsd.org Subject: Re: problem in building modules-with-world re: cvs commit:src/sys/netinet ip_fw_pfil.c Message-ID: <20040820205143.5998C790032@ws1-14.us4.outblaze.com>
next in thread | raw e-mail | index | archive | help
----- Original Message ----- From: Andre Oppermann <andre@freebsd.org> Date: Fri, 20 Aug 2004 22:07:32 +0200 To: "P.D. Seniura" <pdseniura@techie.com> Subject: Re: problem in building modules-with-world re: cvs commit:src/sys/netinet ip_fw_pfil.c > "P.D. Seniura" wrote: > > > > ----- Original Message ----- > > From: Andre Oppermann <andre@freebsd.org> > > Date: Fri, 20 Aug 2004 20:01:25 +0200 > > To: Paul Seniura <pdseniura@techie.com> > > Subject: Re: problem in building modules-with-world re: cvs commit: src/sys/netinet ip_fw_pfil.c > > > > > Paul Seniura wrote: > > > > > > > > Hi, > > > > > > > > I'll try replying directly to the committer > > > > this time rather than post on -current@ since > > > > -current@ seems to be ignored somewhat. And > > > > also CC the cvs list directly, too. > > > > > > > > Got the latest CTM buckets installed. > > > > Doesn't seem to be any commits since then > > > > to cover this problem. > > > > > > > > ident /src/sys/modules/ipfw/../../netinet/ip_fw2.c: > > > > $FreeBSD: src/sys/netinet/ip_fw2.c,v 1.73 2004/08/19 23:31:40 andre Exp $ > > > > > > > > ident /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c: > > > > $FreeBSD: src/sys/netinet/ip_fw_pfil.c,v 1.5 2004/08/20 00:36:55 andre Exp $ > > > > > > > > A snip from my build log freshly done just now: > > > > > > > > [...] > > > > ===> ipfw > > > > rm -f .depend > > > > mkdep -f .depend -a -nostdinc -DIPFIREWALL -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/contrib/altq -I@/../include /src/sys/modules/ipfw/../../netinet/ip_fw2.c /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c > > > > /src/sys/modules/ipfw/../../netinet/ip_fw2.c:35:22: opt_ipfw.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw2.c:36:22: opt_ipdn.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw2.c:37:26: opt_ipdivert.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw2.c:38:22: opt_inet.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw2.c:39:23: opt_ipsec.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw2.c:41:2: #error IPFIREWALL requires INET. > > > > /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c:29:22: opt_ipfw.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c:30:22: opt_ipdn.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c:31:26: opt_ipdivert.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c:32:28: opt_pfil_hooks.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c:33:22: opt_inet.h: No such file or directory > > > > /src/sys/modules/ipfw/../../netinet/ip_fw_pfil.c:35:2: #error IPFIREWALL requires INET. > > > > mkdep: compile failed > > > > *** Error code 1 (continuing) > > > > `depend' not remade because of errors. > > > > ===> ip_mroute_mod > > > > [...] > > > > > > I have just cvsupped -current and the GENERIC kernel compiles just fine. > > > > > > Looking at the error message in your log output one might conclude that you > > > are missing "option INET" in your kernel config? > > > > MODULES_WITH_WORLD > > > > Please read the subject line. ;) > > Ok, there seems to be a problem with setting up the environment when doing > this. Why do you build modules with WORLD instead of doing it with the > kernel? This sounds quite dangerous to me when kernel/modules go out of > sync. It is still supported, no? ;) Do y'all really want to know why? (1) It shaves hours & hours off kernel build times on this puny p2. (2) Things that the hardware needs are built into my custom kernels. Firewall is not needed by IBM's hardware to boot-up. ;) (3) I like having modules-files stored separately (/boot/modules) from the kernel (/boot/kernel) in case I mess-up one or the other during tests. (4) And I LUV Apple's way of doing this same sort of thing. Tiny kernel for booting, then load other stuff as needed, on the fly, change parms and/or kext code WITHOUT REBOOTING, etc. ;) Well I can think of s'more reasons but I hope y'all get my drift... ;) And before I forget _again_ I want to say THANK YOU for taking time working on all this. > Ruslan, do you have any idea what is going wrong? > > -- > Andre -- thx, Paul Seniura. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040820205143.5998C790032>