All of lore.kernel.org
 help / color / mirror / Atom feed
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: perf probe: Build error with missing libraries
Date: Mon, 13 Jan 2014 15:04:00 -0300	[thread overview]
Message-ID: <20140113180400.GD5318@ghostprotocols.net> (raw)

On a Ubuntu system just installed (13.10, x86_64), I'm installing the
devel libs one by one to check if there are problems with the automatic
disabling of features that requires libraries not installed.

Stumbled at this:

  CC       /tmp/build/perf/util/probe-event.o
util/probe-event.c: In function ‘try_to_find_probe_trace_events’:
util/probe-event.c:753:46: error: unused parameter ‘target’
[-Werror=unused-parameter]
     int max_tevs __maybe_unused, const char *target)
                                              ^
util/probe-event.c: At top level:
util/probe-event.c:193:12: error: ‘get_text_start_address’ defined but
not used [-Werror=unused-function]
 static int get_text_start_address(const char *exec, unsigned long
*address)
            ^
cc1: all warnings being treated as errors
make[1]: *** [/tmp/build/perf/util/probe-event.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [install] Error 2
make: Leaving directory `/home/acme/git/linux/tools/perf'
acme@ubuntu13:~/git/linux$ 

Investigating...

- Arnaldo

             reply	other threads:[~2014-01-13 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 18:04 Arnaldo Carvalho de Melo [this message]
2014-01-13 18:14 ` perf probe: Build error with missing libraries Arnaldo Carvalho de Melo
2014-01-14  1:41   ` Masami Hiramatsu
2014-01-14 13:09     ` Arnaldo Carvalho de Melo
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=20140113180400.GD5318@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.