On Thu, 4 Jun 1998, Patrick Welche wrote:

> cc  -O2 -Werror -Wall -Wno-main -I. -I../../../../arch
>   -I../../../.. -nostdinc -DCPU_ARM6 -DIOMD -DRISCPC -DARMFPE -DFIFO
>   -DINET -DPFIL_HOOKS -DCOMPAT_13 -DCOMPAT_12 -DSYSVMSG -DSYSVSEM
>   -DSYSVSHM -DSHMMAXPGS="0x400" -DKTRACE -DIRQSTATS -DMOUSE_IOC_ACK
>   -DDIAGNOSTIC -DPOSTMORTEM -DDDB -DIPFILTER_LOG -DMAXUSERS=32 -D_KERNEL
>   -Darm32 -Wcomment  -c ../../../../arch/arm32/arm32/postmortem.c
> cc1: warnings being treated as errors
>   ../../../../arch/arm32/arm32/postmortem.c: In function `postmortem':
>   ../../../../arch/arm32/arm32/postmortem.c:202: warning: type defaults
>     to `int' in declaration of `postmortem_active'
> 
> $NetBSD: postmortem.c,v 1.12 1998/01/21 22:34:38 mark Exp $
> 
> static  postmortem_active = 0;
> 
> int sounds ok as it only occurs as
> 
> if (postmortem_active)
> ++postmortem_active;
> --postmortem_active;

Hi,
  ok fixed that.

> PS PMAP_NEW is completely unrelated to UVM right? So with options UVM
> in the kernel you only want UVM=yes in /etc/mk.conf, no PMAP business?
It's not completely unrelated. You need to be running UVM in order to use
PMAP_NEW. PMAP_NEW is used to enable a new version of PMAP (typically in
pmap_new.c) which we don't have yet for the arm.

Cheers,
				Mark