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
Building BDE in a Raspberry Pi 3 Model B, using DietPi with GCC 6.5.0, ARM7hf, will fail since C/C++ datatype char is an implementation defined datatype, and in ARM architecture, they are unsigned chars by default.
The error stats here, at line 78 of bdlde_base64decoder.cpp
changing to signed char instead of char may help, but also requires also changing the static class variable s_decoding_p from const char *const bdlde::Base64Decoder::s_decoding_p = decoding; to const signed char *const bdlde::Base64Decoder::s_decoding_p = decoding;
Another solution can be is swap from char to int
The text was updated successfully, but these errors were encountered:
@osubboo - this issue has nothing to do with ARM, it's just a happy accident that your toolchain is defaulting to signed chars on your platform.
It's considered good practice (e.g. MISRA demands that) not to use the char datatype to store numerical values like this; you should always use signed char or unsigned char, depending on your intent.
Building BDE in a Raspberry Pi 3 Model B, using DietPi with GCC 6.5.0, ARM7hf, will fail since C/C++ datatype
char
is an implementation defined datatype, and in ARM architecture, they are unsigned chars by default.The error stats here, at line 78 of bdlde_base64decoder.cpp
changing to
signed char
instead ofchar
may help, but also requires also changing the static class variables_decoding_p
fromconst char *const bdlde::Base64Decoder::s_decoding_p = decoding;
toconst signed char *const bdlde::Base64Decoder::s_decoding_p = decoding;
Another solution can be is swap from
char
toint
The text was updated successfully, but these errors were encountered: