On Monday, July 7, 2003, at 01:28 PM, David Herder wrote:
> I am attempting to install ht://Dig on Mac os 10.2.6. I have =20
> compiled and run the makefile utilities, although when I run the =
> script, I get a command not found error.
This sounds like a problem with the way things were installed. Did you =20=
do a standard 'make install', or did you install the programs in some =20=
other manner? Are you sure you had sufficient permissions to install =20
the file in the location you specified when you ran 'configure'? Does =20=
the BINDIR variable in rundig point to the directory where htdig, et. =20=
al. are located?
> If I separately execute htdig and htmerge, everything seems to be ok, =20=
> when I run htnotify, the script just seems to run forever (about =20
> 5min). When
This is a known issue. If you are interested in the gory details, see =20=
the following thread.
There is a patch that at least partially corrects the problem at
However if you need to use htnotify, the easiest fix is probably to =20
just create prefix and suffix files and specify them accordingly in =20
your ht://Dig config file. See the following links for more information.
> I launch the search.html file, I get a popup error:
> Can't find file. No file exists at =93/cgi-bin/htsearch=94.
Again, this sounds like an installation problem. The error implies that =20=
htsearch was either not installed or not installed in the CGI directory =20=
specified by your Apache configuration file.
How did you specify the location where the components were to be =20
installed? Did you use the 'configure' options described at =20
http://www.htdig.org/install.html (e.g. --prefix, --with-cgi-bin-dir, =20=
> How can I troubleshoot this in Terminal without having to deal with =20=
> problems that Apache config may be causing?
You can try running htsearch from the command line; however it sounds =20=
like the real problem is that something went very wrong with your =20
ht://Dig install. If you don't see some other easy fix, it might be =20
easiest to delete the installed components and try again from scratch. =20=
I was able to install 3.1.6 on a current version of OS X without any =20
major obstacles, so I don't think you will run into any show stoppers.