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

Builds on linux fail to produce a native build log in bin\Logs #8543

Closed
dpodder opened this issue Jul 13, 2017 · 8 comments
Closed

Builds on linux fail to produce a native build log in bin\Logs #8543

dpodder opened this issue Jul 13, 2017 · 8 comments
Assignees
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. enhancement Product code improvement that does NOT require public API changes/additions good first issue Issue should be easy to implement, good for first-time contributors no-recent-activity

Comments

@dpodder
Copy link
Contributor

dpodder commented Jul 13, 2017

Builds of the C++ codebase on Windows produce fairly complete logs thanks to msbuild's logging support. The same build on Linux, however, produces no permanent logs. I'm not sure if it's feasible to log a higher level of verbosity like it is on Windows, but at the very least, it would be helpful to tee stdout from the call to make and save that in an appropriately-named log file.

@noamyogev84
Copy link

I'm new here, and i'd love to start contributing to this repo.
I'd like to start with this issue, can i be assigned?

@dpodder
Copy link
Contributor Author

dpodder commented Jul 28, 2017

Welcome @noamyogev84, thank you for stepping forward and offering to work on this issue! I'm assigning it to you now. Feel free to reach out if you have any questions about the bug, or the process to get the fix PR merged.

@terrajobst
Copy link
Member

terrajobst commented Jul 28, 2017

I should mention that I added @noamyogev84 as a read-only contributor on this repo which will allow us to actually assign the issue. However, first @noamyogev84 has to accept the email invite.

@dpodder
Copy link
Contributor Author

dpodder commented Jul 28, 2017

Thanks @terrajobst, I was just about to reach out to you about the permissions issue. 😄

@noamyogev84
Copy link

Thanks so much @dpodder @terrajobst.

@janvorli
Copy link
Member

@noamyogev84 I've just assigned this issue to you.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 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 12, 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 26, 2024
Infrastructure Backlog automation moved this from Future to Closed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. enhancement Product code improvement that does NOT require public API changes/additions good first issue Issue should be easy to implement, good for first-time contributors no-recent-activity
Projects
Status: Done
Development

No branches or pull requests

5 participants