On Tuesday, July 10, 2001, at 11:23  pm, gabriel rosenkoetter wrote:

> On Tue, Jul 10, 2001 at 11:12:04PM +0100, Matthew Theobalds wrote:
>> I assume that the error codes are the same as their MacOS counterparts,
>> would this be correct?
>
> Only where both operating systems decided to pass whatever error
> number the processor gave them along up the chain.

I was referring to when, in the Mac OS (pre X, of course) one gets 
"Application has quite blah blah. Error type 2." And whether that is the 
same fatal exception as NetBSD's. It looks like it is.

> There's a source file somewhere with the error codes listed, you
> might want to have a look at it. (Maybe somewhere in
> /usr/src/sys/m68k?)

Yes, Thilo pointed me towards it: /usr/include/sys/signal.h

>> Finally, is it okay just to type `make` and let it continue from where
>> it left off, or is that likely to cause problems later?
>
> You were building a kernel? If so, you'll need to add UPDATE=1 to
> your compile-time flags, or the build will start over whether you
> like it or not.

Are you absolutely sure about this?

It's just that what happened last time (and the others) would suggest 
otherwise:

XUSERS=16 -D_KERNEL -D_KERNEL_OPT -Dmac68k  -c 
../../../../coda/coda_vnops.c
cc: Internal compiler error: program cc1 got fatal signal 10
*** Error code 1

Stop.
make: stopped in /sys/arch/mac68k/compile/gellum
gellum:/sys/arch/mac68k/compile/gellum# make
making sure the 68040 FPSP is up to date...
`fpsp.o' is up to date.
cc  -O2 -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes  
-Wpointer-arith -Wno-uninitialized -Wno-main -msoft-float -I. 
-I../../../../arch -I../../../.. -nostdinc -DHZ="0x3c" -DM68030 
-DFPU_EMULATE -DLKM -DDIAGNOSTIC -DGRF_COMPAT -DMAXUSERS=16 -D_KERNEL 
-D_KERNEL_OPT -Dmac68k  -c ../../../../coda/coda_vnops.c

Note the "coda_vnops.c" at each point. Surely that looks like it is just 
continuing on?

All the best.

Matthew