public inbox for trinity@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: davej@redhat.com
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH 1/3] use config.h in USE_* users
Date: Tue, 04 Jun 2013 11:50:47 +0200	[thread overview]
Message-ID: <51ADB877.9050705@suse.cz> (raw)
In-Reply-To: <1370339304-26492-1-git-send-email-jslaby@suse.cz>

Even if I apply those three, I still see:
syscalls/perf_event_open.c: In function 'setup_breakpoints':
syscalls/perf_event_open.c:237: error: 'struct perf_event_attr' has no
member named 'bp_type'
syscalls/perf_event_open.c:240: error: 'struct perf_event_attr' has no
member named 'bp_type'
syscalls/perf_event_open.c:243: error: 'struct perf_event_attr' has no
member named 'bp_type'
syscalls/perf_event_open.c:246: error: 'struct perf_event_attr' has no
member named 'bp_type'
syscalls/perf_event_open.c:249: error: 'struct perf_event_attr' has no
member named 'bp_type'
syscalls/perf_event_open.c:252: error: 'struct perf_event_attr' has no
member named 'bp_type'
syscalls/perf_event_open.c:259: error: 'struct perf_event_attr' has no
member named 'bp_addr'
syscalls/perf_event_open.c:263: error: 'struct perf_event_attr' has no
member named 'bp_len'
syscalls/perf_event_open.c:266: error: 'struct perf_event_attr' has no
member named 'bp_len'
syscalls/perf_event_open.c:269: error: 'struct perf_event_attr' has no
member named 'bp_len'
syscalls/perf_event_open.c:272: error: 'struct perf_event_attr' has no
member named 'bp_len'
syscalls/perf_event_open.c:275: error: 'struct perf_event_attr' has no
member named 'bp_len'
syscalls/perf_event_open.c: In function
'create_mostly_valid_counting_event':
syscalls/perf_event_open.c:377: error: 'struct perf_event_attr' has no
member named 'precise_ip'
syscalls/perf_event_open.c:378: error: 'struct perf_event_attr' has no
member named 'mmap_data'
syscalls/perf_event_open.c:379: error: 'struct perf_event_attr' has no
member named 'sample_id_all'
syscalls/perf_event_open.c:380: error: 'struct perf_event_attr' has no
member named 'exclude_host'
syscalls/perf_event_open.c:381: error: 'struct perf_event_attr' has no
member named 'exclude_guest'
syscalls/perf_event_open.c: In function
'create_mostly_valid_sampling_event':
syscalls/perf_event_open.c:428: error: 'struct perf_event_attr' has no
member named 'precise_ip'
syscalls/perf_event_open.c:429: error: 'struct perf_event_attr' has no
member named 'mmap_data'
syscalls/perf_event_open.c:430: error: 'struct perf_event_attr' has no
member named 'sample_id_all'
syscalls/perf_event_open.c:431: error: 'struct perf_event_attr' has no
member named 'exclude_host'
syscalls/perf_event_open.c:432: error: 'struct perf_event_attr' has no
member named 'exclude_guest'

and I have no idea how to fix those cleanly...

-- 
js
suse labs

       reply	other threads:[~2013-06-04  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1370339304-26492-1-git-send-email-jslaby@suse.cz>
2013-06-04  9:50 ` Jiri Slaby [this message]
2013-06-05 19:14   ` [PATCH 1/3] use config.h in USE_* users Vince Weaver
2013-06-05 19:18     ` Dave Jones
2013-06-06 16:14       ` Vince Weaver
2013-06-06 16:17         ` Dave Jones
2013-06-08 15:51           ` Vince Weaver
2013-06-09  2:38             ` Vince Weaver

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=51ADB877.9050705@suse.cz \
    --to=jslaby@suse.cz \
    --cc=davej@redhat.com \
    --cc=trinity@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