<div dir="ltr">Yes - I can source the script, and I do successfully get my path updated. That's unfortunate. Â I can run the toolchain on the command line, but the developers I am working with need to use Eclipse. The plug-in seems like the right solution, so I would very much like to get this to work.<div><br></div><div>It occurred to me that these issues might be because I'm using an older version of bitbake:</div><div><div>$ bitbake --version</div><div>BitBake Build Tool Core version 1.20.0, bitbake version 1.20.0</div></div><div><br></div><div>Could that have something to do with the failure?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 12, 2014 at 12:24 PM, Bob Cochran <span dir="ltr"><<a href="mailto:yocto@mindchasers.com" target="_blank">yocto@mindchasers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 09/12/2014 12:57 PM, Nemicolopterus Crypticus wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 >Just double checking that you are specifying the "toolchain root<br>
location" as your top level build directory (the one above<br>
/conf/local.conf - the directory where you run bitbake).<br>
<br>
Yes that occurred to me too, since the phrasing is a bit unclear. I<br>
tried both. Here's a depiction of my directory structure:<br>
<br>
oe-core<br>
   |---- build<br>
      |---- conf (including local.conf)<br>
      |---- downloads<br>
      |---- tmp-eglibc<br>
       |---- environment-setup-blahblah<br>
       |---- <etc.><br>
      |---- <etcc><br>
   |---- bitbake<br>
   |---- gcc-toolchain<br>
   |---- meta<br>
   |---- <etc. lots more><br>
<br>
I tried with the root at build, and in build/tmp-eglibc with no luck.<br>
<br>
Is it possible the toolchain didn't get built?<br>
</blockquote>
<br></span>
What happens when you source your environment script? You should have your path set up to find your cross toolchain. If that's the case, you should be able to run the toolchain on the command line.<br>
<br>
I work with the powerpc toolchain, so I can cross-compile a simple test app after sourcing my env script:<br>
<br>
powerpc64-poky-linux-gcc main.c -o tst<br>
<br>
and verify I have generated a 64-bit powerpc ELF executable with<br>
<br>
file tst<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
I'm just wondering since<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
that's what the error claims. Is there any way to confirm that the<br>
toolchain did indeed get built? I ran bitbake meta-ide-toolchain, but<br>
our system is large and I'm not familiar with every aspect of it. Is it<br>
possible some other settings elsewhere got changed in a way that would<br>
prevent the toolchain from building?<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>