> The fixes will have to wait for 3.5.13; why don't you open
> new bugs for
> both issues?
> 
> For 3.5.12, --disable-lame will simply be required, as well
> as the include
> statement ln hack.  I've seen much worse hacking in
> Ubuntu as they try to
> force an upstream package to work on their distribution.
> ;-)  Both issues
> will be a priority for 3.5.13.

Within my chroot environmnet I built both kaffeine 0.8.7 and 0.8.8 from the upstream tarball. That tended to indicate the problem is not with any installed packages.

Tried building with no -j flag. FTBFS.

Next tried --enable-closure.

Kaffeine built.

Well, well. That old ghost returns.

Played an AVI video and MP3.

I'll update the --enable-closure list in the wiki.

I'll submit a bug report for the build warning messages.

I'll submit a bug report for updating the version. Trinity is at 0.8.6. Last KDE3 release was 0.8.8, which I built without error in my chroot. Tested an AVI and MP3 in my virtual machine running Trinity was satisfactory.

Oy!