Ok I see.
Then someone better update the info in the INSTALL file
(https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/INSTALL):
The Hamlib library is required. Currently WSJT-X needs to be built using
a forked version of the Hamlib git master. This fork contains patches
not yet accepted by the Hamlib development team which are essential for
correct operation of WSJT-X. To build the Hamlib fork from sources
something like the following recipe should suffice: $ mkdir
~/hamlib-prefix $ cd ~/hamlib-prefix $ git clone
git://git.code.sf.net/u/bsomervi/hamlib src
Thanks!
On 12/10/23 21:48, Black Michael wrote:
No...that particular fork was created when Hamlib was not getting updated.
Mike W9MDB
On Sunday, December 10, 2023 at 02:27:28 PM CST, Daniel
Uppström<vfz.dan...@gmail.com> wrote:
Oh, that's unfortunate.
I thought this particular fork was necessary for WSJT-X and not the main branch
of Hamlib?
/SM6VFZ
Den sön 10 dec. 2023 19:22Black Michael via
wsjt-devel<wsjt-devel@lists.sourceforge.net> skrev:
Since Bill is silent key that repository has been removed.
The permanent home of Hamlib is here:
https://github.com/Hamlib/Hamlib
Mike W9MDB
On Saturday, December 9, 2023 at 02:33:42 PM CST, Daniel Uppström via
wsjt-devel<wsjt-devel@lists.sourceforge.net> wrote:
Hi,
When trying to build WSJT-X from source these days I cannot any longer access
the Hamlib fork:
git clone git://git.code.sf.net/u/bsomervi/hamlib src
Cloning into 'src'...
fatal: remote error: access denied or repository not exported:
/u/bsomervi/hamlib
Any ideas?
/Daniel SM6VFZ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
