From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: a.p.zijlstra@chello.nl, mingo@elte.hu, paulus@samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Add support to install perf python extension
Date: Thu, 21 Jul 2011 16:04:07 -0300 [thread overview]
Message-ID: <20110721190407.GC24324@ghostprotocols.net> (raw)
In-Reply-To: <20110721184715.GA2425@jolsa.Belkin>
Em Thu, Jul 21, 2011 at 08:47:15PM +0200, Jiri Olsa escreveu:
> On Thu, Jul 21, 2011 at 02:11:48PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Jul 21, 2011 at 06:45:26PM +0200, Jiri Olsa escreveu:
> > > Changing the distutils to use their own default 'build'
> > > directory.
> > >
> > > Such setup makes the install command simple, because using
> > > --build-lib and --build-temp does not seem to comply with
> > > the way the distutils' install commands expect it.
> > >
> > > Also keeping the python/perf.so file, so it could be used
> > > for testing as of until now.
> >
> > Yeah, I gave up when I couldn't get:
> >
> > $ make O=/tmp/build-dir-for-perf/ -C tools/perf/ install
> >
> > to work, does it now? Checking...
>
> nope, I added install-python_ext since it installs to the
> python system lib area, and it could break standard install
But where is that it picks the binaries built? The problem I was
experiencing was that it wasn't obeying O=, just using the source dir
as the build dir, effectively building it again, in a different place.
> I think there's a way to install python modules under $HOME,
> maybe we could do that if no DESTDIR is specified..
> I can add it later ;)
Right, but this is not what I was talking about :-)
- Arnaldo
next prev parent reply other threads:[~2011-07-21 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 16:45 [PATCH] perf tools: Add support to install perf python extension Jiri Olsa
2011-07-21 17:11 ` Arnaldo Carvalho de Melo
2011-07-21 18:47 ` Jiri Olsa
2011-07-21 19:04 ` Arnaldo Carvalho de Melo [this message]
2011-07-21 19:41 ` Jiri Olsa
2011-07-21 21:16 ` Arnaldo Carvalho de Melo
2011-07-22 11:33 ` [PATCHv2] " Jiri Olsa
2011-08-10 8:27 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
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=20110721190407.GC24324@ghostprotocols.net \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.