kchmviewer-7.1安装错误的解决方法
Linux / 2014年11月15日

原创内容,转载请注明出处: https://www.myzhenai.com.cn/post/1925.html
kchmviewer依赖QT,所以在安装之前您必须先要安装QT,请参考官方安装包里的README文档.
3. INSTALLATION
Usually kchmviewer is distributed in source code archive, so you need to compile it first. It requires Qt version
4.4 or higher. Note that you need to install qt4-devel and qt4-tools packages (the last one might be included in
qt4-devel in your distribution), not just qt package.
Also make sure you have chmlib-devel (some distros have it as libchm-devel) package installed. KDE build will check
for its presence, but qmake does not have necessary functionality to do so. If you are getting errors regarding missing
chm_lib.h file this means chmlib-devel is not installed.
3.1. Qt-only version
To compile Qt-only version of kchmviewer, follow the procedure:
> tar zxf kchmviewer-.tar.gz
> cd kchmviewer-

> qmake
> make
The compiled binary is in bin/kchmviewer. You could copy it somewhere, or use it as-is. It does not require installation.
If QtWebKit module is not found, you will get the following error:
> kchmviewwindow_qtwebkit.h:25:21: error: QWebView: No such file or directory
Either install QtWebKit module, or remove “webkit” from QT+= line in src/src.pro

3.2 KDE4 version
To compile the version of kchmviewer with KDE4 support, follow the procedure:
> tar zxf kchmviewer-.tar.gz
> mkdir build
> cd build
> cmake ..
> make
> sudo make install
For KDE version the installation is required, since the KHTML KIO slave cannot be used in place.

ClamTk或Clamav运行提示libclamav错误的解决方法
Linux / 2014年09月2日

原创内容,转载请注明出处:https://www.myzhenai.com.cn/post/1868.html
具体情况是这样的,昨天晚上我运行ClamTk的时候发现窗口停留了一会就自动退出了,并没有弹出程序窗口,我想可能是出现什么问题了,于是在终端里运行clamtk,提示以下的错误.

ERROR: This tool requires libclamav with functionality level 77 or higher (current f-level: 74)
Error parsing time at /usr/lib/perl5/Time/Piece.pm line 470.

 
我卸载了ClamTk和Clamav并且重装了这两款程序,但是发现并没有解决问题,运行的时候仍然是提示以上错误,我知道Libclamav.so肯定是Clamav和ClamTk的一个依赖库,于是我便搜索系统里的这个文件,发现搜到很多个不同版本的文件,我便想会不会是我之前安装了不同版本的程序遗留下来的库文件,于是我便将这些文件全部删除了再重新安装,问题解决了,问题真的出现在这里.