[oe] Where do I override DISTRO_FEATURES?

[Denys Dmytriyenko]

On Tue, May 15, 2012 at 06:44:10PM +0200, Thilo Fromm wrote:
> Hello,
> 
> >> I'm trying to remove an element from DISTRO_FEATURES (specifically
> >> "ld-is-gold"), but I am unable to find the right spot to do it. The
> >> distribution we're using (Angstrom, as it happens) sets this in
> >> conf/distro/angstrom-v2012.x.conf. My machine configuration is the
> >> wrong spot to modify DISTRO_FEATURES, since it will be processed
> >> first. local.conf is not working, too.
> >>
> >> So could anybody please tell me where I need to put my
> >>
> >> DISTRO_FEATURES = "${@'${DISTRO_FEATURES}}'.replace('ld-is-gold',  '')}"
> >>
> >> so it applies for the build?
> >
> > Unfortunately such hacks only work for variables that are not set within the
> > distro configuration, which is applied after local.conf.
> 
> I see. Fortunately I can require conf/distro/angstrom-v2012.x.conf in
> my own distro config file.
> 
> > Ultimately you shouldn't really do this. If you want to change distro policy
> > then you really ought to have your own distro configuration, or try to work
> > with the existing distro to fix whatever problem exists.
> 
> It's a backwards compatibility thing: we're bound to gcc-4.5 (we have
> kernel build issues with newer gcc versions; we're nailed to
> linux-2.6.37 thanks to lack of support by Texas Instruments) which
> fails to detect the correct version of binutils GOLD (LD would work)
> and therefore misses critical features which break the build later on.
> I won't, however, try to convince the Angstrom guys to further support
> ancient toolchains and make gold optional again just because of TI's
> laziness.

I think you are severely misinformed! Above issues (binutils-2.20/gcc-4.5 
requirement and gold ld problem with Thumb) were already fixed. I've been 
testing the builds with gcc-4.6 and binutils-2.22 for few weeks and even 
gcc-4.7 with gold linker since last week. I don't know what layer you are 
using, but you may need to update, if you are using meta-ti.

Otherwise, if your platform is not directly supported by meta-ti, please send 
the bug report with the error message to meta-ti mailing list and I'll try to 
address it.

As of linux-2.6.37 for your specific platform - this one I can't help with, 
you would need to talk to your TI rep from the division that makes the 
platform and convince them to provide support for newer kernels.

-- 
Denys