What makes you think WSJT-X needs to use the system libraries? There's no such
requirement that I've ever heard of.WSJT-X is written (as are all applications)
to use specific capabilities in hamlib.
I'll bet that if you do "ldd wsjtx|grep hamlib" you won't see hamlib referenced
at all...because it's statically linked.
WSJT-X distributes the complete hamlib utility set with it too.
Using the 3.3 version is just going to result in you getting lots of complaints
about bug and rigs that aren't implemented or don't work.
We have finally cleared up all known bugs in hamlib and found a bunch more
through the use of static analysis tools.
de Mike W9MDB
On Thursday, March 26, 2020, 08:45:04 AM CDT, Christoph Berg
<[email protected]> wrote:
Re: Black Michael via wsjt-devel 2020-03-26
<[email protected]>
> The hamlib release you need is in the WSJT-X tarball.Read the directions on
> building it.Since you maintain the Fedora distribution you should be building
> it correctly and not use your system hamlib.
> And you are linking the static libraries when you build WSJT-X unless you
> changed the default flags....you're just using the 3.3 static libraries
> instead of the 4.0 version provided with WSJT-X.
This isn't going to happen. wsjtx need to use the system library like
all other packages in Debian. I guess the situation is the same in
Fedora.
Christoph
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
