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.

AM623: GCC compile tools from SDK can not run in the path which is different from the install path

Part Number: AM623

Tool/software:

HI TI experts

 I download the Linux SDK    ti-processor-sdk-linux-am62xx-evm-10.01.10.04-Linux-x86-Install.bin and install it .  the GCC compile tools can work normally in the install path . 

But if I move the GCC toolchains to another directory, it can  not work 。

 I use the Linux file command to look the aarch64-oe-linux-gcc program,  found the GCC interpreter path is hard-coded to the absolute  install path ,not the relative path。 

so my question is how to change the GCC interpreter  path ? 

  • if not change the GCC interpreter  path, the GCC can not run in the path which is different from the install path 

  • Hi, I am out of office for the next two weeks. Please expect delayed response. 

  • Hi Bert,

    if not change the GCC interpreter  path, the GCC can not run in the path which is different from the install path

    Yes, this is expected.

    so my question is how to change the GCC interpreter  path ? 

    I am not aware of any instruction for this.

    Many years ago, the SDK directory has an executable file, I forgot its filename, which is the toolchain installer. After the SDK install path has been changed, re-run this toolchain installer will update the toolchain path. However, this toolchain installer has been removed in recent SDK versions to reduce the file size of the SDK installer.

  • Hi Bin

       How the SDK file  ti-processor-sdk-linux-am62xx-evm-10.01.10.04-Linux-x86-Install.bin change the GCC path  when install it ?

  • Hi Bert,

    I don't know how the SDK installer does it, it should be something within Yocto and I know little about Yocto.

    But grepping the SDK directory name in "linux-devkit" directory in my SDK10.1 installation, it shows more than 13000 lines/files which have the SDK directory name. This probably tells that it is not trivial to manually update the toolchain path after moved the SDK installation.

    The easiest solution would be to re-install the SDK to the new location.