Debian Patches
Status for m2crypto/0.46.2-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 64-bit-time_t-on-32-bit.patch | fix: allow 64-bit time_t on 32-bit systems in test_is32bit Some modern 32-bit Linux systems (e.g. with glibc >= 2.34 or musl time64 ABI) use 64-bit time_t by default when _TIME_BITS=64 is enabled. The original test assumed time_t was always 32-bit on 32-bit architectures, which is no longer true. Relax the check to accept both 32-bit and 64-bit time_t values: self.assertIn(bit32, (32, 64)) This makes the test compatible with both legacy and time64 ABIs. |
Haixiao Yan <haixiao.yan.cn@windriver.com> | no | debian | upstream, https://git.sr.ht/~mcepl/m2crypto/commit/818c3dfda6ea1b71d7573eb18a86848b22ef2421 | 2026-01-12 |
| correct-struct-packing-on-32-bit.patch | fix: correct struct packing on 32-bit with _TIME_BITS=64 On 32-bit platforms with glibc time64 ABI, time_t is 64-bit wide while `long` remains 32-bit. This causes struct timeval to use two 64-bit fields (tv_sec, tv_usec). The previous code incorrectly packed timeout as "ll", leading to EINVAL in setsockopt(SO_RCVTIMEO). Use "qq" instead when m2.time_t_bits() == 64 to match the actual ABI. |
Haixiao Yan <haixiao.yan.cn@windriver.com> | no | debian | upstream, 473de659f78ead055de7720c191479143c1567ed | 2025-10-22 |