Honestly said, I don't understand, Ray.

Unfortunately, we still don't know what distro you are using etc. Basically all distros are equal :-), however some of them are not well equipped by default (of course all what you need can be instaled).

Also, what does ldd?

Open a terminal window and navigate to your cqrlog folder. You don't need to use sudo, su or switching to root mode. Simply type

ldd cqrlog


and you get a bunch of lines (~20-30) looking similar to this:


bash-3.1$ ldd cqrlog
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7fe6000)
libdl.so.2 => /lib/libdl.so.2 (0xb7fe2000)
librt.so.1 => /lib/librt.so.1 (0xb7fd9000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7fa7000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7ec0000)

... and so on

If any line indicates "not found", you have the culprit!

If all lines seems OK (ie. none of them contains any "not found" remark), continue, please:
...
The Debug=1 option in your cqrlog.cfg switches on the debug mode, however you must start cqrlog from the command line to see something.

Open a terminal window and navigate to your cqrlog folder. You don't need to use sudo, su or switching to root mode. Simply type

./cqrlog

and cqrlog starts. You can watch the terminal window to observe what is happened, how the program responds to commands, incoming spots etc.

You need probably to redirect the output from the terminal window to a text file. Try this :

./cqrlog > err.txt

which generates a text file named err.txt with full output of the terminal window. Content of this file helps a lot!

See ya later,
Martin, OK1RR