[SOLVED] has anyone made kchmviewer worked on slackware13.0 64bit ever??

igxz · 06-06-2010, 01:32 AM

hi there, tried install kchmviewer (5.1) from slackBuilds, but it seems like it's not compatible with slackware13.0 64bit. Also tried to install firefox chm reader add on, but its also 32bit available only! Has anyone installed any kinda of chm reader on slackware 13.0 64bit or any advise will be appreciated! thanks in advance!

Didier Spaier · 06-06-2010, 02:14 AM

To use 32bit only binaries on a 64 bits Slackware go multilib, see this page on AlienBOB's wiki.

mRgOBLIN · 06-06-2010, 06:22 AM

Pretty sure okular can read CHM files

H_TeXMeX_H · 06-06-2010, 06:25 AM

I use chmlib:
http://www.jedrea.com/chmlib/

Extract the chm into html files, then use FF to view them. Works fine.

Ok, I'll be more specific:

Code:

./configure --enable-examples
make
su
make install
extract_chmLib input.chm output_dir

then just click on one of the html files, there might be an index.

Gerard Lally · 06-06-2010, 10:53 AM

Quote:

Originally Posted by igxz

hi there, tried install kchmviewer (5.1) from slackBuilds, but it seems like it's not compatible with slackware13.0 64bit.

The Slackbuild worked fine for me on 13.0 64. Did you set ARCH=x86_64 as per the Slackbuilds FAQ?

igxz · 06-07-2010, 04:20 AM

Quote:

Originally Posted by gezley

The Slackbuild worked fine for me on 13.0 64. Did you set ARCH=x86_64 as per the Slackbuilds FAQ?

worked after set ARCH=x86_64 in "kchmviewer.slackBuild". thanks in bundle!

gauchao · 06-07-2010, 03:44 PM

I am using kchmviewer in Slack 13.1 64 bit - I've compiled it with slackbuilds.org. But Okular can also read your CHM files pretty well.

Gerard Lally · 06-07-2010, 04:20 PM

Quote:

Originally Posted by igxz

worked after set ARCH=x86_64 in "kchmviewer.slackBuild". thanks in bundle!

I could be wrong but I don't think you're supposed to change ARCH in the Slackbuild itself. Read Slackbuild FAQ 18 again!

Didier Spaier · 06-07-2010, 04:37 PM

In recent SlackBuilds available @ slackbuilds.org ARCH setting is done automatically in most cases, e.g. in kchmviewer.SlackBuild for Slackware 13.1:

Code:

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
fi

Thus setting manually ARCH is no more useful, unless architectures of the building system and the target system differ (in which case the ARCH manually set up externally will be preserved by the script).

Anyhow editing the script to do that, though may be inelegant, have never been forbidden AFAIK