04-18-2019, 07:44 AM
Hello,
Building and running the entire toolchain invokes many steps. Ideally the make file should do everything automatically and all the dependencies should have been listed at the top. So in theory the makefile for check-gcc-newlib should have run through. Unless someone does this daily (I don't) it would be very very difficult to guess where the problem is from your explanation. Somewhere there is a shell script that needs a command that can not be found, the log of the makefile should yield some clues as to what is wrong. It could be that a package that was assumed to be in your system is not in the path, or during the build process something went wrong and as a result this executable has not been generated.
Maybe someone who is reading this had exactly the same error and can comment further, but examining the log file should help you also figure out what is going on.
Building and running the entire toolchain invokes many steps. Ideally the make file should do everything automatically and all the dependencies should have been listed at the top. So in theory the makefile for check-gcc-newlib should have run through. Unless someone does this daily (I don't) it would be very very difficult to guess where the problem is from your explanation. Somewhere there is a shell script that needs a command that can not be found, the log of the makefile should yield some clues as to what is wrong. It could be that a package that was assumed to be in your system is not in the path, or during the build process something went wrong and as a result this executable has not been generated.
Maybe someone who is reading this had exactly the same error and can comment further, but examining the log file should help you also figure out what is going on.
Visit pulp-platform.org and follow us on twitter @pulp_platform