I'm not suggesting moving away from shared libraries....just noting that hamlib
wasn't designed to allow references to internal data structures with shared
libraries. Static linking does fix that problem. What happened was a new
variable in hamlib_port_t realigned the rig_caps data structure and vfo_list
points to incorrect data as the 1st thing that gets referenced.Hamlib 5.0 will
completely break such backwards compatibility in shared libraries as I plan on
making changes to reduce the fragile structure layout and eliminate anybody
trying to refer to rig_caps except through an API.
I was hoping that rigctld-wsjtx does work correctly...did you try that one?
Mike W9MDB
On Wednesday, January 6, 2021, 07:42:32 AM CST, Christoph Berg
<m...@debian.org> wrote:
Re: Black Michael via wsjt-devel
> Does the Debian WSJT-X use hamlib as a shared library?
> Sounds like that may be the problem.
Mike, please stop suggesting that moving away from shared linking
would solve any problems. That will not happen on Debian.
> There is a binary incompatibility that happened under shared library use so
> if you use the rigctld-wsjtx from WSJTX it should hopefully work....not the
> rigctld from hamlib-4.0
> There's a future fix that will hopefully be in the 2.3.0 GA release that
> fixes this problem.
I'm using the hamlib rigctld. That works fine with fldigi also linked
against hamlib 4.0, so that shouldn't be a problem.
Christoph
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
