If you were pulling from github and compiling yourself, it was probably looki for 'mygolded.h', which per the first step of the compile instructions you ne to edit 'mygolded.__h' to personalize it, and rename it to 'mygolded.h'.
Also, actually editing the config file and making sure paths and whatever els is correct is also helpful, as it may not successfully run with the default config.
If you were pulling from github and compiling yourself, it was
probably looki for 'mygolded.h', which per the first step of the
compile instructions you ne to edit 'mygolded.__h' to personalize
it, and rename it to 'mygolded.h'.
If it were an 'h' file, wouldn't that blow up the compile? /
This is on linux. I didn't use the default config, I did change it.
Seeing as the program doesn't even give a message to say *which*
file is missing -- I suspect the message I am getting is the OS's
default reaction to a condition code -- it doesn't make me really
want to use the program. One of the first things I learned as a
programmer is that if you have an error opening a file you need to
tell the user/operator which file it is that is the problem -- make
them search for it and you are getting called in the middle of the
night. ;)
If it were an 'h' file, wouldn't that blow up the compile? /
From golded-plus/docs/building.txt:
"Now go to golded3 and copy mygolded.__h to mygolded.h and adjust it for yourself (put your name, FTN address and e-mail). Goto root again."
Question it all you want, it is the first step you should do before compiling per the instructions.
Otherwise, if you don't want to use the program.. don't. It works just fine o other systems, including mine *shrug*. I'm just giving you the information yo need (and I've gained) to get it to compile and run properly. Please don't shoot the messenger.
From golded-plus/docs/building.txt:
"Now go to golded3 and copy mygolded.__h to mygolded.h and adjust it
for yourself (put your name, FTN address and e-mail). Goto root
again."
Question it all you want, it is the first step you should do before
compiling per the instructions.
uhhh, I wasn't questioning that it might need doing, if you are
compiling the code, but I am questioning "wouldn't it blow up the compile?" which, if mygolded.h is a required file, I am 100% certain
that it would.
uhhh, I wasn't questioning that it might need doing, if you are
compiling the code, but I am questioning "wouldn't it blow up the
compile?" which, if mygolded.h is a required file, I am 100% certain
that it would.
I didn't compile code, I got the recent pre-compiled *.deb so that
ain't my problem.
Would have thought that much was
obvious, since I was complaining about golded not giving a proper
error message -- which it did not here.
Installed it on another machine... it complained about a library
being missing - libncurses. The machine in question has two
versions, 4 and 5 including -dev for each, installed and other
programs that need it find it fine, including one I recently did
compile.
My impression is that it is POS-ware and I don't need to bother with
it.
If someone can't read the "buiding.txt" file, witch states what to
do. Then that is not the fault of the package.
Not really that obvious, but now that you've finally mentioned a .deb package, I figured I could let you in on a little secret: There is no "officially" supported .deb package for this program that I know of.
On Mon, Mar 09 2026 18:33:02 -0500, you wrote:
If someone can't read the "buiding.txt" file, witch states what to
do. Then that is not the fault of the package.
No way. It's crap because instructions aren't needed and we try to
install via an old unsupported .deb package! :D
| Sysop: | smooth0401 |
|---|---|
| Location: | New Providence, NJ |
| Users: | 3 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 12:22:31 |
| Calls: | 340 |
| Files: | 698 |
| D/L today: |
1 files (7K bytes) |
| Messages: | 57,500 |