From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH v5 10/11] lto.inc: Disable LTO for perf
Date: Sun, 8 Nov 2020 16:02:16 -0800 [thread overview]
Message-ID: <20201109000217.3008448-10-raj.khem@gmail.com> (raw)
In-Reply-To: <20201109000217.3008448-1-raj.khem@gmail.com>
perf invokes kernel sources, and currently fails in multiple places for
now therefore disable LTO for perf
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/conf/distro/include/lto.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/distro/include/lto.inc b/meta/conf/distro/include/lto.inc
index bd433aa418..bb957084b5 100644
--- a/meta/conf/distro/include/lto.inc
+++ b/meta/conf/distro/include/lto.inc
@@ -18,6 +18,7 @@ LTO_pn-curl = ""
LTO_pn-libcap = ""
LTO_pn-libproxy = ""
LTO_pn-libbsd = ""
+LTO_pn-perf = ""
LTO_pn-xserver-xorg = ""
# Custom LTO flags
--
2.29.2
next prev parent reply other threads:[~2020-11-09 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 0:02 [PATCH v5 01/11] lto: Add global LTO distro policy file Khem Raj
2020-11-09 0:02 ` [PATCH v5 02/11] python3: Enable lto if its in DISTRO_FEATURES Khem Raj
2020-11-09 0:02 ` [PATCH v5 03/11] lto.inc: Add -ffat-lto-objects and -fuse-linker-plugin Khem Raj
2020-11-09 0:02 ` [PATCH v5 04/11] lto: Introduce LTOEXTRA variable Khem Raj
2020-11-09 0:02 ` [PATCH v5 05/11] libaio: Disable LTO Khem Raj
2020-11-09 0:02 ` [PATCH v5 06/11] weston: Fix linking with LTO Khem Raj
2020-11-09 0:02 ` [PATCH v5 07/11] lto.inc: Disable LTO for xserver-xorg Khem Raj
2020-11-09 0:02 ` [PATCH v5 08/11] gcc: Do no parameterize LTO configuration flags Khem Raj
2020-11-09 0:02 ` [PATCH v5 09/11] puzzles: Check for excessive constant arguments Khem Raj
2020-11-09 0:02 ` Khem Raj [this message]
2020-11-09 0:02 ` [PATCH v5 11/11] gcc: Handle duplicate names for variables Khem Raj
2020-11-09 8:30 ` [OE-core] [PATCH v5 01/11] lto: Add global LTO distro policy file Andreas Müller
2020-11-09 19:14 ` Khem Raj
2020-11-09 20:18 ` Andreas Müller
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=20201109000217.3008448-10-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox