From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: commit 4d6a63850b4dc7ca2f060aedda26ddf4efa0e5cc
Date: Wed, 07 Jul 2010 09:17:59 +0200 [thread overview]
Message-ID: <i119n7$ej7$1@dough.gmane.org> (raw)
In-Reply-To: <4C33B301.7010006@mentor.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-07-10 00:49, Tom Rini wrote:
> 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) ?
Putting it in a tune-arch is not a problem, just put it in
conf/distro/include.
Experience has shown that putting it the machine includes is a bad idea,
It rots and after a while a new machine gets added that doesn't use said
machine include.
And not to mention the need to change DISTRO_PR for editing a
machine.conf, that's just backwards.
> 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.
So you have an include file in conf/distro that people can optionally
use or copy/paste. Not all distros can/want to support all machines in
OE. Angstrom tries to, but that's because it's the reference implemention :)
It boils down to this:
The distro needs to make a decision to do strange stuff to support a
platform. Silently forcing it is bad.
In this specific case no distro except angstrom has expressed interest
in supporting nios2, so we could even but this in an angstrom.inc.
Seriously, can the distro maintainers that are willing to support nios2
please raise their hands?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMNConMkyGM64RGpERAon3AJ9keLb8YBEVmCsvWzhEqb3qtLCWKgCfcX+4
kuDgy1Jqhl4qdAIVEWkiTfc=
=0Lny
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-07 7:23 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
2010-07-07 7:17 ` Koen Kooi [this message]
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='i119n7$ej7$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.