From: Dominique Martinet <asmadeus@codewreck.org>
To: Luca Boccassi <bluca@debian.org>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Deepak Kumar Mishra <deepakkumar.mishra@arm.com>,
dwarves@vger.kernel.org, Qais Yousef <qais.yousef@arm.com>,
Jiri Olsa <jolsa@kernel.org>,
siudin@fb.com, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] CMakeLists.txt: enable SHARED and STATIC lib creation
Date: Sat, 12 Jun 2021 08:06:28 +0900 [thread overview]
Message-ID: <YMPsdB9LZATwmn4m@codewreck.org> (raw)
In-Reply-To: <YMPpfzNCSE8DxvOA@codewreck.org>
Dominique Martinet wrote on Sat, Jun 12, 2021 at 07:53:51AM +0900:
> changing btf_loader.c to include bpf/btf.h instead fixes the issue for me:
Sorry that was a bit quick on my part, it's not the proper solution if
there are worse conflicts and I'm actually not sure why that worked...
It still includes the wrong btf.h -- Luca's patch is much better
/me goes back to bed
--
Dominique
next prev parent reply other threads:[~2021-06-11 23:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 19:20 [PATCH v2 0/2] dwarves: enable-SHARED-and-STATIC-lib-creation Deepak Kumar Mishra
2021-06-07 19:20 ` [PATCH v2 1/2] CMakeLists.txt: enable SHARED and STATIC lib creation Deepak Kumar Mishra
2021-06-10 17:31 ` Arnaldo Carvalho de Melo
2021-06-11 19:34 ` Andrii Nakryiko
2021-06-11 19:54 ` Andrii Nakryiko
2021-06-11 20:00 ` Arnaldo Carvalho de Melo
2021-06-11 20:08 ` Andrii Nakryiko
2021-06-11 22:17 ` Luca Boccassi
2021-06-11 22:20 ` Luca Boccassi
2021-06-11 22:45 ` Luca Boccassi
2021-06-11 22:53 ` Dominique Martinet
2021-06-11 23:06 ` Dominique Martinet [this message]
2021-06-11 23:07 ` Luca Boccassi
2021-06-11 23:43 ` Andrii Nakryiko
2021-06-07 19:20 ` [PATCH v2 2/2] README: add documentation for -DBUILD_SHARED_LIBS Deepak Kumar Mishra
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=YMPsdB9LZATwmn4m@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=andrii.nakryiko@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=bluca@debian.org \
--cc=bpf@vger.kernel.org \
--cc=deepakkumar.mishra@arm.com \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=qais.yousef@arm.com \
--cc=siudin@fb.com \
/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.