When something fails, the users have no way of knowing what command
failed other than trying to deduce it from the log (for instance if it
mentions gcc it might be related to one of the two gcc builds).

Here since we add prints, we can at least pinpoint the failure to a
group of commands between two prints.

Signed-off-by: Denis 'GNUtoo' Carikli <[email protected]>
---
 build-toolchain | 35 ++++++++++++++++++++++++++++-------
 1 file changed, 28 insertions(+), 7 deletions(-)

diff --git a/build-toolchain b/build-toolchain
index 1bca51a9..77dc0231 100755
--- a/build-toolchain
+++ b/build-toolchain
@@ -26,7 +26,11 @@ BFD_LD=/usr/bin/ld.bfd
 mkdir -p $BASEDIR/toolchain/clang
 cd $BASEDIR/toolchain/clang
 
-# build llvm and clang binaries
+printf "%s\n%s\n%s\n" \
+    "+-------------------------------+" \
+    "| build llvm and clang binaries |" \
+    "+-------------------------------+"
+
 cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD="X86;ARM" \
       -DLLVM_EXTERNAL_CLANG_SOURCE_DIR=../../external/clang \
       -DCMAKE_C_FLAGS="-O2" ../../external/llvm/
@@ -35,7 +39,11 @@ make -j $(nproc)
 cd $BASEDIR
 
 
-# build binutils for arm
+printf "%s\n%s\n%s\n" \
+       "+------------------------+" \
+       "| build binutils for arm |" \
+       "+------------------------+"
+
 mkdir -p $BASEDIR/toolchain/gcc/arm/arm-linux-androideabi/build/binutils
 cd $BASEDIR/toolchain/gcc/arm/arm-linux-androideabi/build/binutils
 ./../../../../../src/binutils/binutils-2.25/configure \
@@ -48,7 +56,11 @@ cd 
$BASEDIR/toolchain/gcc/arm/arm-linux-androideabi/build/binutils
 make -j $(nproc)
 make install
 
-# build gcc for arm
+printf "%s\n%s\n%s\n" \
+       "+-------------------+" \
+       "| build gcc for arm |" \
+       "+-------------------+"
+
 cd .. && mkdir -p gcc && cd gcc
 ./../../../../../src/gcc/gcc-4.9/configure \
     --prefix=$BASEDIR/toolchain/gcc/arm/arm-linux-androideabi/install \
@@ -89,8 +101,11 @@ cd .. && mkdir -p gcc && cd gcc
 make -j $(nproc)
 make install
 
+printf "%s\n%s\n%s\n" \
+       "+-------------------------+" \
+       "| build binutils for host |" \
+       "+-------------------------+"
 
-# build binutils for host
 cd ../../../../ && mkdir -p host/build/binutils
 cd host/build/binutils
 ./../../../../src/binutils/binutils-2.25/configure \
@@ -106,7 +121,11 @@ cd host/build/binutils
 make -j $(nproc)
 make install
 
-# build gcc for host
+printf "%s\n%s\n%s\n" \
+       "+--------------------+" \
+       "| build gcc for host |" \
+       "+--------------------+"
+
 cd .. && mkdir -p gcc && cd gcc
 ./../../../../src/gcc/gcc-4.9/configure \
     --prefix=$BASEDIR/toolchain/gcc/host/install \
@@ -159,8 +178,10 @@ then
 fi
 
 
-#############################
-# build jack/jill toolchain
+printf "%s\n%s\n%s\n" \
+       "+---------------------------+" \
+       "| build jack/jill toolchain |" \
+       "+---------------------------+"
 
 # first the simple lib
 cd ../../src/jack/simple
-- 
2.37.3

_______________________________________________
Replicant mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/replicant

Reply via email to