From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS = linux-gnuspe for e500
Date: Sat, 29 Aug 2009 09:53:24 +0100 [thread overview]
Message-ID: <1251536004.27780.75.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <19c1b8a90908290133l36f791b2lfe8db1a1c6f333b2@mail.gmail.com>
On Sat, 2009-08-29 at 01:33 -0700, Khem Raj wrote:
> TARGET_OS is really equivalent of TARGET_TRIPLET here and it is tied
> to system C library you choose.
> so logically it seems ok to me. You can also define it in distro confs but then
> you have to check like if LIBC == uclibc do one thing else LIBC =
> glibc do other thing
Well, I dunno. It seems like there are three parts to this
determination, really:
1) does the target hardware support SPE?
2) does the toolchain support it?
3) does the distro want to use it?
Of those, it seems fairly clear that (1) belongs in MACHINE.conf or some
similar place, and (3) belongs in DISTRO.conf or some part of it. The
only one of these that's really tied to the C library would seem to be
(2), and even there I would have thought it would be better for the libc
to just raise an error if it doesn't support the selected options rather
than trying to guess what they should be.
The same thing applies to the ARM EABI, incidentally: the choice of
whether to use EABI or the old ABI ought to be one that's made primarily
(or entirely) by the DISTRO. The current situation where parts of the
toolchain are guessing whether or not the EABI is wanted, based on
${MACHINE}, is somewhat unsatisfactory: it'd be perfectly legitimate,
for example, for a DISTRO to want to use eabi on h3900. The current
EABI logic that resides in sane-toolchain-xxx.inc seems like it is
really a misplaced piece of Angstrom policy.
p.
next prev parent reply other threads:[~2009-08-29 9:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 0:00 [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS = linux-gnuspe for e500 Khem Raj
2009-08-29 2:02 ` Tom Rini
2009-08-29 7:50 ` Khem Raj
2009-08-30 1:22 ` Khem Raj
2009-08-30 8:10 ` Phil Blundell
2009-08-30 8:29 ` Phil Blundell
2009-08-30 9:22 ` Khem Raj
2009-08-30 9:54 ` Phil Blundell
2009-08-30 10:38 ` Khem Raj
2009-08-30 11:18 ` Phil Blundell
2009-08-30 18:08 ` Khem Raj
2009-08-30 18:11 ` Khem Raj
2009-08-30 20:27 ` Phil Blundell
2009-08-30 9:33 ` Koen Kooi
2009-08-30 9:48 ` Khem Raj
2009-08-31 11:33 ` Marcin Juszkiewicz
2009-08-31 18:57 ` [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS?= " Khem Raj
2009-09-01 5:57 ` Khem Raj
2009-09-01 8:21 ` Dirk Opfer
2009-09-01 15:31 ` Khem Raj
2009-09-01 23:07 ` Khem Raj
2009-09-02 19:20 ` Khem Raj
2009-09-02 20:29 ` Phil Blundell
2009-09-02 21:07 ` Khem Raj
2009-09-03 4:36 ` Tom Rini
2009-09-03 5:15 ` Khem Raj
2009-09-03 9:32 ` Phil Blundell
2009-09-03 15:11 ` Khem Raj
2009-09-04 10:51 ` Phil Blundell
2009-09-04 12:45 ` Leon Woestenberg
2009-09-04 15:27 ` Khem Raj
2009-09-04 15:37 ` Phil Blundell
2009-09-04 17:34 ` Khem Raj
2009-09-04 18:59 ` Phil Blundell
2009-09-04 21:52 ` Khem Raj
2009-08-29 8:14 ` [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS = " Phil Blundell
2009-08-29 8:33 ` Khem Raj
2009-08-29 8:53 ` Phil Blundell [this message]
2009-08-29 14:30 ` Koen Kooi
2009-08-29 17:08 ` Khem Raj
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=1251536004.27780.75.camel@mill.internal.reciva.com \
--to=philb@gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox