[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

re: ARRL's LoTW with Debian Sarge



I couldn't use the ARRL binaries because i'm running on a PowerPC, so i
had to build it from scratch.  So here's a (perhaps) boring description
of what it took to get as far as being able to request a certitificate
from the ARRL.

Here's the packages i needed to build 'tqsllib':

   libssl-dev
   libexpat1-dev
   libtool

Compilation still failed because 'openssl_cert.h' contained

   #include <openssl/e_os.h>

which didn't exist after installing the above packages.  So i commented
out the reference to 'e_os.h', since there was a remark about working
around a bug anyway, and it seemed to compile with a nominal number of
warnings.

When i tried to build 'TrustedQSL-1.06', i found no README file, so tried
the procedure for 'tqsllib', given the directory was called 'tqsllib-apps'.
'./configure' failed because it couldn't find 'tqsllib'.  So i tried the
suggestion './configure --with-tqsllib=/usr/src/tqsllib', but no luck there
either.  That didn't work, so i read 'configure' file and then defined
$TQSLLIB as an environment variable [see below].  Then './configure' 
succeeded.  But it shouldn't have, as compilation lost with:

    tqslcert.h:18:23: wx/wxprec.h: No such file or directory
    tqslcert.h:19:23: wx/object.h: No such file or directory
    tqslcert.h:20:23: wx/config.h: No such file or directory
    tqslcert.h:27:27: wx/wx.h: No such file or directory
    tqslcert.h:30:23: wx/wxhtml.h: No such file or directory

So 'configure' needs to check for this as well as having '--with-tqsllib'
work properly.  So add to the package list:

    libwxgtk2.4-dev

Now, i find out that the libraries are in a different directory, so
$TQSLLIB should have been set to '../tqsllib/.libs' instead.  It then
compiles, and one can start './tqsl', once 'libtqsllib.so.0' is put
somewhere in one's library path.  However, './tqslcert' doesn't do so 
well, complaining "Configuration file error" if one tries to request 
a certificate (by answering "Yes" to the initial query, for example).

Hmmm, maybe it needs to be installed...

    sudo make install
    strip tqslcert tqsl
    /usr/bin/install -c -d /usr/bin /usr/share/doc/tqslcert /usr/share/doc/tqslapp /etc/tqsl
    /usr/bin/install -c -C tqslcert tqsl /usr/bin
    /usr/bin/install: invalid option -- C
    Try `/usr/bin/install --help' for more information.
    make: *** [install] Error 1

Changing '-C' to '-D' in the 'Makefile' seemed to fix that, but then i got:

    sudo make install
    strip tqslcert tqsl
    /usr/bin/install -c -d /usr/bin /usr/share/doc/tqslcert /usr/share/doc/tqslapp /etc/tqsl
    /usr/bin/install -c -D tqslcert tqsl /usr/bin
    /usr/bin/install -c -D tqslcert_help/*.* /usr/share/doc/tqslcert
    /usr/bin/install -c -D tqsl_help/*.* /usr/share/doc/tqslapp
    /usr/bin/install -c -D ../licenses/* /usr/share/doc/tqslapp
    /usr/bin/install: cannot stat `../licenses/*': No such file or directory
    make: *** [install] Error 1

So i picked up the .rpm for i386, and tried to convert it, with the
expected failure due to machine-type mismatch.  However, amid the 
debris could be found

    .../tqsllib-1.0/debian/tqsllib/etc/tqsl/config.xml

Which i copied to /etc/tqsl, and then 'tsqlcert' ran nominally (but i'm
still not sure the 'install' completed properly).  

Alas, the certificate information in 'tqsllib-1.2-1.i386.rpm' did not
appear to be valid, as it referred to the beta-test program.  HOWEVER,
it did seem to be accepted if mailed to 'lotw-logs@arrl.org' and not the
address mentioned in the pop-up window (lotw-test@arrl.org).  *whew*
We'll see what happens when i get my postcard in the mail...

I hope this helps and maybe someone can generate a Debian package for
this, as it's not exactly straightforward (and thus help out those of 
us who have clearly chosen not to run Windows by having a non-Intel 
achine).
		      -- KD6PAG  (Networking Old-Timer, Satellite QRPer)

P.S.  Hmmm, i wonder if it has provisions for separate uplink and downlink
frequencies...



Reply to: