Redirect cargo build output to stderr #164
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…dout Redirect cargo build output (messages, warnings) to stderr instead of stdout. This ensures that when redirecting or piping the output of cargo-binutils tools, only the tool's output appears on stdout, not cargo/rustc messages.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the cargo build invocation so that all cargo/rustc messages and warnings are sent to stderr, not stdout. This solves the problem where output from cargo nm, cargo objdump, etc. would include cargo/rustc messages when piping or redirecting stdout, as described in #111.
Why?
cargo objdump -- -s > dumpand similar commands will only save the tool output to file.2>/dev/nullif desired.Fixes: #111