From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C845A1397D3 for ; Tue, 11 Aug 2015 14:44:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 05625E087B; Tue, 11 Aug 2015 14:44:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1B33CE085B for ; Tue, 11 Aug 2015 14:44:24 +0000 (UTC) Received: from red.yakaraplc.local (host213-123-185-55.in-addr.btopenworld.com [213.123.185.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: chewi) by smtp.gentoo.org (Postfix) with ESMTPSA id BEC5B340CA2 for ; Tue, 11 Aug 2015 14:44:23 +0000 (UTC) Date: Tue, 11 Aug 2015 15:44:16 +0100 From: James Le Cuirot To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments Message-ID: <20150811154416.454e7cae@red.yakaraplc.local> In-Reply-To: <55CA07B6.5000905@gentoo.org> References: <20150811104937.089235f7@red.yakaraplc.local> <55CA07B6.5000905@gentoo.org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 16e97612-d54a-4fd2-9170-23bbce4fc330 X-Archives-Hash: 4fee89b01a1b938aaa89089e2842efa7 On Tue, 11 Aug 2015 10:33:26 -0400 Ian Stakenvicius wrote: > On 11/08/15 06:11 AM, Leno Hou wrote: > > I think ppc64le would become popular, > > https://en.wikipedia.org/wiki/Ppc64. > > > > 1. enable porting x86 Linux based application with minimal effort. > > 2. Some PowerPC user, little endian apparently feels cheap, wrong, > > and PCish. 3. Other distrbutions like Ubuntu, Redhat and SUSE > > already support little endian in powerpc. > > > > > > In terms of the codepaths, what's different between ppc64le vs ppc64, > and ppc64le vs amd64 ? Obviously kernels will differ, but in terms of > C/C++/other compiled source code what needs to change? > > If all this needs is its own profile for a CHOST/CBUILD specification > and it can leverage an existing keyword, then this should be rather > simple to implement yes? I spoke to blueness in #gentoo-powerpc and he basically said the same thing, that the existing ppc64 keyword should suffice. He noted that we do not have different keywords for every mips variant because that would be a lot of keywords! Stage 3 tarballs (possibly cross-compiled) could be provided and some initial work could be done to ensure they actually function but beyond that, endian issues would simply be dealt with as they are reported. -- James Le Cuirot (chewi) Gentoo Linux Developer