From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: commit 4d6a63850b4dc7ca2f060aedda26ddf4efa0e5cc
Date: Tue, 06 Jul 2010 15:49:37 -0700 [thread overview]
Message-ID: <4C33B301.7010006@mentor.com> (raw)
In-Reply-To: <i108p5$hd$1@dough.gmane.org>
Koen Kooi wrote:
> +PREFERRED_VERSION_gcc-cross = "4.1.2"
> +PREFERRED_VERSION_gcc-cross-initial = "4.1.2"
> +PREFERRED_VERSION_gcc-cross-intermediate = "4.1.2"
> +PREFERRED_VERSION_binutils = "2.17.50.0.12"
> +PREFERRED_VERSION_binutils-cross = "2.17.50.0.12"
[snip]
> do NOT belong in a machine.conf (or machine include). Those belong in
> the distro (or local.conf), not in the machine.
Just putting this out there (and it's indeed _not_ how things are
today). Why would we not want to move towards having this kind of stuff
be in the tune-ARCH.inc file, when a specific version is really needed
(more avr32 or new'ish core on an existing overall arch) ? Yes, it
should be up to the distro to say "we want 4.4.x + 2.20.x" or whatever,
but then we also get the downside of "special case, XXXX only works well
with 4.3.4 + 2.19.x" or what have you, and those special cases get
introduced in one place and copy/pasted elsewhere.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-06 22:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 21:55 commit 4d6a63850b4dc7ca2f060aedda26ddf4efa0e5cc Koen Kooi
2010-07-06 22:49 ` Tom Rini [this message]
2010-07-07 7:17 ` Koen Kooi
2010-07-07 8:22 ` Frans Meulenbroeks
2010-07-07 8:30 ` Koen Kooi
2010-07-07 9:24 ` Frans Meulenbroeks
2010-07-07 14:23 ` Philip Balister
2010-07-08 0:27 ` Khem Raj
2010-07-08 6:45 ` Frans Meulenbroeks
2010-07-08 0:18 ` Khem Raj
2010-07-08 1:04 ` Tom Rini
2010-07-07 7:01 ` Frans Meulenbroeks
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=4C33B301.7010006@mentor.com \
--to=tom_rini@mentor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox