Re: New Arago - am180x-evm core-image-minimal build is getting MD5 LICENSE errors in daisy

[Denys Dmytriyenko <denys@ti.com>]

On Thu, Jul 17, 2014 at 05:16:57PM -0400, Brian Hutchinson wrote:
> On Thu, Jul 17, 2014 at 5:07 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> 
> >
> > TOOLCHAIN_TYPE=internal will build the toolchain from sources.
> >
> >
> >> I build everything using Yocto 1.5 last year and remember having
> >> issues building 3.12 with the toolchain built by Yocto.  If I remember
> >
> > Hmm, not sure about the issues with the upstream toolchain. Another option
> > would be to use Linaro toolchain - either external or internal. The only catch
> > is that Linaro is not directly targeting or supporting ARM9 platforms. So, any
> > support requests would have to go to upstream GCC.
> >
> 
> Ah, now I'm with you.  So if I set TOOLCHAIN_TYPE=internal, is it
> building the same toolchain that would be built if I had used Yocto
> (upstream gcc I'm assuming although I admit I never dug into it) or
> something else?

Correct, it would build the toolchain from the sources available. Default is 
of course OE-Core - gcc 4.9 in master and 4.8 in daisy.
But if you have meta-linaro-toolchain layer in your stack, you can specify 
to build that one instead:

GCCVERSION ?= "linaro-4.8%"
BINUVERSION ?= "linaro-2.24%"
EGLIBCVERSION ?= "linaro-2.19%"

That would build the Linaro toolchain from sources.


> Should I try again with the latest external Linaro?  Just wondering
> what may be the best option since I've been out of the ARM9 scene for
> a while but now have to update a bunch of our stuff for a new release.

If you use TOOLCHAIN_TYPE=external and TOOLCHAIN_BRAND=linaro (both are the 
defaults for meta-arago), then it will use the external Linaro toolchain. We 
are currently using 2013.03 that is gcc-4.7 based. We've had some issues with 
2014.03, gcc-4.8 one.


> Sorry for the 21 questions ... just trying to stay out of the weeds.
> 
> Regards,
> 
> Brian