[meta-ti] Building Yocto for Pandaboard

[Christian.Schulenberg at bmw.de]

Thanks a lot for your replies. Angstrom is definitely not the way I want to go at the moment, because I prefer to have a clean architecture in my project. So I have to wait, until the meta-ti layer is fixed to work with Poky without any dependencies to angstrom. Do you have any idea, how long this can take?

May be, in the meantime I try to fix some problems on my own to get Pandaboard working, because I really need to set up this device as a prototyping unit.

BR,
Christian

-----Ursprüngliche Nachricht-----
Von: meta-ti-bounces at yoctoproject.org [mailto:meta-ti-bounces at yoctoproject.org] Im Auftrag von William Mills
Gesendet: Montag, 27. Februar 2012 18:06
An: Koen Kooi
Cc: meta-ti at yoctoproject.org
Betreff: Re: [meta-ti] Building Yocto for Pandaboard



On 02/27/2012 11:19 AM, Koen Kooi wrote:
> Op 27 feb. 2012, om 17:06 heeft Philip Balister het volgende geschreven:
>
>> On 02/27/2012 03:50 AM, Koen Kooi wrote:
>>> Op 27 feb. 2012, om 09:26 heeft<Christian.Schulenberg at bmw.de>  <Christian.Schulenberg at bmw.de>  het volgende geschreven:
>>>
>>>> I already added to following line to my local.conf:
>>>>
>>>> BBMASK = ".*/meta-ti/recipes-misc/"
>>>>
>>>> which helps to bypass the first build problem. The next show stopper is building the boot loader (denx version of u-boot):
>>>>
>>>> clocks.c:415:13: internal compiler error: in decode_addr_const, at varasm.c:2632
>>>>
>>>> This seems to be a problem with the used version of gcc. I guess there are two ways to work around this: Use older version of gcc (4.5) or change compiler optimization from -Os to -O0. Unfortunately, neither can I find the right place to switch from gcc 4.6 to 4.5, nor the place to change compiler flags.
>>> Have you read the README in the meta-ti layer yet? That explains how to setup a working environment.
>> The README contains instructions for building Angstrom, which is not the
>> right answer for everyone trying to use meta-ti.
> Since the recipe in question break with gcc 4.6 and/or binutils 2.22 *and* you need SOC_FAMILY in overrides angstrom is the only "out of the box" option. Other routes will involve heavy patching. I agree that needs to be addressed, but it doesn't change the solution *right now*.
>
> And the instructions in the README set things for 'yocto', which is what people are asking for. If they asked for 'poky', that would be a totally different thing.

Denis or Koen:  Before today is over please modify the README.txt to 
describe where we are going and what is possible right now.  If Angstrom 
is the only thing possible right now it should say that until we can 
build with other layer stacks.  However it should also say that we are 
working toward a solution that will build with multiple layer stacks 
including poky.


_______________________________________________
meta-ti mailing list
meta-ti at yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti