---
- branch: MAIN
  date: Fri Oct  7 20:22:57 UTC 2022
  files:
  - new: '1.41'
    old: '1.40'
    path: pkgsrc/sysutils/rsyslog/distinfo
    pathrev: pkgsrc/sysutils/rsyslog/distinfo@1.41
    type: modified
  - new: '1.5'
    old: '1.4'
    path: pkgsrc/sysutils/rsyslog/patches/patch-configure
    pathrev: pkgsrc/sysutils/rsyslog/patches/patch-configure@1.5
    type: modified
  - new: '1.1'
    old: '0'
    path: pkgsrc/sysutils/rsyslog/patches/patch-m4_atomic__operations.m4
    pathrev: pkgsrc/sysutils/rsyslog/patches/patch-m4_atomic__operations.m4@1.1
    type: added
  id: 20221007T202257Z.fbd19b0c89c0813e1b15aa94bf38c14d363d6793
  log: |
    sysutils/rsyslog: also test for atomic ops on time_t.

    This is to cater to 32-bit NetBSD ports, where time_t is also
    (and has been for a long time) __int64_t.  Without this check,
    __sync_bool_compare_and_swap_8 would end up being undefined when
    linking rsyslog, since the compiler isn't obliged to supply that.
    This causes the pthread / locking variant to be chosen on these
    systems, but makes rsyslog build, at least.

    (An earlier attempt at doing this only for time_t was met with
    complications and was therefore abandoned.)

    There's also just a single use of ATOMIC_CAS_time_t() in rsyslog...

    Submitted upstream in
      https://github.com/rsyslog/rsyslog/pull/4994
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/sysutils/rsyslog'
  unixtime: '1665174177'
  user: he