Linux Perf Users
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: sedat.dilek@gmail.com, Sedat Dilek <sedat.dilek@gmail.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	Namhyung Kim <namhyung@kernel.org>,
	Andres Freund <andres@anarazel.de>,
	Quentin Monnet <quentin@isovalent.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [perf-tools] Build-error in tools/perf/util/annotate.c with LLVM-14
Date: Sun, 03 Jul 2022 10:54:45 -0300	[thread overview]
Message-ID: <1496A989-23D2-474D-B941-BA2D74761A7E@gmail.com> (raw)
In-Reply-To: <CA+icZUVpr8ZeOKCj4zMMqbFT013KJz2T1csvXg+VSkdvJH1Ubw@mail.gmail.com>



On July 3, 2022 8:54:41 AM GMT-03:00, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>On Sun, Jul 3, 2022 at 1:06 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>
>> On Sun, Jul 3, 2022 at 1:03 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> >
>> > On Sun, Jul 3, 2022 at 12:57 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> > [ ... ]
>> > > util/annotate.c:1766:33: error: too few arguments to function call,
>> > > expected 4, have 3
>> > >                              (fprintf_ftype) fprintf);
>> > >                                                     ^
>> > > /usr/include/dis-asm.h:472:13: note: 'init_disassemble_info' declared here
>> > > extern void init_disassemble_info (struct disassemble_info *dinfo, void *stream,
>> > >            ^
>> > > 1 error generated.
>> > > make[4]: *** [/home/dileks/src/linux/git/tools/build/Makefile.build:97:
>> > > util/annotate.o] Error 1
>> >
>> > This is with Debian's binutils(-dev) version 2.38.50.20220629-4.
>> >
>> > $ dpkg -S /usr/include/dis-asm.h
>> > binutils-dev: /usr/include/dis-asm.h
>> >
>>
>> [ /usr/include/dis-asm.h ]
>>
>> 470 /* Method to initialize a disassemble_info struct.  This should be
>> 471    called by all applications creating such a struct.  */
>> 472 extern void init_disassemble_info (struct disassemble_info *dinfo,
>> void *stream,
>> 473                                    fprintf_ftype fprintf_func,
>> 474                                    fprintf_styled_ftype
>> fprintf_styled_func);
>>
>
>[ CC Andres F. + bpf folks ]
>
>The patch-series from Andres Freund from [1] fixes the issue for me on
>Debian/unstable AMD64:
>
>[PATCH v1 0/3] tools: fix compilation failure caused by
>init_disassemble_info API changes
>[PATCH v1 1/3] tools build: add feature test for init_disassemble_info
>API changes
>[PATCH v1 2/3] tools: add dis-asm-compat.h to centralize handling of
>version differences
>[PATCH v1 3/3] tools: Use tools/dis-asm-compat.h to fix compilation
>errors with new binutils
>
>Compile-tested only (LLVM-14 x86-64).
>
>link="https://lore.kernel.org/lkml/20220703044814.892617-1-andres@anarazel.de/"
>b4 -d am $link
>
>Andres, you have some test-cases how you verified the built perf is OK?


That series should be split a bit further, so that the 
new features test is in a separate patch, i.e. I don't process bpftool patches, but can process the feature test and the tools/perf part.

Thanks Sedat for drilling deeper, identifying Andres work as a cure, thanks to Andres for that patch kit!

- Arnaldo 
>
>Thanks, Andres.
>
>-Sedat-
>
>[1] https://lore.kernel.org/lkml/20220703044814.892617-1-andres@anarazel.de/
>[2] https://lore.kernel.org/lkml/CA+icZUVVXq0Mh8=QuopF0tMZyZ0Tn8AiKEZoA3jfP47Q8B=x2A@mail.gmail.com/

  reply	other threads:[~2022-07-03 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 10:57 [perf-tools] Build-error in tools/perf/util/annotate.c with LLVM-14 Sedat Dilek
2022-07-03 11:03 ` Sedat Dilek
2022-07-03 11:06   ` Sedat Dilek
2022-07-03 11:54     ` Sedat Dilek
2022-07-03 13:54       ` Arnaldo Carvalho de Melo [this message]
2022-07-03 16:54         ` Andres Freund
2022-07-03 17:46           ` Arnaldo Carvalho de Melo
2022-07-03 20:32             ` Sedat Dilek
2022-07-03 16:51       ` Andres Freund
2022-07-03 20:40         ` Sedat Dilek
2022-07-03 21:31           ` Andres Freund

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=1496A989-23D2-474D-B941-BA2D74761A7E@gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andres@anarazel.de \
    --cc=bpf@vger.kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=quentin@isovalent.com \
    --cc=sedat.dilek@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox