Maintenance on older branches, e.g. bernard

Maintenance on older branches, e.g. bernard

[Elvis Dowson]

Hi,
       I just noticed that if one were to try switching to an older poky branch, say bernard, there are a few errors:

e.g. meta-yocto layer doesn't have a conf folder. 

Also if you use one of the tags, e.g. bernard-5.0, bernard-5.0.1, bernard-5.0.2, you can run into build failures.

I think at the very least, one should be able to build successfully off one of the older branches, and perhaps it should be part of the regular regression tests?

I'm just going to try to revert to bernard branch, temporarily, to see if my root filesystem dynamic linker issues for my powerpc440 target goes away with gcc-4.5.1.

Best regards,

Elvis Dowson

Re: Maintenance on older branches, e.g. bernard

[Scott Garman]

On 08/08/2012 11:20 AM, Elvis Dowson wrote:
> Hi, I just noticed that if one were to try switching to an older poky
> branch, say bernard, there are a few errors:
>
> e.g. meta-yocto layer doesn't have a conf folder.
>
> Also if you use one of the tags, e.g. bernard-5.0, bernard-5.0.1,
> bernard-5.0.2, you can run into build failures.
>
> I think at the very least, one should be able to build successfully
> off one of the older branches, and perhaps it should be part of the
> regular regression tests?

When you say "build successfully", how do you define that? Building 
core-image-minimal? -sato? -lsb? For which machines? On how many host 
distros?

We have a problem of scale here which is why bernard (now three stable 
releases old) is no longer undergoing active maintenance or regression 
testing by the core team.

This is where the community or a partner organization with a financial 
interest in supporting that release for their customers needs to step 
in. As time goes on, we're seeing more commercial adoption our releases 
and I think we'll see more of this for the recent releases (edison and 
denzil in particular, but bernard came out when the Yocto Project was 
still fairly new).

IMO,

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center

Re: Maintenance on older branches, e.g. bernard

[Elvis Dowson]

Hi Scott,

On Aug 8, 2012, at 10:39 PM, Scott Garman wrote:

> 
> When you say "build successfully", how do you define that? Building core-image-minimal? -sato? -lsb? For which machines? On how many host distros?
> 
> We have a problem of scale here which is why bernard (now three stable releases old) is no longer undergoing active maintenance or regression testing by the core team.
> 
> This is where the community or a partner organization with a financial interest in supporting that release for their customers needs to step in. As time goes on, we're seeing more commercial adoption our releases and I think we'll see more of this for the recent releases (edison and denzil in particular, but bernard came out when the Yocto Project was still fairly new).

At the moment, I'm focussing on PowerPC440 CPU support. I usually build two targets core-image-minimal and meta-toolchain, using Ubuntu 12.04 LTS.

I've temporarily switched to the older bernard release, because it was known to have worked for the Xilinx Virtex-5 FPGA PowerPC440 cpu. 

I've spent over 5 weeks, incrementally trying to isolate where the problem was with the latest yocto master builds for the PowerPC440 cpu, and thanks to some timely help from Khem, have narrowed it down to a dynamic linker issue (gcc-4.7.2 & kernel-3.3.0).

I'm just going to switch temporarily to gcc-4.5.1, and check to see if the dynamic linker issue goes away, then decide from there what to do next.

Best regards,

Elvis Dowson