From: Joel Fernandes <joel@joelfernandes.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, acme@kernel.org,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [RFC] Fix python feature detection
Date: Sun, 14 Jul 2019 13:57:59 -0400 [thread overview]
Message-ID: <20190714175759.GA34501@google.com> (raw)
In-Reply-To: <20190714154006.GB16802@krava>
On Sun, Jul 14, 2019 at 05:40:06PM +0200, Jiri Olsa wrote:
> On Sun, Jul 07, 2019 at 10:44:17AM -0400, Joel Fernandes (Google) wrote:
> > I am having a hard time building BPF samples by doing a make in
> > samples/bpf. While I am debugging that, I ran into the Python issue.
> > Even though the system has libpython2.7-dev:
> >
> > If I just do a 'make' inside tools/build/feature/ I get:
> > Python.h: No such file or directory
>
> because you don't have FLAGS_PYTHON_EMBED set?
>
> >
> > This led me to this patch which fixes Python feature detection for me.
> > I am not sure if it is the right fix for Python since it is hardcoded
> > for Python version 2, but I thought it could be useful.
>
> we detect python in tools/perf/Makefile.config and
> set FLAGS_PYTHON_EMBED properly
>
> it's supposed to be set by a project using tools/build
> for feature detection.. what are you building? AFAICS
> samples/bpf do not use tools/build
Yes, you are right. Never mind then. I was debugging feature detection and
ended doing a make in this directory like:
make <something>.bin which works always except for python. But as you said it
is likely a non-issue.
thanks!
- Joel
prev parent reply other threads:[~2019-07-14 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 14:44 Joel Fernandes (Google)
2019-07-14 15:40 ` Jiri Olsa
2019-07-14 17:57 ` Joel Fernandes [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=20190714175759.GA34501@google.com \
--to=joel@joelfernandes.org \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.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
Powered by JetHome