From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] siteinfo.bbclass: add entries for new x86_64 ABI targets
Date: Wed, 27 Jul 2011 16:41:43 -0700 [thread overview]
Message-ID: <4E30A237.2050702@mentor.com> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94DE667A45@orsmsx504.amr.corp.intel.com>
On 07/27/2011 04:27 PM, Kamble, Nitin A wrote:
>
>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Tom Rini
>> Sent: Wednesday, July 27, 2011 4:13 PM
>> To: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH 2/4] siteinfo.bbclass: add entries for
>> new x86_64 ABI targets
>>
>> On 07/27/2011 04:09 PM, nitin.a.kamble@intel.com wrote:
>>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>>>
>>> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
>>> ---
>>> meta/classes/siteinfo.bbclass | 14 +++++++++++++-
>>> 1 files changed, 13 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/meta/classes/siteinfo.bbclass
>> b/meta/classes/siteinfo.bbclass
>>> index 9dacd58..daa7946 100644
>>> --- a/meta/classes/siteinfo.bbclass
>>> +++ b/meta/classes/siteinfo.bbclass
>>> @@ -42,12 +42,15 @@ def siteinfo_data(d):
>>> "sh4": "endian-little bit-32 sh-common",
>>> "sparc": "endian-big bit-32",
>>> "viac3": "endian-little bit-32 ix86-common",
>>> - "x86_64": "endian-little bit-64",
>>> + "x86_64": "endian-little", # bitinfo specified in targetinfo
>>> }
>>> osinfo = {
>>> "darwin": "common-darwin",
>>> "darwin9": "common-darwin",
>>> "linux": "common-linux common-glibc",
>>> + "linux-gnu32": "common-linux common-glibc",
>>> + "linux-gnux32": "common-linux common-glibc",
>>> + "linux-gnu64": "common-linux common-glibc",
>>> "linux-gnueabi": "common-linux common-glibc",
>>> "linux-gnuspe": "common-linux common-glibc",
>>> "linux-uclibc": "common-linux common-uclibc",
>>> @@ -68,6 +71,15 @@ def siteinfo_data(d):
>>> "powerpc-linux-uclibcspe": "powerpc-linux powerpc32-linux
>> powerpc-linux-uclibc",
>>> "powerpc64-linux-gnuspe": "powerpc-linux powerpc64-linux",
>>> "powerpc64-linux": "powerpc-linux",
>>> + "x86_64-cygwin": "bit-64",
>>> + "x86_64-darvin": "bit-64",
>>> + "x86_64-darvin9": "bit-64",
>>
>> dar_v_in? :)
>>
>> Slightly more seriously, lets drop out ones we can't / aren't using,
>> wrt
>> hosts, until we're going to do them for real.
>
> Hi Tom,
> I don't know if they(cygwin, darvin) work or not, I just kept them in the same state. If they are not used/working, then it is good to clean them out.
Well, OSX is dar_w_in :)
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-07-27 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 23:09 [PATCH 0/4] Commits enabling x32 infrastructure in the master branch nitin.a.kamble
2011-07-27 23:09 ` [PATCH 1/4] toolchain-scripts & other classes: add TARGET_LD_ARCH & TARGET_AS_ARCH vars nitin.a.kamble
2011-07-27 23:09 ` [PATCH 2/4] siteinfo.bbclass: add entries for new x86_64 ABI targets nitin.a.kamble
2011-07-27 23:12 ` Tom Rini
2011-07-27 23:27 ` Kamble, Nitin A
2011-07-27 23:41 ` Tom Rini [this message]
2011-07-27 23:10 ` [PATCH 3/4] insane.bbclass: add entries for linux-gnu<ABI> nitin.a.kamble
2011-07-27 23:10 ` [PATCH 4/4] x86 tune inc files: add x32 abi tune parameters nitin.a.kamble
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=4E30A237.2050702@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@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