Closed georgefst closed 3 years ago
I think you need CC_armv7_unknown_linux_gnueabihf
and not CC_TARGET
.
Where did you get the toolchain from? Your linux distro? Maybe you could open an issue on the cc crate to update the c compiler auto-detect logic?
I think you need
CC_armv7_unknown_linux_gnueabihf
and notCC_TARGET
I can confirm that also works. Thanks.
Where did you get the toolchain from? Your linux distro?
It's an official ARM binary distribution, via AUR.
Maybe you could open an issue on the cc crate to update the c compiler auto-detect logic?
Yes, that sounds like a good idea. Though to be honest, I don't think I know enough about what's going on there to really write up a useful bug report. I'm already out of my depth - I'm not even directly a user of backtrace-rs
.
Thanks for the report, but that crate no longer exists in this repository. You'll probably need to specify the compiler manually if you're using a nonstandard compiler or an older version of this crate.
A tool chain update has meant that my
gcc
has changed names fromarm-linux-gnueabihf-gcc
toarm-none-linux-gnueabihf-gcc
. This confuses this crate. I've been able to work around it with a symlink, or by settingTARGET_CC=arm-none-linux-gnueabihf-gcc
, but neither of these were previously necessary.