[OE-core] [PATCH 3/9] gcc-cross: Make gcc-cross-initial as the only intermediate gcc stage

Elvis Dowson elvis.dowson at gmail.com
Sat Oct 6 06:59:07 UTC 2012


Hi Khem,

On Aug 25, 2012, at 1:59 AM, Khem Raj wrote:

> On Friday, August 24, 2012, Elvis Dowson <elvis.dowson at gmail.com> wrote:
> >
> > On Aug 25, 2012, at 1:10 AM, Khem Raj wrote:
> >
> >> On Fri, Aug 24, 2012 at 2:08 PM, Elvis Dowson <elvis.dowson at gmail.com> wrote:
> >>>
> >>> I'm adapting my earlier gcc-4.5 recipes, to try and get them to build with
> >>> the latest poky master.
> >>>
> >>> I'm using eglibc-2.13, so it is possible for this version to drop the
> >>> gcc-cross-intermediate stage, or is it only with newer eglibc versions?
> >>>
> >>
> >> well it wont work with anything older than eglibc 2.16
> >
> > What should I do to get the gcc-4.5 recipes to continue to build, with eglib-2.13,
> > against the poky master branch? Should I retain the gcc-intermediate recipes?
> 
> Back port some patches I did for eglibc 2.16 and drop intermediate recipes

I've back ported the patches you did for eglibc-2.16 for eglibc-2.13, to use with my gcc-4.5 recipe, for the PowerPC 440 target. With that patch applied, in a local copy of my meta-openembedded/toolchain-layer, containing both the eglibc-2.13 and gcc-4.5, recipe,

building against the poky/master commit id works:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b0faebd1f07e1616004bd19664395932e7c2c48f
gcc-cross: Make gcc-cross-initial as the only intermediate gcc stage

I am able to get to the shell prompt, and get no crashes upto this point. The root file system seems to be working fine, and I am able to ping the host machine.

It is with the application of the next patch, that I get a an init crash on the console, as I have been seeing earlier. 

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=48df3fe947c4d900aa6b66d9d8352c0d9e59ebe4
eglibc: Fix eglibc-initial and let eglibc depend on it

I've narrowed down the init problem, to the application of the above patch, but I'm unable to figure out why it is failing. Any suggestions?

Best regards,

Elvis Dowson


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20121006/7e2d8787/attachment-0002.html>


More information about the Openembedded-core mailing list