Menu
▾
▴
wsjt-devel — WSJT software development
You can subscribe to this list here.
| 2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
| 2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
| 2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
| 2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
| 2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
| 2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
| 2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
| 2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
| 2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
| 2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
| 2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
| 2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
| 2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
| 2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(11) |
Sep
(92) |
Oct
(45) |
Nov
(33) |
Dec
(2) |
|
From: Marco C. <mar...@gm...> - 2025-12-05 22:54:09
|
Just a test. --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Philip G. <pjs...@no...> - 2025-12-01 14:16:05
|
Hi It turns out that the timestamp that gets sent to PSKReporter when it reports the time of an FT4/FT8 message etc is (unfortunately) not standardised as to whether it is the *start* of the transmission slot, or the *end* of the transmission slot, or *when* the decode completes. I suspect that WSJT-X reports the time that the decode completes. This timing is important as I want to group reports that happen in the same timeslot in order to determine which receivers are reporting the wrong frequency. Currently, I have a table that maps software versions onto the decoding approach that they use -- but this is pretty horrible. I'd like everybody to move to reporting the *start* of the transmission slot as the relevant time. For FT4, it wouldn't matter whether the start time is rounded up or down. Could you make this change? Thanks Philip> s |
|
From: <ja...@co...> - 2025-11-30 12:56:50
|
All, Using WSJT-X 3.0.0.-rc1 on Windows 10, version 22H2, I was monitoring 3573 kHz FT8 this morning and got the following sequence of decodes in the Rx Frequency window: 104100 -19 0.4 1701 ~ CQ VE3TCS EN82 104130 -11 0.4 1701 ~ CQ VE3TCS EN82 104200 -18 0.4 1700 ~ *** bad message *** a7 104430 -11 0.4 1700 ~ CQ VE3TCS EN82 104500 -20 0.3 1709 ~ CQ VE3TCS EN82 104530 -20 0.4 1709 ~ CQ VE3TCS EN82 104600 -11 0.4 1709 ~ CQ VE3TCS EN82 Interestingly, there was no corresponding "*** bad message ***" decode in the Band Activity window at 104200 (or, indeed, any other decode at or near 1700 Hz df). A priori decoding was, of course, turned on. I was unable to reproduce this event. I've never seen a "*** bad message ***" decode in any WSJT-X version before, so I thought I would report it just for the record, in case this meant more to someone else. If this is considered a feature and not a bug, I would suggest making a note of possible "*** bad message ***" decodes somewhere in the version documentation, including mention that they will (may?) not be seen in the Band Activity window. 73, Ed N4II. |
|
From: Rick <gm...@gm...> - 2025-11-29 11:15:35
|
Hi, I run Linux Mint 22. From the build process for WSJT-X Ver 3 gcc is 4:13.2.0-7ubuntu1 g++ is 4:13.2.0-7ubuntu1 gfortran 4:13.2.0-7ubuntu1 No problems compiling any recent WSJT-X versions HTH Rick (GM4JIB) On 29/11/2025 00:46, grday--- via wsjt-devel wrote: > > What version of the GNU g++ and FORTRAN compilers are currently > recommended for building WSJTX? > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: <gr...@gr...> - 2025-11-29 00:46:57
|
What version of the GNU g++ and FORTRAN compilers are currently recommended for building WSJTX? |
|
From: Marco C. <PY...@ou...> - 2025-11-24 23:39:36
|
LAST message (but not LEAST!) The issue I face with my YAESU FT-100 is independent by the hamlib version installed! _Using WSJTX-2.7.0 this issue is not present._ Using WSJTX-3.0 (classic) or WSJTX-3.0 Enhanced, the issue is present: _cannot use Hamlib NET rigctl!_ Sorry again, I should being testing more time before to speak about hamlib! Marco PY1ZRJ Il 24/11/25 19:55, Marco Calistri via wsjt-devel ha scritto: > Well, > > I finally solved now! > > I "brutally copied" WSJTX-2.7.0 src hamlib version 4.6.1, into > WSJTX-3.0 src, then compile again and this works now! > > Many thanks Adrian for the highlights on this matter! > > Apologies to all the WSJTX-devel users for my "noise". > > Regards, > > Marco, PY1ZRJ > > marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> ls -l src > totale 36704 > -rwxr-xr-x 1 marco users 2909273 24 nov 19.40 *hamlib-4.6.1.tar.gz* > -rwxr-xr-x 1 marco users 69 24 nov 19.40 > *hamlib-4.6.1.tar.gz.md5sum* > -rwxr-xr-x 1 marco users 34658221 12 set 15.16 wsjtx.tgz > -rwxr-xr-x 1 marco users 63 12 set 15.19 wsjtx.tgz.md5sum > > Il 24/11/25 19:38, Marco Calistri ha scritto: >> This has worked well on WSJTX 2.7.0 but on WSJTX 3.0, cmake is still >> extracting and using hamlib-4.7.0 he found inside src: >> >> >> marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> >> >> /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/home/marco/hamlib-4.4/include >> -Dhamlib_LIBRARIES=/home/marco/hamlib-4.4/lib64/libhamlib.a >> -Dhamlib_LIBRARY_DIRS=/home/marco/hamlib-4.4/lib64 >> -DWSJT_GENERATE_DOCS=OFF -DWSJT_SKIP_MANPAGES=ON -DWSJT_QMAP=NO >> -Werror=deprecated-declarations -Wno-error -Wno-dev >> -DCMAKE_POLICY_VERSION_MINIMUM=3.5..3.11 >> -DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx3 . >> -- Configuring done (0.1s) >> -- Generating done (0.0s) >> -- Build files have been written to: >> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1 >> marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> >> /usr/bin/cmake --build . --target wsjtx-install >> [ 7%] Creating directories for 'hamlib' >> [ 14%] Performing download step (verify and extract) for 'hamlib' >> -- verifying file... >> file='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/src/hamlib-4.7.tar.gz' >> -- verifying file... done >> -- extracting... >> src='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/src/hamlib-4.7.tar.gz' >> dst='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/hamlib-prefix/src/hamlib' >> -- extracting... [tar xf] >> -- extracting... [analysis] >> -- extracting... [rename] >> -- extracting... [clean up] >> -- extracting... done >> [ 21%] No update step for 'hamlib' >> [ 28%] Performing patch step for 'hamlib' >> [ 35%] Performing configure step for 'hamlib' >> >> Then I don't know how to force WSJTX to use hamlib-4.4. >> >> Marco, PY1ZRJ >> >> Il 24/11/25 17:57, Marco Calistri via wsjt-devel ha scritto: >>> Adrian, >>> >>> By following your "hamlib custom scheme", I've been able to >>> roll-back hamlib-4.7 to hamlib-4.4 and indeed this version works >>> correctly with my YAESU FT-100, when set to Rig: Hamlib NET rigctl! >>> >>> With newer hamlib versions this is not possible at all and I'm >>> obliged to set WSJTX Rig to my specific radio model! >>> >>> Sad to see that as sometimes happens for other softwares, developers >>> in order to add more features in the code, result to broke what was >>> working perfectly. >>> >>> 73's de Marco PY1ZRJ >>> >>> (Running FT8 with the old YAESU FT-100, still hard as as rock! 😉 >>> ~/hamlib-4.4/bin/rigctld --version >>> *rigctl Hamlib 4.4 Thu Dec 02 23:46:51 2021 +0000 SHA=5f8c4c*) >>> >>> >>> >>> Il 24/11/25 15:32, Marco Calistri via wsjt-devel ha scritto: >>>> Adrian, >>>> >>>> Thanks for the hints! >>>> >>>> My Linux build script is working ok and I disabled the MAN feature. >>>> (DWSJT_SKIP_MANPAGES=OFF). >>>> >>>> The only thing I would try to customize is hamlib integration, >>>> since from some versions on, I started to face VFOs management errors. >>>> >>>> Many thanks again and 73's de Marco PY1ZRJ >>>> >>>> >>>> Il 24/11/25 15:04, Adrian via wsjt-devel ha scritto: >>>>> >>>>> Try the older method and adjust to suit , pointing the paths to >>>>> the extracted hamlib source you want to use ; >>>>> >>>>> To build Hamlib from sources something >>>>> like the following recipe should suffice: >>>>> >>>>> $ mkdir ~/hamlib-prefix >>>>> $ cd ~/hamlib-prefix >>>>> $ git clone https://github.com/Hamlib/Hamlib src >>>>> $ cd src >>>>> $ git checkout integration >>>>> $ ./bootstrap >>>>> $ mkdir ../build >>>>> $ cd ../build >>>>> $ ../src/configure --prefix=$HOME/hamlib-prefix \ >>>>> --disable-shared --enable-static \ >>>>> --without-cxx-binding --disable-winradio \ >>>>> CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \ >>>>> LDFLAGS="-Wl,--gc-sections" >>>>> $ make >>>>> $ make install-strip >>>>> >>>>> This will build a binary hamlib package located at ~/hamlib-prefix so >>>>> you will need to add that to your CMAKE_PREFIX_PATH variable in your >>>>> WSJT-X build. On Linux that is probably the only path you have on >>>>> CMAKE_PREFIX_PATH unless you are using a locally installed Qt >>>>> installation. >>>>> >>>>> To get the sources either download and extract a source tarball from >>>>> the project web site or preferably fetch the sources directly from the >>>>> project's subversion repository. >>>>> >>>>> $ mkdir -p ~/wsjtx-prefix/build >>>>> $ cd ~/wsjtx-prefix >>>>> $ git clone git://git.code.sf.net/p/wsjt/wsjtx src >>>>> >>>>> To build WSJT-X you will need CMake and asciidoc installed. >>>>> >>>>> $ cd ~/wsjtx-prefix/build >>>>> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON \ >>>>> -DWSJT_GENERATE_DOCS=OFF ../src >>>>> $ cmake --build . >>>>> $ cmake --build . --target install >>>>> >>>>> The recipe above will install into /usr by default, if you wish to >>>>> install in you own directory you can add a prefix-path to the >>>>> configure step like: >>>>> >>>>> $ cd ~/wsjtx-prefix/build >>>>> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \ >>>>> -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF \ >>>>> -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix ../src >>>>> $ cmake --build . >>>>> $ cmake --build . --target install >>>>> >>>>> this will install WSJT-X at ~/wsjtx-prefix. >>>>> >>>>> >>>>> On 25/11/25 01:22, Marco Calistri via wsjt-devel wrote: >>>>>> I copied hamlib-4.4 as indicated then I need to rename back to >>>>>> 4.7 otherwise gmake was complaining. >>>>>> >>>>>> Doing that, compile went well until this error below: >>>>>> >>>>>> [ 81%] Building CXX object >>>>>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o >>>>>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp: >>>>>> In member function ‘QByteArray >>>>>> HamlibTransceiver::impl::get_conf(const char*)’: >>>>>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20: >>>>>> error: ‘rig_get_conf2’ was not declared in this scope; did you >>>>>> mean ‘rig_get_conf’? >>>>>> 336 | error_check (rig_get_conf2 (rig_.data (), token, >>>>>> value.data (),value.length()), tr ("getting a configuration >>>>>> item")); //changed to conf2, added parameter for buffer length >>>>>> | ^~~~~~~~~~~~~ >>>>>> | rig_get_conf >>>>>> gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548: >>>>>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1 >>>>>> gmake[5]: *** [CMakeFiles/Makefile2:2058: >>>>>> CMakeFiles/wsjt_qt.dir/all] Error 2 >>>>>> gmake[4]: *** [Makefile:156: all] Error 2 >>>>>> gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78: >>>>>> wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 >>>>>> >>>>>> I don't know how to resolve this. >>>>>> >>>>>> Regards, Marco PY1ZRJ >>>>>> >>>>>> Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto: >>>>>>> Will try your suggestion Adrian, I downloaded hamlib 4.4 since >>>>>>> many reported issues starting with version 4.5. I use old rtx >>>>>>> YAESU FT 100, then I hope to resolve my VFO random splits A, B, >>>>>>> B, A, by using older hamlib. >>>>>>> >>>>>>> 73 Marco PY1ZRJ >>>>>>> >>>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>>> >>>>>>> ------------------------------------------------------------------------ >>>>>>> *Da:* Marco Calistri via wsjt-devel >>>>>>> <wsj...@li...> >>>>>>> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM >>>>>>> *A:* WSJT software development <wsj...@li...> >>>>>>> *Cc:* Marco Calistri <PY...@ou...> >>>>>>> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>>> >>>>>>> This is interesting! >>>>>>> >>>>>>> But my original email was talking about something integrated >>>>>>> into the software, as it has been deployed in Windows. >>>>>>> >>>>>>> Maybe it's not feasible in Linux, then just disregard my feature >>>>>>> request. >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Marco PY1ZRJ >>>>>>> >>>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Adrian via wsjt-devel <wsj...@li...> >>>>>>> *Sent:* Saturday, November 15, 2025 9:26:18 PM >>>>>>> *To:* wsj...@li... >>>>>>> <wsj...@li...> >>>>>>> *Cc:* Adrian <vk...@gm...> >>>>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>>> >>>>>>> You can replace the tar.gz with latest etc as you wish before >>>>>>> compile ; >>>>>>> >>>>>>> 73 >>>>>>> >>>>>>> >>>>>>> vk4tux >>>>>>> >>>>>>> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: >>>>>>>> Hi Karl! >>>>>>>> >>>>>>>> Yes I agree with you (partially). >>>>>>>> >>>>>>>> Hamlib puts the upgrades inside its Git repository then it's >>>>>>>> the unique place wherein the cmake process look at/for. >>>>>>>> >>>>>>>> I use rigctld as you described, but if you look at WSJTX >>>>>>>> settings, you will see the hamlib version which cmake has found >>>>>>>> in the moment you made the code compilation and this is not the >>>>>>>> latest available. >>>>>>>> >>>>>>>> 73s de Marco PY1ZRJ >>>>>>>> >>>>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> *From:* Kari Sillanmäki via wsjt-devel >>>>>>>> <wsj...@li...> >>>>>>>> <mailto:wsj...@li...> >>>>>>>> *Sent:* Saturday, November 15, 2025 8:34:51 PM >>>>>>>> *To:* wsj...@li... >>>>>>>> <mailto:wsj...@li...> >>>>>>>> <wsj...@li...> >>>>>>>> <mailto:wsj...@li...> >>>>>>>> *Cc:* Kari Sillanmäki <kai...@gm...> >>>>>>>> <mailto:kai...@gm...> >>>>>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>>>> Hi Marco, >>>>>>>> >>>>>>>> As you know, Windowzie is this “same pants fit everyone” >>>>>>>> system, which means WSJT-X only needs >>>>>>>> one place to pull a new version of Hamlib from. >>>>>>>> >>>>>>>> But Unix/Linux is far more versatile. You can run it on a wide >>>>>>>> range of distributions >>>>>>>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or >>>>>>>> whatever else you prefer. >>>>>>>> You can even set up your own “distro” if you want to. >>>>>>>> >>>>>>>> Because of this diversity, it would be very difficult for >>>>>>>> WSJT-X to know where to >>>>>>>> download a new version of Hamlib from — assuming such a package >>>>>>>> even exists. >>>>>>>> >>>>>>>> However, there is a workaround. You just need to install >>>>>>>> whatever version of Hamlib >>>>>>>> you want on your system, start the `rigctld` daemon with the >>>>>>>> parameters suitable for your rig, >>>>>>>> and select “Hamlib NET rigctl” as your radio in WSJT-X. >>>>>>>> >>>>>>>> Granted, this requires some IT skills beyond those of an >>>>>>>> “appliance user,” but it’s >>>>>>>> definitely doable. >>>>>>>> >>>>>>>> 73's de Kari, oh2gqc >>>>>>>> >>>>>>>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> Why only Windows version of WSJTX has the feature to >>>>>>>>> upgrade/roll-back Hamlib from within the program? >>>>>>>>> >>>>>>>>> In Linux, at least if you use the WSJTX source-code, in order >>>>>>>>> to get the updated Hamlib version, you need to recompile the code! >>>>>>>>> >>>>>>>>> I think that WSJTX for Linux has limited features in >>>>>>>>> comparison to Windows. >>>>>>>>> >>>>>>>>> I would like to get the same. >>>>>>>>> >>>>>>>>> Regards Marco, PY1ZRJ >>>>>>>>> --- >>>>>>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>>>>>> ** >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> wsjt-devel mailing list >>>>>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> wsjt-devel mailing list >>>>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> wsjt-devel mailing list >>>>>>> wsj...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>>>> >>>>>> >>>>>> --- >>>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>>> ** >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> wsjt-devel mailing list >>>>>> wsj...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>>> >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> wsj...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>> >>>> >>>> --- >>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>> ** >>>> >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsj...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> >>> --- >>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>> ** >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> --- >> *73 de Marco, PY1ZRJ (former IK5BCU)* >> ** > > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Marco C. <PY...@ou...> - 2025-11-24 22:55:22
|
Well, I finally solved now! I "brutally copied" WSJTX-2.7.0 src hamlib version 4.6.1, into WSJTX-3.0 src, then compile again and this works now! Many thanks Adrian for the highlights on this matter! Apologies to all the WSJTX-devel users for my "noise". Regards, Marco, PY1ZRJ marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> ls -l src totale 36704 -rwxr-xr-x 1 marco users 2909273 24 nov 19.40 *hamlib-4.6.1.tar.gz* -rwxr-xr-x 1 marco users 69 24 nov 19.40 *hamlib-4.6.1.tar.gz.md5sum* -rwxr-xr-x 1 marco users 34658221 12 set 15.16 wsjtx.tgz -rwxr-xr-x 1 marco users 63 12 set 15.19 wsjtx.tgz.md5sum Il 24/11/25 19:38, Marco Calistri ha scritto: > This has worked well on WSJTX 2.7.0 but on WSJTX 3.0, cmake is still > extracting and using hamlib-4.7.0 he found inside src: > > > marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> > > /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/home/marco/hamlib-4.4/include > -Dhamlib_LIBRARIES=/home/marco/hamlib-4.4/lib64/libhamlib.a > -Dhamlib_LIBRARY_DIRS=/home/marco/hamlib-4.4/lib64 > -DWSJT_GENERATE_DOCS=OFF -DWSJT_SKIP_MANPAGES=ON -DWSJT_QMAP=NO > -Werror=deprecated-declarations -Wno-error -Wno-dev > -DCMAKE_POLICY_VERSION_MINIMUM=3.5..3.11 > -DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx3 . > -- Configuring done (0.1s) > -- Generating done (0.0s) > -- Build files have been written to: > /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1 > marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> > /usr/bin/cmake --build . --target wsjtx-install > [ 7%] Creating directories for 'hamlib' > [ 14%] Performing download step (verify and extract) for 'hamlib' > -- verifying file... > file='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/src/hamlib-4.7.tar.gz' > -- verifying file... done > -- extracting... > src='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/src/hamlib-4.7.tar.gz' > dst='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/hamlib-prefix/src/hamlib' > -- extracting... [tar xf] > -- extracting... [analysis] > -- extracting... [rename] > -- extracting... [clean up] > -- extracting... done > [ 21%] No update step for 'hamlib' > [ 28%] Performing patch step for 'hamlib' > [ 35%] Performing configure step for 'hamlib' > > Then I don't know how to force WSJTX to use hamlib-4.4. > > Marco, PY1ZRJ > > Il 24/11/25 17:57, Marco Calistri via wsjt-devel ha scritto: >> Adrian, >> >> By following your "hamlib custom scheme", I've been able to roll-back >> hamlib-4.7 to hamlib-4.4 and indeed this version works correctly with >> my YAESU FT-100, when set to Rig: Hamlib NET rigctl! >> >> With newer hamlib versions this is not possible at all and I'm >> obliged to set WSJTX Rig to my specific radio model! >> >> Sad to see that as sometimes happens for other softwares, developers >> in order to add more features in the code, result to broke what was >> working perfectly. >> >> 73's de Marco PY1ZRJ >> >> (Running FT8 with the old YAESU FT-100, still hard as as rock! 😉 >> ~/hamlib-4.4/bin/rigctld --version >> *rigctl Hamlib 4.4 Thu Dec 02 23:46:51 2021 +0000 SHA=5f8c4c*) >> >> >> >> Il 24/11/25 15:32, Marco Calistri via wsjt-devel ha scritto: >>> Adrian, >>> >>> Thanks for the hints! >>> >>> My Linux build script is working ok and I disabled the MAN feature. >>> (DWSJT_SKIP_MANPAGES=OFF). >>> >>> The only thing I would try to customize is hamlib integration, since >>> from some versions on, I started to face VFOs management errors. >>> >>> Many thanks again and 73's de Marco PY1ZRJ >>> >>> >>> Il 24/11/25 15:04, Adrian via wsjt-devel ha scritto: >>>> >>>> Try the older method and adjust to suit , pointing the paths to the >>>> extracted hamlib source you want to use ; >>>> >>>> To build Hamlib from sources something >>>> like the following recipe should suffice: >>>> >>>> $ mkdir ~/hamlib-prefix >>>> $ cd ~/hamlib-prefix >>>> $ git clone https://github.com/Hamlib/Hamlib src >>>> $ cd src >>>> $ git checkout integration >>>> $ ./bootstrap >>>> $ mkdir ../build >>>> $ cd ../build >>>> $ ../src/configure --prefix=$HOME/hamlib-prefix \ >>>> --disable-shared --enable-static \ >>>> --without-cxx-binding --disable-winradio \ >>>> CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \ >>>> LDFLAGS="-Wl,--gc-sections" >>>> $ make >>>> $ make install-strip >>>> >>>> This will build a binary hamlib package located at ~/hamlib-prefix so >>>> you will need to add that to your CMAKE_PREFIX_PATH variable in your >>>> WSJT-X build. On Linux that is probably the only path you have on >>>> CMAKE_PREFIX_PATH unless you are using a locally installed Qt >>>> installation. >>>> >>>> To get the sources either download and extract a source tarball from >>>> the project web site or preferably fetch the sources directly from the >>>> project's subversion repository. >>>> >>>> $ mkdir -p ~/wsjtx-prefix/build >>>> $ cd ~/wsjtx-prefix >>>> $ git clone git://git.code.sf.net/p/wsjt/wsjtx src >>>> >>>> To build WSJT-X you will need CMake and asciidoc installed. >>>> >>>> $ cd ~/wsjtx-prefix/build >>>> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON \ >>>> -DWSJT_GENERATE_DOCS=OFF ../src >>>> $ cmake --build . >>>> $ cmake --build . --target install >>>> >>>> The recipe above will install into /usr by default, if you wish to >>>> install in you own directory you can add a prefix-path to the >>>> configure step like: >>>> >>>> $ cd ~/wsjtx-prefix/build >>>> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \ >>>> -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF \ >>>> -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix ../src >>>> $ cmake --build . >>>> $ cmake --build . --target install >>>> >>>> this will install WSJT-X at ~/wsjtx-prefix. >>>> >>>> >>>> On 25/11/25 01:22, Marco Calistri via wsjt-devel wrote: >>>>> I copied hamlib-4.4 as indicated then I need to rename back to 4.7 >>>>> otherwise gmake was complaining. >>>>> >>>>> Doing that, compile went well until this error below: >>>>> >>>>> [ 81%] Building CXX object >>>>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o >>>>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp: >>>>> In member function ‘QByteArray >>>>> HamlibTransceiver::impl::get_conf(const char*)’: >>>>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20: >>>>> error: ‘rig_get_conf2’ was not declared in this scope; did you >>>>> mean ‘rig_get_conf’? >>>>> 336 | error_check (rig_get_conf2 (rig_.data (), token, >>>>> value.data (),value.length()), tr ("getting a configuration >>>>> item")); //changed to conf2, added parameter for buffer length >>>>> | ^~~~~~~~~~~~~ >>>>> | rig_get_conf >>>>> gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548: >>>>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1 >>>>> gmake[5]: *** [CMakeFiles/Makefile2:2058: >>>>> CMakeFiles/wsjt_qt.dir/all] Error 2 >>>>> gmake[4]: *** [Makefile:156: all] Error 2 >>>>> gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78: >>>>> wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 >>>>> >>>>> I don't know how to resolve this. >>>>> >>>>> Regards, Marco PY1ZRJ >>>>> >>>>> Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto: >>>>>> Will try your suggestion Adrian, I downloaded hamlib 4.4 since >>>>>> many reported issues starting with version 4.5. I use old rtx >>>>>> YAESU FT 100, then I hope to resolve my VFO random splits A, B, >>>>>> B, A, by using older hamlib. >>>>>> >>>>>> 73 Marco PY1ZRJ >>>>>> >>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> *Da:* Marco Calistri via wsjt-devel >>>>>> <wsj...@li...> >>>>>> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM >>>>>> *A:* WSJT software development <wsj...@li...> >>>>>> *Cc:* Marco Calistri <PY...@ou...> >>>>>> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>> >>>>>> This is interesting! >>>>>> >>>>>> But my original email was talking about something integrated into >>>>>> the software, as it has been deployed in Windows. >>>>>> >>>>>> Maybe it's not feasible in Linux, then just disregard my feature >>>>>> request. >>>>>> >>>>>> Best, >>>>>> >>>>>> Marco PY1ZRJ >>>>>> >>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Adrian via wsjt-devel <wsj...@li...> >>>>>> *Sent:* Saturday, November 15, 2025 9:26:18 PM >>>>>> *To:* wsj...@li... >>>>>> <wsj...@li...> >>>>>> *Cc:* Adrian <vk...@gm...> >>>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>> >>>>>> You can replace the tar.gz with latest etc as you wish before >>>>>> compile ; >>>>>> >>>>>> 73 >>>>>> >>>>>> >>>>>> vk4tux >>>>>> >>>>>> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: >>>>>>> Hi Karl! >>>>>>> >>>>>>> Yes I agree with you (partially). >>>>>>> >>>>>>> Hamlib puts the upgrades inside its Git repository then it's the >>>>>>> unique place wherein the cmake process look at/for. >>>>>>> >>>>>>> I use rigctld as you described, but if you look at WSJTX >>>>>>> settings, you will see the hamlib version which cmake has found >>>>>>> in the moment you made the code compilation and this is not the >>>>>>> latest available. >>>>>>> >>>>>>> 73s de Marco PY1ZRJ >>>>>>> >>>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Kari Sillanmäki via wsjt-devel >>>>>>> <wsj...@li...> >>>>>>> <mailto:wsj...@li...> >>>>>>> *Sent:* Saturday, November 15, 2025 8:34:51 PM >>>>>>> *To:* wsj...@li... >>>>>>> <mailto:wsj...@li...> >>>>>>> <wsj...@li...> >>>>>>> <mailto:wsj...@li...> >>>>>>> *Cc:* Kari Sillanmäki <kai...@gm...> >>>>>>> <mailto:kai...@gm...> >>>>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>>> Hi Marco, >>>>>>> >>>>>>> As you know, Windowzie is this “same pants fit everyone” system, >>>>>>> which means WSJT-X only needs >>>>>>> one place to pull a new version of Hamlib from. >>>>>>> >>>>>>> But Unix/Linux is far more versatile. You can run it on a wide >>>>>>> range of distributions >>>>>>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or >>>>>>> whatever else you prefer. >>>>>>> You can even set up your own “distro” if you want to. >>>>>>> >>>>>>> Because of this diversity, it would be very difficult for WSJT-X >>>>>>> to know where to >>>>>>> download a new version of Hamlib from — assuming such a package >>>>>>> even exists. >>>>>>> >>>>>>> However, there is a workaround. You just need to install >>>>>>> whatever version of Hamlib >>>>>>> you want on your system, start the `rigctld` daemon with the >>>>>>> parameters suitable for your rig, >>>>>>> and select “Hamlib NET rigctl” as your radio in WSJT-X. >>>>>>> >>>>>>> Granted, this requires some IT skills beyond those of an >>>>>>> “appliance user,” but it’s >>>>>>> definitely doable. >>>>>>> >>>>>>> 73's de Kari, oh2gqc >>>>>>> >>>>>>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> Why only Windows version of WSJTX has the feature to >>>>>>>> upgrade/roll-back Hamlib from within the program? >>>>>>>> >>>>>>>> In Linux, at least if you use the WSJTX source-code, in order >>>>>>>> to get the updated Hamlib version, you need to recompile the code! >>>>>>>> >>>>>>>> I think that WSJTX for Linux has limited features in comparison >>>>>>>> to Windows. >>>>>>>> >>>>>>>> I would like to get the same. >>>>>>>> >>>>>>>> Regards Marco, PY1ZRJ >>>>>>>> --- >>>>>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>>>>> ** >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> wsjt-devel mailing list >>>>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> wsjt-devel mailing list >>>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> wsjt-devel mailing list >>>>>> wsj...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>>> >>>>> >>>>> --- >>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>> ** >>>>> >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> wsj...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>> >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsj...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> >>> --- >>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>> ** >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> --- >> *73 de Marco, PY1ZRJ (former IK5BCU)* >> ** >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Marco C. <PY...@ou...> - 2025-11-24 22:38:34
|
This has worked well on WSJTX 2.7.0 but on WSJTX 3.0, cmake is still extracting and using hamlib-4.7.0 he found inside src: marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/home/marco/hamlib-4.4/include -Dhamlib_LIBRARIES=/home/marco/hamlib-4.4/lib64/libhamlib.a -Dhamlib_LIBRARY_DIRS=/home/marco/hamlib-4.4/lib64 -DWSJT_GENERATE_DOCS=OFF -DWSJT_SKIP_MANPAGES=ON -DWSJT_QMAP=NO -Werror=deprecated-declarations -Wno-error -Wno-dev -DCMAKE_POLICY_VERSION_MINIMUM=3.5..3.11 -DCMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx3 . -- Configuring done (0.1s) -- Generating done (0.0s) -- Build files have been written to: /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1 marco@linux-turion64:~/WSJT-X_build/build/wsjtx-3.0.0-rc1> /usr/bin/cmake --build . --target wsjtx-install [ 7%] Creating directories for 'hamlib' [ 14%] Performing download step (verify and extract) for 'hamlib' -- verifying file... file='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/src/hamlib-4.7.tar.gz' -- verifying file... done -- extracting... src='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/src/hamlib-4.7.tar.gz' dst='/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/hamlib-prefix/src/hamlib' -- extracting... [tar xf] -- extracting... [analysis] -- extracting... [rename] -- extracting... [clean up] -- extracting... done [ 21%] No update step for 'hamlib' [ 28%] Performing patch step for 'hamlib' [ 35%] Performing configure step for 'hamlib' Then I don't know how to force WSJTX to use hamlib-4.4. Marco, PY1ZRJ Il 24/11/25 17:57, Marco Calistri via wsjt-devel ha scritto: > Adrian, > > By following your "hamlib custom scheme", I've been able to roll-back > hamlib-4.7 to hamlib-4.4 and indeed this version works correctly with > my YAESU FT-100, when set to Rig: Hamlib NET rigctl! > > With newer hamlib versions this is not possible at all and I'm obliged > to set WSJTX Rig to my specific radio model! > > Sad to see that as sometimes happens for other softwares, developers > in order to add more features in the code, result to broke what was > working perfectly. > > 73's de Marco PY1ZRJ > > (Running FT8 with the old YAESU FT-100, still hard as as rock! 😉 > ~/hamlib-4.4/bin/rigctld --version > *rigctl Hamlib 4.4 Thu Dec 02 23:46:51 2021 +0000 SHA=5f8c4c*) > > > > Il 24/11/25 15:32, Marco Calistri via wsjt-devel ha scritto: >> Adrian, >> >> Thanks for the hints! >> >> My Linux build script is working ok and I disabled the MAN feature. >> (DWSJT_SKIP_MANPAGES=OFF). >> >> The only thing I would try to customize is hamlib integration, since >> from some versions on, I started to face VFOs management errors. >> >> Many thanks again and 73's de Marco PY1ZRJ >> >> >> Il 24/11/25 15:04, Adrian via wsjt-devel ha scritto: >>> >>> Try the older method and adjust to suit , pointing the paths to the >>> extracted hamlib source you want to use ; >>> >>> To build Hamlib from sources something >>> like the following recipe should suffice: >>> >>> $ mkdir ~/hamlib-prefix >>> $ cd ~/hamlib-prefix >>> $ git clone https://github.com/Hamlib/Hamlib src >>> $ cd src >>> $ git checkout integration >>> $ ./bootstrap >>> $ mkdir ../build >>> $ cd ../build >>> $ ../src/configure --prefix=$HOME/hamlib-prefix \ >>> --disable-shared --enable-static \ >>> --without-cxx-binding --disable-winradio \ >>> CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \ >>> LDFLAGS="-Wl,--gc-sections" >>> $ make >>> $ make install-strip >>> >>> This will build a binary hamlib package located at ~/hamlib-prefix so >>> you will need to add that to your CMAKE_PREFIX_PATH variable in your >>> WSJT-X build. On Linux that is probably the only path you have on >>> CMAKE_PREFIX_PATH unless you are using a locally installed Qt >>> installation. >>> >>> To get the sources either download and extract a source tarball from >>> the project web site or preferably fetch the sources directly from the >>> project's subversion repository. >>> >>> $ mkdir -p ~/wsjtx-prefix/build >>> $ cd ~/wsjtx-prefix >>> $ git clone git://git.code.sf.net/p/wsjt/wsjtx src >>> >>> To build WSJT-X you will need CMake and asciidoc installed. >>> >>> $ cd ~/wsjtx-prefix/build >>> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON \ >>> -DWSJT_GENERATE_DOCS=OFF ../src >>> $ cmake --build . >>> $ cmake --build . --target install >>> >>> The recipe above will install into /usr by default, if you wish to >>> install in you own directory you can add a prefix-path to the >>> configure step like: >>> >>> $ cd ~/wsjtx-prefix/build >>> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \ >>> -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF \ >>> -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix ../src >>> $ cmake --build . >>> $ cmake --build . --target install >>> >>> this will install WSJT-X at ~/wsjtx-prefix. >>> >>> >>> On 25/11/25 01:22, Marco Calistri via wsjt-devel wrote: >>>> I copied hamlib-4.4 as indicated then I need to rename back to 4.7 >>>> otherwise gmake was complaining. >>>> >>>> Doing that, compile went well until this error below: >>>> >>>> [ 81%] Building CXX object >>>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o >>>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp: >>>> In member function ‘QByteArray >>>> HamlibTransceiver::impl::get_conf(const char*)’: >>>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20: >>>> error: ‘rig_get_conf2’ was not declared in this scope; did you mean >>>> ‘rig_get_conf’? >>>> 336 | error_check (rig_get_conf2 (rig_.data (), token, >>>> value.data (),value.length()), tr ("getting a configuration >>>> item")); //changed to conf2, added parameter for buffer length >>>> | ^~~~~~~~~~~~~ >>>> | rig_get_conf >>>> gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548: >>>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1 >>>> gmake[5]: *** [CMakeFiles/Makefile2:2058: >>>> CMakeFiles/wsjt_qt.dir/all] Error 2 >>>> gmake[4]: *** [Makefile:156: all] Error 2 >>>> gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78: >>>> wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 >>>> >>>> I don't know how to resolve this. >>>> >>>> Regards, Marco PY1ZRJ >>>> >>>> Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto: >>>>> Will try your suggestion Adrian, I downloaded hamlib 4.4 since >>>>> many reported issues starting with version 4.5. I use old rtx >>>>> YAESU FT 100, then I hope to resolve my VFO random splits A, B, B, >>>>> A, by using older hamlib. >>>>> >>>>> 73 Marco PY1ZRJ >>>>> >>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>> >>>>> ------------------------------------------------------------------------ >>>>> *Da:* Marco Calistri via wsjt-devel <wsj...@li...> >>>>> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM >>>>> *A:* WSJT software development <wsj...@li...> >>>>> *Cc:* Marco Calistri <PY...@ou...> >>>>> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>> >>>>> This is interesting! >>>>> >>>>> But my original email was talking about something integrated into >>>>> the software, as it has been deployed in Windows. >>>>> >>>>> Maybe it's not feasible in Linux, then just disregard my feature >>>>> request. >>>>> >>>>> Best, >>>>> >>>>> Marco PY1ZRJ >>>>> >>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>> ------------------------------------------------------------------------ >>>>> *From:* Adrian via wsjt-devel <wsj...@li...> >>>>> *Sent:* Saturday, November 15, 2025 9:26:18 PM >>>>> *To:* wsj...@li... >>>>> <wsj...@li...> >>>>> *Cc:* Adrian <vk...@gm...> >>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>> >>>>> You can replace the tar.gz with latest etc as you wish before >>>>> compile ; >>>>> >>>>> 73 >>>>> >>>>> >>>>> vk4tux >>>>> >>>>> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: >>>>>> Hi Karl! >>>>>> >>>>>> Yes I agree with you (partially). >>>>>> >>>>>> Hamlib puts the upgrades inside its Git repository then it's the >>>>>> unique place wherein the cmake process look at/for. >>>>>> >>>>>> I use rigctld as you described, but if you look at WSJTX >>>>>> settings, you will see the hamlib version which cmake has found >>>>>> in the moment you made the code compilation and this is not the >>>>>> latest available. >>>>>> >>>>>> 73s de Marco PY1ZRJ >>>>>> >>>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Kari Sillanmäki via wsjt-devel >>>>>> <wsj...@li...> >>>>>> <mailto:wsj...@li...> >>>>>> *Sent:* Saturday, November 15, 2025 8:34:51 PM >>>>>> *To:* wsj...@li... >>>>>> <mailto:wsj...@li...> >>>>>> <wsj...@li...> >>>>>> <mailto:wsj...@li...> >>>>>> *Cc:* Kari Sillanmäki <kai...@gm...> >>>>>> <mailto:kai...@gm...> >>>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>>> Hi Marco, >>>>>> >>>>>> As you know, Windowzie is this “same pants fit everyone” system, >>>>>> which means WSJT-X only needs >>>>>> one place to pull a new version of Hamlib from. >>>>>> >>>>>> But Unix/Linux is far more versatile. You can run it on a wide >>>>>> range of distributions >>>>>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or >>>>>> whatever else you prefer. >>>>>> You can even set up your own “distro” if you want to. >>>>>> >>>>>> Because of this diversity, it would be very difficult for WSJT-X >>>>>> to know where to >>>>>> download a new version of Hamlib from — assuming such a package >>>>>> even exists. >>>>>> >>>>>> However, there is a workaround. You just need to install whatever >>>>>> version of Hamlib >>>>>> you want on your system, start the `rigctld` daemon with the >>>>>> parameters suitable for your rig, >>>>>> and select “Hamlib NET rigctl” as your radio in WSJT-X. >>>>>> >>>>>> Granted, this requires some IT skills beyond those of an >>>>>> “appliance user,” but it’s >>>>>> definitely doable. >>>>>> >>>>>> 73's de Kari, oh2gqc >>>>>> >>>>>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >>>>>>> Hello, >>>>>>> >>>>>>> Why only Windows version of WSJTX has the feature to >>>>>>> upgrade/roll-back Hamlib from within the program? >>>>>>> >>>>>>> In Linux, at least if you use the WSJTX source-code, in order to >>>>>>> get the updated Hamlib version, you need to recompile the code! >>>>>>> >>>>>>> I think that WSJTX for Linux has limited features in comparison >>>>>>> to Windows. >>>>>>> >>>>>>> I would like to get the same. >>>>>>> >>>>>>> Regards Marco, PY1ZRJ >>>>>>> --- >>>>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>>>> ** >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> wsjt-devel mailing list >>>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> wsjt-devel mailing list >>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> wsj...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>>> >>>> >>>> --- >>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>> ** >>>> >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsj...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> --- >> *73 de Marco, PY1ZRJ (former IK5BCU)* >> ** >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Marco C. <PY...@ou...> - 2025-11-24 20:57:50
|
Adrian, By following your "hamlib custom scheme", I've been able to roll-back hamlib-4.7 to hamlib-4.4 and indeed this version works correctly with my YAESU FT-100, when set to Rig: Hamlib NET rigctl! With newer hamlib versions this is not possible at all and I'm obliged to set WSJTX Rig to my specific radio model! Sad to see that as sometimes happens for other softwares, developers in order to add more features in the code, result to broke what was working perfectly. 73's de Marco PY1ZRJ (Running FT8 with the old YAESU FT-100, still hard as as rock! 😉 ~/hamlib-4.4/bin/rigctld --version *rigctl Hamlib 4.4 Thu Dec 02 23:46:51 2021 +0000 SHA=5f8c4c*) Il 24/11/25 15:32, Marco Calistri via wsjt-devel ha scritto: > Adrian, > > Thanks for the hints! > > My Linux build script is working ok and I disabled the MAN feature. > (DWSJT_SKIP_MANPAGES=OFF). > > The only thing I would try to customize is hamlib integration, since > from some versions on, I started to face VFOs management errors. > > Many thanks again and 73's de Marco PY1ZRJ > > > Il 24/11/25 15:04, Adrian via wsjt-devel ha scritto: >> >> Try the older method and adjust to suit , pointing the paths to the >> extracted hamlib source you want to use ; >> >> To build Hamlib from sources something >> like the following recipe should suffice: >> >> $ mkdir ~/hamlib-prefix >> $ cd ~/hamlib-prefix >> $ git clone https://github.com/Hamlib/Hamlib src >> $ cd src >> $ git checkout integration >> $ ./bootstrap >> $ mkdir ../build >> $ cd ../build >> $ ../src/configure --prefix=$HOME/hamlib-prefix \ >> --disable-shared --enable-static \ >> --without-cxx-binding --disable-winradio \ >> CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \ >> LDFLAGS="-Wl,--gc-sections" >> $ make >> $ make install-strip >> >> This will build a binary hamlib package located at ~/hamlib-prefix so >> you will need to add that to your CMAKE_PREFIX_PATH variable in your >> WSJT-X build. On Linux that is probably the only path you have on >> CMAKE_PREFIX_PATH unless you are using a locally installed Qt >> installation. >> >> To get the sources either download and extract a source tarball from >> the project web site or preferably fetch the sources directly from the >> project's subversion repository. >> >> $ mkdir -p ~/wsjtx-prefix/build >> $ cd ~/wsjtx-prefix >> $ git clone git://git.code.sf.net/p/wsjt/wsjtx src >> >> To build WSJT-X you will need CMake and asciidoc installed. >> >> $ cd ~/wsjtx-prefix/build >> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON \ >> -DWSJT_GENERATE_DOCS=OFF ../src >> $ cmake --build . >> $ cmake --build . --target install >> >> The recipe above will install into /usr by default, if you wish to >> install in you own directory you can add a prefix-path to the >> configure step like: >> >> $ cd ~/wsjtx-prefix/build >> $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \ >> -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF \ >> -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix ../src >> $ cmake --build . >> $ cmake --build . --target install >> >> this will install WSJT-X at ~/wsjtx-prefix. >> >> >> On 25/11/25 01:22, Marco Calistri via wsjt-devel wrote: >>> I copied hamlib-4.4 as indicated then I need to rename back to 4.7 >>> otherwise gmake was complaining. >>> >>> Doing that, compile went well until this error below: >>> >>> [ 81%] Building CXX object >>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o >>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp: >>> In member function ‘QByteArray >>> HamlibTransceiver::impl::get_conf(const char*)’: >>> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20: >>> error: ‘rig_get_conf2’ was not declared in this scope; did you mean >>> ‘rig_get_conf’? >>> 336 | error_check (rig_get_conf2 (rig_.data (), token, >>> value.data (),value.length()), tr ("getting a configuration item")); >>> //changed to conf2, added parameter for buffer length >>> | ^~~~~~~~~~~~~ >>> | rig_get_conf >>> gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548: >>> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1 >>> gmake[5]: *** [CMakeFiles/Makefile2:2058: >>> CMakeFiles/wsjt_qt.dir/all] Error 2 >>> gmake[4]: *** [Makefile:156: all] Error 2 >>> gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78: >>> wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 >>> >>> I don't know how to resolve this. >>> >>> Regards, Marco PY1ZRJ >>> >>> Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto: >>>> Will try your suggestion Adrian, I downloaded hamlib 4.4 since many >>>> reported issues starting with version 4.5. I use old rtx YAESU FT >>>> 100, then I hope to resolve my VFO random splits A, B, B, A, by >>>> using older hamlib. >>>> >>>> 73 Marco PY1ZRJ >>>> >>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>> >>>> ------------------------------------------------------------------------ >>>> *Da:* Marco Calistri via wsjt-devel <wsj...@li...> >>>> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM >>>> *A:* WSJT software development <wsj...@li...> >>>> *Cc:* Marco Calistri <PY...@ou...> >>>> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>> >>>> This is interesting! >>>> >>>> But my original email was talking about something integrated into >>>> the software, as it has been deployed in Windows. >>>> >>>> Maybe it's not feasible in Linux, then just disregard my feature >>>> request. >>>> >>>> Best, >>>> >>>> Marco PY1ZRJ >>>> >>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>> ------------------------------------------------------------------------ >>>> *From:* Adrian via wsjt-devel <wsj...@li...> >>>> *Sent:* Saturday, November 15, 2025 9:26:18 PM >>>> *To:* wsj...@li... >>>> <wsj...@li...> >>>> *Cc:* Adrian <vk...@gm...> >>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>> >>>> You can replace the tar.gz with latest etc as you wish before compile ; >>>> >>>> 73 >>>> >>>> >>>> vk4tux >>>> >>>> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: >>>>> Hi Karl! >>>>> >>>>> Yes I agree with you (partially). >>>>> >>>>> Hamlib puts the upgrades inside its Git repository then it's the >>>>> unique place wherein the cmake process look at/for. >>>>> >>>>> I use rigctld as you described, but if you look at WSJTX settings, >>>>> you will see the hamlib version which cmake has found in the >>>>> moment you made the code compilation and this is not the latest >>>>> available. >>>>> >>>>> 73s de Marco PY1ZRJ >>>>> >>>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>>> ------------------------------------------------------------------------ >>>>> *From:* Kari Sillanmäki via wsjt-devel >>>>> <wsj...@li...> >>>>> <mailto:wsj...@li...> >>>>> *Sent:* Saturday, November 15, 2025 8:34:51 PM >>>>> *To:* wsj...@li... >>>>> <mailto:wsj...@li...> >>>>> <wsj...@li...> >>>>> <mailto:wsj...@li...> >>>>> *Cc:* Kari Sillanmäki <kai...@gm...> >>>>> <mailto:kai...@gm...> >>>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>>> Hi Marco, >>>>> >>>>> As you know, Windowzie is this “same pants fit everyone” system, >>>>> which means WSJT-X only needs >>>>> one place to pull a new version of Hamlib from. >>>>> >>>>> But Unix/Linux is far more versatile. You can run it on a wide >>>>> range of distributions >>>>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or >>>>> whatever else you prefer. >>>>> You can even set up your own “distro” if you want to. >>>>> >>>>> Because of this diversity, it would be very difficult for WSJT-X >>>>> to know where to >>>>> download a new version of Hamlib from — assuming such a package >>>>> even exists. >>>>> >>>>> However, there is a workaround. You just need to install whatever >>>>> version of Hamlib >>>>> you want on your system, start the `rigctld` daemon with the >>>>> parameters suitable for your rig, >>>>> and select “Hamlib NET rigctl” as your radio in WSJT-X. >>>>> >>>>> Granted, this requires some IT skills beyond those of an >>>>> “appliance user,” but it’s >>>>> definitely doable. >>>>> >>>>> 73's de Kari, oh2gqc >>>>> >>>>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >>>>>> Hello, >>>>>> >>>>>> Why only Windows version of WSJTX has the feature to >>>>>> upgrade/roll-back Hamlib from within the program? >>>>>> >>>>>> In Linux, at least if you use the WSJTX source-code, in order to >>>>>> get the updated Hamlib version, you need to recompile the code! >>>>>> >>>>>> I think that WSJTX for Linux has limited features in comparison >>>>>> to Windows. >>>>>> >>>>>> I would like to get the same. >>>>>> >>>>>> Regards Marco, PY1ZRJ >>>>>> --- >>>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>>> ** >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> wsjt-devel mailing list >>>>>> wsj...@li... <mailto:wsj...@li...> >>>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> wsj...@li... <mailto:wsj...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>> >>>> >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsj...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> >>> --- >>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>> ** >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Marco C. <PY...@ou...> - 2025-11-24 18:32:57
|
Adrian, Thanks for the hints! My Linux build script is working ok and I disabled the MAN feature. (DWSJT_SKIP_MANPAGES=OFF). The only thing I would try to customize is hamlib integration, since from some versions on, I started to face VFOs management errors. Many thanks again and 73's de Marco PY1ZRJ Il 24/11/25 15:04, Adrian via wsjt-devel ha scritto: > > Try the older method and adjust to suit , pointing the paths to the > extracted hamlib source you want to use ; > > To build Hamlib from sources something > like the following recipe should suffice: > > $ mkdir ~/hamlib-prefix > $ cd ~/hamlib-prefix > $ git clone https://github.com/Hamlib/Hamlib src > $ cd src > $ git checkout integration > $ ./bootstrap > $ mkdir ../build > $ cd ../build > $ ../src/configure --prefix=$HOME/hamlib-prefix \ > --disable-shared --enable-static \ > --without-cxx-binding --disable-winradio \ > CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \ > LDFLAGS="-Wl,--gc-sections" > $ make > $ make install-strip > > This will build a binary hamlib package located at ~/hamlib-prefix so > you will need to add that to your CMAKE_PREFIX_PATH variable in your > WSJT-X build. On Linux that is probably the only path you have on > CMAKE_PREFIX_PATH unless you are using a locally installed Qt > installation. > > To get the sources either download and extract a source tarball from > the project web site or preferably fetch the sources directly from the > project's subversion repository. > > $ mkdir -p ~/wsjtx-prefix/build > $ cd ~/wsjtx-prefix > $ git clone git://git.code.sf.net/p/wsjt/wsjtx src > > To build WSJT-X you will need CMake and asciidoc installed. > > $ cd ~/wsjtx-prefix/build > $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON \ > -DWSJT_GENERATE_DOCS=OFF ../src > $ cmake --build . > $ cmake --build . --target install > > The recipe above will install into /usr by default, if you wish to > install in you own directory you can add a prefix-path to the > configure step like: > > $ cd ~/wsjtx-prefix/build > $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \ > -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF \ > -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix ../src > $ cmake --build . > $ cmake --build . --target install > > this will install WSJT-X at ~/wsjtx-prefix. > > > On 25/11/25 01:22, Marco Calistri via wsjt-devel wrote: >> I copied hamlib-4.4 as indicated then I need to rename back to 4.7 >> otherwise gmake was complaining. >> >> Doing that, compile went well until this error below: >> >> [ 81%] Building CXX object >> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o >> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp: >> In member function ‘QByteArray >> HamlibTransceiver::impl::get_conf(const char*)’: >> /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20: >> error: ‘rig_get_conf2’ was not declared in this scope; did you mean >> ‘rig_get_conf’? >> 336 | error_check (rig_get_conf2 (rig_.data (), token, >> value.data (),value.length()), tr ("getting a configuration item")); >> //changed to conf2, added parameter for buffer length >> | ^~~~~~~~~~~~~ >> | rig_get_conf >> gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548: >> CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1 >> gmake[5]: *** [CMakeFiles/Makefile2:2058: CMakeFiles/wsjt_qt.dir/all] >> Error 2 >> gmake[4]: *** [Makefile:156: all] Error 2 >> gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78: >> wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 >> >> I don't know how to resolve this. >> >> Regards, Marco PY1ZRJ >> >> Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto: >>> Will try your suggestion Adrian, I downloaded hamlib 4.4 since many >>> reported issues starting with version 4.5. I use old rtx YAESU FT >>> 100, then I hope to resolve my VFO random splits A, B, B, A, by >>> using older hamlib. >>> >>> 73 Marco PY1ZRJ >>> >>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>> >>> ------------------------------------------------------------------------ >>> *Da:* Marco Calistri via wsjt-devel <wsj...@li...> >>> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM >>> *A:* WSJT software development <wsj...@li...> >>> *Cc:* Marco Calistri <PY...@ou...> >>> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib >>> >>> This is interesting! >>> >>> But my original email was talking about something integrated into >>> the software, as it has been deployed in Windows. >>> >>> Maybe it's not feasible in Linux, then just disregard my feature >>> request. >>> >>> Best, >>> >>> Marco PY1ZRJ >>> >>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>> ------------------------------------------------------------------------ >>> *From:* Adrian via wsjt-devel <wsj...@li...> >>> *Sent:* Saturday, November 15, 2025 9:26:18 PM >>> *To:* wsj...@li... >>> <wsj...@li...> >>> *Cc:* Adrian <vk...@gm...> >>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>> >>> You can replace the tar.gz with latest etc as you wish before compile ; >>> >>> 73 >>> >>> >>> vk4tux >>> >>> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: >>>> Hi Karl! >>>> >>>> Yes I agree with you (partially). >>>> >>>> Hamlib puts the upgrades inside its Git repository then it's the >>>> unique place wherein the cmake process look at/for. >>>> >>>> I use rigctld as you described, but if you look at WSJTX settings, >>>> you will see the hamlib version which cmake has found in the moment >>>> you made the code compilation and this is not the latest available. >>>> >>>> 73s de Marco PY1ZRJ >>>> >>>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>>> ------------------------------------------------------------------------ >>>> *From:* Kari Sillanmäki via wsjt-devel >>>> <wsj...@li...> >>>> <mailto:wsj...@li...> >>>> *Sent:* Saturday, November 15, 2025 8:34:51 PM >>>> *To:* wsj...@li... >>>> <mailto:wsj...@li...> >>>> <wsj...@li...> >>>> <mailto:wsj...@li...> >>>> *Cc:* Kari Sillanmäki <kai...@gm...> >>>> <mailto:kai...@gm...> >>>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>>> Hi Marco, >>>> >>>> As you know, Windowzie is this “same pants fit everyone” system, >>>> which means WSJT-X only needs >>>> one place to pull a new version of Hamlib from. >>>> >>>> But Unix/Linux is far more versatile. You can run it on a wide >>>> range of distributions >>>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or >>>> whatever else you prefer. >>>> You can even set up your own “distro” if you want to. >>>> >>>> Because of this diversity, it would be very difficult for WSJT-X to >>>> know where to >>>> download a new version of Hamlib from — assuming such a package >>>> even exists. >>>> >>>> However, there is a workaround. You just need to install whatever >>>> version of Hamlib >>>> you want on your system, start the `rigctld` daemon with the >>>> parameters suitable for your rig, >>>> and select “Hamlib NET rigctl” as your radio in WSJT-X. >>>> >>>> Granted, this requires some IT skills beyond those of an “appliance >>>> user,” but it’s >>>> definitely doable. >>>> >>>> 73's de Kari, oh2gqc >>>> >>>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >>>>> Hello, >>>>> >>>>> Why only Windows version of WSJTX has the feature to >>>>> upgrade/roll-back Hamlib from within the program? >>>>> >>>>> In Linux, at least if you use the WSJTX source-code, in order to >>>>> get the updated Hamlib version, you need to recompile the code! >>>>> >>>>> I think that WSJTX for Linux has limited features in comparison to >>>>> Windows. >>>>> >>>>> I would like to get the same. >>>>> >>>>> Regards Marco, PY1ZRJ >>>>> --- >>>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>>> ** >>>>> >>>>> >>>>> _______________________________________________ >>>>> wsjt-devel mailing list >>>>> wsj...@li... <mailto:wsj...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>>> >>>> >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsj...@li... <mailto:wsj...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>> >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> --- >> *73 de Marco, PY1ZRJ (former IK5BCU)* >> ** >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Adrian <vk...@gm...> - 2025-11-24 18:05:03
|
Try the older method and adjust to suit , pointing the paths to the extracted hamlib source you want to use ; To build Hamlib from sources something like the following recipe should suffice: $ mkdir ~/hamlib-prefix $ cd ~/hamlib-prefix $ git clone https://github.com/Hamlib/Hamlib src $ cd src $ git checkout integration $ ./bootstrap $ mkdir ../build $ cd ../build $ ../src/configure --prefix=$HOME/hamlib-prefix \ --disable-shared --enable-static \ --without-cxx-binding --disable-winradio \ CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \ LDFLAGS="-Wl,--gc-sections" $ make $ make install-strip This will build a binary hamlib package located at ~/hamlib-prefix so you will need to add that to your CMAKE_PREFIX_PATH variable in your WSJT-X build. On Linux that is probably the only path you have on CMAKE_PREFIX_PATH unless you are using a locally installed Qt installation. To get the sources either download and extract a source tarball from the project web site or preferably fetch the sources directly from the project's subversion repository. $ mkdir -p ~/wsjtx-prefix/build $ cd ~/wsjtx-prefix $ git clone git://git.code.sf.net/p/wsjt/wsjtx src To build WSJT-X you will need CMake and asciidoc installed. $ cd ~/wsjtx-prefix/build $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON \ -DWSJT_GENERATE_DOCS=OFF ../src $ cmake --build . $ cmake --build . --target install The recipe above will install into /usr by default, if you wish to install in you own directory you can add a prefix-path to the configure step like: $ cd ~/wsjtx-prefix/build $ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix \ -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF \ -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix ../src $ cmake --build . $ cmake --build . --target install this will install WSJT-X at ~/wsjtx-prefix. On 25/11/25 01:22, Marco Calistri via wsjt-devel wrote: > I copied hamlib-4.4 as indicated then I need to rename back to 4.7 > otherwise gmake was complaining. > > Doing that, compile went well until this error below: > > [ 81%] Building CXX object > CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o > /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp: > In member function ‘QByteArray HamlibTransceiver::impl::get_conf(const > char*)’: > /home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20: > error: ‘rig_get_conf2’ was not declared in this scope; did you mean > ‘rig_get_conf’? > 336 | error_check (rig_get_conf2 (rig_.data (), token, > value.data (),value.length()), tr ("getting a configuration item")); > //changed to conf2, added parameter for buffer length > | ^~~~~~~~~~~~~ > | rig_get_conf > gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548: > CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1 > gmake[5]: *** [CMakeFiles/Makefile2:2058: CMakeFiles/wsjt_qt.dir/all] > Error 2 > gmake[4]: *** [Makefile:156: all] Error 2 > gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78: > wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 > > I don't know how to resolve this. > > Regards, Marco PY1ZRJ > > Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto: >> Will try your suggestion Adrian, I downloaded hamlib 4.4 since many >> reported issues starting with version 4.5. I use old rtx YAESU FT >> 100, then I hope to resolve my VFO random splits A, B, B, A, by using >> older hamlib. >> >> 73 Marco PY1ZRJ >> >> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >> >> ------------------------------------------------------------------------ >> *Da:* Marco Calistri via wsjt-devel <wsj...@li...> >> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM >> *A:* WSJT software development <wsj...@li...> >> *Cc:* Marco Calistri <PY...@ou...> >> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib >> >> This is interesting! >> >> But my original email was talking about something integrated into the >> software, as it has been deployed in Windows. >> >> Maybe it's not feasible in Linux, then just disregard my feature request. >> >> Best, >> >> Marco PY1ZRJ >> >> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >> ------------------------------------------------------------------------ >> *From:* Adrian via wsjt-devel <wsj...@li...> >> *Sent:* Saturday, November 15, 2025 9:26:18 PM >> *To:* wsj...@li... <wsj...@li...> >> *Cc:* Adrian <vk...@gm...> >> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >> >> You can replace the tar.gz with latest etc as you wish before compile ; >> >> 73 >> >> >> vk4tux >> >> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: >>> Hi Karl! >>> >>> Yes I agree with you (partially). >>> >>> Hamlib puts the upgrades inside its Git repository then it's the >>> unique place wherein the cmake process look at/for. >>> >>> I use rigctld as you described, but if you look at WSJTX settings, >>> you will see the hamlib version which cmake has found in the moment >>> you made the code compilation and this is not the latest available. >>> >>> 73s de Marco PY1ZRJ >>> >>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg> >>> ------------------------------------------------------------------------ >>> *From:* Kari Sillanmäki via wsjt-devel >>> <wsj...@li...> >>> <mailto:wsj...@li...> >>> *Sent:* Saturday, November 15, 2025 8:34:51 PM >>> *To:* wsj...@li... >>> <mailto:wsj...@li...> >>> <wsj...@li...> >>> <mailto:wsj...@li...> >>> *Cc:* Kari Sillanmäki <kai...@gm...> >>> <mailto:kai...@gm...> >>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib >>> Hi Marco, >>> >>> As you know, Windowzie is this “same pants fit everyone” system, >>> which means WSJT-X only needs >>> one place to pull a new version of Hamlib from. >>> >>> But Unix/Linux is far more versatile. You can run it on a wide range >>> of distributions >>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or >>> whatever else you prefer. >>> You can even set up your own “distro” if you want to. >>> >>> Because of this diversity, it would be very difficult for WSJT-X to >>> know where to >>> download a new version of Hamlib from — assuming such a package even >>> exists. >>> >>> However, there is a workaround. You just need to install whatever >>> version of Hamlib >>> you want on your system, start the `rigctld` daemon with the >>> parameters suitable for your rig, >>> and select “Hamlib NET rigctl” as your radio in WSJT-X. >>> >>> Granted, this requires some IT skills beyond those of an “appliance >>> user,” but it’s >>> definitely doable. >>> >>> 73's de Kari, oh2gqc >>> >>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >>>> Hello, >>>> >>>> Why only Windows version of WSJTX has the feature to >>>> upgrade/roll-back Hamlib from within the program? >>>> >>>> In Linux, at least if you use the WSJTX source-code, in order to >>>> get the updated Hamlib version, you need to recompile the code! >>>> >>>> I think that WSJTX for Linux has limited features in comparison to >>>> Windows. >>>> >>>> I would like to get the same. >>>> >>>> Regards Marco, PY1ZRJ >>>> --- >>>> *73 de Marco, PY1ZRJ (former IK5BCU)* >>>> ** >>>> >>>> >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsj...@li... <mailto:wsj...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >>> >>> >>> >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsj...@li... <mailto:wsj...@li...> >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-11-24 15:22:58
|
I copied hamlib-4.4 as indicated then I need to rename back to 4.7
otherwise gmake was complaining.
Doing that, compile went well until this error below:
[ 81%] Building CXX object
CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o
/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:
In member function ‘QByteArray HamlibTransceiver::impl::get_conf(const
char*)’:
/home/marco/WSJT-X_build/build/wsjtx-3.0.0-rc1/wsjtx-prefix/src/wsjtx/Transceiver/HamlibTransceiver.cpp:336:20:
error: ‘rig_get_conf2’ was not declared in this scope; did you mean
‘rig_get_conf’?
336 | error_check (rig_get_conf2 (rig_.data (), token,
value.data (),value.length()), tr ("getting a configuration item"));
//changed to conf2, added parameter for buffer length
| ^~~~~~~~~~~~~
| rig_get_conf
gmake[6]: *** [CMakeFiles/wsjt_qt.dir/build.make:548:
CMakeFiles/wsjt_qt.dir/Transceiver/HamlibTransceiver.cpp.o] Error 1
gmake[5]: *** [CMakeFiles/Makefile2:2058: CMakeFiles/wsjt_qt.dir/all]
Error 2
gmake[4]: *** [Makefile:156: all] Error 2
gmake[3]: *** [CMakeFiles/wsjtx-install.dir/build.make:78:
wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
I don't know how to resolve this.
Regards, Marco PY1ZRJ
Il 24/11/25 09:54, Marco Calistri via wsjt-devel ha scritto:
> Will try your suggestion Adrian, I downloaded hamlib 4.4 since many
> reported issues starting with version 4.5. I use old rtx YAESU FT 100,
> then I hope to resolve my VFO random splits A, B, B, A, by using older
> hamlib.
>
> 73 Marco PY1ZRJ
>
> Inviato da Outlook per Android <https://aka.ms/AAb9ysg>
>
> ------------------------------------------------------------------------
> *Da:* Marco Calistri via wsjt-devel <wsj...@li...>
> *Inviato:* Sabato, Novembre 15, 2025 9:42:33 PM
> *A:* WSJT software development <wsj...@li...>
> *Cc:* Marco Calistri <PY...@ou...>
> *Oggetto:* Re: [wsjt-devel] WSJTX Linux Hamlib
>
> This is interesting!
>
> But my original email was talking about something integrated into the
> software, as it has been deployed in Windows.
>
> Maybe it's not feasible in Linux, then just disregard my feature request.
>
> Best,
>
> Marco PY1ZRJ
>
> Inviato da Outlook per Android <https://aka.ms/AAb9ysg>
> ------------------------------------------------------------------------
> *From:* Adrian via wsjt-devel <wsj...@li...>
> *Sent:* Saturday, November 15, 2025 9:26:18 PM
> *To:* wsj...@li... <wsj...@li...>
> *Cc:* Adrian <vk...@gm...>
> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib
>
> You can replace the tar.gz with latest etc as you wish before compile ;
>
> 73
>
>
> vk4tux
>
> On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote:
>> Hi Karl!
>>
>> Yes I agree with you (partially).
>>
>> Hamlib puts the upgrades inside its Git repository then it's the
>> unique place wherein the cmake process look at/for.
>>
>> I use rigctld as you described, but if you look at WSJTX settings,
>> you will see the hamlib version which cmake has found in the moment
>> you made the code compilation and this is not the latest available.
>>
>> 73s de Marco PY1ZRJ
>>
>> Inviato da Outlook per Android <https://aka.ms/AAb9ysg>
>> ------------------------------------------------------------------------
>> *From:* Kari Sillanmäki via wsjt-devel
>> <wsj...@li...>
>> <mailto:wsj...@li...>
>> *Sent:* Saturday, November 15, 2025 8:34:51 PM
>> *To:* wsj...@li...
>> <mailto:wsj...@li...>
>> <wsj...@li...>
>> <mailto:wsj...@li...>
>> *Cc:* Kari Sillanmäki <kai...@gm...>
>> <mailto:kai...@gm...>
>> *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib
>> Hi Marco,
>>
>> As you know, Windowzie is this “same pants fit everyone” system,
>> which means WSJT-X only needs
>> one place to pull a new version of Hamlib from.
>>
>> But Unix/Linux is far more versatile. You can run it on a wide range
>> of distributions
>> such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or whatever
>> else you prefer.
>> You can even set up your own “distro” if you want to.
>>
>> Because of this diversity, it would be very difficult for WSJT-X to
>> know where to
>> download a new version of Hamlib from — assuming such a package even
>> exists.
>>
>> However, there is a workaround. You just need to install whatever
>> version of Hamlib
>> you want on your system, start the `rigctld` daemon with the
>> parameters suitable for your rig,
>> and select “Hamlib NET rigctl” as your radio in WSJT-X.
>>
>> Granted, this requires some IT skills beyond those of an “appliance
>> user,” but it’s
>> definitely doable.
>>
>> 73's de Kari, oh2gqc
>>
>> On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote:
>>> Hello,
>>>
>>> Why only Windows version of WSJTX has the feature to
>>> upgrade/roll-back Hamlib from within the program?
>>>
>>> In Linux, at least if you use the WSJTX source-code, in order to get
>>> the updated Hamlib version, you need to recompile the code!
>>>
>>> I think that WSJTX for Linux has limited features in comparison to
>>> Windows.
>>>
>>> I would like to get the same.
>>>
>>> Regards Marco, PY1ZRJ
>>> ---
>>> *73 de Marco, PY1ZRJ (former IK5BCU)*
>>> **
>>>
>>>
>>> _______________________________________________
>>> wsjt-devel mailing list
>>> wsj...@li... <mailto:wsj...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
>>
>>
>>
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li... <mailto:wsj...@li...>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
|
|
From: Marco C. <PY...@ou...> - 2025-11-24 12:54:51
|
Will try your suggestion Adrian, I downloaded hamlib 4.4 since many reported issues starting with version 4.5. I use old rtx YAESU FT 100, then I hope to resolve my VFO random splits A, B, B, A, by using older hamlib. 73 Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ Da: Marco Calistri via wsjt-devel <wsj...@li...> Inviato: Sabato, Novembre 15, 2025 9:42:33 PM A: WSJT software development <wsj...@li...> Cc: Marco Calistri <PY...@ou...> Oggetto: Re: [wsjt-devel] WSJTX Linux Hamlib This is interesting! But my original email was talking about something integrated into the software, as it has been deployed in Windows. Maybe it's not feasible in Linux, then just disregard my feature request. Best, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Adrian via wsjt-devel <wsj...@li...> Sent: Saturday, November 15, 2025 9:26:18 PM To: wsj...@li... <wsj...@li...> Cc: Adrian <vk...@gm...> Subject: Re: [wsjt-devel] WSJTX Linux Hamlib You can replace the tar.gz with latest etc as you wish before compile ; [cid:par...@gm...] 73 vk4tux On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: Hi Karl! Yes I agree with you (partially). Hamlib puts the upgrades inside its Git repository then it's the unique place wherein the cmake process look at/for. I use rigctld as you described, but if you look at WSJTX settings, you will see the hamlib version which cmake has found in the moment you made the code compilation and this is not the latest available. 73s de Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Kari Sillanmäki via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Saturday, November 15, 2025 8:34:51 PM To: wsj...@li...<mailto:wsj...@li...> <wsj...@li...><mailto:wsj...@li...> Cc: Kari Sillanmäki <kai...@gm...><mailto:kai...@gm...> Subject: Re: [wsjt-devel] WSJTX Linux Hamlib Hi Marco, As you know, Windowzie is this “same pants fit everyone” system, which means WSJT-X only needs one place to pull a new version of Hamlib from. But Unix/Linux is far more versatile. You can run it on a wide range of distributions such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or whatever else you prefer. You can even set up your own “distro” if you want to. Because of this diversity, it would be very difficult for WSJT-X to know where to download a new version of Hamlib from — assuming such a package even exists. However, there is a workaround. You just need to install whatever version of Hamlib you want on your system, start the `rigctld` daemon with the parameters suitable for your rig, and select “Hamlib NET rigctl” as your radio in WSJT-X. Granted, this requires some IT skills beyond those of an “appliance user,” but it’s definitely doable. 73's de Kari, oh2gqc On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: Hello, Why only Windows version of WSJTX has the feature to upgrade/roll-back Hamlib from within the program? In Linux, at least if you use the WSJTX source-code, in order to get the updated Hamlib version, you need to recompile the code! I think that WSJTX for Linux has limited features in comparison to Windows. I would like to get the same. Regards Marco, PY1ZRJ --- 73 de Marco, PY1ZRJ (former IK5BCU) [cid:par...@gm...] _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Glenn W. <af...@al...> - 2025-11-23 02:40:06
|
I will start with all that. Thanks. Time will pass for a while... :) --73, Glenn, AF8C On 11/22/2025 6:48 PM, George Baltz via wsjt-devel wrote: > You can see the live text commands, but only mixed in with lots of other > debugging stuff; with WSJT-X improved, you turn on rig control > debugging. The commands sent to the TS-590S/SG are those in the PC > CONTROL COMMAND Reference Guide[https://www.kenwood.com/i/products/info/ > amateur/pdf/ts590_g_pc_command_en_rev3.pdf]. The pseudo-commands that > Hamlib uses internally are (sorta) listed in the man pages for rigctl/ > rigctld. If you want all the rig commands for all 317 rigs Hamlib > supports, I'm afraid the only single source for those is to download the > Hamlib source and browse the code. > > Be happy to help you narrow down your search. > > 73 n3gb (hamlib developer) > > On 11/22/25 10:11 AM, Glenn Williams via wsjt-devel wrote: >> It's time for dumb questions here. I have never needed to peek inside >> Hamlib for using my Kenwood TS590SG here. Everything has operated >> well. But I would like to be able to see all the commands that Hamlib >> has for all the rigs, including things like all the USB port text >> strings sent to the rig for a TS590SG, or similar for rigs like K3 >> and K4, and what is used in "English" for older rigs using Signalink >> interfaces, etc. The WSJT-X 3.0.0 User Guide only says Hamlib is a >> DLL which will not reveal the list of human readable commands for >> each type of rig (True/False?). >> >> --Glenn, AF8C >> > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: Alan M. <al...@me...> - 2025-11-23 02:19:25
|
https://hamlib.sourceforge.net/html/rigctl.1.html On Sun, 23 Nov 2025 at 02:11, Glenn Williams via wsjt-devel < wsj...@li...> wrote: > It's time for dumb questions here. I have never needed to peek inside > Hamlib for using my Kenwood TS590SG here. Everything has operated > well. But I would like to be able to see all the commands that Hamlib > has for all the rigs, including things like all the USB port text > strings sent to the rig for a TS590SG, or similar for rigs like K3 > and K4, and what is used in "English" for older rigs using Signalink > interfaces, etc. The WSJT-X 3.0.0 User Guide only says Hamlib is a > DLL which will not reveal the list of human readable commands for > each type of rig (True/False?). > > --Glenn, AF8C > > -- > This email has been checked for viruses by Avast antivirus software. > www.avast.com > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- regards Alan McDonald |
|
From: George B. <geo...@gm...> - 2025-11-22 23:48:44
|
You can see the live text commands, but only mixed in with lots of other debugging stuff; with WSJT-X improved, you turn on rig control debugging. The commands sent to the TS-590S/SG are those in the PC CONTROL COMMAND Reference Guide[https://www.kenwood.com/i/products/info/amateur/pdf/ts590_g_pc_command_en_rev3.pdf]. The pseudo-commands that Hamlib uses internally are (sorta) listed in the man pages for rigctl/rigctld. If you want all the rig commands for all 317 rigs Hamlib supports, I'm afraid the only single source for those is to download the Hamlib source and browse the code. Be happy to help you narrow down your search. 73 n3gb (hamlib developer) On 11/22/25 10:11 AM, Glenn Williams via wsjt-devel wrote: > It's time for dumb questions here. I have never needed to peek inside > Hamlib for using my Kenwood TS590SG here. Everything has operated > well. But I would like to be able to see all the commands that Hamlib > has for all the rigs, including things like all the USB port text > strings sent to the rig for a TS590SG, or similar for rigs like K3 > and K4, and what is used in "English" for older rigs using Signalink > interfaces, etc. The WSJT-X 3.0.0 User Guide only says Hamlib is a > DLL which will not reveal the list of human readable commands for > each type of rig (True/False?). > > --Glenn, AF8C > |
|
From: Glenn W. <af...@al...> - 2025-11-22 22:48:20
|
It's time for dumb questions here. I have never needed to peek inside Hamlib for using my Kenwood TS590SG here. Everything has operated well. But I would like to be able to see all the commands that Hamlib has for all the rigs, including things like all the USB port text strings sent to the rig for a TS590SG, or similar for rigs like K3 and K4, and what is used in "English" for older rigs using Signalink interfaces, etc. The WSJT-X 3.0.0 User Guide only says Hamlib is a DLL which will not reveal the list of human readable commands for each type of rig (True/False?). --Glenn, AF8C -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: Marco C. <PY...@ou...> - 2025-11-16 00:39:16
|
This is interesting! But my original email was talking about something integrated into the software, as it has been deployed in Windows. Maybe it's not feasible in Linux, then just disregard my feature request. Best, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Adrian via wsjt-devel <wsj...@li...> Sent: Saturday, November 15, 2025 9:26:18 PM To: wsj...@li... <wsj...@li...> Cc: Adrian <vk...@gm...> Subject: Re: [wsjt-devel] WSJTX Linux Hamlib You can replace the tar.gz with latest etc as you wish before compile ; [cid:par...@gm...] 73 vk4tux On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: Hi Karl! Yes I agree with you (partially). Hamlib puts the upgrades inside its Git repository then it's the unique place wherein the cmake process look at/for. I use rigctld as you described, but if you look at WSJTX settings, you will see the hamlib version which cmake has found in the moment you made the code compilation and this is not the latest available. 73s de Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Kari Sillanmäki via wsjt-devel <wsj...@li...><mailto:wsj...@li...> Sent: Saturday, November 15, 2025 8:34:51 PM To: wsj...@li...<mailto:wsj...@li...> <wsj...@li...><mailto:wsj...@li...> Cc: Kari Sillanmäki <kai...@gm...><mailto:kai...@gm...> Subject: Re: [wsjt-devel] WSJTX Linux Hamlib Hi Marco, As you know, Windowzie is this “same pants fit everyone” system, which means WSJT-X only needs one place to pull a new version of Hamlib from. But Unix/Linux is far more versatile. You can run it on a wide range of distributions such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or whatever else you prefer. You can even set up your own “distro” if you want to. Because of this diversity, it would be very difficult for WSJT-X to know where to download a new version of Hamlib from — assuming such a package even exists. However, there is a workaround. You just need to install whatever version of Hamlib you want on your system, start the `rigctld` daemon with the parameters suitable for your rig, and select “Hamlib NET rigctl” as your radio in WSJT-X. Granted, this requires some IT skills beyond those of an “appliance user,” but it’s definitely doable. 73's de Kari, oh2gqc On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: Hello, Why only Windows version of WSJTX has the feature to upgrade/roll-back Hamlib from within the program? In Linux, at least if you use the WSJTX source-code, in order to get the updated Hamlib version, you need to recompile the code! I think that WSJTX for Linux has limited features in comparison to Windows. I would like to get the same. Regards Marco, PY1ZRJ --- 73 de Marco, PY1ZRJ (former IK5BCU) [cid:par...@gm...] _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Adrian <vk...@gm...> - 2025-11-16 00:26:35
|
You can replace the tar.gz with latest etc as you wish before compile ; 73 vk4tux On 16/11/25 09:52, Marco Calistri via wsjt-devel wrote: > Hi Karl! > > Yes I agree with you (partially). > > Hamlib puts the upgrades inside its Git repository then it's the > unique place wherein the cmake process look at/for. > > I use rigctld as you described, but if you look at WSJTX settings, you > will see the hamlib version which cmake has found in the moment you > made the code compilation and this is not the latest available. > > 73s de Marco PY1ZRJ > > Inviato da Outlook per Android <https://aka.ms/AAb9ysg> > ------------------------------------------------------------------------ > *From:* Kari Sillanmäki via wsjt-devel <wsj...@li...> > *Sent:* Saturday, November 15, 2025 8:34:51 PM > *To:* wsj...@li... <wsj...@li...> > *Cc:* Kari Sillanmäki <kai...@gm...> > *Subject:* Re: [wsjt-devel] WSJTX Linux Hamlib > Hi Marco, > > As you know, Windowzie is this “same pants fit everyone” system, which > means WSJT-X only needs > one place to pull a new version of Hamlib from. > > But Unix/Linux is far more versatile. You can run it on a wide range > of distributions > such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or whatever > else you prefer. > You can even set up your own “distro” if you want to. > > Because of this diversity, it would be very difficult for WSJT-X to > know where to > download a new version of Hamlib from — assuming such a package even > exists. > > However, there is a workaround. You just need to install whatever > version of Hamlib > you want on your system, start the `rigctld` daemon with the > parameters suitable for your rig, > and select “Hamlib NET rigctl” as your radio in WSJT-X. > > Granted, this requires some IT skills beyond those of an “appliance > user,” but it’s > definitely doable. > > 73's de Kari, oh2gqc > > On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: >> Hello, >> >> Why only Windows version of WSJTX has the feature to >> upgrade/roll-back Hamlib from within the program? >> >> In Linux, at least if you use the WSJTX source-code, in order to get >> the updated Hamlib version, you need to recompile the code! >> >> I think that WSJTX for Linux has limited features in comparison to >> Windows. >> >> I would like to get the same. >> >> Regards Marco, PY1ZRJ >> --- >> *73 de Marco, PY1ZRJ (former IK5BCU)* >> ** >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... <mailto:wsj...@li...> >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-11-15 23:52:56
|
Hi Karl! Yes I agree with you (partially). Hamlib puts the upgrades inside its Git repository then it's the unique place wherein the cmake process look at/for. I use rigctld as you described, but if you look at WSJTX settings, you will see the hamlib version which cmake has found in the moment you made the code compilation and this is not the latest available. 73s de Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Kari Sillanmäki via wsjt-devel <wsj...@li...> Sent: Saturday, November 15, 2025 8:34:51 PM To: wsj...@li... <wsj...@li...> Cc: Kari Sillanmäki <kai...@gm...> Subject: Re: [wsjt-devel] WSJTX Linux Hamlib Hi Marco, As you know, Windowzie is this “same pants fit everyone” system, which means WSJT-X only needs one place to pull a new version of Hamlib from. But Unix/Linux is far more versatile. You can run it on a wide range of distributions such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or whatever else you prefer. You can even set up your own “distro” if you want to. Because of this diversity, it would be very difficult for WSJT-X to know where to download a new version of Hamlib from — assuming such a package even exists. However, there is a workaround. You just need to install whatever version of Hamlib you want on your system, start the `rigctld` daemon with the parameters suitable for your rig, and select “Hamlib NET rigctl” as your radio in WSJT-X. Granted, this requires some IT skills beyond those of an “appliance user,” but it’s definitely doable. 73's de Kari, oh2gqc On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: Hello, Why only Windows version of WSJTX has the feature to upgrade/roll-back Hamlib from within the program? In Linux, at least if you use the WSJTX source-code, in order to get the updated Hamlib version, you need to recompile the code! I think that WSJTX for Linux has limited features in comparison to Windows. I would like to get the same. Regards Marco, PY1ZRJ --- 73 de Marco, PY1ZRJ (former IK5BCU) [cid:par...@gm...] _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Kari S. <kai...@gm...> - 2025-11-15 23:35:02
|
Hi Marco, As you know, Windowzie is this “same pants fit everyone” system, which means WSJT-X only needs one place to pull a new version of Hamlib from. But Unix/Linux is far more versatile. You can run it on a wide range of distributions such as Debian, Ubuntu, Fedora, Raspberry Pi OS, Red Hat, or whatever else you prefer. You can even set up your own “distro” if you want to. Because of this diversity, it would be very difficult for WSJT-X to know where to download a new version of Hamlib from — assuming such a package even exists. However, there is a workaround. You just need to install whatever version of Hamlib you want on your system, start the `rigctld` daemon with the parameters suitable for your rig, and select “Hamlib NET rigctl” as your radio in WSJT-X. Granted, this requires some IT skills beyond those of an “appliance user,” but it’s definitely doable. 73's de Kari, oh2gqc On 11/16/25 00:08, Marco Calistri via wsjt-devel wrote: > Hello, > > Why only Windows version of WSJTX has the feature to upgrade/roll-back > Hamlib from within the program? > > In Linux, at least if you use the WSJTX source-code, in order to get > the updated Hamlib version, you need to recompile the code! > > I think that WSJTX for Linux has limited features in comparison to > Windows. > > I would like to get the same. > > Regards Marco, PY1ZRJ > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Marco C. <PY...@ou...> - 2025-11-15 22:28:15
|
Il 15/11/25 19:22, Christoph Berg ha scritto: > Re: Marco Calistri via wsjt-devel >> In Linux, at least if you use the WSJTX source-code, in order to get the >> updated Hamlib version, you need to recompile the code! > If you do it properly, everything installed lands in a package (.deb, > .rpm, whatever). Then you can up- and downgrade easily by installing > that package. > > Christoph Yes Christoph, But I never create .deb or .rpm, I use to compile directly the source code and use the binaries. If you can observe during the compilation, the process download the last hamlib available from its repository then use it internally. It should be nice to have a feature to run just the the hamlib upgrade from within the software, as it is available in Windows, that's what I meant. 73,s de PY1ZRJ --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Christoph B. <my...@de...> - 2025-11-15 22:22:59
|
Re: Marco Calistri via wsjt-devel > In Linux, at least if you use the WSJTX source-code, in order to get the > updated Hamlib version, you need to recompile the code! If you do it properly, everything installed lands in a package (.deb, .rpm, whatever). Then you can up- and downgrade easily by installing that package. Christoph |
|
From: Marco C. <PY...@ou...> - 2025-11-15 22:08:36
|
Hello, Why only Windows version of WSJTX has the feature to upgrade/roll-back Hamlib from within the program? In Linux, at least if you use the WSJTX source-code, in order to get the updated Hamlib version, you need to recompile the code! I think that WSJTX for Linux has limited features in comparison to Windows. I would like to get the same. Regards Marco, PY1ZRJ --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Scott <ss...@pt...> - 2025-11-14 20:21:25
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Thanks, Adrian. I tried installing libboist-dev and while that worked, there was no change to my problems with the install. However, just before I began to build from source, there was a push to update/upgrade several Trixie packages, one of which was wsjtx2.7.1. After the update, wsjtx works!<br id="lineBreakAtBeginningOfSignature"><div dir="ltr">73 de W3WT </div><div dir="ltr"><br><blockquote type="cite">On Nov 14, 2025, at 13:05, Adrian via wsjt-devel <wsj...@li...> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>When compiling you are looking for the dev packages for that
dependency, so </p>
<h1 style="margin: 0.83333em 0px; padding: 0px; border: 0px; outline: 0px; font-weight: normal; font-style: normal; font-size: 1.8em; font-family: sans-serif; vertical-align: baseline; color: rgb(0, 0, 0); line-height: 0.83333; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">libboost-dev</h1>
<div class="moz-cite-prefix">Just compile from source instead</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">73</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">vk4tux (Trixie user)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 14/11/25 23:22, Scott via wsjt-devel
wrote:<br>
</div>
<blockquote type="cite" cite="mid:34D...@pt...">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 15">
<meta name="Originator" content="Microsoft Word 15">
<link rel="File-List" href="cid:filelist.xml@01DC5343.20B0BC80">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]-->
<link rel="themeData" href="~~themedata~~">
<link rel="colorSchemeMapping" href="~~colorschememapping~~">
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>90</w:Zoom>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false" DefSemiHidden="false" DefQFormat="false" DefPriority="99" LatentStyleCount="371">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true" UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true" Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true" Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true" Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true" Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true" Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true" Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true" Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true" UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true" UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful Accent 6"/>
</w:LatentStyles>
</xml><![endif]-->
<style>@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Calibri; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; }
a:link, span.MsoHyperlink { color: rgb(5, 99, 193); text-decoration: underline; }
a:visited, span.MsoHyperlinkFollowed { color: rgb(149, 79, 114); text-decoration: underline; }
span.EmailStyle17 { font-family: Calibri, sans-serif; color: windowtext; }
span.SpellE { }
.MsoChpDefault { font-size: 10pt; font-family: Calibri, sans-serif; }
div.WordSection1 { page: WordSection1; }</style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">I upgraded to Trixie on my Pi4 and am
attempting to install the installation package 2.7.1.<span style="mso-spacerun:yes"> </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Aside from a few overwrite issues I
overcame, the install terminates looking for packages <span class="SpellE">libboost</span>-log, -filesystem, and
–thread.<span style="mso-spacerun:yes"> </span>Specifically,
the installation is looking for versions 1.74 of each but
not finding any version of them.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To address this, I ran commands <span class="SpellE">sudo</span> apt install <span class="SpellE">libboost</span>-log, <span class="SpellE">sudo</span>
apt install <span class="SpellE">libboost</span>-filesystem,
and <span class="SpellE">sudo</span> apt install <span class="SpellE">libboost</span>-thread.<span style="mso-spacerun:yes"> </span>For each command,
Trixie informed me that the latest version of the respective
package was installed and the most up-to-date:
libbost-log1.83.0.2+b2, libboost-filesystem1.83.02+b2, and
libboost-thread1.83.0.2+b2.<span style="mso-spacerun:yes">
</span>So, while Trixie says they exist, <span class="SpellE">wsjtx</span> is unable to find any.<span style="mso-spacerun:yes"> </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Trying 2.6.0 results in the same failure.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does anyone have a suggestion on how to
overcome this? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">73 W3WT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
wsjt-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wsj...@li...">wsj...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel">https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a>
</pre>
</blockquote>
<span>_______________________________________________</span><br><span>wsjt-devel mailing list</span><br><span>wsj...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/wsjt-devel</span><br></div></blockquote></body></html> |
68 messages has been excluded from this view by a project administrator.
