Date: Wed, 14 Jan 2004 21:57:15 -0700 From: Rich Hampton <rich@hamptonhouse.org> To: freebsd-sparc64@freebsd.org Subject: Re: syscons on U10 /w Creator Message-ID: <40061DAB.9090002@hamptonhouse.org> In-Reply-To: <20040115044616.GB18510@electra.cse.Buffalo.EDU> References: <4005FFC9.20308@hamptonhouse.org> <20040115031013.GA52532@xor.obsecurity.org> <400613C4.1090105@hamptonhouse.org> <20040115042921.GA18510@electra.cse.Buffalo.EDU> <4006191C.6000108@hamptonhouse.org> <20040115044616.GB18510@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
Ken Smith wrote: >On Wed, Jan 14, 2004 at 09:37:48PM -0700, Rich Hampton wrote: > > > >>Nope, I used vim. >> >> > >Ok, I don't think vim can do what I had in mind but I've seen the >symptoms you described. Emacs is capable of leaving a file that >doesn't have a newline character at the end of the last line of >the file. config(8) *really* loses it if either the kernel config >file itself or any of the support files config(8) uses doesn't have >the newline character at the end of the last line. > >The students here tend to use emacs, and I usually have around five >each year that have kernel builds blow up because when they added >some new files to include in the kernel build they didn't press >the return key at the end of the last line in sys/conf/files. Usually >config(8) runs without complaint but the kernel compile fails with >issues like what you had. > > > You know, for what it's worth, I've been bouncing back and forth between the old build method and the new. I didn't expect that to make any difference but maybe it's worth mentioning. Rich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40061DAB.9090002>