crankstart: Hardware Build Fails with Playdate SDK 1.13.1
Build fails on hardware with Playdate SDK 1.13.1. The build worked last time I checked with 1.12.X. My device did not get the 1.13.0 update.
$ cat $PLAYDATE_SDK_PATH/VERSION.txt
1.13.1
$ rustc -V
rustc 1.69.0-nightly (13471d3b2 2023-03-02)
$ crank run --release --example=hello_world --device
warning: dropping unsupported crate type `cdylib` for target `thumbv7em-none-eabihf`
warning: `crankstart` (example "hello_world") generated 1 warning
Finished release [optimized] target(s) in 0.09s
/usr/local/playdate/gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: /Users/bsechter/projects/playdate/crankstart/target/thumbv7em-none-eabihf/release/examples/libhello_world.a(compiler_builtins-8d574003699b34d6.compiler_builtins.58342f1c-cgu.4.rcgu.o): in function `OUTLINED_FUNCTION_15':
compiler_builtins.58342f1c-cgu.4:(.text.OUTLINED_FUNCTION_15+0x6): undefined reference to `<T as core::convert::TryInto<U>>::try_into'
collect2: error: ld returned 1 exit status
Error: gcc failed with error ExitStatus(unix_wait_status(256))
$
All examples and the Klondike solitaire application fail with the above error. They all run fine in the simulator.
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 26 (4 by maintainers)
@sgeos, crank internally requests nightly for the rustup cargo bin (via
+nightly
) but only when building for the deviceSo when it succeeds to actually build for the device, it’s still using nightly instead of the default toolchain (try uninstalling the nightly toolchain instead of just changing the default to confirm this)