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 I try to compile a crate including secp256k1 with cargo build --target thumbv7em-none-eabi, I run into the error printed below.
is it expected that this crate will fail to compile on this target? Perhaps you've encountered this issue before and, if so, perhaps you might have pointers on how to avoid it?
Ah, no, this is different from #663. This is about string.h in lax_der_parsing. Interesting.
This standards page says that a freestanding implementation must have stdint.h; possibly your compiler does not support C99. But string.h is not required and in theory even a confirming C99 compiler might not have it (but we use e.g. memcpy throughout the codebase, so it would be quite invasive to try to fix this).
Possibly there is way to configure your compiler to provide paths to standard headers? For the things we're doing in this library you could maybe also define your own versions somewhere.
When I try to compile a crate including
secp256k1
withcargo build --target thumbv7em-none-eabi
, I run into the error printed below.is it expected that this crate will fail to compile on this target? Perhaps you've encountered this issue before and, if so, perhaps you might have pointers on how to avoid it?
The text was updated successfully, but these errors were encountered: