[poky] [PATCH 0/5] Fedora 14 Patches

[Saul Wold]

On 12/09/2010 12:58 AM, Wolfgang Denk wrote:
> Dear Saul,
>
> In message<4D00042C.6040403 at linux.intel.com>  you wrote:
>>
>> Thanks for your patches and assistance.
>>
>> Not sure if you saw the Release Notes regarding F14 and building
>> make-native first and installing that locally due to problems with F14's
>> make.  See http://bugzilla.pokylinux.org/show_bug.cgi?id=467
>> and http://www.yoctoproject.org/download/yocto-project-4-0-release-notes
>
> Yes, I saw trhis, but decided it made more sense to fix the broken
> Makefiles, especially as this was trivial to do, and in case of eglibc
> I could just apply the corresponding commit from OE.
>
> But actually the make-3.82 issues are the smallest of my problems.
>
> I'm trying to build Poky for some PowerPC and ARM architectures
> (PPC6xx, PPC4xx, ARM Kirkwood, etc.), and see a number of build
> issues.  I started reportung these:
> http://bugzilla.pokylinux.org/show_bug.cgi?id=572
> http://bugzilla.pokylinux.org/show_bug.cgi?id=574
>
> Are there any plans to include PPC and ARM targets for example int he
> autobuilder testing?
>
This has been addressed by both Josh and RP.

>> Yes, this should build you can see the status of master on our build
>> machine at http://autobuilder.pokylinux.org:8010/waterfall we are
>> working on stabilizing the build (meta-toolchain-sdk is failing currently).
>
> What I cannot see (maybe I just don't know where to look) is if the
> autobuilder includes any PPC and ARM targets at all, and if so, which
> these are.
>
Again already answered.

>>> Yes, it is unrelated. It's one of the targets I use for testing.
>>>
>> You should investigate creating a BSP Layer such as meta-kilauea that
>> you can put your changes into.
>
> Sorry for asking stupid questions - I'm still pretty new to Poky and
> haven't really understood some of the concepts: what would be the
> benefit (for me, or for the project) of such a layer?  Why not adding
> just another machine configuration?
>
The intent of the core metadata provided with poky is that it is stable 
and tested regularly, so a core set of machines (including qemu) for 
each major architecture are chosen.  These are maintained and QA'ed by 
the Yocto maintainers.

We help support layers where other machines configurations can reside 
and are maintained and tested by their contributors, but are not part of 
the core metadata.

As the community builds a clearer policy and selection mechanism will be 
developed.

Sau!

>> Thanks again, if you find more problems please let us now and we will
>> pull the changes.
>
> Thanks!
>
> Best regards,
>
> Wolfgang Denk
>