> > I probably should try building koffice without the wv > package installed > > since that package is not part of the stock > Slackware. > > > > I don't know if kdepim will build without wvware as it is > used to import > MS documents, but please let me know either way. Did you mean koffice rather than kdepim? I'm a tad confused, but I was getting sleepy when I quit last night. Short story: the wv package is not a part of the stock Slackware and was not installed in my chroot environment. So what caused the build failure? Today I realized there is a wv2 package installed by the stock Slackware. The wv and wv2 packages are not the same. Looking at the include declarations in texthandler.cpp shows wv2 and not wv. Therefore the wv2 package was the problem. Now I'm less confused. The wv2 version provided by Slackware 12.2 and 13.0 is 0.2.3. The version provided in Slackware 13.1 and Current is 0.4.2. I'll run a koffice build with the newer version of wv2. If koffice builds without failing with that same error then 0.4.2 will become another dependency. Yet that raises a question. What changed from 3.5.10/1.6.3 that created this error? As koffice built in 12.2 with the older version of wv2 without such errors, something changed. I should know what changed since 3.5.10/1.6.3 to create this newer dependency so I can add that information to the documentation I am preparing.