Your message dated Fri, 11 Nov 2022 09:25:11 +0530
with message-id <87cz9uqh5s....@debian.org>
and subject line Re: bpfcc: FTBFS with libbpf 1.0.0
has caused the Debian Bug report #1018818,
regarding bpfcc: FTBFS with libbpf 1.0.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1018818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bpfcc
Version: 0.24.0+ds-1
Severity: important
X-Debbugs-Cc: sudipm.mukher...@gmail.com
Tags: ftbfs
Usertags: libbpf1

Dear Maintainer,

bpfcc FTBFS with libbpf 1.0.0 (available in experimental).
These are some of the errors from the build log:

In file included from /<<PKGBUILDDIR>>/src/cc/bcc_libbpf_inc.h:5,
                 from /<<PKGBUILDDIR>>/src/cc/libbpf.c:57:
/usr/include/bpf/btf.h: In function ‘btf_enum64_value’:
/usr/include/bpf/btf.h:496:25: error: invalid use of undefined type ‘const 
struct btf_enum64’
  496 |         return ((__u64)e->val_hi32 << 32) | e->val_lo32;
      |                         ^~


/<<PKGBUILDDIR>>/src/cc/libbpf.c: In function ‘libbpf_bpf_map_create’:
/<<PKGBUILDDIR>>/src/cc/libbpf.c:304:28: error: invalid use of undefined type 
‘struct bpf_create_map_attr’
  304 |   p.map_flags = create_attr->map_flags;
      |                            ^~


/<<PKGBUILDDIR>>/src/cc/libbpf.c: In function ‘bcc_create_map’:
/<<PKGBUILDDIR>>/src/cc/libbpf.c:376:10: error: variable ‘attr’ has initializer 
but incomplete type
  376 |   struct bpf_create_map_attr attr = {};
      |          ^~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/src/cc/libbpf.c:376:30: error: storage size of ‘attr’ isn’t 
known
  376 |   struct bpf_create_map_attr attr = {};
      |                              ^~~~


/<<PKGBUILDDIR>>/src/cc/libbpf.c: In function ‘libbpf_bpf_prog_load’:
/<<PKGBUILDDIR>>/src/cc/libbpf.c:640:37: error: invalid use of undefined type 
‘const struct bpf_load_program_attr’
  640 |   p.expected_attach_type = load_attr->expected_attach_type;
      |                                     ^~


In file included from /<<PKGBUILDDIR>>/src/cc/bcc_libbpf_inc.h:5,
                 from /<<PKGBUILDDIR>>/src/cc/libbpf.c:57:
/usr/include/bpf/btf.h: In function ‘btf_enum64_value’:
removing 'bcc-0.24.0' (and everything under it)
/usr/include/bpf/btf.h:496:25: error: invalid use of undefined type ‘const 
struct btf_enum64’
  496 |         return ((__u64)e->val_hi32 << 32) | e->val_lo32;
      |                         ^~


/<<PKGBUILDDIR>>/src/cc/libbpf.c: In function ‘bpf_attach_xdp’:
/<<PKGBUILDDIR>>/src/cc/libbpf.c:1549:9: warning: implicit declaration of 
function ‘bpf_set_link_xdp_fd’; did you mean ‘bpf_link__fd’? 
[-Wimplicit-function-declaration]
 1549 |   ret = bpf_set_link_xdp_fd(ifindex, progfd, flags);
      |         ^~~~~~~~~~~~~~~~~~~
      |         bpf_link__fd


-- 
Regards
Sudip

--- End Message ---
--- Begin Message ---
Control: fixed -1 0.25.0+ds-1

Hi Sudip,

Thanks for the report new upstream release is fixing this issue and I've
already uploaded new version and is building fine against all release
architecture. So closing this bug.

Thanks and Regards,
Vasudev

--- End Message ---

Reply via email to