Will

> > Abbreviated error logs from meson-log.txt > > The full error logs as an attachment would be elucidative here, I think. It would include the exact compiler command line...

> ``` > c++ sanitycheckcpp.cc -o sanitycheckcpp.exe > ``` > > If you run this, is the resulting executable supposed to be functional? The above command does not produce runnable...

> Sure, and I'm just trying to reduce the problem in order to better understand what the the scenario is. TYVM and apologies if I came off as hostile --...

> with 1.4.0 (Via a virtualenv + pip install of meson 1.4.0)

> The sanitycheck was passing just a couple months ago By "a couple months ago" I mean that it was passing while I was developing [this project](https://github.com/e-dant/watcher/tree/next/watcher-py) for a python+c+cpp...

libbpf-tools version: `Version: 0.26.0+ds-1` (via apt) ``` $ uname -v #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) ``` Stuff from os-release ``` NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" ```

I'm not sure which headers are being used. They're from whatever Debian is packaging -- I didn't compile this program If time allows I can see if things work as...

The current master branch doesn't have this issue (`git pull && cd libbpf-tools && make && sudo ./tcprtt -a 192.168.1.1` works ok) Is this a Debian packaging issue?

Apologies beforehand -- I haven't included a code sample because the top-level issue is a crate up in my dependency tree (so I didn't have one handy at the time...

FWIW One way to do this on non-Linux platforms is with the IP_BOUND_IF (and v6 variant) with whatever the index, from if_nametoindex, happens to be. (Scope ids seem to be...