From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf probe: Build error with missing libraries
Date: Tue, 14 Jan 2014 10:09:07 -0300 [thread overview]
Message-ID: <20140114130907.GA29798@ghostprotocols.net> (raw)
In-Reply-To: <52D495D1.5080505@hitachi.com>
Em Tue, Jan 14, 2014 at 10:41:37AM +0900, Masami Hiramatsu escreveu:
> (2014/01/14 3:14), Arnaldo Carvalho de Melo wrote:
> > Jiri, this is something else for the give-me-more-ponies list for
> > tests/make: build it on freshly provisioned systems with multiple mixes
> > of devel packages installed ;-)
> I think we can change makefile to get some combinations of config options
> when building perf tools.
This is what:
make -C tools/perf -f tests/make
does, and we use it already, many config combos are tested, but that
kinda expects that all optional devel libs be installed.
What I'm talking about is to, in addition, install the devel packages
iteratively, testing those config options combos with and without
installed devel packages combos.
- Arnaldo
next prev parent reply other threads:[~2014-01-14 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 18:04 perf probe: Build error with missing libraries Arnaldo Carvalho de Melo
2014-01-13 18:14 ` Arnaldo Carvalho de Melo
2014-01-14 1:41 ` Masami Hiramatsu
2014-01-14 13:09 ` Arnaldo Carvalho de Melo [this message]
2014-01-14 13:15 ` Jiri Olsa
2014-01-14 14:21 ` Arnaldo Carvalho de Melo
2014-01-15 1:58 ` Namhyung Kim
2014-01-15 18:38 ` Arnaldo Carvalho de Melo
2014-01-16 1:26 ` Namhyung Kim
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=20140114130907.GA29798@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
/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.