From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf build: Fix a compiler error in util/libbfd.c
Date: Thu, 16 Jul 2026 11:06:00 -0700 [thread overview]
Message-ID: <alkdiIHB8yiSf8e5@google.com> (raw)
In-Reply-To: <CAP-5=fU00=N5h5h-SJVhbK6858agvO=Yf_6GgAd99FZTKOtOmg@mail.gmail.com>
Hi Ian,
On Wed, Jul 15, 2026 at 07:44:53PM -0700, Ian Rogers wrote:
> On Wed, Jul 15, 2026 at 5:43 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > The bfd_boolean type was gone and converted to the standard bool type
> > but we have some old code that uses the type. It caused a failure in
> > the build test.
> >
> > util/libbfd.c: In function 'slurp_symtab':
> > util/libbfd.c:94:9: error: unknown type name 'bfd_boolean'
> > 94 | bfd_boolean dynamic = FALSE;
> > | ^~~~~~~~~~~
> > util/libbfd.c:94:31: error: 'FALSE' undeclared (first use in this function)
> > 94 | bfd_boolean dynamic = FALSE;
> > | ^~~~~
> > util/libbfd.c:94:31: note: each undeclared identifier is reported only once for each function it appears in
> > util/libbfd.c:102:27: error: 'TRUE' undeclared (first use in this function)
> > 102 | dynamic = TRUE;
> > | ^~~~
> >
> > Fix it with standard bool type and constants.
> >
> > Link: https://sourceware.org/pipermail/binutils-cvs/2021-March/056231.html
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
>
> Should we add a fixes tag for backports? It's not clear we can provide
> a sensible SHA.
Thanks for your review. Yep, the file was moved and it had the bug
before. I was thinking about adding SHA of the move but not sure if
it's really worth it.
Thanks,
Namhyung
prev parent reply other threads:[~2026-07-16 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 0:43 [PATCH] perf build: Fix a compiler error in util/libbfd.c Namhyung Kim
2026-07-16 2:44 ` Ian Rogers
2026-07-16 18:06 ` Namhyung Kim [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=alkdiIHB8yiSf8e5@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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.