Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain-eglibc.inc: Set TARGET_OS = linux-gnuspe for e500
Date: Sun, 30 Aug 2009 11:33:24 +0200	[thread overview]
Message-ID: <h7dh14$47o$1@ger.gmane.org> (raw)
In-Reply-To: <1251620948.4215.673.camel@lenovo.internal.reciva.com>

On 30-08-09 10:29, Phil Blundell wrote:
> On Sun, 2009-08-30 at 09:10 +0100, Phil Blundell wrote:
>> On Sat, 2009-08-29 at 18:22 -0700, Khem Raj wrote:
>>> We can override only for powerpc second time around. So changing it
>> to
>>>
>>> TARGET_OS_powerpc =
>>> "linux${@['','-gnuspe'][bb.data.getVar('TARGET_ARCH',d,1) in ['ppc',
>>> 'powerpc'] and bb.data.getVar('MACHINE',d) in ['calamari',
>> 'tqm8540']]}"
>>>
>>> will that be ok ?
>>
>> That's better, but it still doesn't seem terribly elegant.  I also
>> remain slightly unconvinced that the eglibc-specific file is,
>> conceptually, the right place for this logic.
>
> Actually, there is still a bigger problem with this change: it will
> cause the ABI to change in a semi-random way depending on the selected
> MACHINE and this will screw up people who are trying to do multimachine
> builds.
>
> For example, if I set MACHINE=calamari and then bitbake micro-image, it
> will select linux-gnuspe and I will presumably get the SPE ABI.  But
> then, if I set MACHINE=efika, say, and build another package in the same
> tree, it'll now select regular linux and the ABI will change, although
> this won't be reflected in the naming of the output packages: they'll
> all just be named "powerpc".

The efika ones are named 'ppc603e' fwiw.

regards,

Koen




  parent reply	other threads:[~2009-08-30  9:52 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 [this message]
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
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='h7dh14$47o$1@ger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox