|
From: Black M. <mdb...@ya...> - 2020-03-26 13:39:55
|
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.
de Mike W9MDB
On Thursday, March 26, 2020, 08:31:33 AM CDT, Christoph Berg <my...@de...> wrote:
Re: Bill Somerville 2020-03-26 <6a2...@cl...>
> All I can say is that I think that type
> of restriction is wise with dynamically linked libraries, but with static
> linking there are no real issues since the forked content is fully
> encapsulated within the package using it.
Debian hates statically linked embedded code copies as well because we
don't want to have to rebuild all the reverse-dependencies if there's
a (security?) fix in the library.
If wsjtx requires a newer hamlib release, please make that hamlib
release happen.
Thanks,
Christoph
_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
|