• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 107 subscribers
  • Views 4791 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.

building with arago

Charles Krinke
Prodigy 230 points

I'm having a little trouble using arago to create a root filesystem for the AM3517EVM and keep getting a "No valid toolchain in PATH" from bitbake. I *thought* I followed the receipe for setting this up correctly at http://arago-project.org/wiki/index.php/Building_with_Arago. When I do this, I get an error which I suspect is an arago/oe configuration setting as the $PATH appears to be fine. I wonder if someone could give me a pointer on how to get past this, please.

ckrinke@hwa:~/arago$ echo $CROSS_COMPILE
arm-arago-linux-gnueabi-
ckrinke@hwa:~/arago$ arm-arago-linux-gnueabi-gcc -v
...
gcc version 4.5.3 20110311 (prerelease) (GCC)
ckrinke@hwa:~/arago$ bitbake arago-base-tisdk-image
FATAL: No valid toolchain in PATH
ckrinke@hwa:~/arago$

Charles

  • 0
    TI__Intellectual 1195 points

    Charles,

    Check your <arago root dir>/conf/local.conf file and make sure that the TOOLCHAIN_BRAND is set to "arago". For example:

    TOOLCHAIN_BRAND ?= "arago"

    Regards,

    Carlos 

  • 0 in reply to Carlos Hernandez
    Prodigy 230 points

    Well, phrumph, that wasn't it. It must be something else. I tried following the "Building with arago" wiki page to set this up and here is what happens when I try to build.

    $ cd arago
    $ source arago/setenv
    $ grep TOOLCHAIN_BRAND arago/conf/local.conf
    TOOLCHAIN_BRAND ?= "arago"
    $ bitbake arago-base-tisdk-image
    FATAL: No valid toolchain in PATH
    $

    So, what else could it be besides TOOLCHAIN_BRAND?

    Charles

  • 0 in reply to Charles Krinke
    Expert 2765 points

    Hello Charles,

    I'm having the same trouble, were you able to fix it? If so could you please let me know how you fixed it?

    Thanks a lot.

    Regards

    Santhosh

  • 0 in reply to Santhosh Ramani
    Prodigy 150 points

    I'v solved the problem, please chech the file "setenv", and the content is as blow:

    please be careful for the line in the red box

  • 0 in reply to wang tidus
    Expert 1990 points

    you can always set your PATH variable to toolchain path, or else you can set it from /conf/local.conf 

    best luck

  • 0 in reply to nikunj.rudani
    Expert 1280 points

    What is the proper way to add path entries in local.conf? The following result in "$PATH" being in the path rather than expanding it:

    export PATH=/opt/csl/bin:$PATH

    export PATH="$PATH:/opt/csl/bin"

    The following complains about circular reference for PATH

    export PATH="${PATH}:/opt/csl/bin"

    I cannot get it work, even though the user's guide tells me to put it in local.conf (the first way listed). I know the first two instances work from the shell. I also know that bitbake does not expand $PATH in the export because I have printed the resulting path from within a bitbake class.

    Thanks