• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 451 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SDK8 setup produces odd path values

Andrew W.
Intellectual 260 points

After installing and running setup of SDK 8.0 for Sitara, there are many odd path values in the linux-devkit area. One example is the i686-arago-linux-libtool file, there is a concatenated path value. In other files, the concatenations are much longer. My install dir is /home/demo/TISDK.

LTCFLAGS="-isystem/home/jenkins/amsdk-nightly-build/build-CORTEX_1/arago-tmp-external-linaro-toolchain/sysroots/i686-nativesdk-arago-linux/home/demo/TISDK/ti-sdk-am335x-evm-08_clean/linux-devkit/sysroots/i686-arago-linux/usr/include

Setup does seem to complete and building does produce a functional image file. I am just very concerned that these odd concatenations are breaking other parts of the build process.


Thanks

  • 0
    TI__Guru**** 393215 points

    Hi Andrew,

    I will forward this to the SW team.

  • 0 in reply to Biser Gatchev-XID
    TI__Intellectual 2020 points

    Those paths shouldn't be in there since those comes from our build machine when we develop the SDK. However, its harmless since all that line is doing is providing an additional path for the compiler to find headers. However, since the path doesn't exist on your local machine it will be ignored.

  • 0 in reply to Franklin Cooper
    Intellectual 260 points

    Thanks for getting back so quickly. Would you know if "my dev path" component in that path is essential for proper builds? There is also this piece in bin/i686-arago-linux-libtool script that concerns me. Should it simply define my /home/demo/... path?

    compiler_lib_search_dirs="/home/jenkins/amsdk-nightly-build/build-CORTEX_1/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux/usr/lib/i686-arago-linux/gcc/i686-arago-linux/4.8.2 /home/jenkins/amsdk-nightly-build/build-CORTEX_1/arago-tmp-external-linaro-toolchain/sysroots/i686-nativesdk-arago-linux/home/demo/TISDK/ti-sdk-am335x-evm-08_clean/linux-devkit/sysroots/i686-arago-linux/lib /home/jenkins/amsdk-nightly-build/build-CORTEX_1/arago-tmp-external-linaro-toolchain/sysroots/i686-nativesdk-arago-linux/home/demo/TISDK/ti-sdk-am335x-evm-08_clean/linux-devkit/sysroots/i686-arago-linux/usr/lib/i686-arago-linux/4.8.2 /home/jenkins/amsdk-nightly-build/build-CORTEX_1/arago-tmp-external-linaro-toolchain/sysroots/i686-nativesdk-arago-linux/home/demo/TISDK/ti-sdk-am335x-evm-08_clean/linux-devkit/sysroots/i686-arago-linux/usr/lib"

  • 0 in reply to Andrew W.
    TI__Intellectual 2020 points

    No you shouldn't need to alter these paths. Honestly these paths shouldn't be there but I wouldn't worry about any of these weird paths unless your running into an error.