Ensure that an artifact is indeed no_std

[gnzlbg]

It would be good if cargo build would have a --nostd option that would ensure that the resulting artifact doesn't indeed link against the std library and fails if this is the case.

To check this, it needs to at least check that rustc is not called with the std feature enabled. A bonus point would be to use nm on Linux and MacOSX (and its equivalent on windows) to check that the artifact does not contain any std symbols.

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[gnzlbg]

Is this still relevant?

Yes.

If so, what is blocking it?

Nothing.

[hobofan]

For the meantime I built cargo nono to help with this.

[epage]

rust-lang/rfcs#3875 will elevate no_std into the dependency tree for analysis, like #8798.

[epage]

Hmm, looking at this again, I'm inclined to close in favor of #8798. If there is a reason for us to re-evaluate this, let us know!