Re: [PATCH bpf-next v1 6/8] selftests/bpf: Fix compile if backtrace support missing in libc

On Fri, Jul 26, 2024 at 8:48 PM Tony Ambardar wrote: > > On Thu, Jul 25, 2024 at 01:22:37PM -0700, Andrii Nakryiko wrote: > > On Thu, Jul 25, 2024 at 3:39 AM Tony Ambardar > > wrote: > > > > > > From: Tony Ambardar > > > > > > Use backtrace functions only with glibc and otherwise provide stubs

Re: [PATCH bpf-next v1 6/8] selftests/bpf: Fix compile if backtrace support missing in libc

On Thu, Jul 25, 2024 at 01:22:37PM -0700, Andrii Nakryiko wrote: > On Thu, Jul 25, 2024 at 3:39 AM Tony Ambardar wrote: > > > > From: Tony Ambardar > > > > Use backtrace functions only with glibc and otherwise provide stubs in > > test_progs.c. This avoids compile errors (e.g. with musl libc) lik

Re: [PATCH bpf-next v1 6/8] selftests/bpf: Fix compile if backtrace support missing in libc

On Thu, Jul 25, 2024 at 3:39 AM Tony Ambardar wrote: > > From: Tony Ambardar > > Use backtrace functions only with glibc and otherwise provide stubs in > test_progs.c. This avoids compile errors (e.g. with musl libc) like: > > test_progs.c:13:10: fatal error: execinfo.h: No such file or directo

[PATCH bpf-next v1 6/8] selftests/bpf: Fix compile if backtrace support missing in libc

From: Tony Ambardar Use backtrace functions only with glibc and otherwise provide stubs in test_progs.c. This avoids compile errors (e.g. with musl libc) like: test_progs.c:13:10: fatal error: execinfo.h: No such file or directory 13 | #include /* backtrace */ | ^~~~