On 10/29/2017 4:35 AM, Bill Somerville wrote:
Hi Denton,
as noted in the User Guide and this file:
https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0/README.txt/download
the binary packages for Linux systems that we provide at release time
are specifically for the listed distributions and versions, in this
case for Ubuntu 16.04 LTS. I assume you are not using that
distribution or version or if you are you have not updated to the
latest updates.
For other distributions and versions you must either build yourself or
wait for our Linux packagers to make appropriate builds available. For
Ubuntu that has already happened via Greg, KI7MT's, Launchpad based
PPA. He posted yesterday with details for WSJT-X v1.8.0 GA.
The problem here isn't that he isn't up to date. The problem is he is
out in front. Debian 9.2 has libreadline version 7, not 6. This means
that this wsjtx release will work for the older Ubuntu 16.04 LTS, but it
probably won't work for newer Ubuntu releases either, since Ubuntu (not
LTS versions) is typically out in front of Debian stable releases, since
Ubuntu is based on Debian testing.
Two notes, one for Denton and one for the wsjtx developers in general:
1) For Denton: Sometimes it is possible, depending on dependencies, to
install both versions of a library on your system. This doesn't cause a
collision, it just allows things linked against libreadline7 to work
with libreadline7 (for example) and things that link against
libreadline6 to work with libreadline6. The problem is that
libreadline6 may have required dependencies that will prevent it from
installing. You can try the experiment by downloading the libreadline6
package from the oldstable release. Looking at your posting it appears
you are running a 64 bit version of Debian, so here is the link to
libreadline6 from Debian Jessie (8.0):
http://http.us.debian.org/debian/pool/main/r/readline6/libreadline6_6.3-8+b3_amd64.deb
You would need to download that and install it with dpkg -i (as root).
As long as you don't pass in an option to force the install, dpkg will
let you know whether that is workable or not. It may not work, but it
should be safe to try the experiment.
2) For the wsjtx developers: It's tough to release binary packages that
cover the wide range of linux releases. But you can greatly increase
the chance of things working by linking statically against smaller
libraries like libreadline. Of course, you could link statically against
everything, and it might be worth experimenting with that to see how big
wsjtx gets. The disadvantage of linking statically is that if there are
bugs in the libraries you use they won't be fixed by people updating to
a new version of the library (i.e. they would be dependent on you
releasing a new version of wsjtx), which can be especially bad if the
problem is a security issue. However, wsjtx by its nature isn't likely
to be used as an exploit path for hackers.
But even if you only link statically against smaller libraries you can
improve your portability. Note that even when you link statically
against large libraries (e.g. libc) you only pull in the modules you use
out of libc. Anyway, it's just a suggestion to weigh the pluses and
minuses of linking statically against at least some of the libraries
used by wsjtx.
Regards,
John
AC0ZG
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
