[GRADLE-3363] Clang argument list to long error when linking many object files Created: 15/Nov/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Sterling Greene Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Some people get the following error when building a bigger component using Clang:

clang: error: unable to execute command: posix_spawn failed: Argument list too long
clang: error: linker command failed due to signal (use -v to see invocation)

It looks like Clang expands the @argfile before calling the linker and ends up passing everything to the linker as a single command line.


Comment by Maxime Lussier [ 25/May/16 ]

Hi @Sterling Greene @big-guy,

I appear to be experiencing a similar issue. The linking command using clang is 50k characters due to the presence of many object files and fails when called from Gradle. However, calling clang++.exe @argumentsFile succeeds.

The workaround does not seem to be doing anything. calling Gradle with --info still shows the long linking command.

I am using android studio 2.2 Preview 1 and this bug currently blocks me from progressing. I can attach logs if necessary.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:46:50 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.