From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/7] package/perf: build outside kernel tree
Date: Fri, 20 Mar 2015 00:21:51 +0100 [thread overview]
Message-ID: <550B5A0F.7080904@mind.be> (raw)
In-Reply-To: <1426714983-24803-4-git-send-email-steven@uplinklabs.net>
On 18/03/15 22:43, Steven Noonan wrote:
> This is necessary for introducing patches.
Although I think it's really messy to build perf within the the linux source
like we do now, your proposed approach has some showstopper drawbacks.
- It doesn't work for LINUX_OVERRIDE_SRCDIR or BR2_LINUX_KERNEL_CUSTOM_LOCAL.
- Any custom patches to the kernel are not taken into account, and I believe
perf uses the private headers so there's a risk there.
- It requires an expensive second extract of the entire kernel.
As an alternative, you could copy in just the perf stuff from the linux source
as a POST_EXTRACT_HOOK.
Or you could apply the patches on the kernel sources instead of on the perf
directory. But that would be a bit more complicated.
Or you could add a LINUX_POST_PATCH_HOOK to apply the perf patches. I'm not
entirely sure if that would work though.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-03-19 23:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 21:42 [Buildroot] [PATCH 1/7] package/perf: if slang is enabled, depend on it Steven Noonan
2015-03-18 21:42 ` [Buildroot] [PATCH 2/7] package/perf: if numactl (libnuma) " Steven Noonan
2015-03-18 21:42 ` [Buildroot] [PATCH 3/7] package/perf: if libunwind " Steven Noonan
2015-03-18 21:43 ` [Buildroot] [PATCH 4/7] package/perf: build outside kernel tree Steven Noonan
2015-03-19 23:21 ` Arnout Vandecappelle [this message]
2015-03-20 3:08 ` Steven Noonan
2015-03-18 21:43 ` [Buildroot] [PATCH 5/7] package/perf: patch installation paths Steven Noonan
2015-07-14 22:06 ` Romain Naour
2015-03-18 21:43 ` [Buildroot] [PATCH 6/7] package/perf: add patch to prevent crash on empty history buffer Steven Noonan
2015-03-18 21:43 ` [Buildroot] [PATCH 7/7] package/perf: use correct definition of ARCH on x86_64 Steven Noonan
2015-07-14 15:45 ` [Buildroot] [PATCH 1/7] package/perf: if slang is enabled, depend on it Romain Naour
2015-07-14 17:00 ` Romain Naour
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=550B5A0F.7080904@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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