Hello,

From: Greg Earle <earle@isolar.DynDNS.ORG>
Date: Sat, 17 Feb 2001 11:12:32 -0800

> > # make depend && make
> > (snip)
> > cc -g -O -pipe -Wimplicit -Wunused -Wswitch -Wcomment -Wtrigraphs \
> > -Wchar-subscripts -Wparentheses -Wstrict-prototypes -Wmissing-prototypes \
> > -Wpointer-arith -Wa,-Av9a -mno-fpu -I. -I../../../../arch -I../../../.. \
> > -nostdinc -DSUN4U -DTRAPWIN -D__ELF__ -DLKM -DDEBUG -D_LP64 \
> > -DMAXUSERS=32 -D_KERNEL   -c ../../../../kern/vfs_syscalls.c
> > {standard input}: Assembler messages:
> > {standard input}:322: Fatal error: Can't extend frag 98. chars
> > In file included from ../../../../kern/vfs_syscalls.c:60:
> > ../../../../sys/syscallargs.h:305: output pipe has been closed
> > cpp: output pipe has been closed
> > *** Error code 1
> 
> I ran into this building something in userland.  If you hand build this
> file without the "-g", I bet the "Can't extend frag 98. chars" message
> will go away.  However, it might come back again on the next file ...

I commented out the line as like
> #makeoptions    DEBUG="-g"
Then I succeeded to build my custom kernel.

But I have a question. 
How can I report bugs caused by the kernel?
The stack back trace without symbol information seems to be useless, 
I think.

Anyway, thank you very much for your suggestion.

koya