Using the init-log feature on targets that do not support atomics (e.g. riscv32imc-unknown-none-elf) causes builds to fail, because the currently used version of rtt-log (v0.3.0) assumes that there always exist functions log::set_logger() and log::set_max_level(). However, this is is not the case for these architectures. Here, log::set_logger_racy() and log::set_max_level_racy() have to be called instead. This problem has been fixed in rtt-log v0.4.0. Therefore, this commit bumps the dependency to that version, allowing init-log to be used on targets without native atomics support.
Using the
init-logfeature on targets that do not support atomics (e.g. riscv32imc-unknown-none-elf) causes builds to fail, because the currently used version of rtt-log (v0.3.0) assumes that there always exist functionslog::set_logger()andlog::set_max_level(). However, this is is not the case for these architectures. Here,log::set_logger_racy()andlog::set_max_level_racy()have to be called instead. This problem has been fixed in rtt-log v0.4.0. Therefore, this commit bumps the dependency to that version, allowinginit-logto be used on targets without native atomics support.Fixes #45