Date: Fri, 7 Jul 2000 16:17:51 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: duhring@charter.net Cc: stable@freebsd.org Subject: Re: 4.0 Stable Compile Failure Message-ID: <200007072317.QAA42847@vashon.polstra.com> In-Reply-To: <00070620523100.08450@foo> References: <4.3.2.7.2.20000706135041.00bff100@64.20.73.233> <00070620523100.08450@foo>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <00070620523100.08450@foo>, David Uhring
<duhring@charter.net> wrote:
> Suggest you look at the file with an editor like kwrite which
> will color the text by syntax. I've several times found ???.c
> files that had one character converted to something else, either
> in TCP/IP transmission or tar -zxpf from the CD or maybe the file
> is corrupted in the repository. For instance, one time, make
> reported a missing endif; it was caused by a /* xxxxxxx */ showing
> up as /* xxxxxxx j/. Last night when I tried a make buildworld
> again, make reported a syntax error before '(' in line 121 of
> /usr/src/lib/libc/regex/regcomp.c. Where a space should have been
> was an extraneous '('. Changed it to a space and made buildworld
> just fine.
You've got hardware problems. "*" and "j" are identical except for
1 bit. That's a classic sign of bad RAM or cache.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007072317.QAA42847>