On Thu, Nov 5, 2026 at 2:30 AM Miao Wang <[email protected]> wrote: > > Hi, > > I believe the root cause is that socket-wrapper tries to wrap around > glibc symbols but fails to provide symbols for both the 32-bit time > ABI and 64-bit time ABI as glibc does. In the code of socket-wrapper > we can see the compatibility for LFS64 ABI has already been integrated. > In [1] I proposed a patch series to add the compatibility to both > time abis, and in the same time add tests for both abis, to ensure > that the compiled library can correctly intercept calls to libc > functions from executables in both ABIs. > > I have tested my patch on: > > - arm64 trixie, as a smoke test; > - armhf trixie, to test on t64 ABI systems; > - armhf bookworm, to test on t32 ABI systems with t64 support > - armhf bullseye, to test on t32 ABI systems without t64 support > - i386 trixie, to test on t32 ABI systems with t64 support > > Cheers, > > Miao Wang > > [1]: > https://salsa.debian.org/shankerwangmiao/socket-wrapper/-/commits/pr-time64 >
I gave this patch a try with the reported failed version of ocserv and the relevant test cases are passing. Regards, Aron
