From: jjohnson@codeaurora.org
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Prasad Sodagudi <psodagud@quicinc.com>,
eberman@quicinc.com, Nick Desaulniers <ndesaulniers@google.com>,
Mahesh Kumar Kalikot Veetil <mkalikot@codeaurora.org>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] kbuild: handle excessively long argument lists
Date: Fri, 15 Jan 2021 12:15:26 -0800 [thread overview]
Message-ID: <4c02050c4e95e4cb8cc04282695f8404@codeaurora.org> (raw)
In-Reply-To: <CAK7LNASHC5sNWxL0Ve8=f6=Gpf8ekVS41ETacBCTv5p72SVkNA@mail.gmail.com>
On 2021-01-14 17:12, Masahiro Yamada wrote:
> On Fri, Jan 15, 2021 at 6:50 AM Jeff Johnson <jjohnson@codeaurora.org>
> wrote:
>>
>> From: Mahesh Kumar Kalikot Veetil <mkalikot@codeaurora.org>
>>
>> Modules with a large number of compilation units may be
>> exceeding AR and LD command argument list. Handle this gracefully by
>> writing the long argument list in a file. The command line options
>> read from file are inserted in place of the original @file option.
>>
>> The usage is well documented at
>> https://www.gnu.org/software/make/manual/html_node/File-Function.html
>>
>> Signed-off-by: Mahesh Kumar Kalikot Veetil <mkalikot@codeaurora.org>
>> Signed-off-by: Jeff Johnson <jjohnson@codeaurora.org>
>> ---
>
>
>
>
> First, is this a real problem?
> If so, which module is exceeding the command line limit?
On 2021-01-14 17:12, Masahiro Yamada wrote:
> First, is this a real problem?
> If so, which module is exceeding the command line limit?
Mahesh & I appreciate all of the feedback.
The issue is seen in an Android environment with an out-of-tree
driver. The combination of long path names and a large number
of source files is leading to the issue.
Since Mahesh & I are not Kbuild gurus, is there an alternative
solution to this issue?
Jeff
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2021-01-15 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 1:18 [PATCH 1/2] kbuild: simplify cmd_mod Jeff Johnson
2021-01-13 1:18 ` [PATCH 2/2] kbuild: handle excessively long argument lists Jeff Johnson
2021-01-14 21:07 ` Nick Desaulniers
2021-01-14 21:32 ` jjohnson
2021-01-14 21:49 ` [PATCH v2 " Jeff Johnson
2021-01-15 1:00 ` Nick Desaulniers
2021-01-15 1:25 ` Masahiro Yamada
2021-01-15 1:12 ` Masahiro Yamada
2021-01-15 20:15 ` jjohnson [this message]
2021-01-15 21:53 ` Masahiro Yamada
2021-01-19 20:02 ` mkalikot
2021-01-15 1:07 ` [PATCH 1/2] kbuild: simplify cmd_mod Nick Desaulniers
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=4c02050c4e95e4cb8cc04282695f8404@codeaurora.org \
--to=jjohnson@codeaurora.org \
--cc=eberman@quicinc.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mkalikot@codeaurora.org \
--cc=ndesaulniers@google.com \
--cc=psodagud@quicinc.com \
/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).