public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Mayer <mmayer@broadcom.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>
Cc: Markus Mayer <mmayer@broadcom.com>,
	Perf Mailing List <linux-perf-users@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/1] perf build: fix "argument list too long" in second location
Date: Thu,  9 Apr 2026 15:14:16 -0700	[thread overview]
Message-ID: <20260409221418.185343-1-mmayer@broadcom.com> (raw)

Hi all,

My apologies for not catching this one sooner. Using xargs in the actual
build recipe worked, but it turns out echoing $^ in quiet_cmd_rm also
offends the shell. Somehow, it didn't show up during my tests before
submitting the previous fix[1] for this issue or I would have addressed
both together.

But then it did start to show up. Like this:

  GEN     linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v3/extra-metricgroups.json
  TEST    linux/tools/perf/pmu-events/metric_test.log
make[5]: /bin/sh: Argument list too long
make[5]: *** [pmu-events/Build:220: prune_orphans] Error 127

This was a bit of a head-scratcher before I realized that this came from
    quiet_cmd_rm  = RM      $^
and that no attempt of putting quotes around $^ would help.

With change proposed here, it'll look like this instead:

  GEN     linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v3/extra-metricgroups.json
  TEST    linux/tools/perf/pmu-events/metric_test.log
  RM      ...634 orphan file(s)...
  LD      linux/tools/perf/util/perf-util-in.o

This is probably a good thing, regardless of the shell complaining,
since listing 634 files in a so-called "quiet" message is probably not
very fitting.

I don't know why my build has 634 orphans every single time it runs
(straight-up cross-build on x86_64 for ARM64) or if that is a lot. I do
get the impression that it is probably rather unusual. Not really doing
anything special, though.

Also, the build machines are running Ubuntu 24.04. As such, /bin/sh is
provided by /bin/dash. This may also factor into why I might be seeing
this issue while others may not.

Again, sorry for the churn. Hopefully this is it now on the orphan front.

Regards,
-Markus

[1] https://lore.kernel.org/linux-perf-users/20260303211503.165337-1-mmayer@broadcom.com/

Markus Mayer (1):
  perf build: fix "argument list too long" in second location

 tools/perf/pmu-events/Build | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-04-09 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 22:14 Markus Mayer [this message]
2026-04-09 22:14 ` [PATCH 1/1] perf build: fix "argument list too long" in second location Markus Mayer

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=20260409221418.185343-1-mmayer@broadcom.com \
    --to=mmayer@broadcom.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.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 \
    /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