> > > So I doubt your problems will go away when moving from ELDK v5.5 to > > > v5.5.2; if you cannot fall back to ELDK v5.4 (gcc 4.7.2) you will have > > > to wait for ELDk v5.7 (gcc 4.9.1).
... > You (as a layer provider) should never hack meta/ . If you need to override > something, then such override should go into the meta-foo/ layer, which you > generated (meta-eldk in this case). Though I disagree that downgrading the > GCC version is a good way to go. > > Do we already know what's the stance of the Yocto guys on the GCC 4.8.x > problem? No, I just want to show that ELDK 5.5 and 5.6 can be made to work. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
