Subject: Re: kernel compile problems
To: bryan collins <bryan@bwyan.anu.edu.au>
From: Alistair G. Crooks <agc@uts.amdahl.com>
List: current-users
Date: 09/27/1994 03:24:50
> >    cpp -DLOCORE -I. -I../../../../arch -I../../../.. -I../../../../sys -DSPHI
> NX -DI
> >    486_CPU -DUCONSOLE -DXSERVER -DTCP_COMPAT_42 -DCOMPAT_43 -DCOMPAT_09 -DCOM
> PAT_NO
> >    MID -DUSER_LDT -DINET -DKERNFS -DFDESC -DMSDOSFS -DCD9660 -DMROUTING -DMUL
> TICAST
> >     -DNFSCLIENT -DNFSSERVER -DMFS -DQUOTA -DFFS -DFIFO -DKTRACE -DDEVPAGER -D
> VNODEP
> >    AGER -DSWAPPAGER -DMACHINE_NONCONTIG -DKERNEL -Di386 ../../i386/locore.s |
>  as  -
> >    o locore.o
> >    sh: warning: running as root with dot in PATH
> >    ../../i386/locore.s:144: unterminated character constant
> >    ../../i386/locore.s:487: unterminated character constant
> >    ../../i386/locore.s:566: unterminated character constant
> > 
> > This could only happen if you're using a different `cpp' or `as' than
> > the ones supplied in NetBSD.
> > 
> 
> I'm using binaries compiled from the sept 12th source.
> 
> 102 ~ > file `which cpp`
> /usr/libexec/cpp: NetBSD/i386 demand paged dynamically linked executable
> 103 ~ > file `which as`
> /usr/bin/as: NetBSD/i386 demand paged dynamically linked executable

Can you show us what's on lines 130 (ish) to 160 (ish) of locore.s?

I did get some problems (see the duplicated inode thread) with
certain sources being overwritten by blocks from other files, which
was solved by renaming the corrupted file, and getting a new version
of the file in. But this was immediately obvious from the source
when this happened.

(I didn't report it as a bug, as I thought my hardware was suspect).

Alistair
--
Alistair G. Crooks (agc@uts.amdahl.com)			   +44 125 234 6377
Amdahl European HQ, Dogmersfield Park, Hartley Wintney, Hants RG27 8TE, UK.