On Wed, 11 Apr 2001, Micha�l Hug wrote:
> always"cannot open CONFIG"
> I think it's a problem of the CONFIG file.
Yes, this is probably correct.
> How have I to edit the file CONFIG ? With telnet or modifying the file locally
> before transferring it (after ./configure I suppose)
You can either edit it on the server using a program like pico, vi, or
emacs, or transfer it to another machine, edit it, and transfer it back.
> Is the file CONFIG.in or the file CONFIG that appear after the command
> .../configure that should be edited ? (the very first line of CONFIG is the good
> path to shell, #! usr/bin/sh )
If the first few lines of CONFIG don't look exactly like:
##
## CONFIG
##
then something is *very* wrong.
> Do I have to put all the support for the directories or only --prefix= and
> --exec-prefix= ?
No. If you like, you can supply --prefix= and --exec-prefix= when you run
the configure script, or you can edit them later in the CONFIG file.
> How should the root of the directory be specified ?
> "--prefix=/web/home/users/myself" for example ?
That's fine.
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
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
