+- PULP Community (https://pulp-platform.org/community)
+-- Forum: PULP's Community forum (https://pulp-platform.org/community/forumdisplay.php?fid=1)
+--- Forum: PULP General questions (https://pulp-platform.org/community/forumdisplay.php?fid=2)
+--- Thread: problem when testing gcc (/showthread.php?tid=79)
problem when testing gcc - zhouqiang - 04-18-2019
When I tested gcc according to the "test suit" in the readme at https://github.com/pulp-platform/pulp-riscv-gnu-toolchain, after running the command "make check-gcc-newlib", it appeared " /bin/sh: line 17: runtest: command not found", is this problem serious? What is the reason, how to fix it?
RE: problem when testing gcc - kgf - 04-18-2019
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.
RE: problem when testing gcc - zhouqiang - 04-18-2019
(04-18-2019, 07:44 AM)kgf Wrote: 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.
Thank you for your answer. Some problems are really difficult to locate, I will try to solve this problem. Here I also sent the wrong part, I hope people with the same mistake can discuss it together. Here are the tips for the error section:
“
make[3]: Entering directory '/home/lee/Downloads/pulp-riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc'
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd /home/lee/Downloads/pulp-riscv-gnu-toolchain/riscv-gcc/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
if [ -n "" ] \
&& [ -n "$GCC_RUNTEST_PARALLELIZE_DIR" ] \
&& [ -f testsuite/gcc-parallel/finished ]; then \
rm -rf testsuite/gcc; \
else \
cd testsuite/gcc; \
rm -f tmp-site.exp; \
sed '/set tmpdir/ s|testsuite$|testsuite/gcc|' \
< ../../site.exp > tmp-site.exp; \
/bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
EXPECT=`if [ -f ${rootme}/../expect/expect ] ; then echo ${rootme}/../expect/expect ; else echo expect ; fi` ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ; \
export TCL_LIBRARY ; \
fi ; \
`if [ -f ${srcdir}/../dejagnu/runtest ] ; then echo ${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool gcc --target_board=riscv-sim; \
if [ -n "$GCC_RUNTEST_PARALLELIZE_DIR" ] ; then \
touch ${rootme}/testsuite/gcc-parallel/finished; \
fi ; \
fi )
/bin/sh: line 17: runtest: command not found
make[3]: Leaving directory '/home/lee/Downloads/pulp-riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc'
rm -rf testsuite/g++-parallel
make[3]: Entering directory '/home/lee/Downloads/pulp-riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc'
(rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd /home/lee/Downloads/pulp-riscv-gnu-toolchain/riscv-gcc/gcc; ${PWDCMD-pwd}` ; export srcdir ; \
if [ -n "" ] \
&& [ -n "$GCC_RUNTEST_PARALLELIZE_DIR" ] \
&& [ -f testsuite/g++-parallel/finished ]; then \
rm -rf testsuite/g++; \
else \
cd testsuite/g++; \
rm -f tmp-site.exp; \
sed '/set tmpdir/ s|testsuite$|testsuite/g++|' \
< ../../site.exp > tmp-site.exp; \
/bin/sh ${srcdir}/../move-if-change tmp-site.exp site.exp; \
EXPECT=`if [ -f ${rootme}/../expect/expect ] ; then echo ${rootme}/../expect/expect ; else echo expect ; fi` ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then \
TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ; \
export TCL_LIBRARY ; \
fi ; \
`if [ -f ${srcdir}/../dejagnu/runtest ] ; then echo ${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool g++ --target_board=riscv-sim; \
if [ -n "$GCC_RUNTEST_PARALLELIZE_DIR" ] ; then \
touch ${rootme}/testsuite/g++-parallel/finished; \
fi ; \
fi )
/bin/sh: line 17: runtest: command not found
make[3]: Leaving directory '/home/lee/Downloads/pulp-riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc'
make[2]: Leaving directory '/home/lee/Downloads/pulp-riscv-gnu-toolchain/build-gcc-newlib-stage2/gcc'
make[1]: Leaving directory '/home/lee/Downloads/pulp-riscv-gnu-toolchain/build-gcc-newlib-stage2'
“