You must run “make tools” to build the compiler before running “make software”. Or alternatively, install a binary toolchain package obtained from elsewhere, and set RISCV_PATH to point at the top of the install tree, so that $(RISCV_PATH)/bin/riscv64-unknown-elf-gcc is valid. See the README.md file.
hello all ,
I am changing the led_fade, from legacy to MEE option ,after modifying the things ,while its compiling
its shows me this error,
I/home/algo/Board/freedom-e-sdk/bsp/env/sifive-hifive1 -include sys/cdefs.h -c -o led_fade.o led_fade.c
make[1]: *** No rule to make target ‘/home/algo/Board/freedom-e-sdk/bsp/env/sifive-hifive1/init.c’, needed by ‘/home/algo/Board/freedom-e-sdk/bsp/env/sifive-hifive1/init.o’. Stop.
make[1]: Leaving directory ‘/home/algo/Board/freedom-e-sdk/software/led_fade’
Makefile:267: recipe for target ‘software’ failed
make: *** [software] Error 2
freedom-e-sdk is in the middle of a major rewrite, which is unfortunately being done on mainline instead of on a branch, and is likely to be broken for months. I would recommend that you check out a copy from before the rewrite started, and don’t try to use the mee support.
If you really want to use the mee support, then you should file issues into the github freedom-e-sdk project to report bugs, rather than reporting them here. Github issues are tracked. Forum posts are not.