As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option.
If neither "-c" command line option, nor FIDOCONFIG environment
variable is defined, then the fidoconfig location is given by CFGDIR
and CFGNAME defined in huskymak.cfg during compilation.
$ hptlink -t crimea.talk hptlink/lnx 1.9 2023-01-07
Could not find Config-file
Would you be so kind to add "-c" option?
As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option.
Some mails before:
If neither "-c" command line option, nor FIDOCONFIG environment
variable is defined, then the fidoconfig location is given by
CFGDIR and CFGNAME defined in huskymak.cfg during compilation.
I think that's a good usual default.
$ hptlink -t crimea.talk hptlink/lnx 1.9 2023-01-07
Could not find Config-file
Would you be so kind to add "-c" option?
And fix the usual default config detection first? ;-)
Btw, is the config file detection part of every individual module or
is it a centralized fidoconfig function?
Sysop: | Angel Ripoll |
---|---|
Location: | Madrid, Spain |
Users: | 13 |
Nodes: | 8 (0 / 8) |
Uptime: | 79:43:38 |
Calls: | 386 |
Files: | 15,077 |
Messages: | 56,277 |