Just made some compile tests from source code loaded from WSJT home
page. I used instructions from file INSTALL of the tgz.
I found interesting "feature" when using Fedora 33, Icom 7300 having
split=rig and rig net Hamlib rigctld, localhost:4532 with rigctld
started before wsjtx (to share rig with other programs)
When I select any frequency from band selector IC7300 jumps to that
frequency, but when I start to Tune or enable TX rig will take the
frequency what exist in that moment in vfo B and put it to vfo A for
transmit.
I.E. if I have selected 50.313 and my vfo B is still in 21.095 then TX
or Tune will took 21.095 to vfoA and start transmit on 15m when it
should be at 6m.
This happens with wsjtx compiled from WSJT home page's wsjtx-2.4.0.tgz
and wsjtx-2.5.0-rc1.tgz in same way.
But it does not happen with previously downloaded wsjtx-2.3.1 source
from WSJT home page.
I do the compile always in same way, so there must be something happened
from jump 2.3.1 upwards.
What makes it more weird is that wsjt-x 2.4.0 installed from Fedora33
repository package works ok, like self compiled 2.3.1
On the other hand package wsjtx-2.5.0-rc1.x86_64.rpm from WSJT home page
does not install at all having several conflicts with liboost, libc and
libstdc++
Just to FYI, I'm keeping 2.3.1 as it works.
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
