From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and e6500 support
Date: Tue, 18 Nov 2014 14:00:19 -0300 [thread overview]
Message-ID: <546B7B23.9030004@zacarias.com.ar> (raw)
In-Reply-To: <20141118175637.49a03275@free-electrons.com>
On 11/18/2014 01:56 PM, Thomas Petazzoni wrote:
> What do you call the full multilib dance?
>
> I guess if we go multilib, we should build the C library for both
> "variants", but then build the rest of the userspace with only one of
> the two variants, and keep the other variant just to build the special
> stuff (kernel, bootloader, etc.).
Building all (necessary) libraries as well to accomodate for ugly BLOBs
like the flash plugin or other cr^H^Hstuff like that, say i386 zlib and
more.
I don't think we want that.
Regards.
next prev parent reply other threads:[~2014-11-18 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 23:14 [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Gustavo Zacarias
2014-11-17 23:14 ` [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and " Gustavo Zacarias
2014-11-18 13:56 ` Matthew Weber
2014-11-18 14:28 ` Gustavo Zacarias
2014-11-18 15:20 ` Thomas Petazzoni
2014-11-18 16:28 ` Gustavo Zacarias
2014-11-18 16:56 ` Thomas Petazzoni
2014-11-18 17:00 ` Gustavo Zacarias [this message]
2014-11-18 17:04 ` Thomas Petazzoni
2014-11-18 18:31 ` Baruch Siach
2014-11-18 20:59 ` Thomas Petazzoni
2014-11-17 23:14 ` [Buildroot] [PATCH 2/2] package/gcc: set e5500 and e6500 version mask Gustavo Zacarias
2014-12-07 22:48 ` [Buildroot] [RFC PATCH 0/2] Add Freescale e5500 & e6500 support Thomas Petazzoni
2014-12-07 23:17 ` Gustavo Zacarias
2014-12-07 23:21 ` Thomas Petazzoni
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=546B7B23.9030004@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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