Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build verbose generates very long command line #5490

Closed
manu-st opened this issue Apr 5, 2016 · 2 comments
Closed

Build verbose generates very long command line #5490

manu-st opened this issue Apr 5, 2016 · 2 comments

Comments

@manu-st
Copy link

manu-st commented Apr 5, 2016

When I perform a cross compilation for arm using the verbose flag the output window is barely readable. The main cause is that some arguments are replicated many times. For example, building libryujit.so will have 115 times the following arguments:

-target arm-linux-gnueabihf -B /home/local/Microsoft/coreclr/cross/rootfs/arm/usr/lib/gcc/arm-linux-gnueabihf -L/home/local/Microsoft/coreclr/cross/rootfs/arm/lib/arm-linux-gnueabihf --sysroot=/home/local/Microsoft/coreclr/cross/rootfs/arm  
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
@msftgits msftgits added this to the Future milestone Jan 30, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels May 13, 2024
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone May 27, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jun 27, 2024
@dotnet-policy-service dotnet-policy-service bot removed no-recent-activity backlog-cleanup-candidate An inactive issue that has been marked for automated closure. labels Jun 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

2 participants