Pluto FW Failed Build using Make CMD

Hello, I have been trying to use Vivado 2017.4 on ubuntu and using the CMD line to build the source. I am following the below steps to build and I am getting an error when running make.

     sudo apt-get install git build-essential fakeroot libncurses5-dev libssl-dev ccache 
     sudo apt-get install dfu-util u-boot-tools device-tree-compiler libssl1.0-dev mtools
     git clone --recursive github.com/.../plutosdr-fw.git
     cd plutosdr-fw
     export CROSS_COMPILE=arm-xilinx-linux-gnueabi-
     export PATH=$PATH:/opt/Xilinx/SDK/2017.2/gnu/arm/lin/bin
     export VIVADO_SETTINGS=/opt/Xilinx/Vivado/2017.4/settings64.sh

When I run make, I get the following output:

ed2@ED2-Ubuntu:~/plutosdr-fw$ make
rm -f
rm -rf build/*
make -C u-boot-xlnx ARCH=arm zynq_pluto_defconfig
make[1]: Entering directory '/home/ed2/plutosdr-fw/u-boot-xlnx'
#
# configuration written to .config
#
make[1]: Leaving directory '/home/ed2/plutosdr-fw/u-boot-xlnx'
make -C u-boot-xlnx ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi- UBOOTVERSION="PlutoSDR v0.20-PlutoSDR"
make[1]: Entering directory '/home/ed2/plutosdr-fw/u-boot-xlnx'
make[1]: arm-xilinx-linux-gnueabi-gcc: Command not found
/bin/sh: 1: arm-xilinx-linux-gnueabi-gcc: not found
dirname: missing operand
Try 'dirname --help' for more information.
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config.h
  GEN     include/autoconf.mk
/bin/sh: 1: arm-xilinx-linux-gnueabi-gcc: not found
scripts/Makefile.autoconf:75: recipe for target 'include/autoconf.mk' failed
make[2]: *** [include/autoconf.mk] Error 1
make[1]: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'.  Stop.
make[1]: Leaving directory '/home/ed2/plutosdr-fw/u-boot-xlnx'
Makefile:54: recipe for target 'u-boot-xlnx/tools/mkimage' failed
make: *** [u-boot-xlnx/tools/mkimage] Error 2
ed2@ED2-Ubuntu:~/plutosdr-fw$

I have seen in other post's both online and in this forum that others were having the same issue. Where can I look to correct this problem?

Should I try to be using the latest version of vivado?