From owner-freebsd-stable@FreeBSD.ORG Sat Nov 11 18:58:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EA0D16A403 for ; Sat, 11 Nov 2006 18:58:12 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50CFA43D49 for ; Sat, 11 Nov 2006 18:58:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 499651A3C1E; Sat, 11 Nov 2006 10:58:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 75EFC51390; Sat, 11 Nov 2006 13:58:02 -0500 (EST) Date: Sat, 11 Nov 2006 13:58:02 -0500 From: Kris Kennaway To: Alex Roman Message-ID: <20061111185802.GA7505@xor.obsecurity.org> References: <8c0c43de0611111055g51464f8dy77fe38053669597a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <8c0c43de0611111055g51464f8dy77fe38053669597a@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: 6-STABLE oddity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 18:58:12 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 11, 2006 at 01:55:52PM -0500, Alex Roman wrote: > Hello list, >=20 > I've installed 6.1 on my laptop, then proceeded with an upgrade to > 6-STABLE (as per the handbook). >=20 > During the make buildworld step, a file had a spelling error (atomoc > instead of atomic). Becaose o and i were so close I fixed the problem > and ignored it, thinking it was human error. >=20 > However, now, after the upgrade, I'm trying to install KDE from ports. > I've seen several such spelling problems: #defone instead of #define, > fanse instead of false. >=20 > Here's an example: > /usr/X11R6/bin/moc ./kfilesharedlg.h -o kfilesharedlg.moc > if /bin/sh /usr/local/bin/libtool --silent --tag=3DCXX --mode=3Dcompile > c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop -I../../kdecore > -I../../kio/kssl -I../../kjs -I./../libltdl/ -I../.. -I../../kdefx > -I../../kio/kio -I../../kio/bookmarks -I../../dcop -I../../libltdl > -I../../kdefx -I../../kdecore -I../../kdecore -I../../kdeui > -I../../kio -I../../kio/kio -I../../kio/kfile -I../.. > -I/usr/X11R6/include -I/usr/local/include -I/usr/local/include > -I/usr/local/include/libart-2.0 -D_THREAD_SAFE -pthread > -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include > -I/usr/X11R6/include -D_GETOPT_H -D_THREAD_SAFE -Wno-long-long > -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -pipe > -march=3Dpentium-m -fconserve-space -Wno-non-virtual-dtor > -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE > -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT > kfilesharedlg.lo -MD -MP -MF ".deps/kfilesharedlg.Tpo" -c -o > kfilesharedlg.lo kfilesharedlg.cpp; \ > then mv -f ".deps/kfilesharedlg.Tpo" > ".deps/kfilesharedlg.Plo"; else rm -f ".deps/kfilesharedlg.Tpo"; exit > 1; fi > In file included from kfilesharedlg.h:23, > from kfilesharedlg.cpp:20: > ./kpropertiesdialog.h:117: error: `fanse' was not declared in this scope > gmake[3]: *** [kfilesharedlg.lo] Error 1 > gmake[3]: Leaving directory > `/usr/ports/x11/kdelibs3/work/kdelibs-3.5.4/kio/kfile' >=20 > I've opened the file kpropertiesdialog.h, line 117, and here's what's in= =20 > there: > bool modal =3D false, bool autoShow =3D true); > No, I've not misspelled it now, now false is spelled correctly! >=20 > What is going on? There seems to be some sort of corruption happening, > but at what layer, I'm not sure. I don't think it's the disk, since > the information was right the second time... Such things are almost always bad ram. Kris --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFVh05Wry0BWjoQKURAtAjAKDW//4+4qGkVVkiaxpgZ67/VNLR2gCgkpE4 VjhgUelV3n2ma8cASs6LsIU= =jAe8 -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF--