You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with no_std crates that have a custom target, it is possible to to define "panic-strategy": "abort" in the custom target .json file, and xargo will happily compile your crate without a definition of the eh_personality lang item.
However, clippy will fail:
xargo clippy
[...]
error: language item required, but not found: `eh_personality`
error: aborting due to previous error
This is a tad late, but maybe it will help someone who finds this via search. In order for xargo clippy to work with a custom target, you either do xargo clippy --target=your_target or set a default target in .cargo/config and invoke xargo clippy. Either that or I can't reproduce this bug ¯_(ツ)_/¯
When working with
no_std
crates that have a custom target, it is possible to to define"panic-strategy": "abort"
in the custom target .json file, and xargo will happily compile your crate without a definition of theeh_personality
lang item.However, clippy will fail:
xargo clippy [...] error: language item required, but not found: `eh_personality` error: aborting due to previous error
One workaround is:
but that causes recompilation of core.
Another one would be adding the item to your source, although it is not needed.
I'm not really sure which of all the involved tools is the culprit here, I'm happy to raise the bug elsewhere if needed.
The text was updated successfully, but these errors were encountered: