From: <changqing.li@windriver.com>
To: <namhyung@kernel.org>, <charlie@rivosinc.com>,
<james.clark@linaro.org>, <irogers@google.com>,
<linux-kernel@vger.kernel.org>
Cc: <changqing.li@windriver.com>
Subject: [RFC][PATCH 0/1] tools/build: Let link command read option from file
Date: Tue, 22 Jul 2025 14:13:34 +0800 [thread overview]
Message-ID: <20250722061335.285249-1-changqing.li@windriver.com> (raw)
From: Changqing Li <changqing.li@windriver.com>
Hi, Dear Maintainers
I am building perf with yocto project, and we don't want to put compile
object files to source folder, so pass O=xxx;
When we use a relatively long path like this:
O=/buildarea1/wrlinux-10.25/build/Virtualization/customized-WRLINUX1025_Nightly_Linux_systemd/250609-044304/lxbuilds/Harcuvar_platform_up/intel-x86-64-preempt-rt-glibc-std/wrlinux/build/tmp/work/intel_x86_64-wrs-linux/perf/1.0/perf-1.0
perf will compile failed with error:
| make[4]: /bin/sh: Argument list too long
| make[4]: *** [.../perf/1.0/perf-1.0/tools/build/Makefile.build:156: .../perf/1.0/perf-1.0/util/perf-in.o] Error 127
The error is from this line: "$(call if_changed,$(host)ld_multi)",
Since perf have many .o, and when above long O passed, if_changed will
evoke sh with long argument list.
So I try to fix this issue by this RFC patch. This is the first time I
touch this part, so the patch may not perfect, please help to review and
give your comments, thanks.
Changqing Li (1):
tools/build: Let link command read option from file
tools/build/Makefile.build | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2025-07-22 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 6:13 changqing.li [this message]
2025-07-22 6:13 ` [PATCH 1/1] " changqing.li
2025-07-22 15:43 ` Ian Rogers
2025-08-11 1:37 ` Changqing Li
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=20250722061335.285249-1-changqing.li@windriver.com \
--to=changqing.li@windriver.com \
--cc=charlie@rivosinc.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®