From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC} Disable multilib in gcc recipes
Date: Mon, 05 Jul 2010 09:24:52 +0200 [thread overview]
Message-ID: <4C3188C4.2080402@vollmann.ch> (raw)
In-Reply-To: <AANLkTilFDDCYu-dFabnPFc34UwJGTIlwuMy1WcxPlUA_@mail.gmail.com>
On 07/04/10 19:52, Khem Raj wrote:
> On Sun, Jul 4, 2010 at 6:59 AM, Detlef Vollmann <dv@vollmann.ch> wrote:
>> But what you need to keep in mind if you actually drop multilib support
>> is that you need to rename the prefix for the SDK toolchains.
>> It would be bad if PowerPC 32-bit and 64-bit toolchains were both named
>> powerpc-angstrom-linux-
>
> I think that does not happen. toolchain prefix is generally ${TARGET_ARCH}-x-x
> for 64 bit powerpc TARGET_ARCH = "powerpc64"
But TARGET_ARCH typically doesn't include what typ of floating point
you have.
Detlef
next prev parent reply other threads:[~2010-07-05 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 7:14 [RFC} Disable multilib in gcc recipes Khem Raj
2010-07-01 8:04 ` Roman I Khimov
2010-07-01 22:01 ` Richard Purdie
2010-07-02 5:41 ` Roman I Khimov
2010-07-04 13:59 ` Detlef Vollmann
2010-07-04 17:52 ` Khem Raj
2010-07-05 7:24 ` Detlef Vollmann [this message]
2010-07-06 16:23 ` Tom Rini
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=4C3188C4.2080402@vollmann.ch \
--to=dv@vollmann.ch \
--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