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.

TI Android GingerBread 2.3.4 DevKit2.1 Developers Guide Issue

I followed the instructions on TI's DevKit 2.1 Developers Guide and using 32-bit Ubuntu V10.04 I was able to compile all but the Android kernel. To build the kernel it said that it required 64-bit Linux. I talked to TI and they forwarded me to http://source.android.com/source/initializing.html for the requirements on initializing a build environment.
 
There they recommend using 64-bit Ubuntu V10.04. So I set up a 64-bit Ubuntu V10.04 machine and installed the GingerBread 2.3.4 repository from TI. Now I can't get anything to compile. When I try to run the compiler, I get the error "arm-eabi-gcc: command not found" even when I am in the folder containing the arm-eabi-gcc binary file. My path includes the location of the arm-eabi-gcc binary.
 
Does anyone know if the tools supplied in the GingerBread 2.3.4 repository from TI are compatible with 64bit Ubuntu?

 
  • Hi.

    Build should succeed if you have installed all necessary packages.

    Please make sure that you have installed packages mentioned in below link.

    http://processors.wiki.ti.com/index.php/TI-Android-GingerBread-2.3.4-DevKit-2.1_DeveloperGuide#For_Ubuntu_on_32-bit_machines

    Please provide build  log to debug this further.

    Regards,

    Pankaj Bharadiya

  • Hello,

    I don't have a build log because the compiler does not run on my 64-bit machine. Thr error I get is "make: arm-eabi-gcc: command not found". I have updated my path to point to the compiler, but even if I try to launch arm-eabi.gcc from the folder that contains the arm-eabi-gcc executable I still get the error "arm-eabi-gcc: command not found".

    The instructions that you suggest work fine on 32-bit Ubuntu except that the Android kernel will not compile because it says that it requires a 64-bit OS. The x-loader and u-boot compile fine on the 32-bit OS. That's why I switched to 64-bit Ubuntu. Is there a separate set of instructions for 64-bit machines?

    Dan

  • Dan Welch said:

    Thr error I get is "make: arm-eabi-gcc: command not found"

    This error means that the path is not setup correctly.

    Please refer to the following link for setting up the compiler path:

    http://processors.wiki.ti.com/index.php/TI-Android-ICS-4.0.3-DevKit-3.0.0_DevelopersGuide#Toolchain_setup

  • Hello,

     

    Following the instructions in the GingerBread2.3.4DevKit2.1 developers guide fro using the pre-packaged repo places the tools in "<PATH_TO_ROWBOAT>/rowboat-android/TI_Android_GingerBread_2_3_4Sources/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin. Which I have included in my path. This is not the same as the path that the instructions say to use: "<PATH_TO_ROWBOAT>/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin". I did'n use this path because after following the instructions for installing the pre-packaged repo, this path does not exist.

    I also get the same error when I try to launch the compiler from the folder that contains the compiler binary.

     

    Thanks,

    Dan

  • Could you provide us the full path where your android arm-eabi- toolchain is installed and the $PATH setting that you are trying to use?

  • Hello,

    The path to my toolchain is:

    ~/rowboat-android/TI_Android_GingerBread_2_3_4Sources/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

    My path is:

    /home/dan/rowboat-android/TI_Android_GingerBread_2_3_4Sources/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:/home/dan/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

    Thanks,

     

    Dan

  • The paths look ok.

    I suspect that some ubuntu dependencies may not be satisfied. Do make sure you have all the x86 compatibility libraries recommended by google are installed.

    The arm-eabi- toolchain is for x86 and probably may not run directly on x86_64

  • THANKS,

     

    It compiles fine now. Too bad it took a week to get an answer to my origional question?

     

    Dan