@d-e-s-o @ work

The main problem, I suspect, will be that the moment anything looking like a thread is involved there is a requirement for data to be `'static`. For us, I believe,...

> The main problem, I suspect, will be that the moment anything looking like a thread is involved there is a requirement for data to be `'static`. Well, that's not...

For what it's worth, I got some basic "runtime"/scheduler scaffolding coded up over in https://github.com/d-e-s-o/blazesym/tree/topic/threading. So in principle we could start using it. The "problem" is that right now I...

Would be best if you could share a sample project and build invocation. Perhaps we have to introduce a variant of this variable to be used in a cross compilation...

> I have made a minimal reproduction repo based on the capable example: https://github.com/kxxt/libbpf-sys-106-repro Okay, thanks for this, that's tremendously useful. I finally got the error reproduced. > But the...

Yeah, so if I adjust your script as follows: ```diff --- build-aarch64.sh +++ build-aarch64.sh @@ -1,6 +1,8 @@ #!/bin/sh -export LIBBPF_SYS_LIBRARY_PATH="$(realpath 3rdparty/aarch64/usr/lib/aarch64-linux-gnu)" -export LIBBPF_SYS_EXTRA_CFLAGS="-I $(realpath 3rdparty/aarch64/usr/include)" +export LIBBPF_SYS_LIBRARY_PATH_x86_64="$(realpath 3rdparty/x86_64/usr/lib/x86_64-linux-gnu)" +export...

Likely the next problem we hit will be that, in the above scenario, the skeleton will be created for x86, it seems. Which makes sense, because the build script is...

Have you gotten it to work end-to-end, @kxxt ? If so, feel free to open a pull request.

I think this lint has a [false positive](https://github.com/libbpf/blazesym/actions/runs/10724198163/job/29739299322#step:4:576) ``` error: can be more succinctly written as a byte str --> src/symbolize/perf_map.rs:381:58 | 381 | let () = child.stdin.as_ref().unwrap().write_all(&[b'\n']).unwrap(); | ^^^^^^^^...

Ah my bad. Sorry for the noise then.