Date: Mon, 17 Feb 1997 16:29:33 +1100 From: Bruce Evans <bde@zeta.org.au> To: current@FreeBSD.org, sysseh@devetir.qld.gov.au Subject: Re: *Ahem*!!! Message-ID: <199702170529.QAA15899@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>cc -c -O2 -m486 -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wne
>sted-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdin
>c -I- -I. -I../.. -I../../../include -DNCONS=4 -DMFS -DNFS -DFFS -DTCP_COMPAT_42
> -DINET -DPQ_MEDIUMCACHE -DCOMPAT_43 -DKERNEL ../../vm/kern_lock.c
>../../vm/kern_lock.c:92: parse error before `lock_t'
>../../vm/kern_lock.c:92: warning: data definition has no type or storage class
>../../vm/kern_lock.c:94: parse error before `{'
You need run config. kern_lock.c isn't used in -current. It should
go away after someone checks than kern/kern_lock.c completely replaces
vm/kern_lock.c and merges the relevant parts of the cvs history.
Similarly for vm/lock.h -> sys/lock.h.
The evil *lock_t, typedefs aren't used much now. Unfortunately,
vm/vm_map.h has `simple_lock_data_t ref_lock', where simple_lock_data_t is
typedefed as `struct simplelock', so everything that includes vm/vm_map.h
has to include sys/lock.h. An include of <sys/lock.h> is currently spammed
into <vm/vm.h>.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702170529.QAA15899>