> Conspicuous is the 'shouldnotlink' directives. In 0.2.3 > that directive is no and in 0.4.2 the directive is yes. > > I'm just guessing here. I changed the 0.4.2 directive to no > and tried to build. FTBFS. > Another noticeable difference is the 0.4.2 la file does not > contain a header statement about being a libtool library > file. that missing header statement would correlate with the > build error message that the file is not valid. I copied this header statement from 0.2.3 to 0.4.2: # libwv2.la - a libtool library file # Generated by ltmain.sh - GNU libtool 1.5.18 (1.1220.2.245 2005/05/16 08:55:27) koffice built. File size is slightly larger, which probably is correct. I haven't yet tested the MS Word import features, but for the moment I'll presume the package compiled correctly. I'll take a wild guess only the first line in that header statement is necessary. wv2-0.4.2 was not introduced into Slackware until release 13.1. The problems I am experiencing with the package would not be discovered in that release because KDE 4 is included and not 3.5. Hence, the build bug with the missing header statement is unlikely to surface with that release. As wv2-0.4.2 is built with cmake, I don't know how the libwv2.la file gets created during the build process. I could rebuild that package and try to learn. Questions: Am I correct Debian does not include a libwv2.la file in its package? Should I try to build koffice without that la file installed?