Try building with NOWERROR=1 as I suggested for Mac PowerPC. Unfortunately Aaron sneak-attacked the release so I wasn't able to run it against the gauntlet beforehand (although that specific warning is invalid and a sign of a broken version of GCC).
It's weird. I didnt get that src/emu/ui.c error when i compiled just before u3. But I did get it when I compiled from mess svn. No idea how that happened, my mame tree is clean.
Yeah. I'm also a little surprised later Xcode didn't care about the "ObjC won't call C++ constructors" issue. I guess that's something Apple eventually changed, although since the debugger explicitly initialized the class members and that's all the constructor did it would work out anyway.
Incidentally, that warning is a bug in GCC that was fixed for 4.3 (Red Hat had been patching it in the Fedora and RHEL packages since 4.1.something). The variable isn't actually uninitialized.