All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	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: Makefile.perf:1149: *** Missing bpftool input for generating vmlinux.h.  Stop.
Date: Wed, 8 May 2024 09:39:06 +0200	[thread overview]
Message-ID: <ZjssGrj+abyC6mYP@gmail.com> (raw)


So I've been getting this perf build failure for some time:

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

... but if I clone a new repository, it works fine, until a point.

'make clean' doesn't work - and 'make mrproper' in the main kernel 
directory doesn't clean up properly.

Only if I do a brute-force:

	rm -rf tools/
	git checkout HEAD -f

does it get resolved.

The failure condition triggers if I Ctrl-C the following build a couple of 
times, without it being finished:


   cd tools/perf; make clean install
   ...

   LD      util/perf-in.o
   LD      perf-in.o
   CC      pmu-events/pmu-events.o
 ^Cmake[3]: *** [pmu-events/Build:43: pmu-events/pmu-events.o] Interrupt
 make[2]: *** [Makefile.perf:709: pmu-events/pmu-events-in.o] Interrupt
 make[1]: *** [Makefile.perf:264: sub-make] Interrupt
 make: *** [Makefile:113: install] Interrupt
 kepler:~/tip> perfi
 Makefile.perf:1149: *** Missing bpftool input for generating vmlinux.h.  Stop.
 make: *** [Makefile:90: clean] Error 2

Thanks,

	Ingo

             reply	other threads:[~2024-05-08  7:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  7:39 Ingo Molnar [this message]
2024-05-08 20:44 ` Makefile.perf:1149: *** Missing bpftool input for generating vmlinux.h. Stop 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

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=ZjssGrj+abyC6mYP@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 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.