[yocto] Maintenance on older branches, e.g. bernard

Elvis Dowson elvis.dowson at gmail.com
Wed Aug 8 11:52:53 PDT 2012


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


More information about the yocto mailing list