crosstar's bits of Sat, 17 Nov 2001 translated to:
> After this, you may wish to edit the file CONFIG. There are several
>values which you need to change in this file. Note that more recent
>versions of ht://Dig (after 3.1.0b2) will allow you to use At
>
>--------
You terminate the quote just before an important part ;) It goes
on to explain how you can pass 'configure' a number of arguments
that specify paths to important files/directories. For example
--prefix=
--with-cgi-bin-dir=
--with-image-dir=
--with-search-dir=
While manual modifications of CONFIG should work, using the
provided 'configure' arguments is probably a bit safer. Except
for exceptional cases, it should not be necessary to edit the
CONFIG file.
Also, if I recall your previous message correctly, you edited
CONFIG *after* running 'make' and 'make install'. Some of the
paths are compiled into the executables, so CONFIG would need
to be edited before building any executables.
>I believe you are suggesting that I edit CONFIG BEFORE running./configure,
>is that correct?
Not really. I was just suggesting that you use the 'configure'
arguments rather than editing CONFIG. Though in fact, the problem
you ran into is most likely due to the fact that you ran make
before completing the build configuration.
>One final point, would I need to delete everything and start over,
>extracting anew? I figured
That shouldn't be necessary. The following should work...
> make distclean
> ./configure (with arguments)
or
> ./configure (without arguments, followed by editing
CONFIG if you prefer)
> make
> make install
Jim
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
