From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [93.97.173.237] (helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QqPV8-0006Jk-C9 for openembedded-core@lists.openembedded.org; Mon, 08 Aug 2011 15:04:14 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p78CxjBd002805; Mon, 8 Aug 2011 13:59:45 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02202-05; Mon, 8 Aug 2011 13:59:41 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p78Cxcqs002799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Aug 2011 13:59:38 +0100 From: Richard Purdie To: Kumar Gala In-Reply-To: References: Date: Mon, 08 Aug 2011 13:59:08 +0100 Message-ID: <1312808348.14274.188.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Virus-Scanned: amavisd-new at rpsys.net Cc: Patches and discussions about the oe-core layer Subject: Re: multilib theory & practice X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Aug 2011 13:04:14 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Sun, 2011-08-07 at 11:50 -0500, Kumar Gala wrote: > On Aug 6, 2011, at 3:56 PM, Kumar Gala wrote: > > > I'm looking at trying to get multilib working for powerpc. However I'm a bit lost in how this is suppose to work from a few different perspectives: > > > > 1. from user perspective (I'm starting with a 64-bit build in /lib64 and adding 32-bit that would be in /lib): > > > > (i've added in local/conf): > > require conf/multilib.conf > > MULTILIBS = "multilib:lib" > > DEFAULTTUNE_virtclass-multilib-lib = "powerpc" > > > > What should this end up producing? Do I get a 32-bit set of libs built automatically? What else do I need to do? > > > > 2. From a infrastructure point of view: > > > > * Do have a single compiler that is multi-arch or 2 compilers? (not sure how the x86_64 toolchain works today) > > * what areas should I investigate that might need tweaking that are arch specific? > > * should I see different task names for the new multilib builds? (or the 32-bit specific builds?) > > To add to this I'm wondering how we get proper eglibc for 32-bit, how we get proper gcc libs (libgcc, etc). As per my reply, we currently treat this as two separate toolchains so this makes this part of the problem very easy. Cheers, Richard