buildkernel problems
Here's problems I'm having with the latest (as of now) cvsup'd sources. - Donn perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/pci/pci_if.m perl @/kern/makeobjops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/sis/../../pci/if_sis.c === sk @ - /usr/src/sys machine - /usr/src/sys/i386/include touch opt_bdg.h perl @/kern/makeobjops.pl -h @/kern/device_if.m perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/pci/pci_if.m perl @/kern/makeobjops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/sk/../../pci/if_sk.c === sn @ - /usr/src/sys machine - /usr/src/sys/i386/include perl @/kern/makeobjops.pl -h @/kern/device_if.m perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/isa/isa_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/sn/../../dev/sn/if_sn.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_isa.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c:60: card_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/sn. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/CUSTOM. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src.
Re: buildkernel problems
In message [EMAIL PROTECTED] Donn Miller writes: : Here's problems I'm having with the latest (as of now) cvsup'd sources. I fixed this as of 8:35am MDT today. Sorry about any inconveince my incomplete checkin caused. This is one reason I don't like the modules/foo dev/foo split we have today. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current buildkernel problems.
after doing a cvsup I tried to build a new kernel and found that I was getting this error: (while doing config) ../../conf/files: coda/coda_fbsd.c must be optional, mandatory or standard so, I searched the mailing lists and found that I needed to update /usr/sbin/config, so I did, and was able to config, and start building the kernel. well, that led me to a rather nice compile error: cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s /tmp/ccv99837.s: Assembler messages: /tmp/ccv99837.s:772: Error: operands given don't match any known 386 instruction /tmp/ccv99837.s:837: Error: operands given don't match any known 386 instruction *** Error code 1 After searching the mailing lists (this one) again, I found that the answer was to use the newest gcc, and that I probably want to be using "make buildkernel" in /usr/src, so, thats what I did, and I'm getting this error again: ../../conf/files: coda/coda_fbsd.c must be optional, mandatory or standard so, anyone have an answer? I've also tried compiling the newest gcc, standalone, with no luck. -Rex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current buildkernel problems.
On Wed, Aug 02, 2000 at 12:04:19PM -0400, Rex A. Roof wrote: /tmp/ccv99837.s: Assembler messages: /tmp/ccv99837.s:772: Error: operands given don't match any known 386 instruction /tmp/ccv99837.s:837: Error: operands given don't match any known 386 instruction After searching the mailing lists (this one) again, I found that the answer was to use the newest gcc, and that I probably Not GCC, Binutils (assembler and linker). Of course you've told us nothing that allows us to help you. The output from ``uname -a'' being the most important. Also why reather than build and install the various bits you will have to in order to compile a -current kernel, you don't just do a ``make world'' first. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current buildkernel problems.
ok, here's the output from uname -a FreeBSD shaolin.wccnet.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Apr 27 19:04:53 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SHAOLIN i386 usually, in the past, I've found the best way to upgrade (and, what I thought was the proper way) was to make a new kernel, reboot on it, and then build world is that not the right away? -Rex On Wed, Aug 02, 2000 at 11:38:57AM -0700, David O'Brien wrote: On Wed, Aug 02, 2000 at 12:04:19PM -0400, Rex A. Roof wrote: /tmp/ccv99837.s: Assembler messages: /tmp/ccv99837.s:772: Error: operands given don't match any known 386 instruction /tmp/ccv99837.s:837: Error: operands given don't match any known 386 instruction After searching the mailing lists (this one) again, I found that the answer was to use the newest gcc, and that I probably Not GCC, Binutils (assembler and linker). Of course you've told us nothing that allows us to help you. The output from ``uname -a'' being the most important. Also why reather than build and install the various bits you will have to in order to compile a -current kernel, you don't just do a ``make world'' first. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current buildkernel problems.
On Wed, 2 Aug 2000, Rex A. Roof wrote: ok, here's the output from uname -a FreeBSD shaolin.wccnet.org 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Apr 27 19:04:53 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/SHAOLIN i386 usually, in the past, I've found the best way to upgrade (and, what I thought was the proper way) was to make a new kernel, reboot on it, and then build world is that not the right away? Not according to the handbook. The above is used under OpenBSD though. - Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
