All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viktor Malik <vmalik@redhat.com>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, Donald Zickus <dzickus@redhat.com>,
	Viktor Malik <vmalik@redhat.com>
Subject: [PATCH bpf-next 0/3] samples/bpf: Allow building as PIE
Date: Wed, 25 Oct 2023 08:19:11 +0200	[thread overview]
Message-ID: <cover.1698213811.git.vmalik@redhat.com> (raw)

Hi,

when trying to build samples/bpf as PIE in Fedora, we came across
several issues, mainly related to the way compiler/linker flags are
handled in samples/bpf/Makefile. The first 2 commits in this patchset
address these issues (see commit messages for details).

At the same time, this proposes to allow passing an already built
bpftool to samples/bpf/Makefile. The reason is to remove a redundant
build step but also because I was not able to find a correct combination
of build flags to build libbpf.a for samples/bpf/bpftool/ with -fPIE.

Viktor Malik (3):
  samples/bpf: Allow building with custom CFLAGS/LDFLAGS
  samples/bpf: Fix passing LDFLAGS to libbpf
  samples/bpf: Allow building with custom bpftool

 samples/bpf/Makefile | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-10-25  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  6:19 Viktor Malik [this message]
2023-10-25  6:19 ` [PATCH bpf-next 1/3] samples/bpf: Allow building with custom CFLAGS/LDFLAGS Viktor Malik
2023-10-25  6:19 ` [PATCH bpf-next 2/3] samples/bpf: Fix passing LDFLAGS to libbpf Viktor Malik
2023-10-25  6:19 ` [PATCH bpf-next 3/3] samples/bpf: Allow building with custom bpftool Viktor Malik
2023-10-26 13:40 ` [PATCH bpf-next 0/3] samples/bpf: Allow building as PIE patchwork-bot+netdevbpf

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=cover.1698213811.git.vmalik@redhat.com \
    --to=vmalik@redhat.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dzickus@redhat.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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.