Stop throwing away make stderr output - #1055
Conversation
Calling '$(MAKE)' against a sub-directory, while redirecting the stderr output to /dev/null makes it impossible to debug build failures, as it hides all compiler error messages. Stop sending output to /dev/null, so users can figure out what's wrong when a new compiler release fails to build SGX. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
6d786b0 to
db5f647
Compare
|
Rebased to resolved conflicts with HEAD |
|
Important 🔀 The Intel® SGX SDK codebase has movedThank you for your contribution! If you have any questions or need assistance migrating, please ask here. As we complete the migration, older pull requests may eventually be closed. No work is lost, though, and you are welcome to re-open your change in the new repository at any time. Footnotes
|
Calling '$(MAKE)' against a sub-directory, while redirecting the stderr output to /dev/null makes it impossible to debug build failures, as it hides all compiler error messages. Stop sending output to /dev/null, so users can figure out what's wrong when a new compiler release fails to build SGX.