All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: SuHsueyu <anolasc13@gmail.com>,
	"Jose E. Marchesi" <jemarch@gnu.org>,
	bpf@vger.kernel.org
Subject: Re: Support for gcc
Date: Wed, 21 Dec 2022 19:26:27 +0100	[thread overview]
Message-ID: <87wn6kwr3g.fsf@oracle.com> (raw)
In-Reply-To: <CAEf4BzbQYUQu1RaVrqBNJzjPxRa=W7R-ezuZoXY4O=tUP22dTA@mail.gmail.com> (Andrii Nakryiko's message of "Tue, 20 Dec 2022 16:34:13 -0800")


> On Tue, Dec 20, 2022 at 3:56 AM SuHsueyu <anolasc13@gmail.com> wrote:
>>
>> Hello, I use gcc 12.1.0 to compile a source file:
>> t.c
>> struct t {
>>   int a:2;
>>   int b:3;
>>   int c:2;
>> } g;
>> with gcc -c -gbtf t.c
>> and try to use libbpf API btf__parse_split, bpf_object__open, and
>> bpf_object__open to parse and load into the kernel, but it failed with
>> "libbpf: elf: /path/to/t.o is not a valid eBPF object file".
>
> if (ehdr->e_type != ET_REL || (ehdr->e_machine && ehdr->e_machine != EM_BPF))
>
> This check is failing in libbpf. So check which of those two are not
> set appropriately. cc Jose to point where to report GCC-BPF specific
> issues.

Thanks for the CC.
That would be https://gcc.gnu.org/bugzilla.

(I don't think this is a GCC issue and certainly not a libbpf one.
 Seems like the op is building a x86_64 object and not a BPF object.)

>
>>
>> Is it wrong for me to do so? Due to some constraint, I cannot use
>> clang but gcc. How to parse and load gcc compiled object file with
>> libbpf?

  parent reply	other threads:[~2022-12-21 18:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 11:45 Support for gcc SuHsueyu
2022-12-20 17:27 ` sdf
2022-12-21  0:34 ` Andrii Nakryiko
2022-12-21 11:03   ` SuHsueyu
2022-12-21 17:41     ` Alan Maguire
2022-12-21 18:26   ` Jose E. Marchesi [this message]
2022-12-21 18:22 ` Jose E. Marchesi
2022-12-21 18:30   ` Jose E. Marchesi
2022-12-25 15:24     ` SuHsueyu
2022-12-26  9:42       ` Jose E. Marchesi
  -- strict thread matches above, loose matches on Subject: below --
2022-12-29 18:22 Marc Poulhiès

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=87wn6kwr3g.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=anolasc13@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=jemarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.