From: Florian Fainelli <f.fainelli@gmail.com>
To: buildroot@buildroot.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
mmayer@broadcom.com, marcin@bis.org.pl, d.lang@abatec.at,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: [Buildroot] [PATCH] package/linux-tools: Disable libtracevent detection
Date: Fri, 21 Jul 2023 20:23:32 -0700 [thread overview]
Message-ID: <20230722032332.3960-1-f.fainelli@gmail.com> (raw)
Since upstream Linux commit 6898e60f709b0047206110d3ec9f4612210e3ff7
("perf build: If libtraceevent isn't present error the build") present
in Linux 6.4 and newer, Linux will fail to build if libtraceevent is not
present. Since we do not currently have support for libtracevent in
buildroot, pass NO_LIBTRACEVENT=1 to get perf to build again.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
package/linux-tools/linux-tool-perf.mk.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/linux-tools/linux-tool-perf.mk.in b/package/linux-tools/linux-tool-perf.mk.in
index 122c7cbbc42e..ee308a85dfd1 100644
--- a/package/linux-tools/linux-tool-perf.mk.in
+++ b/package/linux-tools/linux-tool-perf.mk.in
@@ -27,7 +27,8 @@ PERF_MAKE_FLAGS = \
NO_GTK2=1 \
NO_LIBPERL=1 \
NO_LIBPYTHON=1 \
- NO_LIBBIONIC=1
+ NO_LIBBIONIC=1 \
+ NO_LIBTRACEEVENT=1
# We need to pass an argument to ld for setting the emulation when
# building for MIPS architecture, otherwise the default one will always
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-07-22 3:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 3:23 Florian Fainelli [this message]
2023-07-22 21:26 ` [Buildroot] [PATCH] package/linux-tools: Disable libtracevent detection Thomas Petazzoni via buildroot
2023-08-29 19:58 ` Peter Korsgaard
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=20230722032332.3960-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=buildroot@buildroot.org \
--cc=d.lang@abatec.at \
--cc=marcin@bis.org.pl \
--cc=mmayer@broadcom.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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