From: Anthony Foiani <tkil@scrye.com>
To: linux-kernel@vger.kernel.org
Subject: Re: trouble building 'perf' for 3.9.7
Date: Sun, 30 Jun 2013 15:27:28 -0600 [thread overview]
Message-ID: <gehbjqofz.fsf@dworkin.scrye.com> (raw)
In-Reply-To: <g38s0l697.fsf@dworkin.scrye.com> (Anthony Foiani's message of "Sat\, 29 Jun 2013 19\:47\:00 -0600")
Greetings --
I wrote:
> Anyway, this worked fine for 2.6.late, as well as 3.0 stable and 3.4
> stable. However, I wanted the improvements to 'usbip', so I switched
> to 3.9; currently I'm using 3.9.7.
>
> Using exactly the same scripts (see below), perf now fails to build:
I have to eat some of those words.
I tried switching back to 3.4, and the build still failed. I'm
mystified, as I thought I had done a full rebuild with that kernel,
but maybe I hadn't (and the build succeeded due to bits left over from
earlier kernels).
The final fix (for 3.4 -- testing with 3.9 now) was to *not* point the
perf build at the target ("staging") headers. Instead, perf finds the
sysroot headers installed as a part of the cross-compile toolchain.
This left issues with elfutils, but I changed that build step to put
them in a custom subdirectory. That way, I could configure perf to
use that location without pulling in the sanitized headers.
Sorry if anyone wasted their time chasing down my carelessness.
(Although, to be fair, 'perf' is the only package out of about 20 that
fails when I explicitly point the build at the target's "include"
directory.)
Thanks again!
Best regards,
Anthony Foiani
prev parent reply other threads:[~2013-06-30 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 1:47 trouble building 'perf' for 3.9.7 Anthony Foiani
2013-06-30 21:27 ` Anthony Foiani [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=gehbjqofz.fsf@dworkin.scrye.com \
--to=tkil@scrye.com \
--cc=linux-kernel@vger.kernel.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