test -d build/riscv-pk || mkdir build/riscv-pk
test -x build/riscv-pk/bbl || (
cd build/riscv-pk
../../src/riscv-pk/configure \
--host=${CROSS_COMPILE%-} \
--with-payload=../linux-${LINUX_KERNEL_VERSION}/vmlinux
make -j$(nproc)
)
In conf/busybear.config, CROSS_COMPILE is set to riscv64-unknown-linux-gnu-, while in https://github.com/riscv/riscv-pk, it's said we should use the newlib compiler to compile riscv-pk, will the current *.sh file lead to any errors?
In https://github.com/michaeljclark/busybear-linux/blob/master/scripts/build.sh#L80-L87:
In conf/busybear.config,![image](https://user-images.githubusercontent.com/18757974/57938998-f0960a00-78fb-11e9-8fa9-e303e8a85ab1.png)
CROSS_COMPILE
is set toriscv64-unknown-linux-gnu-
, while in https://github.com/riscv/riscv-pk, it's said we should use the newlib compiler to compile riscv-pk, will the current *.sh file lead to any errors?