hamlib-developer Mailing List for Ham Radio Control Libraries (Page 7)
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
hamlib-developer — hamlib developers forum
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(24) |
Oct
(16) |
Nov
(8) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(49) |
Feb
(17) |
Mar
(3) |
Apr
(7) |
May
(3) |
Jun
(1) |
Jul
(2) |
Aug
(8) |
Sep
(18) |
Oct
(15) |
Nov
(15) |
Dec
(26) |
| 2002 |
Jan
(46) |
Feb
(14) |
Mar
(44) |
Apr
(3) |
May
(6) |
Jun
(47) |
Jul
(40) |
Aug
(14) |
Sep
(59) |
Oct
(39) |
Nov
(58) |
Dec
(76) |
| 2003 |
Jan
(82) |
Feb
(66) |
Mar
(37) |
Apr
(56) |
May
(34) |
Jun
(19) |
Jul
(23) |
Aug
(55) |
Sep
(31) |
Oct
(40) |
Nov
(21) |
Dec
(60) |
| 2004 |
Jan
(57) |
Feb
(110) |
Mar
(41) |
Apr
(17) |
May
(18) |
Jun
(19) |
Jul
(18) |
Aug
(5) |
Sep
(31) |
Oct
(16) |
Nov
(26) |
Dec
(36) |
| 2005 |
Jan
(69) |
Feb
(26) |
Mar
(62) |
Apr
(120) |
May
(31) |
Jun
(47) |
Jul
(7) |
Aug
(27) |
Sep
(4) |
Oct
(9) |
Nov
(26) |
Dec
(21) |
| 2006 |
Jan
(13) |
Feb
(26) |
Mar
(38) |
Apr
(31) |
May
(17) |
Jun
(6) |
Jul
(23) |
Aug
(6) |
Sep
(38) |
Oct
(87) |
Nov
(49) |
Dec
(49) |
| 2007 |
Jan
(52) |
Feb
(19) |
Mar
(20) |
Apr
(5) |
May
(25) |
Jun
(15) |
Jul
(49) |
Aug
(43) |
Sep
(21) |
Oct
(21) |
Nov
(27) |
Dec
(10) |
| 2008 |
Jan
(23) |
Feb
(20) |
Mar
(25) |
Apr
(39) |
May
(36) |
Jun
(17) |
Jul
(10) |
Aug
(18) |
Sep
(44) |
Oct
(88) |
Nov
(60) |
Dec
(65) |
| 2009 |
Jan
(99) |
Feb
(91) |
Mar
(49) |
Apr
(34) |
May
(52) |
Jun
(9) |
Jul
(11) |
Aug
(4) |
Sep
(41) |
Oct
(16) |
Nov
(51) |
Dec
(71) |
| 2010 |
Jan
(43) |
Feb
(79) |
Mar
(59) |
Apr
(55) |
May
(51) |
Jun
(38) |
Jul
(38) |
Aug
(61) |
Sep
(53) |
Oct
(46) |
Nov
(43) |
Dec
(41) |
| 2011 |
Jan
(74) |
Feb
(96) |
Mar
(41) |
Apr
(42) |
May
(61) |
Jun
(66) |
Jul
(50) |
Aug
(40) |
Sep
(11) |
Oct
(30) |
Nov
(21) |
Dec
(45) |
| 2012 |
Jan
(59) |
Feb
(4) |
Mar
(52) |
Apr
(19) |
May
(62) |
Jun
(46) |
Jul
(61) |
Aug
(18) |
Sep
(21) |
Oct
(25) |
Nov
(66) |
Dec
(41) |
| 2013 |
Jan
(36) |
Feb
(64) |
Mar
(37) |
Apr
(24) |
May
(74) |
Jun
(40) |
Jul
(43) |
Aug
(34) |
Sep
(65) |
Oct
(52) |
Nov
(23) |
Dec
(20) |
| 2014 |
Jan
(18) |
Feb
(29) |
Mar
(13) |
Apr
(41) |
May
(10) |
Jun
(12) |
Jul
(16) |
Aug
(25) |
Sep
(20) |
Oct
(56) |
Nov
(43) |
Dec
(61) |
| 2015 |
Jan
(36) |
Feb
(38) |
Mar
(92) |
Apr
(42) |
May
(13) |
Jun
(19) |
Jul
(18) |
Aug
(22) |
Sep
(21) |
Oct
(2) |
Nov
(49) |
Dec
(22) |
| 2016 |
Jan
(55) |
Feb
(144) |
Mar
(40) |
Apr
(98) |
May
(61) |
Jun
(36) |
Jul
(16) |
Aug
(33) |
Sep
(59) |
Oct
(16) |
Nov
(37) |
Dec
(32) |
| 2017 |
Jan
(70) |
Feb
(71) |
Mar
(14) |
Apr
(43) |
May
(31) |
Jun
(24) |
Jul
(38) |
Aug
(54) |
Sep
(24) |
Oct
(15) |
Nov
(26) |
Dec
(27) |
| 2018 |
Jan
(22) |
Feb
(24) |
Mar
(109) |
Apr
(12) |
May
(46) |
Jun
(23) |
Jul
(39) |
Aug
(34) |
Sep
(22) |
Oct
(43) |
Nov
(26) |
Dec
(157) |
| 2019 |
Jan
(102) |
Feb
(51) |
Mar
(63) |
Apr
(60) |
May
(91) |
Jun
(55) |
Jul
(27) |
Aug
(76) |
Sep
(52) |
Oct
(95) |
Nov
(67) |
Dec
(204) |
| 2020 |
Jan
(311) |
Feb
(148) |
Mar
(230) |
Apr
(122) |
May
(204) |
Jun
(204) |
Jul
(114) |
Aug
(36) |
Sep
(120) |
Oct
(186) |
Nov
(60) |
Dec
(151) |
| 2021 |
Jan
(182) |
Feb
(171) |
Mar
(202) |
Apr
(153) |
May
(110) |
Jun
(50) |
Jul
(58) |
Aug
(142) |
Sep
(112) |
Oct
(120) |
Nov
(97) |
Dec
(125) |
| 2022 |
Jan
(175) |
Feb
(147) |
Mar
(54) |
Apr
(73) |
May
(127) |
Jun
(95) |
Jul
(88) |
Aug
(85) |
Sep
(38) |
Oct
(40) |
Nov
(116) |
Dec
(159) |
| 2023 |
Jan
(175) |
Feb
(55) |
Mar
(83) |
Apr
(70) |
May
(165) |
Jun
(79) |
Jul
(123) |
Aug
(90) |
Sep
(40) |
Oct
(95) |
Nov
(84) |
Dec
(88) |
| 2024 |
Jan
(105) |
Feb
(60) |
Mar
(52) |
Apr
(43) |
May
(56) |
Jun
(59) |
Jul
(53) |
Aug
(47) |
Sep
(62) |
Oct
(36) |
Nov
(45) |
Dec
(100) |
| 2025 |
Jan
(52) |
Feb
(45) |
Mar
(30) |
Apr
(97) |
May
(72) |
Jun
(83) |
Jul
(124) |
Aug
(83) |
Sep
(84) |
Oct
(20) |
Nov
(39) |
Dec
|
|
From: Peter M. <pet...@gm...> - 2025-08-31 21:58:26
|
Dear Hamlib developers, I don’t seem to be able to create a feature request ticket on sourceforge. The button is dim. When hamlib reports an error, typically a timeout talking to the radio, the error string returned by rigerror() is very detailed and includes a stack trace. const char* rigerror <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db> ( int errnum ) get string describing the error code I’m involved in the FreeDV <https://freedv.org/> project which uses hamlib. We show the error string and find that it is intimidating to users. They sometimes report that FreeDV has “crashed”. It would be great if there was a second version of the error string with just the bit that the user needs. “Timeout talking to rig” for example. Many thanks for your great work. Peter VK3TPM |
|
From: Daniele F. <iu...@gm...> - 2025-08-31 21:55:03
|
Brian, it appears to fail in bindings/tcltest.tcl which hasn't been modified in many years, so the actual issue seems to be somewhere else; if you can look at the core dump with gdb, it could tell which function is failing. You can also edit tcltest.tcl to find what is the line that causes the error but it can get tricky. Is the spec file that you are using available somewhere? -- 73 de IU5HKX Daniele |
|
From: Richard E. <DO...@ho...> - 2025-08-31 19:25:43
|
Hello everyone, I noticed that Hamlib provides a Send Morse function, but it is only available for some rigs, since it depends on features implemented in the transceiver itself. My question is whether it would be possible, or maybe already planned, to emulate or implement this functionality directly within Hamlib. Some rigs allow control of PTT via the interface, and for certain models it is also possible to set the operating mode to CW. In principle, this could make it feasible to send Morse text at a specified speed directly through Hamlib, even if the rig itself does not provide a native Send Morse function. Could you please let me know what the current status is in this regard, and what the general opinion is about such an idea? Thank you very much for your time and for the great work you are doing with Hamlib. 73 Richard, DO9RE |
|
From: Brian M. <bd...@fe...> - 2025-08-31 18:12:20
|
On Sun, 31 Aug 2025 12:44:09 -0500 Nate Bargmann <n0...@n0...> wrote: > Brian. > > That doesn't make much sense to me but I Daniele can help as he has > been working on the bindings recently. Thanks. -- Brian G8SEZ |
|
From: Brian M. <bd...@fe...> - 2025-08-31 17:57:28
|
On Sun, 31 Aug 2025 15:16:27 +0100 Brian Morrison via Hamlib-developer <ham...@li...> wrote: > On Sun, 31 Aug 2025 08:50:28 -0500 > Nate Bargmann <n0...@n0...> wrote: > > > I think the run-time stability of 4.7~git is as good as any prior > > release right now and has received a lot of fixes over the past > > couple of months. As we'd like to release 4.7.0 sometime in the > > next couple of months or so, the ABI will not change so when it is > > released, current versions of applications should work with the > > resulting .so/.DLL. > > Hi Nate > > I have just tried to get the Fedora hamlib.spec file to build the > current hamlib-4.7~git and towards the end of the process I see this: > > make check-TESTS > make[2]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++' > make[3]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++' > PASS: testcpp > ============================================================================ > Testsuite summary for Hamlib 4.7~git > ============================================================================ > # TOTAL: 1 # PASS: 1 # SKIP: 0 > # XFAIL: 0 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > ============================================================================ > make[3]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++' > make[2]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++' > make[1]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++' > Making check in bindings make[1]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make check-am make[2]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make -f Hamlib-pl.mk all make[3]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Hamlib.bs > blib/arch/auto/Hamlib/Hamlib.bs 644 make[3]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make check-local make[3]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make -f Hamlib-pl.mk all make[4]: Entering directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Hamlib.bs > blib/arch/auto/Hamlib/Hamlib.bs 644 make[4]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > LD_LIBRARY_PATH=../src/.libs perl ../bindings/perltest.pl Perl > 5.040003 test, version: Hamlib 4.7~git > > get_conf: path = "/dev/Rig", retry = 50 > freq: 14266000 > get_mode: FM > width: 15000 > get_vfo: VFOA > Backend copyright: LGPL > Model: Dummy > Manufacturer: Hamlib > Backend version: 20240709.0 > get_info: Nothing much (dummy) > VOX delay: 0 > VOX delay: 5 > strength: -40 > get_channel status: 0 = rig_setting2idx called > VFO: MainA, 14266000 > Attenuators: 10 20 30 0 0 0 0 0 > > Sending Morse, '73' > > Sending raw string > > Some static functions: > Loc1: IN98XC -> -0.0417, 48.1042-> IN98XC > Loc1: DM33DX -> -113.7083, 33.9792-> DM33DX > Distance: 8765.814 km, azimuth 309.00, long path: 31266.186 km > Longitude: -0.0417, 0° 2' 29" W recoded: -0.0414 > Latitude: 48.1042, 48° 6' 15" N recoded: 48.1042 > PYTHONPATH=.:./.libs \ > /usr/bin/pytest --capture=no ./ > =========================================================== test > session starts > ============================================================ platform > linux -- Python 3.13.7, pytest-8.3.4, pluggy-1.5.0 rootdir: > /home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings > plugins: anyio-4.8.0, hypothesis-6.123.0 collected 19 items > > > python/test_Hamlib_Amp_class.py .. > python/test_Hamlib_Rig_class.py .. > python/test_Hamlib_Rot_class.py .. > python/test_Hamlib_class.py .. > python/test_amp.py ... > python/test_rig.py .... > python/test_rot.py ... > python/test_startup.py . > > ============================================================ 19 > passed in 2.87s > ============================================================ cp > ./pkgIndex.tcl ./.libs TCLLIBPATH=./.libs tclsh ./tcltest.tcl > make[3]: *** [Makefile:1183: check-tcl] Segmentation fault (core > dumped) make[3]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make[2]: *** [Makefile:947: check-am] Error 2 make[2]: Leaving > directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make[1]: *** [Makefile:949: check] Error 2 make[1]: Leaving directory > '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings' > make: *** [Makefile:672: check-recursive] Error 1 error: Bad exit > status from /home/bdm/rpmbuild/tmp/rpm-tmp.JwA7ey (%check) > > RPM build errors: > Bad exit status from /home/bdm/rpmbuild/tmp/rpm-tmp.JwA7ey > (%check) > > As you can see this is in the make check-TESTS section of the .spec > file however all of this was working with previous 4.7~git snapshots. > > Anything that makes any sense to you? > > I may have another try as the latest Fedora 42 src rpm might work > better. > And indeed the same error if I base the build on the: hamlib-4.6.4-1.fc42.src.rpm downloaded from Fedora koji, I suppose I had better ask Richard Shaw as he's the packager. -- Brian G8SEZ |
|
From: Nate B. <n0...@n0...> - 2025-08-31 17:44:16
|
Brian. That doesn't make much sense to me but I Daniele can help as he has been working on the bindings recently. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: Uwe, D. <dg...@gm...> - 2025-08-31 14:23:12
|
Hi Nate, Thanks for your reply. Then I will take one of the Hamlib Git daily snapshots for v3.0.0-rc1. I can wait another week or so. If any major bugs pop up in Hamlib, it would be great if someone could fix them by then (or at least let me know if you discover critical bugs that can't be fixed so quickly). FYI: This time, it will most likely be a joint release of WSJT-X and WSJT-X Improved, where WSJT-X is just the i+ variant of WSJT-X improved. Since WSJT-X Improved is updated more frequently, we will use these updates to gradually fix any bugs and/or further improve our code before eventually merging it into a new joint v3.0.0-rc2 release. That's our plan. However, the additional GUI variants (AL and widescreen), the packages for macOS M1 and possible special versions will continue to be available only under the WSJT-X Improved brand for the time being. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB Am 31.08.2025 um 15:50 schrieb Nate Bargmann: > * On 2025 30 Aug 11:31 -0500, Uwe, DG2YCB via Hamlib-developer wrote: >> Dear Hamlib developers, >> >> In about two weeks from now, a new 3.0.0-rc1 version of both WSJT-X and >> WSJT-X Improved is planned. My question is: which Hamlib version can you >> recommend? >> >> It should already have a driver for the Yaesu FTX-1, but has to be stable >> enough, of course. Does only the current 4.7 development version support the >> Yaesu FTX-1? Or is there already a 4.6.x version that includes this? Or do >> you want to release a new one in time for that? Thanks. > As you want the FTX-1, then a snapshot of 4.7~git will be your choice. > I will be releasing 4.6.5 this week but it only pertains to a couple of > segfault fixes and has no support for the FTX-1. Of course, those fixes > have been applied to 4.7~git as well. > > I think the run-time stability of 4.7~git is as good as any prior > release right now and has received a lot of fixes over the past couple > of months. As we'd like to release 4.7.0 sometime in the next couple of > months or so, the ABI will not change so when it is released, current > versions of applications should work with the resulting .so/.DLL. > > Expect ABI changes after the 4.7 branch is created as work will commence > toward 5.0. > > 73, Nate > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer |
|
From: Brian M. <bd...@fe...> - 2025-08-31 14:16:42
|
On Sun, 31 Aug 2025 08:50:28 -0500
Nate Bargmann <n0...@n0...> wrote:
> I think the run-time stability of 4.7~git is as good as any prior
> release right now and has received a lot of fixes over the past couple
> of months. As we'd like to release 4.7.0 sometime in the next couple
> of months or so, the ABI will not change so when it is released,
> current versions of applications should work with the resulting
> .so/.DLL.
Hi Nate
I have just tried to get the Fedora hamlib.spec file to build the
current hamlib-4.7~git and towards the end of the process I see this:
make check-TESTS
make[2]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++'
make[3]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++'
PASS: testcpp
============================================================================
Testsuite summary for Hamlib 4.7~git
============================================================================
# TOTAL: 1
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
make[3]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++'
make[2]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++'
make[1]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/c++'
Making check in bindings
make[1]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make check-am
make[2]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make -f Hamlib-pl.mk all
make[3]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Hamlib.bs blib/arch/auto/Hamlib/Hamlib.bs 644
make[3]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make check-local
make[3]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make -f Hamlib-pl.mk all
make[4]: Entering directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Hamlib.bs blib/arch/auto/Hamlib/Hamlib.bs 644
make[4]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
LD_LIBRARY_PATH=../src/.libs perl ../bindings/perltest.pl
Perl 5.040003 test, version: Hamlib 4.7~git
get_conf: path = "/dev/Rig", retry = 50
freq: 14266000
get_mode: FM
width: 15000
get_vfo: VFOA
Backend copyright: LGPL
Model: Dummy
Manufacturer: Hamlib
Backend version: 20240709.0
get_info: Nothing much (dummy)
VOX delay: 0
VOX delay: 5
strength: -40
get_channel status: 0 = rig_setting2idx called
VFO: MainA, 14266000
Attenuators: 10 20 30 0 0 0 0 0
Sending Morse, '73'
Sending raw string
Some static functions:
Loc1: IN98XC -> -0.0417, 48.1042-> IN98XC
Loc1: DM33DX -> -113.7083, 33.9792-> DM33DX
Distance: 8765.814 km, azimuth 309.00, long path: 31266.186 km
Longitude: -0.0417, 0° 2' 29" W recoded: -0.0414
Latitude: 48.1042, 48° 6' 15" N recoded: 48.1042
PYTHONPATH=.:./.libs \
/usr/bin/pytest --capture=no ./
=========================================================== test session starts ============================================================
platform linux -- Python 3.13.7, pytest-8.3.4, pluggy-1.5.0
rootdir: /home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings
plugins: anyio-4.8.0, hypothesis-6.123.0
collected 19 items
python/test_Hamlib_Amp_class.py ..
python/test_Hamlib_Rig_class.py ..
python/test_Hamlib_Rot_class.py ..
python/test_Hamlib_class.py ..
python/test_amp.py ...
python/test_rig.py ....
python/test_rot.py ...
python/test_startup.py .
============================================================ 19 passed in 2.87s ============================================================
cp ./pkgIndex.tcl ./.libs
TCLLIBPATH=./.libs tclsh ./tcltest.tcl
make[3]: *** [Makefile:1183: check-tcl] Segmentation fault (core dumped)
make[3]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make[2]: *** [Makefile:947: check-am] Error 2
make[2]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make[1]: *** [Makefile:949: check] Error 2
make[1]: Leaving directory '/home/bdm/rpmbuild/BUILD/hamlib-4.7_git-build/hamlib-4.7~git/bindings'
make: *** [Makefile:672: check-recursive] Error 1
error: Bad exit status from /home/bdm/rpmbuild/tmp/rpm-tmp.JwA7ey (%check)
RPM build errors:
Bad exit status from /home/bdm/rpmbuild/tmp/rpm-tmp.JwA7ey (%check)
As you can see this is in the make check-TESTS section of the .spec
file however all of this was working with previous 4.7~git snapshots.
Anything that makes any sense to you?
I may have another try as the latest Fedora 42 src rpm might work
better.
--
Brian G8SEZ
|
|
From: Nate B. <n0...@n0...> - 2025-08-31 13:50:41
|
* On 2025 30 Aug 11:31 -0500, Uwe, DG2YCB via Hamlib-developer wrote: > Dear Hamlib developers, > > In about two weeks from now, a new 3.0.0-rc1 version of both WSJT-X and > WSJT-X Improved is planned. My question is: which Hamlib version can you > recommend? > > It should already have a driver for the Yaesu FTX-1, but has to be stable > enough, of course. Does only the current 4.7 development version support the > Yaesu FTX-1? Or is there already a 4.6.x version that includes this? Or do > you want to release a new one in time for that? Thanks. As you want the FTX-1, then a snapshot of 4.7~git will be your choice. I will be releasing 4.6.5 this week but it only pertains to a couple of segfault fixes and has no support for the FTX-1. Of course, those fixes have been applied to 4.7~git as well. I think the run-time stability of 4.7~git is as good as any prior release right now and has received a lot of fixes over the past couple of months. As we'd like to release 4.7.0 sometime in the next couple of months or so, the ABI will not change so when it is released, current versions of applications should work with the resulting .so/.DLL. Expect ABI changes after the 4.7 branch is created as work will commence toward 5.0. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: Uwe, D. <dg...@gm...> - 2025-08-30 16:31:38
|
Dear Hamlib developers, In about two weeks from now, a new 3.0.0-rc1 version of both WSJT-X and WSJT-X Improved is planned. My question is: which Hamlib version can you recommend? It should already have a driver for the Yaesu FTX-1, but has to be stable enough, of course. Does only the current 4.7 development version support the Yaesu FTX-1? Or is there already a 4.6.x version that includes this? Or do you want to release a new one in time for that? Thanks. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg...@gm... Info: www.qrz.com/db/DG2YCB |
|
From: Nate B. <n0...@n0...> - 2025-08-30 16:21:45
|
Just a note that I'm working the Kansas QSO Party this weekend so probably won't be acting on PRs and issues until late Sunday. 73, Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: Nate B. <no...@gi...> - 2025-08-24 22:24:49
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 06a2a25cb71b50b0ddac6ce0770846373455e6df https://github.com/Hamlib/Hamlib/commit/06a2a25cb71b50b0ddac6ce0770846373455e6df Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M tests/rigmem.c Log Message: ----------- Remove misleading duplicated error message The correct error message has been printed by getopt_long() before returning. Test cases: $ rigmem -Q rigmem: invalid option -- 'Q' Unknown option '?' Usage: rigmem [OPTION]... COMMAND... FILE ... $ rigmem --foo rigmem: unrecognized option '--foo' Unknown option '?' Usage: rigmem [OPTION]... COMMAND... FILE ... Commit: 0a06af1ddef5e56593276e9c4bd069741a487f80 https://github.com/Hamlib/Hamlib/commit/0a06af1ddef5e56593276e9c4bd069741a487f80 Author: Nate Bargmann <n0...@n0...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M tests/rigmem.c Log Message: ----------- Merge GitHub PR #1867 Compare: https://github.com/Hamlib/Hamlib/compare/233282671325...0a06af1ddef5 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-24 22:15:30
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 6a700023abdec3c7ae021d7dc981b0cd5d5dbd29 https://github.com/Hamlib/Hamlib/commit/6a700023abdec3c7ae021d7dc981b0cd5d5dbd29 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-23 (Sat, 23 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Remove duplicated custom debug output It has several issues: * these are trace messages so RIG_DEBUG_ERR is inappropriate * they are in a custom format which doesn't handle end of line chars * write_block() and read_string() print the same information when debug level is set to TRACE Commit: f4d4d855b928c11b03552acabd3f60e798f0d98f https://github.com/Hamlib/Hamlib/commit/f4d4d855b928c11b03552acabd3f60e798f0d98f Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-23 (Sat, 23 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Show the error code and the failure count in debug messages Commit: 05a9034d2e94df1c901377927b2dfa52f5454ac3 https://github.com/Hamlib/Hamlib/commit/05a9034d2e94df1c901377927b2dfa52f5454ac3 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-23 (Sat, 23 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Reduce severity of some debug messages from ERR to TRACE They do not depend on an error situation. Commit: 5acd75fecc111458f5816b560099c626cc568274 https://github.com/Hamlib/Hamlib/commit/5acd75fecc111458f5816b560099c626cc568274 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-23 (Sat, 23 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Remove code that only prints debug messages and add new debug messages Commit: 7fdbc999110ef1fa983d202d21c61f939742dfbc https://github.com/Hamlib/Hamlib/commit/7fdbc999110ef1fa983d202d21c61f939742dfbc Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-23 (Sat, 23 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Return the error code from grbl_init() Commit: feef144bb85d4d2a737d1c351c5ffc2adffa35a9 https://github.com/Hamlib/Hamlib/commit/feef144bb85d4d2a737d1c351c5ffc2adffa35a9 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-23 (Sat, 23 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Propagate the actual error code from grbl_request() Instead of overridng first with -RIG_EPROTO then with -RIG_EIO. Commit: 233282671325283b64518bae98282c62fde618db https://github.com/Hamlib/Hamlib/commit/233282671325283b64518bae98282c62fde618db Author: Nate Bargmann <n0...@n0...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M rotators/grbltrk/grbltrk.c Log Message: ----------- Merge GitHub PR #1866 Compare: https://github.com/Hamlib/Hamlib/compare/4340198076ea...233282671325 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-24 21:20:09
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 1194125b3d58170f3bd32a1d1b8e0c47ba614650 https://github.com/Hamlib/Hamlib/commit/1194125b3d58170f3bd32a1d1b8e0c47ba614650 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M tests/ampctl_parse.c Log Message: ----------- Remove unused code, apparently copied from rotctl_parse.c and modified Commit: b5db8e3200cc59651bf2e2e2eee186671b21f564 https://github.com/Hamlib/Hamlib/commit/b5db8e3200cc59651bf2e2e2eee186671b21f564 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M tests/.gitignore M tests/Makefile.am Log Message: ----------- Add conditionally generated file to .gitignore and CLEANFILES No need to add it *conditionally* to CLEANFILES because for make it isn't an error trying to delete a file that doesn't exist. Commit: 844bd8eba8c3efd06e90e3b8157b1295d8bde9a2 https://github.com/Hamlib/Hamlib/commit/844bd8eba8c3efd06e90e3b8157b1295d8bde9a2 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M tests/Makefile.am Log Message: ----------- Remove unneeded dependencies make knows how to build an executable from a single C source file Commit: 5ba906c9aaf532c3d4817ab01ba027f2c9dc58fc https://github.com/Hamlib/Hamlib/commit/5ba906c9aaf532c3d4817ab01ba027f2c9dc58fc Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M tests/Makefile.am Log Message: ----------- Document building testsecurity At some time, the commented out line check_PROGRAMS removed by this commit was identical to the line following it, plus testsecurity appended, then they went out of sync. The commented out line check_PROGRAMS added by this commit appends testsecurity in an explicit way. Commit: bc8dbca1f3a06de5faa69cd96f7b4e6c5819ac34 https://github.com/Hamlib/Hamlib/commit/bc8dbca1f3a06de5faa69cd96f7b4e6c5819ac34 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M tests/dumpcaps.c M tests/dumpstate.c Log Message: ----------- Remove duplicated rig_type[] lines Commit: 4340198076ea9f0e65e34356fef3a82d8c3583e9 https://github.com/Hamlib/Hamlib/commit/4340198076ea9f0e65e34356fef3a82d8c3583e9 Author: Nate Bargmann <n0...@n0...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M tests/.gitignore M tests/Makefile.am M tests/ampctl_parse.c M tests/dumpcaps.c M tests/dumpstate.c Log Message: ----------- Merge GitHub PR #1865 Compare: https://github.com/Hamlib/Hamlib/compare/17cb45f2f042...4340198076ea To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-24 20:52:52
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: ee7c0c323503d7dc95bf10744a4fc2e0dfbe4edf https://github.com/Hamlib/Hamlib/commit/ee7c0c323503d7dc95bf10744a4fc2e0dfbe4edf Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Make a C++11 compiler mandatory if INDI or C++ binding are requested Otherwise make it optional. Fixes issue #1730. Commit: 7dc8462b20f597184bd942569b50cdad03977f6f https://github.com/Hamlib/Hamlib/commit/7dc8462b20f597184bd942569b50cdad03977f6f Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Add missing AC_MSG_RESULT Commit: 3b2df4ecd0ce49311f75612c56de78349ff24e35 https://github.com/Hamlib/Hamlib/commit/3b2df4ecd0ce49311f75612c56de78349ff24e35 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Fix detecting the availability of a C++ compiler that needs arguments If the earlier macro AC_PROG_CXX found a compiler that needs some arguments, the variable CXX will contain also the arguments, so the macro AC_CHECK_PROG will try to find a file that doesn't exist (such as "g++ -std=gnu++11" instead of just "g++"). If AC_PROG_CXX didn't find a compiler, the variable CXX is empty. Commit: e772d6481ef7d016a687ae6f57a26d1087543ae1 https://github.com/Hamlib/Hamlib/commit/e772d6481ef7d016a687ae6f57a26d1087543ae1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Fix usage of AS_IF Needs one set of square brackets for the true case and one sert for false case. Commit: cb6866ff8650b266f2fa8d4554b5de51d6cdba35 https://github.com/Hamlib/Hamlib/commit/cb6866ff8650b266f2fa8d4554b5de51d6cdba35 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-22 (Fri, 22 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Fix detecting functional C++11 compilers Allows to build Hamlib when a C++ compiler isn't available, by running: ./configure --without-indi --without-cxx-binding Commit: 8febac180a6f98900ccb5d2c2cffd12ba46886f9 https://github.com/Hamlib/Hamlib/commit/8febac180a6f98900ccb5d2c2cffd12ba46886f9 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-22 (Fri, 22 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Fix typo Commit: b300747aa228d42740a76e6d6d3418ae2be7ec51 https://github.com/Hamlib/Hamlib/commit/b300747aa228d42740a76e6d6d3418ae2be7ec51 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Fix comment and messages Looks like they were copied from the texts for readline. Commit: 91e5f1441f43f638a0698fe037a4127ea6a11493 https://github.com/Hamlib/Hamlib/commit/91e5f1441f43f638a0698fe037a4127ea6a11493 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M configure.ac Log Message: ----------- If neither yes or no were given, build INDI only if prerequisites are met Options availables are: ./configure # same as --with-indi=detect ./configure --with-indi=detect # build if prerequisites are met ./configure --with-indi=no # do not build ./configure --without-indi # do not build ./configure --with-indi=yes # fail if prerequisites aren't met Commit: e81e40ed70062765ad21a6eadfd5cb4753722165 https://github.com/Hamlib/Hamlib/commit/e81e40ed70062765ad21a6eadfd5cb4753722165 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M configure.ac Log Message: ----------- If neither yes or no were given, build C++ binding only if prerequisites are met Options availables are: ./configure # same as --with-cxx-binding=detect ./configure --with-cxx-binding=detect # build if prerequisites are met ./configure --with-cxx-binding=no # do not build ./configure --without-cxx-binding # do not build ./configure --with-cxx-binding=yes # fail if prerequisites aren't met Commit: 43d9b3d35487a5344b3eca6df2398a356f7451a2 https://github.com/Hamlib/Hamlib/commit/43d9b3d35487a5344b3eca6df2398a356f7451a2 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M configure.ac Log Message: ----------- If --with-indi[=yes] was given, error out if prerequisites aren't met Error out also if libnova or libindi are missing, not just if a C++11 compiler is missing. Commit: a0792e4f85833f499daf007f7e5fef8302494ec9 https://github.com/Hamlib/Hamlib/commit/a0792e4f85833f499daf007f7e5fef8302494ec9 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M .github/workflows/c-cpp.yml Log Message: ----------- Excercise the detect logic for INDI on the macOS CI libnova is available in brew, but libindi isn't available; ./configure will detect that and not build the INDI driver. Commit: d66a601c8395178bf02955a0f99b42180438701b https://github.com/Hamlib/Hamlib/commit/d66a601c8395178bf02955a0f99b42180438701b Author: Nate Bargmann <n0...@n0...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M configure.ac Log Message: ----------- Fix typo in digraph Commit: 17cb45f2f0424bff46dc0ac26d93543a2781136e https://github.com/Hamlib/Hamlib/commit/17cb45f2f0424bff46dc0ac26d93543a2781136e Author: Nate Bargmann <n0...@n0...> Date: 2025-08-24 (Sun, 24 Aug 2025) Changed paths: M .github/workflows/c-cpp.yml M configure.ac Log Message: ----------- Merge GitHub PR #1862 Compare: https://github.com/Hamlib/Hamlib/compare/ad8707c74cea...17cb45f2f042 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-22 20:49:34
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 6eb7c1d6dd24f77b8232bca83f90eecaa18e2711 https://github.com/Hamlib/Hamlib/commit/6eb7c1d6dd24f77b8232bca83f90eecaa18e2711 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-22 (Fri, 22 Aug 2025) Changed paths: M bindings/rig.swg Log Message: ----------- Fix build failure on openSUSE Tumbleweed, Slowroll and Leap 16.0 Thanks to @dl8fcl Walter. Commit: ad8707c74cea2bea661ffd1a187db36dc269e06c https://github.com/Hamlib/Hamlib/commit/ad8707c74cea2bea661ffd1a187db36dc269e06c Author: Nate Bargmann <n0...@n0...> Date: 2025-08-22 (Fri, 22 Aug 2025) Changed paths: M bindings/rig.swg Log Message: ----------- Merge GitHub PR #1864 Compare: https://github.com/Hamlib/Hamlib/compare/b953141b0f53...ad8707c74cea To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <n0...@n0...> - 2025-08-22 17:59:51
|
* On 2025 22 Aug 12:19 -0500, Walter Fey wrote: > This commit is breaking the build on openSUSE Tumbleweed, Slowroll and the upcomming Leap 16.0. Leap 15.6 is not affected. > This patch is solving the build problem, but I do not know, if it is working correctly. Thanks, Walter. If Daniele approves it, I'll get it committed. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 |
|
From: Michael M. <no...@gi...> - 2025-08-22 11:30:52
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: b953141b0f538f21cc696c2a1b874c311f3154c5 https://github.com/Hamlib/Hamlib/commit/b953141b0f538f21cc696c2a1b874c311f3154c5 Author: aa5sh <844...@us...> Date: 2025-08-21 (Thu, 21 Aug 2025) Changed paths: M rigs/yaesu/ftx1.h M rigs/yaesu/newcat.c Log Message: ----------- Bug Fixes for FTX1 Needed to adjust one of the timeouts. Was causing issues on Windows. Also made some changes due to IF command response size being 30, it was erroring out. And last band mapping was a little different on this rig for 2m, 70cm, 4m and Air Band. To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Daniele F. <iu...@gm...> - 2025-08-21 11:49:20
|
I agree that it would be nice to compile only what is needed, however ordinary users should prefer using packages from distributions, while I argue that experimenters that want to use SOCs should cross-compile. For the time needed to compile, on my 13 years old PC it takes less than 1 minute to compile the library only (make -j12 src), it takes me much longer to write this email :-( An "interesting project" if I can somehow pass just the model number(s) and have compiled only those, otherwise choosing what to compile risks to become similar to Linux kbuild (nice the first time, then a pain): there are 36 brands of rigs, 26 of rotators and 3 of amplifiers, 317 rigs, 57 rotators, 5 amplifiers. -- 73 de IU5HKX Daniele |
|
From: Daniele F. <iu...@gm...> - 2025-08-21 11:29:09
|
George Baltz wrote:
> I think the first half of this is done - rig_open() builds a list of
> opened rig_structs, but nobody checks it on each rig_*() call. Overhead
> problem?
maby, but there is already some overhead because many (all?) functions
use the macro
#define CHECK_RIG_ARG(r) (!(r) || !(r)->caps || !STATE((r))->comm_state)
in some cases the last macro check is equivalent to checking if the
rig is in the list because rig_close() calls remove_opened_rig(rig);
and sets rs->comm_state = 0;
So comm_state is certainly zero when the struct is not in the list (it
may be zero even when the rig is in the list but it is a different
case).
rig_close is like this:
int HAMLIB_API rig_close(RIG *rig)
{
[...]
if (!rs->comm_state)
{
RETURNFUNC(-RIG_EINVAL);
}
remove_opened_rig(rig);
[...]
rs->comm_state = 0;
[...]
}
However issue #785 talked about memory corruption (so that even
comm_state may appear non-zero when the rig is no more in the list and
what I have written above doesn't hold).
I'm not sure if this issue #807 still covers the memory corruption,
but I don't think that protecting against this kind of memory
corruption is worth our time when there are many fixed length buffers
and suspicious uses of sprintf-like functions.
This list of open rigs could be useful if rigctld gets the ability to
handle more than one rig at a time, but it would add extra complexity
to clients, that in some cases can be avoided running more copies of
rigctld on different ports.
If everybody agrees that it is a rare case not worth protecting
against, that memory corruption affects only a rig pointer and not
other important data or the stack, can we close this?
--
73 de IU5HKX Daniele
|
|
From: dforsi <no...@gi...> - 2025-08-21 03:16:52
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 0317e64dc83f9b0b3999d2c98df67608e4fa960e https://github.com/Hamlib/Hamlib/commit/0317e64dc83f9b0b3999d2c98df67608e4fa960e Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-20 (Wed, 20 Aug 2025) Changed paths: M tests/rigctl_parse.c M tests/rotctl_parse.c Log Message: ----------- Remove double call to rig_token_lookup() and rot_token_lookup() The needed value is already in the variable. Test case /to check that the changes don't break the code): tests/rigctl --set-conf=rig_pathname=test,write_delay=1,timeout=2 --show-conf Q | grep --no-group-separator -A1 -E "(rig_pathname|^write_delay|^timeout):" tests/rotctl --set-conf=rot_pathname=test,write_delay=1,timeout=2 --show-conf Q | grep --no-group-separator -A1 -E "(rot_pathname|^write_delay|^timeout):" The output before and after this patch is: rig_pathname: "Path name to the device file of the rig" Default: /dev/rig, Value: test write_delay: "Delay in ms between each byte sent out" Default: 0, Value: 1 timeout: "Timeout in ms" Default: 0, Value: 2 Command 'Q' not found! rot_pathname: "Path name to the device file of the rotator" Default: /dev/rotator, Value: test write_delay: "Delay in ms between each byte sent out" Default: 0, Value: 1 timeout: "Timeout in ms" Default: 0, Value: 2 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-20 18:20:26
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 8847cbeafb1cfdebcad62e9f3eaeab1980a15040 https://github.com/Hamlib/Hamlib/commit/8847cbeafb1cfdebcad62e9f3eaeab1980a15040 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-20 (Wed, 20 Aug 2025) Changed paths: M bindings/perltest.pl M bindings/rig.swg Log Message: ----------- Implement send_raw for the Perl bindings Doesn't allow '\0' embedded in the strings to be sent or received. Closes #1479. Commit: 32d064d60ba6ae732fc7b1c590ae91296b9e1217 https://github.com/Hamlib/Hamlib/commit/32d064d60ba6ae732fc7b1c590ae91296b9e1217 Author: Nate Bargmann <n0...@n0...> Date: 2025-08-20 (Wed, 20 Aug 2025) Changed paths: M bindings/perltest.pl M bindings/rig.swg Log Message: ----------- Merge GitHub PR #1860 Compare: https://github.com/Hamlib/Hamlib/compare/cbefd0835f52...32d064d60ba6 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: dforsi <no...@gi...> - 2025-08-20 17:59:51
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: ead67ec17005f5aa2790d429dd72a39c9dead7e1 https://github.com/Hamlib/Hamlib/commit/ead67ec17005f5aa2790d429dd72a39c9dead7e1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-20 (Wed, 20 Aug 2025) Changed paths: M tests/ampctl.c M tests/ampctld.c M tests/rigctl.c M tests/rigmem.c M tests/rigsmtr.c M tests/rigswr.c M tests/rotctl.c M tests/rotctld.c Log Message: ----------- Replace magic number with define Commit: 5a001ab3aa31b7d2458f54d998f3281f9bf5cb13 https://github.com/Hamlib/Hamlib/commit/5a001ab3aa31b7d2458f54d998f3281f9bf5cb13 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-20 (Wed, 20 Aug 2025) Changed paths: M tests/rigctlcom.c M tests/rigctld.c M tests/rigctlsync.c M tests/rigctltcp.c Log Message: ----------- Explicitely initialize static int verbose Commit: cbefd0835f5284509d5b32b1f50251aa2c3f82f3 https://github.com/Hamlib/Hamlib/commit/cbefd0835f5284509d5b32b1f50251aa2c3f82f3 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-20 (Wed, 20 Aug 2025) Changed paths: M tests/ampctl.c M tests/ampctld.c M tests/rigctl.c M tests/rigctlcom.c M tests/rigctld.c M tests/rigctlsync.c M tests/rigctltcp.c M tests/rigmem.c M tests/rigsmtr.c M tests/rigswr.c M tests/rotctl.c M tests/rotctld.c Log Message: ----------- Do not show any debug trace messages unless requested with -vvvvv This fixes the following commands that always printed debug messages at the trace level: tests/ampctld -l >/dev/null tests/ampctl -h >/dev/null tests/rigctld -l >/dev/null tests/rigctltcp -l >/dev/null tests/rotctld -l >/dev/null It doesn't affect other software which worked around this issue, but changes all software to avoid regressions in future. Test case (should print nothing in bash): { tests/ampctl -l -h tests/ampctld -l -h tests/rigctl -l -h tests/rigctlcom -l -h tests/rigctld -l -h tests/rigctlsync -l -h tests/rigctltcp -l -h tests/rotctl -l -h tests/rotctld -l -h } >/dev/null Compare: https://github.com/Hamlib/Hamlib/compare/d6165f74115a...cbefd0835f52 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-20 01:44:21
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 7a9e101b9d81e341f9d4a7cbb11f286fe5b1a45c https://github.com/Hamlib/Hamlib/commit/7a9e101b9d81e341f9d4a7cbb11f286fe5b1a45c Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M src/misc.c Log Message: ----------- Add missing string form for RIG_FUNC_SLICE Commit: d6165f74115aa4794ebacc7d775477eaacd02445 https://github.com/Hamlib/Hamlib/commit/d6165f74115aa4794ebacc7d775477eaacd02445 Author: Nate Bargmann <n0...@n0...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M src/misc.c Log Message: ----------- Merge GitHub PR #1859 Compare: https://github.com/Hamlib/Hamlib/compare/db7219b731e8...d6165f74115a To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
|
From: Nate B. <no...@gi...> - 2025-08-20 01:19:43
|
Branch: refs/heads/master Home: https://github.com/Hamlib/Hamlib Commit: 7fce140970f93569b68af6dbe5e18b1092633d63 https://github.com/Hamlib/Hamlib/commit/7fce140970f93569b68af6dbe5e18b1092633d63 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M tests/ampctl.c M tests/ampctld.c M tests/rigctlcom.c M tests/rigctld.c M tests/rigctlsync.c M tests/rigctltcp.c M tests/rigmem.c Log Message: ----------- Make help texts more similar Commit: 67038154db238bec7b51cc66417665c9ee828918 https://github.com/Hamlib/Hamlib/commit/67038154db238bec7b51cc66417665c9ee828918 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M tests/rigctl.c M tests/rigctl_parse.c M tests/rigctld.c M tests/rigctltcp.c Log Message: ----------- Refactor to remove code duplication in rigctl*.c Commit: 90ffcadfa516176e26275b680baa68a689bd5dc1 https://github.com/Hamlib/Hamlib/commit/90ffcadfa516176e26275b680baa68a689bd5dc1 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M tests/ampctl.c M tests/ampctl_parse.c M tests/ampctld.c Log Message: ----------- Refactor to remove code duplication in ampctl*.c Commit: a0fa2def82abd321aa547e1f7ba5cf7417dfe359 https://github.com/Hamlib/Hamlib/commit/a0fa2def82abd321aa547e1f7ba5cf7417dfe359 Author: Daniele Forsi IU5HKX <iu...@gm...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M tests/rotctl.c M tests/rotctl_parse.c M tests/rotctld.c Log Message: ----------- Refactor to remove code duplication in rotctl*.c Commit: db7219b731e8c4f68e54a05e7ed4248c6a59c239 https://github.com/Hamlib/Hamlib/commit/db7219b731e8c4f68e54a05e7ed4248c6a59c239 Author: Nate Bargmann <n0...@n0...> Date: 2025-08-19 (Tue, 19 Aug 2025) Changed paths: M tests/ampctl.c M tests/ampctl_parse.c M tests/ampctld.c M tests/rigctl.c M tests/rigctl_parse.c M tests/rigctlcom.c M tests/rigctld.c M tests/rigctlsync.c M tests/rigctltcp.c M tests/rigmem.c M tests/rotctl.c M tests/rotctl_parse.c M tests/rotctld.c Log Message: ----------- Merge GitHub PR #1858 Compare: https://github.com/Hamlib/Hamlib/compare/285b44add695...db7219b731e8 To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications |
33 messages has been excluded from this view by a project administrator.
