Skip to content

fllog

Logging server the W1HKJ programs write contacts into

What it does

Keeps an ADIF log and serves it over XML-RPC, so fldigi, flnet, flrig and the rest record contacts into one place rather than each keeping its own. It has a modest interface of its own for searching, editing and exporting.

Why you would want it

The suite's logging problem is that several programs each know part of a contact. This is the shared answer: one log, written by whichever program is in front of you, without export-and-merge afterwards. As a standalone logger it is thin -- CQRLOG, KLog and xlog are all better at that -- and as the suite's log server it has no substitute.

Before it will work

Nothing to start. The programs that will write into it need to be pointed at its XML-RPC address, which is a setting in each of them.

How it installs

  • source (autotools) from https://w1hkj.org/files/fllog/fllog-1.2.9.tar.gz
  • build dependencies: build-essential, pkg-config, libfltk1.3-dev
  • Build dependencies are MEASURED, not copied. Built in a Debian 13 container on 2026-08-28 with build-essential, pkg-config and libfltk1.3-dev and nothing else: configure exits 0, make exits 0, and the binary appears. AHRL lists extra packages for some of these (libpng-dev and libxft-dev for flcluster, libsamplerate0-dev for flnet); they are not needed, because libfltk1.3-dev already pulls what the build uses. This is the same over-specification the fldigi manifest records for libportaudio-ocaml-dev. The sha256 is ours. Upstream publishes checksums for its Windows installers only -- w1hkj.org/files/sha256vals.txt lists .exe files and no source tarballs -- so this digest was computed from the tarball fetched from the project's own site on 2026-08-28. It pins the exact bytes that were reviewed and built, which is the guarantee actually on offer; it is not an upstream signature and this manifest does not imply one.

Binaries this produces:

  • src/fllog

Known problems

Not a general-purpose logger and not trying to be: no award tracking, no online-service uploads, no QSL management. Use it as the suite's log and export ADIF into a real logger if you want those. Not packaged on any target. Debian carries libflxmlrpc-dev at 0.1.4 and this build asks pkg-config for flxmlrpc >= 1.0.1, so the system library is NOT used: configure falls back to the copy bundled in the tarball and its summary line reads "Have flxmlrpc library ....... internal lib". Measured, not inferred. Installing libflxmlrpc-dev alongside would change nothing, which is why it is not a build dependency here.

Keeping it current

  • probe: none
  • strategy: rebuild
  • W1HKJ releases irregularly and announces on the linuxham list rather than through a tagged repository, so there is nothing to probe automatically. Check w1hkj.org/files/fllog/ when something else in the suite moves.

Where to get help with the software itself

The W1HKJ suite. The linuxham group on groups.io is where questions are answered. Note that Debian's Homepage field for the packaged members of this suite points at w1hkj.com, which now redirects to an unrelated site -- .org is the project.

Source: catalog/packages/fllog.yaml