On Tue, Sep 6, 2022 at 3:16 PM Domenico Andreoli <ca...@debian.org> wrote: > > On Tue, Sep 06, 2022 at 10:47:44AM +0100, Sudip Mukherjee wrote: > > Hi Dom, > > > > On Sun, Sep 4, 2022 at 5:54 PM Domenico Andreoli <ca...@debian.org> wrote: > > > > > > On Thu, Sep 01, 2022 at 08:57:21PM +0100, Sudip Mukherjee wrote: > > > > > > > > Dear Maintainer, > > > > > > Hi Sudip, > > > > > > > > > > > dwarves FTBFS with libbpf 1.0.0 (available in experimental). > > > > Hopefully this is the error from the build log: > > > >
<snip> > > It does look like libbpf has now added a hard dependency on v6.0+ > > kernel even though they said it will have "transparent handling of > > older kernels". > > I have mentioned it in > > https://github.com/libbpf/libbpf/issues/562#issuecomment-1237299951. > > So, we either need to wait for some fix from libbpf upstream or wait > > for the Debian kernel team to update to v6.0 after its released next > > month. > > This already happened in the past, I solved it by adding linux-libc-dev > to dwarves' build depends. > > It's not obvious why this is visible only when building dwarves and > not libbpf itself. I nevertheless think it should be libbpf to depend > on the right linux-libc-dev, not the packages using it. > > What do you think? yes, if libbpf upstream can not fix it then I will need to update libbpf with a dependency like linux-libc-dev (>= 6.0) -- Regards Sudip
