specifying "--crate-type=x" in RUSTFLAGS gives an unexpected error on some crate types

[oyvindln]

$ RUSTFLAGS="--crate-type=staticlib" cargo build
error: unexpected character in cfg `/`, expected parens, a comma, an identifier, or a string

The same happens with dylib, cdylib and proc-macro.

rlib, lib and bin seems to work better, though they give me "can't find crate" errors instead (don't know if this is expected or not).

If passing an invalid crate type it behaves as expected:

RUSTFLAGS="--crate-type=wrong" cargo build
error: failed to run `rustc` to learn about target-specific information
---<cut>---
error: unknown crate type: `wrong`

[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!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

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!

[stale]

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!