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 521001386F3 for ; Wed, 12 Aug 2015 07:20:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DBEF4E07EA; Wed, 12 Aug 2015 07:20:08 +0000 (UTC) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8054FE07E0; Wed, 12 Aug 2015 07:20:07 +0000 (UTC) Received: by wibhh20 with SMTP id hh20so15110011wib.0; Wed, 12 Aug 2015 00:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sj7gFfay7u+o8kw9BrKxf+ib3Z8JucAfDA063qaVY2o=; b=ekIfF8f34A1/lgV25P+DnaXDnnIV78enx86crVbRAVg+GABaH8PkwyE6+H7tPOSByh xIVXSBWdj1OENQ7BeuXZ6PWK4M14XeW/Woa3tGnlbNS2Ab8UYm8o2TpajylSoTAiAntu g924q0DV5S4vliwI2d+Uiv5cpTO6fbD9XKNLOh9e2W7eDXosJcz5LEhqUDZBcMohzy3d N3PMlBlfMn2MusM9S0CfzIaWxz2jEzNZzcCAgfNhw2YWhQj603H3xZwvAZEjOWaaPVgF pI92VPtUcs8vCW8qDLlHDQsvkv84t+Zb9m4cYF9s/LxRyAQjNbge9BeOWOAwrT2BV7ao 6NrQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo on PowerPC X-BeenThere: gentoo-powerpc@gentoo.org X-BeenThere: gentoo-powerpc@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.194.175.233 with SMTP id cd9mr26449568wjc.68.1439364006183; Wed, 12 Aug 2015 00:20:06 -0700 (PDT) Received: by 10.27.216.203 with HTTP; Wed, 12 Aug 2015 00:20:06 -0700 (PDT) In-Reply-To: <20150812035001.GE9481@vapier> References: <20150811104937.089235f7@red.yakaraplc.local> <55CA07B6.5000905@gentoo.org> <55CA0A91.7020000@gentoo.org> <20150812035001.GE9481@vapier> Date: Wed, 12 Aug 2015 15:20:06 +0800 Message-ID: Subject: [gentoo-powerpc] Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments From: Leno Hou To: gentoo-dev@lists.gentoo.org, gentoo-powerpc@lists.gentoo.org, "Anthony G. Basile" , Mike Frysinger Content-Type: multipart/alternative; boundary=089e0149371e4a873b051d180c17 X-Archives-Salt: 353d377f-d848-4ba1-a399-dccff2d04ef2 X-Archives-Hash: d3519e1ffc4f802854fb174b0f1ba7f7 --089e0149371e4a873b051d180c17 Content-Type: text/plain; charset=UTF-8 On Wed, Aug 12, 2015 at 11:50 AM, Mike Frysinger wrote: > On 11 Aug 2015 10:45, Anthony G. Basile wrote: > > On 8/11/15 10:33 AM, 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? > > > > We would leverage this on ppc64 keyword. It is a bit dangerous to claim > > that a pkg stable on ppc64 is stable on ppc64le, but we would live with > > that risk. Ideally you should test on both. The situation is analogous > > to mips where there are many different ISAs and both be and le. It is > > one of the reasons mips is hard to move back into stable. But having > > stable keywords is really nice when it comes to building and maintaining > > stages and keeping base pkgs versions in sync with the other arches. > > For this reason, I would even been in favor of restoring stable mips > > with the understanding that "stable" carries something of a risk when > > crossing the be/le boundry, or the mips I vs mips III, or 32 vs 64, etc. > > yes, we should just re-use the existing KEYWORDS and control the endian > differences via profiles. it's how other arches (mips, ppc, arm, arm64) > are handled currently. > > note: people have already built Gentoo for ppc little endian, but that > tends to only be used in embedded setups, so the builds don't get published > like other arches as stages. -mike > 1. I have successfully complied ppc64le chroot environment manually. General Steps that omitted modify USE flag are here. https://docs.google.com/document/d/1zGO5Gvu4DGPX7Pn70q5vbW_uF___4h8_pIpOtoOEdnY/edit?usp=sharing 2. How to control endian difference via profiles ? i.e. *How to get ppc64le as a full stage/profile along side ppc64* ? Could you give me in detail ? 3. ppc64 already have stage3, why ppc64le tends to only be used in embedded setups ? If embedded setups, please let me know any forward/ steps . http://distfiles.gentoo.org/releases/ppc/autobuilds/current-iso/ 4. I would like become a developer of porting gentoo on ppc64le. Anyone could help/mentor me to join this project ? https://wiki.gentoo.org/wiki/Project:PowerPC appreciated your assistance and help. 5. https://wiki.gentoo.org/wiki/Porting The Section 'Converting to Gentoo' needs to be updated. From portage-2.2.20 on, please download portage and install it by 'python setup.py install' **Most importantly, Any Ideas/steps of how to porting gentoo on ppc64le architecture?** Leno Hou E-mail: lenohou@gmail.com --089e0149371e4a873b051d180c17 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On W= ed, Aug 12, 2015 at 11:50 AM, Mike Frysinger <vapier@gentoo.org> wrote:
On 11 Aug 2= 015 10:45, Anthony G. Basile wrote:
> On 8/11/15 10:33 AM, 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 ef= fort.
> >>=C2=A0 =C2=A02. Some PowerPC user, little endian apparently fe= els 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 v= s ppc64,
> > and ppc64le vs amd64 ?=C2=A0 Obviously kernels will differ, but i= n terms of
> > C/C++/other compiled source code what needs to change?
> >
> > If all this needs is its own profile for a CHOST/CBUILD specifica= tion
> > and it can leverage an existing keyword, then this should be rath= er
> > simple to implement yes?
>
> We would leverage this on ppc64 keyword.=C2=A0 It is a bit dangerous t= o claim
> that a pkg stable on ppc64 is stable on ppc64le, but we would live wit= h
> that risk.=C2=A0 Ideally you should test on both.=C2=A0 The situation = is analogous
> to mips where there are many different ISAs and both be and le.=C2=A0 = It is
> one of the reasons mips is hard to move back into stable.=C2=A0 But ha= ving
> stable keywords is really nice when it comes to building and maintaini= ng
> stages and keeping base pkgs versions in sync with the other arches. > For this reason, I would even been in favor of restoring stable mips > with the understanding that "stable" carries something of a = risk when
> crossing the be/le boundry, or the mips I vs mips III, or 32 vs 64, et= c.

yes, we should just re-use the existing KEYWORDS and control the end= ian
differences via profiles.=C2=A0 it's how other arches (mips, ppc= , arm, arm64)
are handled currently.

note: people have already built Gentoo for ppc little endian, but that
tends to only be used in embedded setups, so the builds don't get publi= shed
like other arches as stages.
-mike


1.= =C2=A0 I have successfully complied ppc64le chroot environment manually.
=C2=A0 =C2=A0 =C2=A0 General Steps that omitted modify USE flag ar= e here.
=C2=A0=C2=A0
2.=C2=A0 = How to control endian difference via profiles ? i.e. =C2=A0How to get pp= c64le as a full stage/profile along side ppc64=C2=A0?
=C2=A0 = =C2=A0 =C2=A0Could you give me in detail ?=C2=A0

3= . =C2=A0ppc64 already have stage3, =C2=A0why ppc64le tends to only be used = in embedded setups ?=C2=A0 If embedded setups, please
=C2=A0 =C2= =A0 =C2=A0let me know any forward/ steps .

4.=C2=A0 I would like become a developer of porting gento= o on ppc64le.=C2=A0 Anyone could help/mentor me to join this project ?=C2= =A0
=C2=A0 =C2=A0=C2=A0https://wiki.gentoo.org/wiki/Project:PowerPC=C2=A0=C2=A0= appreciated your assistance and help.

5. =C2=A0https://wiki.gentoo.org/wiki/= Porting=C2=A0 =C2=A0The Section 'Converting to Gentoo' needs to= be updated. =C2=A0
=C2=A0 =C2=A0 =C2=A0From portage-2.2.20 on, p= lease download portage and install it by 'python setup.py install'<= /div>
=C2=A0 =C2=A0 =C2=A0
*Most importantly,=C2=A0Any Ideas/steps of how to =C2=A0porti= ng gentoo on =C2=A0ppc64le architecture?*

Leno Hou

--089e0149371e4a873b051d180c17--