Re: Installed Samba, cannot compile new kernel now?!
Jud wrote:
7/22/2002 12:50:01 AM, Kent Stewart [EMAIL PROTECTED] wrote:
sagacious wrote:
Wtf? Check this out.
[labs] /usr/src/sys/compile/ghost# make clean
rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel linterrs
makelinks setdef[01].c setdefs.h tags vers.c vnode_if.c vnode_if.h
device_if.c device_if.h bus_if.c bus_if.h miibus_if.c miibus_if.h
pci_if.c pci_if.h isa_if.c isa_if.h
cd ../../modules ; env
MAKEOBJDIRPREFIX=/usr/src/sys/compile/ghost/modules
DEBUG=-g
DEBUG_FLAGS=-g MACHINE=i386 make clean
=== accf_data
/usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 63: Could
not
find bsd.init.mk
/usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 190: Could
not
find bsd.links.mk
make: fatal errors encountered -- cannot continue
The only ?new? thing I did was install /usr/ports/samba/ other than
that, my system gets fresh source, every so often?. Any ideas where
I
should begin with this?
Try a different cvsup server. I was using cvsup16 and had the same
error. I switched to cvsup13 and it went away.
Kent
I got the same error after cvsup-ing from cvsup13. :)
Bsd.links.mk, etc., were among the files in the cvsup. I think what may
be happening is that in this one instance installing world before
rebuilding the kernel will install the new files and allow the kernel to build.
At least it worked for me.
Did you do a config style kernel build or a buildkernel. I did the
build{install]kernel without any problems.
Kent
Jud
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
.
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Installed Samba, cannot compile new kernel now?!
-Original Message-
From: Kent Stewart [EMAIL PROTECTED]
To: Jud [EMAIL PROTECTED]
Date: Mon, 22 Jul 2002 07:15:50 -0700
Subject: Re: Installed Samba, cannot compile new kernel now?!
Jud wrote:
7/22/2002 12:50:01 AM, Kent Stewart [EMAIL PROTECTED] wrote:
sagacious wrote:
Wtf? Check this out.
[labs] /usr/src/sys/compile/ghost# make clean
rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel linterrs
makelinks setdef[01].c setdefs.h tags vers.c vnode_if.c vnode_if.h
device_if.c device_if.h bus_if.c bus_if.h miibus_if.c miibus_if.h
pci_if.c pci_if.h isa_if.c isa_if.h
cd ../../modules ; env
MAKEOBJDIRPREFIX=/usr/src/sys/compile/ghost/modules
DEBUG=-g
DEBUG_FLAGS=-g MACHINE=i386 make clean
=== accf_data
/usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 63: Could
not
find bsd.init.mk
/usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 190: Could
not
find bsd.links.mk
make: fatal errors encountered -- cannot continue
The only ?new? thing I did was install /usr/ports/samba/ other than
that, my system gets fresh source, every so often?. Any ideas where
I
should begin with this?
Try a different cvsup server. I was using cvsup16 and had the same
error. I switched to cvsup13 and it went away.
Kent
I got the same error after cvsup-ing from cvsup13. :)
Bsd.links.mk, etc., were among the files in the cvsup. I think what may
be happening is that in this one instance installing world before
rebuilding the kernel will install the new files and allow the kernel to build.
At least it worked for me.
Did you do a config style kernel build or a buildkernel. I did the
build{install]kernel without any problems.
Kent
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Both - first buildkernel, then the old way. But I
was also doing some fiddling with files. After
buildworld (in multi-user mode), I thought I'd try
the kernel scheduler patch so that the subsequent
kernel recompile would be two for the price of one.
Both the new and old ways of recompiling then gave
me the same error Sagacious reported.
Jud
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Installed Samba, cannot compile new kernel now?!
Wtf? Check this out. [labs] /usr/src/sys/compile/ghost# make clean rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel linterrs makelinks setdef[01].c setdefs.h tags vers.c vnode_if.c vnode_if.h device_if.c device_if.h bus_if.c bus_if.h miibus_if.c miibus_if.h pci_if.c pci_if.h isa_if.c isa_if.h cd ../../modules ; env MAKEOBJDIRPREFIX=/usr/src/sys/compile/ghost/modules DEBUG=-g DEBUG_FLAGS=-g MACHINE=i386 make clean === accf_data /usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 63: Could not find bsd.init.mk /usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 190: Could not find bsd.links.mk make: fatal errors encountered -- cannot continue The only new thing I did was install /usr/ports/samba/ other than that, my system gets fresh source, every so often. Any ideas where I should begin with this? sagacious (Mike) Network administrator The unixhideout network http://www.unixhideout.com
Re: Installed Samba, cannot compile new kernel now?!
sagacious wrote: Wtf? Check this out. [labs] /usr/src/sys/compile/ghost# make clean rm -f *.o *.so *.So *.ko *.s eddep errs kernel.debug kernel linterrs makelinks setdef[01].c setdefs.h tags vers.c vnode_if.c vnode_if.h device_if.c device_if.h bus_if.c bus_if.h miibus_if.c miibus_if.h pci_if.c pci_if.h isa_if.c isa_if.h cd ../../modules ; env MAKEOBJDIRPREFIX=/usr/src/sys/compile/ghost/modules DEBUG=-g DEBUG_FLAGS=-g MACHINE=i386 make clean === accf_data /usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 63: Could not find bsd.init.mk /usr/src/sys/modules/accf_data/../../conf/kmod.mk, line 190: Could not find bsd.links.mk make: fatal errors encountered -- cannot continue The only ?new? thing I did was install /usr/ports/samba/ other than that, my system gets fresh source, every so often?. Any ideas where I should begin with this? Try a different cvsup server. I was using cvsup16 and had the same error. I switched to cvsup13 and it went away. Kent sagacious (Mike) Network administrator The unixhideout network http://www.unixhideout.com -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
