From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS?= linux-gnuspe for e500
Date: Mon, 31 Aug 2009 11:57:32 -0700 [thread overview]
Message-ID: <20090831185732.GA22032@gmail.com> (raw)
In-Reply-To: <200908311333.20189.marcin@juszkiewicz.com.pl>
On (31/08/09 13:33), Marcin Juszkiewicz wrote:
> What about using MACHINE_FEATURES (or CPU_FEATURES) for things like eabi/spe?
yes that is a very good idea.
>
> TARGET_OS = "linux-"
> if ARCH in [ppc,powerpc] and MACHINE_FEATURES.find('spe') then
>
> if LIBC=uclibc then
> TARGET_OS += "uclibc"
> fi
>
> TARGET_OS += "gnuspe"
> fi
>
> Same for adding eabi:
>
> TARGET_OS = "linux-"
> if ARCH in [arm,armeb] and MACHINE_FEATURES.find('eabi') then
>
> if LIBC=uclibc then
> TARGET_OS += "uclibc"
> fi
>
> TARGET_OS += "gnueabi"
> fi
>
> spe/eabi can be added to MACHINE_FEATURES in conf/machine/include/tune-* files
> and distros can choose do they support it or not by DISTRO_FEATURES (examples
> needs to be changed then to use COMBINED_FEATURES variable). This way no one
> has to change XY files just because he has new board with ppc500v2 core, we do
> not have to remember about armv4 devices which are not capable of EABI with
> gcc 4.3.x and older (but if they will support EABI in future we just change
> tune-strongarm.inc file).
seems a nice approach. Let me try to implement something on these lines.
>
> Regards,
> --
> JID: hrw@jabber.org
> Website: http://marcin.juszkiewicz.com.pl/
> LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2009-08-31 19:16 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 ` Khem Raj [this message]
2009-09-01 5:57 ` [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS?= " 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
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=20090831185732.GA22032@gmail.com \
--to=raj.khem@gmail.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