public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "james.hilliard1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106773] libbpf: failed to find BTF info for global/extern symbol 'bpf_link_fops'
Date: Mon, 05 Dec 2022 21:57:03 +0000	[thread overview]
Message-ID: <bug-106773-4-w1KXqeFDcv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106773-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106773

--- Comment #16 from James Hilliard <james.hilliard1 at gmail dot com> ---
(In reply to David Faust from comment #15)
> Created attachment 54021 [details]
> [v2] DATASEC entries for extern funcs
> 
> v2 fixes an off-by-one bug introduced in the patch which was causing
> libbpf: Invalid BTF total size

Yeah, this seems to work.

  parent reply	other threads:[~2022-12-05 21:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 22:07 [Bug c/106773] New: " james.hilliard1 at gmail dot com
2022-09-01 20:31 ` [Bug target/106773] " james.hilliard1 at gmail dot com
2022-09-01 22:33 ` james.hilliard1 at gmail dot com
2022-11-29  0:44 ` david.faust at oracle dot com
2022-11-30 21:20 ` david.faust at oracle dot com
2022-12-01  0:04 ` james.hilliard1 at gmail dot com
2022-12-01  0:12 ` james.hilliard1 at gmail dot com
2022-12-01  2:07 ` james.hilliard1 at gmail dot com
2022-12-01 17:09 ` david.faust at oracle dot com
2022-12-01 21:49 ` david.faust at oracle dot com
2022-12-01 22:09 ` james.hilliard1 at gmail dot com
2022-12-01 22:11 ` james.hilliard1 at gmail dot com
2022-12-01 22:30 ` james.hilliard1 at gmail dot com
2022-12-05 17:42 ` david.faust at oracle dot com
2022-12-05 19:01 ` james.hilliard1 at gmail dot com
2022-12-05 21:06 ` david.faust at oracle dot com
2022-12-05 21:57 ` james.hilliard1 at gmail dot com [this message]
2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org
2022-12-14 18:25 ` cvs-commit at gcc dot gnu.org
2022-12-14 18:26 ` cvs-commit at gcc dot gnu.org
2023-01-06 14:18 ` jemarch at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106773-4-w1KXqeFDcv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).