Consider, if you will, the following:

[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/xmlgui/kxmlguiversionhandler.o
[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/util/kkeyserver_mac.o
[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/windowmanagement/kwindowsystem_mac.o
[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/windowmanagement/kwindowinfo_mac.o
[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/kwallet_interface.o
[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/jobviewserverinterface.o
[ 26%] Building CXX object kdeui/CMakeFiles/kdeui.dir/jobviewiface.o
Linking CXX shared library ../lib/libkdeui.dylib
Undefined symbols:
  "mac_initialize_dbus()", referenced from:
      KApplicationPrivate::init(bool)  in kapplication.o
      KUniqueApplication::start(QFlags)in kuniqueapplication.o
  "mac_fork_and_reexec_self()", referenced from:
      KUniqueApplication::start(QFlags)in kuniqueapplication.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [lib/libkdeui.5.1.0.dylib] Error 1
make[1]: *** [kdeui/CMakeFiles/kdeui.dir/all] Error 2
make: *** [all] Error 2

Above is a linking error I received during the KDE 4.1 betas on OS X.

It is also, as it turns out, the linking error which people are getting when they try to compile kde 4.2 beta 2 on OS X. Back in my younger, more formidable years, I was actually able to not only identify the problem but also propose a solution. Then all of a sudden the problem disappeared and I didn't need to worry about it anymore.
Now, it seems, the bitch is back,
and, we here, on the mac,
would pretty please, like it sack. t.

Per'aps I should skip the poetry. Anyhoo, I reported this to kde-buildsystem and it seems that mail was lost to the ether. Also I hear bugs.kde.org isn't the proper place for this sorta thing. How 'bout one of you just fix it? I've even done half the work for you already, you just have to make it pretty (or somethin').

While we're on the subject of build issues, kdelibs doesn't build with gcc 4.0.1 which has prompted me, in my infinite wisdom, to force building with gcc 4.2. The problem is people on Tiger (OS 10.4) only have 4.0.1. Did I mention that Apple's gcc is patched to accept special non-gnu options. Yah. Soooooooo, in comes this patch to macports (packaging system like BSDs ports i suppose) which allows the masses still in the mire of Tiger to enjoy the KDE 4.1 goodness. The problem is it uses gnu's gcc not apple's. Is it OK to build KDE this way? Are there any apple gcc-isms in the mac specific KDE code? Will Benjamin ever return to save me? These and other questions possibly answered in the comments!