From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
paulus@samba.org, cjashfor@linux.vnet.ibm.com,
fweisbec@gmail.com, linux-kernel@vger.kernel.org,
Caspar Zhang <czhang@redhat.com>
Subject: Re: [PATCHv3 0/5] perf, tool: Fix endian issues
Date: Mon, 07 May 2012 21:37:23 -0600 [thread overview]
Message-ID: <4FA894F3.10500@gmail.com> (raw)
In-Reply-To: <4FA8811C.6050300@gmail.com>
On 5/7/12 8:12 PM, David Ahern wrote:
>
> LINK /tmp/pbuild/perf
> /tmp/pbuild/libperf.a(pmu.o): In function `pmu_format_parse':
> /mnt/src/tools/perf/util/pmu.c:47: undefined reference to `perf_pmu_in'
> /mnt/src/tools/perf/util/pmu.c:47: undefined reference to `perf_pmu_in'
> /tmp/pbuild/libperf.a(pmu-bison.o): In function `perf_pmu_parse':
> /tmp/pbuild/util/pmu-bison.c:1287: undefined reference to `perf_pmu_lex'
> collect2: ld returned 1 exit status
> make: *** [/tmp/pbuild/perf] Error 1
nevermind. This one is a weird side effect of not having flex and bison
installed the first time I tried compiling it. After nuking the build
directory, installing flex and bison, perf compiled fine.
David
next prev parent reply other threads:[~2012-05-08 3:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 11:29 [PATCHv3 0/5] perf, tool: Fix endian issues Jiri Olsa
2012-05-07 11:29 ` [PATCH 1/5] perf, tool: Handle different endians properly during symbol load Jiri Olsa
2012-05-07 11:29 ` [PATCH 2/5] perf, tool: Carry perf_event_attr bitfield throught different endians Jiri Olsa
2012-05-07 11:29 ` [PATCH 3/5] perf, tool: Handle endianity swap on sample_id_all header data Jiri Olsa
2012-05-07 11:29 ` [PATCH 4/5] perf, tool: Fix 32 bit values endianity swap for sample_id_all header Jiri Olsa
2012-05-07 11:29 ` [PATCH 5/5] perf, tool: Fix endianity trick for adds_features bitmask Jiri Olsa
2012-05-07 16:15 ` David Ahern
2012-05-08 2:12 ` [PATCHv3 0/5] perf, tool: Fix endian issues David Ahern
2012-05-08 3:37 ` David Ahern [this message]
2012-05-08 3:49 ` David Ahern
2012-05-10 10:38 ` Jiri Olsa
2012-05-10 16:30 ` 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=4FA894F3.10500@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=czhang@redhat.com \
--cc=fweisbec@gmail.com \
--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.