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 961B91386F3 for ; Fri, 14 Aug 2015 07:52:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E669A14218; Fri, 14 Aug 2015 07:52:43 +0000 (UTC) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) (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 65AE1E07EA; Fri, 14 Aug 2015 07:52:42 +0000 (UTC) Received: by wicja10 with SMTP id ja10so10100202wic.1; Fri, 14 Aug 2015 00:52:41 -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=yyIArJXHrsMFop3rZ+4i70xPx+v8tvzM4KT5FLQ20VA=; b=pjw0sEi/3DcesBGVd3kn1s4eVXbRIUUQRGTocrvw+0EEGFhQXz55CuZrRDAbTVpuAg KfPrIi2XONF590xaioOm/PirJfgRB4A/+1pHjG22V6x+R8Lr9GIgI1mlTYkv8rMDEBS0 dRRY8QAVxDTXRQvczVFLT8BYOrZEx0ogGaiqkXpyXCRgmFAF5KntOW0UPfpgRuGptwvd h1zU4rp9SqwJPT0kFtP9MsrWYefGQ45ZBZM/BRKf0+4RAgl+EhKlhxYSaVDa6DBYqq/O omQe0HNj5+JbTefq2Qidddouro2l8v17D7mgRuShSCs6TmHsvuEQCwllxXQWuoDAVR02 GMsg== 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 X-Received: by 10.180.97.134 with SMTP id ea6mr4131869wib.63.1439538761249; Fri, 14 Aug 2015 00:52:41 -0700 (PDT) Received: by 10.27.216.203 with HTTP; Fri, 14 Aug 2015 00:52:41 -0700 (PDT) In-Reply-To: <20150812074716.GA23037@vapier> References: <20150811104937.089235f7@red.yakaraplc.local> <55CA07B6.5000905@gentoo.org> <55CA0A91.7020000@gentoo.org> <20150812035001.GE9481@vapier> <20150812074716.GA23037@vapier> Date: Fri, 14 Aug 2015 15:52:41 +0800 Message-ID: Subject: Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments From: Leno Hou To: Leno Hou , gentoo-dev@lists.gentoo.org, gentoo-powerpc@lists.gentoo.org, "Anthony G. Basile" , Mike Frysinger Content-Type: multipart/alternative; boundary=90e6ba181ad88137e6051d40bca8 X-Archives-Salt: 19e3b58c-eacc-4f31-878a-a5e0b65260a4 X-Archives-Hash: 113336d7950b895a811723df7f3f3809 --90e6ba181ad88137e6051d40bca8 Content-Type: text/plain; charset=UTF-8 On Wed, Aug 12, 2015 at 3:47 PM, Mike Frysinger wrote: > On 12 Aug 2015 15:20, Leno Hou wrote: > > 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 ? > > you probably want to create a new profile dir: > profiles/arch/powerpc/ppc64/little-endian/ > then add a make.defaults file with the right CHOST defaults. as we find > packages that have problems on little endian, that provides you a safe > space to mask features too. > > then create a new target for linux users: > > profiles/default/linux/powerpc/ppc64/13.0/64bit-userland/little-endian/ > that'll inherit the arch/powerpc/ppc64/little-endian parent > > > 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' > > you mean my bootstrap-portage script ? > See my comments in below mail. > > > **Most importantly, Any Ideas/steps of how to porting gentoo on ppc64le > > architecture?** > > do you have hardware ? then it's simply a matter of booting Gentoo in it > and > filing/fixing bugs :). > YES. We have KVM virtual machine of ppc64le. Can we booting/filing/fixing by KVM ? > -mike > Greetings !~~ *What I have done according to your suggestions.* Once you have these packages, you can easily install Portage. root #wget http://distfiles.gentoo.org/distfiles/portage-2.2.20.tar.bz2 root #tar -xvf portage-2.2.20 root #cd portage-2.2.20 && python setup.py install 1, sync up and we should have our Portage tree! root #emerge --sync Then we need to create a new profile for the new architecture ppc64le: root #cd /usr/portage/profiles/arch/powerpc/ppc64/ && mkdir little-endian root #cd little-endian root #echo '..' > parent root #cat << EOF > make.defaults CHOST="powerpc64le-linux-gnu" EOF 2, create a new target for linux users: root #cd /usr/portage/profiles/default/linux/powerpc/ppc64/13.0/64bit-userland/ root #mkdir little-endian && cd little-endian root #cat << EOF > parent .. ../../../../../../../arch/powerpc/ppc64/little-endian EOF root #cd /etc/portage root #ln -s ../../usr/portage/profiles/default/linux/powerpc/ppc64/13.0/64bit-userland/little-endian make.profile root #cd /etc/portage root #cat << EOF > make.conf PORTDIR_OVERLAY=/usr/local/portage MAKEOPTS="-j8" CFLAGS="-mcpu=power8 -mtune=power8 -O2 -pipe -I/gentoo/usr/include -L/gentoo/usr/lib64 -L/gentoo/lib -L/gentoo/lib64 -lpthread " CXXFLAGS="${CFLAGS}" CPPFLAGS="${CFLAGS}" LDFLAGS="-I/gentoo/usr/include -L/gentoo/usr/lib64 -L/gentoo/lib -L/gentoo/lib64 -lpthread " LC_ALL="en_US.UTF-8" FEATURES="buildpkg" USE="python_targets_python2_7" EOF 3, Fix Problem with sandbox root #apt-get install pax-utils build-essential gawk root # emerge --nodeps --ask sandbox 4, Build the whole system root #ROOT=/gentoo emerge @system Results: https://bpaste.net/show/e6db5a5a70aa Should `ROOT=/gentoo emerge glibc` or `ROOT=/gentoo emerge gcc` first to fix the circle dependencies ? Please let me know forward/steps to port gentoo on ppc64le. /etc/portage/package.accept_keywords in ppc64le and bug reports as following links. >=dev-libs/libffi-3.2.1 ~ppc64 >=dev-libs/gmp-6.0.0a ~ppc64 Links: https://bugzilla.redhat.com/show_bug.cgi?id=1083429 https://github.com/ffi/ffi/issues/413 --90e6ba181ad88137e6051d40bca8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On W= ed, Aug 12, 2015 at 3:47 PM, Mike Frysinger <vapier@gentoo.org> wrote:
On 12 Aug 2015 15:20, Leno H= ou wrote:
> 2.=C2=A0 How to control endian difference via profiles ? i.e.=C2=A0 *H= ow to get
> ppc64le as a full stage/profile along side ppc64* ?
>=C2=A0 =C2=A0 =C2=A0 Could you give me in detail ?

you probably want to create a new profile dir:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 profiles/arch/powerpc/ppc64/little-endian/
then add a make.defaults file with the right CHOST defaults.=C2=A0 as we fi= nd
packages that have problems on little endian, that provides you a safe
space to mask features too.

then create a new target for linux users:
=C2=A0 =C2=A0 =C2=A0 =C2=A0 profiles/default/linux/powerpc/ppc64/13.0/64bit= -userland/little-endian/
that'll inherit the arch/powerpc/ppc64/little-endian parent

> 5.=C2=A0 https://wiki.gentoo.org/wiki/Porting=C2=A0 =C2= =A0The Section 'Converting to
> Gentoo' needs to be updated.
>=C2=A0 =C2=A0 =C2=A0 From portage-2.2.20 on, please download portage an= d install it by
> 'python setup.py install'

you mean my bootstrap-portage script ?

See my comments in below mail.=C2=A0

> **Most importantly, Any Ideas/steps of how to=C2=A0 porting gentoo on= =C2=A0 ppc64le
> architecture?**

do you have hardware ?=C2=A0 then it's simply a matter of booting Gento= o in it and
filing/fixing bugs :).
=C2=A0
YES. We have K= VM virtual machine of ppc64le.=C2=A0 Can we booting/filing/fixing by KVM ?<= /div>
-mike

Greet= ings !~~

=C2=A0
<= div>
What I have done according to your suggestions.
<= br>
Once you have these packages, you can easily install Portage.= =C2=A0
=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sh= ould `ROOT=3D/gentoo emerge glibc` =C2=A0or `ROOT=3D/gentoo emerge gcc` fir= st to fix the circle dependencies ?=C2=A0
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0Please let me know forward/steps to port gentoo on ppc6= 4le.
=C2=A0=C2=A0
=C2=A0/etc/por= tage/package.accept_keywords =C2=A0in ppc64le and bug reports as following = links.
>=3Dde= v-libs/libffi-3.2.1 ~ppc64
>=3Ddev-libs/= gmp-6.0.0a ~ppc64

Links:


--90e6ba181ad88137e6051d40bca8--