From: sashiko-bot@kernel.org
To: "Dmitry Safonov" <dima@arista.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf build: Override OUTPUT when building internal libraries
Date: Tue, 03 Nov 2026 17:01:34 +0000 [thread overview]
Message-ID: <sashiko-outbox-195768@kernel.org> (raw)
In-Reply-To: <20261103-perf-output-v1-1-df33a0368cf2@arista.com>
> From: Dmitry Safonov <dima@arista.com>
>
> After commit 1572ba36fbca ("perf tests: Improvements to build-test
> performance"), building perf with OUTPUT on the command line fails:
> make -C tools/perf OUTPUT=/tmp/linux/bld/perf/ ARCH=x86_64 LC_ALL=C CC=gcc HOSTCC=gcc LD=ld
> ...
> make[3]: *** No rule to make target '/tmp/linux/perf/libsubcmd/libsubcmd.a'. Stop.
>
> MAKEFLAGS propagates the command-line OUTPUT assignment to recursive makes.
> The library builds pass their output directories through $O, but the assignment
> to $OUTPUT in tools/scripts/Makefile.include cannot replace a command-line
> argument. This affects libapi, libperf, libsubcmd and libsymbol.
>
> With "unexport MAKEFLAGS" returned and added $(info) debug in libsubcmd
> Makefile produces:
> OUTPUT = /tmp/linux/perf/libsubcmd/
> Without it, on current master it prints:
> OUTPUT = /tmp/linux/perf/
>
> Pass OUTPUT explicitly to each library build, including the trailing slash
> required when constructing file names. This follows the existing libbpf
> build rule and preserves MAKEFLAGS and jobserver propagation.
>
> Fixes: 1572ba36fbca ("perf tests: Improvements to build-test performance")
> Signed-off-by: Dmitry Safonov <dima@arista.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103-perf-output-v1-1-df33a0368cf2@arista.com?part=1
next prev parent reply other threads:[~2026-11-03 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 16:55 [PATCH] perf build: Override OUTPUT when building internal libraries Dmitry Safonov via B4 Relay
2026-11-03 16:55 ` Dmitry Safonov
2026-11-03 17:01 ` sashiko-bot [this message]
2026-11-04 20:44 ` Arnaldo Carvalho de Melo
2026-11-04 21:09 ` Dmitry Safonov
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=sashiko-outbox-195768@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dima@arista.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.