That's done in the devel tree and now we just hit the kde compiler blacklisting.
 *sigh*

I've looked at the KDE spec files in CVS and I've search the list archives, but
I can't find The Right Way to deal with this. I've seen that gcc4 in FC4 is
patched against the bug causing KDE to be miscompiled, but how should I deal
with the blacklisting itself now ? Should I just patch the configure script ?

Yeah, that's the way I'd do it.

x86_64:
checking for Qt... configure: error: Qt (>= Qt 3.2) (library qt-mt) not found. P
lease check your installation!
For more details about this problem, look at the end of config.log.
Make sure that you have compiled Qt with thread support!

i386:
grep: /usr/lib/libltdl.la: No such file or directory
/bin/sed: can't read /usr/lib/libltdl.la: No such file or directory
libtool: link: `/usr/lib/libltdl.la' is not a valid libtool archive

ppc:
ERROR: something went wrong rebuilding the .src.rpm


[...]

Comments:

x86_64: looks like $QTDIR problems, though I wonder why? (multilib installation
sourcing the i386 one?)

ppc: some dependency missing? Could not find a missing package on ppc in a brief
BR check?

i386: smells like the %fedora conditional BuildRequires on libtool-ltdl-devel
doesn't work.

=> giving 1.2.4-3.fc4 a try in the build system

Status update: Some unknown update in the extras buildsys now causes the build
to fail with lots of C++ errors, also on i386. One can see how it managed to
build a few hours ago:
http://extras64.linux.duke.edu/failed/4/amarok/1.2.4-3/i386/  The new problems
are probably related to gcc-4.0.0-9, since I cannot reproduce it with
gcc-4.0.0-8 and need to sync with Rawhide. Additionally, on ppc, the src.rpm
refused to build, again without no reason given. Filed that as 159414.

1.2.4-6 made it. No ppc src.rpm build problem fortunately.