From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 18 Nov 2014 18:04:05 +0100 Subject: [Buildroot] [PATCH 1/2] arch/powerpc: add fsl e5500 and e6500 support In-Reply-To: <546B7B23.9030004@zacarias.com.ar> References: <1416266092-6465-1-git-send-email-gustavo@zacarias.com.ar> <1416266092-6465-2-git-send-email-gustavo@zacarias.com.ar> <546B5779.9010708@zacarias.com.ar> <20141118162020.02921a54@free-electrons.com> <546B7395.4040804@zacarias.com.ar> <20141118175637.49a03275@free-electrons.com> <546B7B23.9030004@zacarias.com.ar> Message-ID: <20141118180405.7ea733ae@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Gustavo Zacarias, On Tue, 18 Nov 2014 14:00:19 -0300, Gustavo Zacarias wrote: > 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. Unfortunately, it's typically the kind of thing that's very hard to do with kconfig, as it would require the ability to specify for each package for which multilib variant it should be built. Same issue as having a per-package "build this statically" or "build this with debugging symbol" option. Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com