This is a large package and build failures do not occur until well into the build process. Painfully slow. :) So let's move one step at a time. I would like to ignore previous koffice FTBFS reports. Start clean, now that the core packages all build and we have a known foundation and baseline.
The first failure errors seem to be related to wv2, an MS Word import package.
I'm still building packages on Slackware 12.2. That release came with wv2 0.2.3. Release 13.0 uses 0.2.3. The wv2 package was updated to 0.4.2 in Slackware 13.1.
Unless there is no choice, I believe 12.2 and 13.0 users should not have to update the wv2 package to build or install koffice. Certainly that might be required, but I prefer to work from the thesis that Trinity KDE should build and install on previous KDE 3.5.10 distros without such tinkering.
Previously we thought the failure was caused by an old version of wv2. Yet Lenny uses the same 0.2.3 version. Trinity koffice builds for that operating system. Thus we should proceed with the presumption the problem is not wv2 directly but the build process. As we have discovered the past several weeks, what builds on Debian does not always build on Slackware without some modifications. We don't know why but that is not important right now. :)
When I build koffice on 12.2 with wv2 0.2.3 installed, the first fatal build errors I receive:
document.cpp:393: error: 'const struct wvWare::Word97::BRC' has no member named 'cv'
I'm no C++ programmer, but seems some constants are not being used correctly or as expected or are not being declared correctly.
Note: Koffice builds successfully with no errors when wv2 is not installed.
I suspect only a few people will be interested in that version. Most people want basic MS Word import functions.