GNU Arm Embedded Toolchain

How do you build GNU Arm Toolchain?

Asked by Chris Dickerson

RE: 9-2020-q2-update

I installed Ubuntu and followed the PDF to the letter -- and every time, the build fails. I even tried an older version (I have a patch for making the toolchain big-endian for TMS570) but it fails the same way. With or without the patch, the build fails.

NAME="Ubuntu"
VERSION="14.04.6 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.6 LTS"
VERSION_ID="14.04"

Last few lines of failed build:

/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/install-native/arm-none-eabi/bin/ranlib libgcc.a
# Now that we have built all the objects, we need to copy
# them back to the GCC directory. Too many things (other
# in-tree libraries, and DejaGNU) know about the layout
# of the build tree, for now.
make install-leaf DESTDIR=../../../.././gcc \
   slibdir= libsubdir= MULTIOSDIR=thumb/nofp
make[5]: Entering directory `/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/build-native/gcc-final/arm-none-eabi/thumb/nofp/libgcc'
/bin/sh /home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/src/gcc/libgcc/../mkinstalldirs ../../../.././gcc/thumb/nofp
/usr/bin/install -c -m 644 libgcc.a ../../../.././gcc/thumb/nofp/
chmod 644 ../../../.././gcc/thumb/nofp/libgcc.a
/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/install-native/arm-none-eabi/bin/ranlib ../../../.././gcc/thumb/nofp/libgcc.a
/usr/bin/install -c -m 644 libgcov.a ../../../.././gcc/thumb/nofp/
chmod 644 ../../../.././gcc/thumb/nofp/libgcov.a
/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/install-native/arm-none-eabi/bin/ranlib ../../../.././gcc/thumb/nofp/libgcov.a
parts="crtbegin.o crtend.o crti.o crtn.o crtfastmath.o"; \
 for file in $parts; do \
   rm -f ../../../.././gcc/thumb/nofp/$file; \
   /usr/bin/install -c -m 644 $file ../../../.././gcc/thumb/nofp/; \
   case $file in \
     *.a) \
       /home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/install-native/arm-none-eabi/bin/ranlib ../../../.././gcc/thumb/nofp/$file ;; \
   esac; \
 done
make[5]: Leaving directory `/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/build-native/gcc-final/arm-none-eabi/thumb/nofp/libgcc'
make[4]: Leaving directory `/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/build-native/gcc-final/arm-none-eabi/thumb/nofp/libgcc'
make[4]: write error
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/build-native/gcc-final/arm-none-eabi/libgcc'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/build-native/gcc-final/arm-none-eabi/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/home/chris/projects/gcc-arm-none-eabi-9-2020-q2-update/build-native/gcc-final'
make: *** [all] Error 2
chris@Ryzen0:~/projects/gcc-arm-none-eabi-9-2020-q2-update$

Question information

Language:
English Edit question
Status:
Expired
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Chris Dickerson (chris-dickerson) said : 		#1

The last make[x] messages, I went into those folders and did a "make all" and they completed without issue.

Searching for text in the comment block:

# Now that we have built all the objects, we need to copy
# them back to the GCC directory. Too many things (other
# in-tree libraries, and DejaGNU) know about the layout
# of the build tree, for now.

Results in ALOT of make files... it's not clear which one is blowing up.

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.