From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC} Disable multilib in gcc recipes
Date: Thu, 01 Jul 2010 23:01:34 +0100 [thread overview]
Message-ID: <1278021694.30247.438.camel@rex> (raw)
In-Reply-To: <AANLkTilva4t_1fBYfzHthbUInh43adY9VYbU9EjgZL7V@mail.gmail.com>
On Thu, 2010-07-01 at 00:14 -0700, Khem Raj wrote:
> I would like to propose to remove building multilib with gcc recipes.
> It creates problems
> and we do not package correct bits on some platforms. As we tend to
> build toolchains keeping in mind the machine it is targetting I think
> multilib is not that significant
>
> Concerns ? comments?
I'm backing this. Currently multilib is broken and for a good
implementation we really needs a ground up proposal for how to handle it
well. I'm starting to look into the problem FWIW so I'd appreciate being
in the loop in any discussions.
Cheers,
Richard
next prev parent reply other threads:[~2010-07-01 22:06 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 [this message]
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
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=1278021694.30247.438.camel@rex \
--to=rpurdie@rpsys.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.