The wiki states:
The libwv2.la file provided upstream is broken with respect to automake and will cause automake to fail. Basically, /usr/lib/libwv2.la is missing a proper header statement. This should be patched when creating the wv2-0.4.2 package.
I built the latest wv2 source using cmake. When using this package, koffice build fails at libwv2.la (as mentioned). Does this need patching for cmake too? If so where does one find the patch?
This is the snippet I use in my SlackBuild build script:
if [ -n "`/bin/ls /var/log/packages/wv2-0.4.2* 2>/dev/null`" ]; then # This newer version of wv2 is compiled with cmake and ignores compiling with automake. # The libwv2.la file provided upstream is broken with respect to automake and will cause # automake to fail. This should be patched when creating the wv2-0.4.2 package, but if # not then patch the installed version here. The wv2-0.4.2 package from Slackware 13.1 or # later will contain this same bug. echo "wv2-0.4.2 is installed. Checking /usr/lib/libwv2.la header." if [ -f /usr/lib/libwv2.la ]; then if [ -n "`grep 'libwv2.la - a libtool library file' /usr/lib/libwv2.la`" ]; then echo "Looks like libwv2.la contains a proper header statement." else echo "/usr/lib/libwv2.la is missing a proper header statement." ( cd /usr/lib echo "Creating backup copy libwv2.la.orig." cp -p /usr/lib/libwv2.la /usr/lib/libwv2.la.orig echo "Patching..." cat $CWD/libwv2.diff | patch -p0 --verbose --no-backup-if-mismatch || exit 1 ) fi else echo "The /usr/lib/libwv2.la file is missing. Exiting." exit 1 fi fi
This is the patch is use:
--- libwv2.la 2010-09-18 11:40:09.000000000 -0500 +++ libwv2.la.new 2010-09-18 11:39:18.000000000 -0500 @@ -1 +1,3 @@ +# libwv2.la - a libtool library file +# Generated by ltmain.sh - GNU libtool 1.5.26 (1.1220.2.492 2008/01/30 06:40:56)
Koffice crashing after opening template.
When i start some of the koffice apps (kword, kspread) they crash after opening the default template. Removing the %u from the .desktop files and provding the full path to the executable seems to work for me.
I do not experience any crashing, but sounds similar to bug report 657.
Darrell