From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Where do I override DISTRO_FEATURES?
Date: Tue, 15 May 2012 16:16:20 -0400 [thread overview]
Message-ID: <20120515201620.GA14162@denix.org> (raw)
In-Reply-To: <CADZ6=at4UmAFwAgggrDYOs0L-rMQBNU1idmD+Eo9FGMoqnKq1g@mail.gmail.com>
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
next prev parent reply other threads:[~2012-05-15 20:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 16:12 Where do I override DISTRO_FEATURES? Thilo Fromm
2012-05-15 16:23 ` Paul Eggleton
2012-05-15 16:44 ` Thilo Fromm
2012-05-15 20:16 ` Denys Dmytriyenko [this message]
2012-05-16 8:30 ` Thilo Fromm
2012-05-15 20:19 ` Denys Dmytriyenko
2012-05-16 8:34 ` Thilo Fromm
2012-05-16 5:31 ` Koen Kooi
2012-05-16 8:37 ` Thilo Fromm
2012-05-16 20:55 ` R U Local
2012-05-16 21:19 ` Khem Raj
2012-05-17 0:35 ` Otavio Salvador
2012-05-18 7:42 ` Thilo Fromm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120515201620.GA14162@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.