Eliminate the 'no debug symbols in executable' warning on mac

[brson]

Perhaps there's a minimum amount of debug info we can output by default without breaking things. This is alarming to newcomers.

[jdm]

I am 99% confident this comes straight from dsymutil.

[brson]

Possibly related to #3899

[graydon]

non-critical for 0.6, de-milestoning

[ryanseys]

+1 to fix this or provide temporary "fix"

[Mr0grog]

As a new user curious about the language, this definitely made me think I'd done something wrong while building. This issue is also not a top result in Google if you search for the full error message and I haven't seen anywhere else that the issue is detailed.

While this is totally understandable in a pre 1.0 release, it would be really nice to have a note that it's expected in the README and/or printed to the console at the end of the build output.

[carter-thaxton]

+1
30 seconds into playing with rust, initial impression: 0.6 is still not ready for anything more than casual experimentation.
If that's the message you intend to send, well done!

[rroels]

+1

Occurs when building rust, and when compiling .rs files. I was almost certain my build had failed since the last ~6 lines were these warnings (while everything was fine). I also get this warning every time I compile any .rs file.

[brson]

Nominating, production ready.

[graydon]

accepted for production-ready milestone

[Mr0grog]

Thanks! I know it's a small thing, but I certainly appreciate it :)

[jdm]

I'd be curious what happens if we stop running dsymutil for non-debug builds. In particular, does the gdb experience suffer at all when debugging the resulting binary?

[cadencemarseille]

I am writing a rustpkg script for rust-pcre to fix cadencemarseille/rust-pcre#1 and this is tripping me up because part of the script looks at rust run output, which includes this warning in the ProcessOutput.output data.

For now I think I'll just use the last line of output, but it would be great to have this issue fixed.