public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@arm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Dmitrii Dolgov <9erthalion6@gmail.com>,
	James Clark <james.clark@linaro.org>,
	Blake Jones <blakejones@google.com>,
	Yuzhuo Jing <yuzhuo@google.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools build: Link crypto lib for libopenssl feature
Date: Tue, 17 Mar 2026 08:48:49 +0000	[thread overview]
Message-ID: <20260317084849.GI8048@e132581.arm.com> (raw)
In-Reply-To: <abhOpjDG6hr-Sfe2@google.com>

Hi Namhyung,

On Mon, Mar 16, 2026 at 11:40:38AM -0700, Namhyung Kim wrote:
> Hi Leo,
> 
> On Sat, Mar 07, 2026 at 02:05:53PM +0000, Leo Yan wrote:
> > The perf static build reports that the BPF skeleton is disabled due to
> > the missing libopenssl feature.
> > 
> > Linking the crypto library fixes the static build failure.
> 
> I'm not sure if it's enough.  My build still doesn't have BPF skeleton
> support even with this change.  It seems to want zlib and zstd as well.

I did not see the build failure on Ubuntu 24.04 but I can reproduce the
issue after changed to Debian sid.  I will send a new version.

Thanks!

      reply	other threads:[~2026-03-17  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 14:05 [PATCH] tools build: Link crypto lib for libopenssl feature Leo Yan
2026-03-16 18:40 ` Namhyung Kim
2026-03-17  8:48   ` Leo Yan [this message]

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=20260317084849.GI8048@e132581.arm.com \
    --to=leo.yan@arm.com \
    --cc=9erthalion6@gmail.com \
    --cc=acme@kernel.org \
    --cc=blakejones@google.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=yuzhuo@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox