• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 102 subscribers
  • Views 21271 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

arm-none-linux-gnueabi-gcc: Command not found

Palak Shah
Prodigy 110 points

Hi,

I am referring to this document - http://www.omappedia.com/wiki/4AI.1.7_OMAP4_Icecream_Sandwich_Release_Notes

I am using OMAP4 processor with ICS on Blaze 2 tablet. I downloaded the sources and followed all the steps till -

Setting up build environment

export YOUR_PATH=`pwd`
export PATH=$PATH:<toolchain_parent_dir>/arm-2010q1/bin
export MYDROID=${YOUR_PATH}/mydroid
mkdir ${MYDROID}/logs
export CROSS_COMPILE=arm-none-linux-gnueabi-
export PATH=${YOUR_PATH}/u-boot/tools:$PATH

I verified that all the paths above all set correctly in my terminal.
palakshah@ubuntu:/$ echo $PATH
{HOME}/bin:{HOME}/TI_OMAP4_ICS/4AI.1.7/u-boot/tools:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/arm-2010q1/bin

But still when I run 
make ift 2>&1 |tee ${MYDROID}/logs/x-loader_make.out 

I get the following error -

ubuntu:~/TI_OMAP4_ICS/4AI.1.7/u-boot$ make 2>&1 |tee ${MYDROID}/logs/u-boot_make.out

make: arm-none-linux-gnueabi-gcc: Command not found
make[1]: arm-none-linux-gnueabi-gcc: Command not found
make[1]: Entering directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/tools'
ln -s ../common/environment.c environment.c
ln -s ../lib_generic/crc32.c crc32.c
gcc -M -Wall -pedantic -idirafter ../include -DTEXT_BASE=0x80e80000 -DUSE_HOSTCC environment.c img2srec.c mkimage.c crc32.c envcrc.c gen_eth_addr.c bmp_logo.c > .depend
make[1]: Leaving directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/tools'
make[1]: arm-none-linux-gnueabi-gcc: Command not found
make[1]: Entering directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/tools'
make[1]: `.depend' is up to date.
make[1]: Leaving directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/tools'
make[1]: arm-none-linux-gnueabi-gcc: Command not found
make[1]: Entering directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/post'
arm-none-linux-gnueabi-gcc -M -g  -Os   -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float  -D__KERNEL__ -DTEXT_BASE=0x80e80000 -I/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__ -march=armv7-a -mabi=apcs-gnu -Wall -Wstrict-prototypes cache_8xx.S cache.c codec.c cpu.c dsp.c ether.c i2c.c memory.c post.c rtc.c spr.c sysmon.c tests.c uart.c usb.c watchdog.c > .depend
/bin/sh: 1: arm-none-linux-gnueabi-gcc: not found
make[1]: *** No rule to make target `.depend'.  Stop.
make[1]: Leaving directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/post'
make[1]: arm-none-linux-gnueabi-gcc: Command not found
make[1]: Entering directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/examples'
/bin/sh: 1: arm-none-linux-gnueabi-gcc: not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/sh: 1: arm-none-linux-gnueabi-gcc: not found
dirname: missing operand
Try `dirname --help' for more information.
arm-none-linux-gnueabi-gcc -M -g  -Os   -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float  -D__KERNEL__ -DTEXT_BASE=0x80e80000 -I/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__ -march=armv7-a -mabi=apcs-gnu -Wall -Wstrict-prototypes hello_world.c stubs.c  > .depend
/bin/sh: 1: arm-none-linux-gnueabi-gcc: not found
make[1]: *** No rule to make target `.depend'.  Stop.
make[1]: Leaving directory `/home/palakshah/TI_OMAP4_ICS/4AI.1.7/u-boot/examples'
make[1]: arm-none-linux-gnueabi-gcc: Command not found

I have set the path to the tool chain in PATH variable then why am I still getting error? What am I missing here?

Thanks in advance for your help.

- Palak Shah
  • 0
    Guru 31670 points

    Palak,

    Simple and permanent solution is to add the path to the toolchain's bin directory to /etc/environment file and logout and login back again.

  • 0 in reply to Renjith Thomas
    Prodigy 110 points

    I added the path to the bin folder of the toolchain in the environment file. Logged out and Logged in again.

    But that still did not solve the problem. It gives the same error.

    When I do, locate arm-none-linux-gnueabi-gcc, it gives the following - 

    /opt/arm-2010q1/bin/arm-none-linux-gnueabi-gcc-4.4.1
    /opt/arm-2010q1/share/doc/arm-arm-none-linux-gnueabi/man/man1/arm-none-linux-gnueabi-gcc.1

    Do you think the extension gcc-4.4.1 has anything to do with this? Makefile is looking for arm-none-linux-gnueabi-gcc but I have arm-none-linux-gnueabi-gcc-4.4.1...? Not sure if that's a problem but just making sure.

    -Palak

  • 0 in reply to Palak Shah
    Guru 31670 points

    Palak,

    Just run the command "arm-none-linux-gnueabi-gcc" and see what happens. Also can you try to locate the file "arm-none-linux-gnueabi-gcc" in /opt/arm-2010q1?

  • 0
    TI__Mastermind 43955 points

    Hi Palak,

    Try out the following:

    1. Export the PATH variable into ".bashrc "

    For example,

    host$ export PATH=<your_tools_directory>:$PATH

    to the ~/.bashrc file. You can then source the ~/.bashrc file with the following command

    host$ source ~/.bashrc

    or

    2. Try giving the complete path for CROSS_COMPILE. For example:"export CROSS_COMPILE=/opt/arm-2010q1/bin/arm-none-linux-gnueabi-"

    or

    3. verify the user privileges for your build versus the root/user privileges for your installation of tools like gcc e.t.c.

    If there are some conflicts related to privilege, try with prefix 'sudo'. For example "sudo make all "

     

    Regards,

    Shankari

     

    --------------------------------------------------------------------------------------------------------
    Please click the Verify Answer button on this post if it answers your question.

    --------------------------------------------------------------------------------------------------------

  • 0 in reply to Renjith Thomas
    Prodigy 110 points

    Hi Renjith,

    I checked the toolchain folder and the bin folder had only arm-none-linux-gnueabi-gcc.4.1.1. Just to verify that the toolchain folder is not incomplete, I downloaded it again and compared. The new one had both arm-none-linux-gnueabi-gcc and arm-none-linux-gnueabi-gcc.4.1.1.

    Now I am able to build the boot-loader.

    Thank you for all your help. :)

    -Palak Shah

  • 0 in reply to Shankari G
    Prodigy 110 points

    Hi Shankari,

    Thanks for your help. The toolchain for some reason was not completely downloaded. I re downloaded it and it started working.

    Thank you for your suggestion.

    -Palak