linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: Makefile.perf:1149: *** Missing bpftool input for generating vmlinux.h. Stop.
Date: Wed, 5 Jun 2024 09:09:39 +0200	[thread overview]
Message-ID: <ZmAPM27gkBNVinMT@gmail.com> (raw)
In-Reply-To: <ZkJK3x3zQ9a4wp8E@gmail.com>


* Ingo Molnar <mingo@kernel.org> wrote:

> 
> * Ian Rogers <irogers@google.com> wrote:
> 
> > > Was this regression fix propagated to v6.9 in time?
> > 
> > We switched to using the handwritten file in v6.4:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/tools/perf/util/bpf_skel/vmlinux.h?id=a887466562b425bd6183bf75b523c1477c9fd22d
> 
> So there must be some different regression then, as this is readily 
> reproducible for me on v6.9, as per the build log below - I simply 
> Ctrl-C-ed a build, and the next build results in:
> 
>   kepler:~/tip/tools/perf> make clean install
>   Makefile.perf:1149: *** Missing bpftool input for generating vmlinux.h.  Stop.
>   make: *** [Makefile:90: clean] Error 2
>   kepler:~/tip/tools/perf> 

This happens easily on latest upstream v6.10-rc1 as well:

  kepler:~/tip> perfi
  Makefile.perf:1173: *** Missing bpftool input for generating vmlinux.h.  Stop.
  make: *** [Makefile:90: clean] Error 2
  kepler:~/tip> 

What's going on here?

Thanks,

	Ingo

      parent reply	other threads:[~2024-06-05  7:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  7:39 Makefile.perf:1149: *** Missing bpftool input for generating vmlinux.h. Stop Ingo Molnar
2024-05-08 20:44 ` Ian Rogers
2024-05-13  6:50   ` Ingo Molnar
2024-05-13 15:52     ` Ian Rogers
2024-05-13 17:16       ` Ingo Molnar
2024-05-13 17:24         ` Ian Rogers
2024-05-13 17:51           ` Ian Rogers
2024-05-21 17:07             ` Namhyung Kim
2024-06-05  7:15               ` Ingo Molnar
2024-06-05  7:18                 ` Ingo Molnar
2024-06-05 14:47                   ` Arnaldo Carvalho de Melo
2024-06-05  7:12             ` Ingo Molnar
2024-06-05  7:09         ` Ingo Molnar [this message]

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=ZmAPM27gkBNVinMT@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).