[Hamlib-developer] [Hamlib/Hamlib] 3a84b2: Fix errors found by glibc 2.43

[Nate B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.7
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 3a84b2dd29aa333076ae2fb833c2db74fe607e4b
      https://github.com/Hamlib/Hamlib/commit/3a84b2dd29aa333076ae2fb833c2db74fe607e4b
  Author: George Baltz N3GB <Geo...@gm...>
  Date:   2026-05-06 (Wed, 06 May 2026)

  Changed paths:
    M tests/ampctl_parse.c
    M tests/rigctl_parse.c
    M tests/rotctl_parse.c

  Log Message:
  -----------
  Fix errors found by glibc 2.43

glibc implements some new parts of the C23 standard:
(Taken from https://download.opensuse.org/tumbleweed/iso/Changes.20260430.txt)

  * For ISO C23, the functions bsearch, memchr, strchr, strpbrk, strrchr,
    strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr that return
    pointers into their input arrays now have definitions as macros that
    return a pointer to a const-qualified type when the input argument is
    a pointer to a const-qualified type

and

  * The aforementioned change in ISO C23 of the declaration of bsearch,
    memchr, strchr, strpbrk, strrchr, strstr, wcschr, wcspbrk, wcsrchr,
    wcsstr, and wmemchr as const-preserving macros can lead to compilation
    issues in code not set up for it

This lead to some warnings about assigning returns from strchr(const, target)
  to non-const pointers, and then discovering that Hamlib was modifying
  those const parameters.

This commit aligns the const-ness of the offending parameters. Only affects
  internal functions in ampctl_parse.c, rigctl_parse.c and rotctl_parse.c,
  so API/ABI should not change.

(cherry picked from commit 7df5ae1a00a93aa798865e594ba26f3e838ce369)


  Commit: 99d55f3c9d2a7dae252eb2ef89fcc422a5a30683
      https://github.com/Hamlib/Hamlib/commit/99d55f3c9d2a7dae252eb2ef89fcc422a5a30683
  Author: Jeff Sheldon <jef...@gm...>
  Date:   2026-05-06 (Wed, 06 May 2026)

  Changed paths:
    M rigs/alinco/dxsr8.c

  Log Message:
  -----------
  alinco/dxsr8: fix serial configuration, timing, and control bugs

- serial_stop_bits corrected from 1 to 2 per protocol documentation;
  incorrect stop bits caused systematic transaction timing errors
- post_write_delay increased from 0 to 100ms to allow radio processing
  time between commands
- timeout increased from 200ms to 600ms to accommodate slower responses
- retry reduced from 3 to 1 to prevent command flooding on failure
- DXSR8_LEVEL_ALL advertised RIG_LEVEL_RF but implemented ATT and
  PREAMP; corrected capability flags accordingly
- set_mode NAR command acknowledgment timeout treated as non-fatal;
  radio executes the command correctly but does not reliably return
  OK within the timeout window — logs WARN instead of propagating error
- get_mode RR_NAR query removed; radio does not respond reliably
  causing systematic timeouts — normal passband returned always
- get_level ATT case 2 returned 10 instead of 20 (copy-paste error)
- get_level RFPOWER case 3 never matched radio response of 2,
  leaving val->f uninitialized in QRP mode

(cherry picked from commit b8eee851dcc13024185c5a6ea73e625850912b0e)


  Commit: 1dafaa748082b44b2a204d0db2f410e4a3524a12
      https://github.com/Hamlib/Hamlib/commit/1dafaa748082b44b2a204d0db2f410e4a3524a12
  Author: Nate Bargmann <n0...@n0...>
  Date:   2026-05-06 (Wed, 06 May 2026)

  Changed paths:
    M NEWS

  Log Message:
  -----------
  Update NEWS for C23 and DX-SR8 fixes


Compare: https://github.com/Hamlib/Hamlib/compare/837e1ff82e8d...1dafaa748082

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications