6-STABLE oddity

Alex Roman alex.roman at gmail.com
Sat Nov 11 18:55:55 UTC 2006

Hello list,

I've installed 6.1 on my laptop, then proceeded with an upgrade to
6-STABLE (as per the handbook).

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.

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.

Here's an example:
/usr/X11R6/bin/moc ./kfilesharedlg.h -o kfilesharedlg.moc
if /bin/sh /usr/local/bin/libtool --silent --tag=CXX --mode=compile
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=pentium-m -fconserve-space -Wno-non-virtual-dtor
-fno-exceptions -fno-check-new -fno-common  -DQT_CLEAN_NAMESPACE
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

I've opened the file kpropertiesdialog.h, line 117, and here's what's in there:
                     bool modal = false, bool autoShow = true);
No, I've not misspelled it now, now false is spelled correctly!

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...

Any suggestions would be appreciated.
Thank you!


Alex Roman <alex.roman at gmail.com>

More information about the freebsd-stable mailing list