public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Leno Hou <lenohou@gmail.com>
To: Leno Hou <lenohou@gmail.com>,
	gentoo-dev@lists.gentoo.org,  gentoo-powerpc@lists.gentoo.org,
	"Anthony G. Basile" <blueness@gentoo.org>,
	 Mike Frysinger <vapier@gentoo.org>
Subject: Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments
Date: Fri, 14 Aug 2015 15:52:41 +0800	[thread overview]
Message-ID: <CAGQVrL8ei1py2LW2vNnwQbCa1r4gAeB4mfWg8iLatw9_a7c3Ww@mail.gmail.com> (raw)
In-Reply-To: <20150812074716.GA23037@vapier>

[-- Attachment #1: Type: text/plain, Size: 3467 bytes --]

On Wed, Aug 12, 2015 at 3:47 PM, Mike Frysinger <vapier@gentoo.org> 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

[-- Attachment #2: Type: text/html, Size: 7432 bytes --]

  parent reply	other threads:[~2015-08-14  7:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  9:22 [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments Leno Hou
2015-08-11  9:49 ` James Le Cuirot
2015-08-11 10:11   ` Leno Hou
2015-08-11 14:33     ` Ian Stakenvicius
2015-08-11 14:44       ` James Le Cuirot
2015-08-11 14:45       ` Anthony G. Basile
2015-08-12  3:50         ` Mike Frysinger
2015-08-12  7:20           ` Leno Hou
2015-08-12  7:47             ` Mike Frysinger
2015-08-12  8:30               ` Anthony G. Basile
2015-09-11 12:01                 ` Leno Hou
2015-09-11 14:18                   ` Ian Stakenvicius
2015-09-13 18:36                   ` Mike Gilbert
2015-09-17  6:53                   ` Leno Hou
2015-09-24 12:23                   ` Leno Hou
2015-09-25 18:27                     ` [gentoo-powerpc] " Luca Barbato
2015-09-26 19:16                     ` Anthony G. Basile
2015-10-21  8:55                       ` Kevin Zhao
2015-11-23 19:54                         ` Richard Yao
2015-09-17  7:06                 ` Leno Hou
2015-08-12  9:46               ` Shuai Zhao
2015-08-12  9:50                 ` [gentoo-powerpc] " Luca Barbato
2015-08-12 23:58               ` 姜渠
2015-08-13  3:19                 ` Mike Frysinger
2015-08-14  7:52               ` Leno Hou [this message]
2015-09-24 15:07                 ` Mike Frysinger
2015-09-25  2:32                   ` Leno Hou
2015-09-25  5:05                     ` Mike Frysinger
2015-09-25  7:34                       ` Anthony G. Basile
2015-09-25  9:09                         ` Leno Hou
2015-09-25 10:59                           ` Anthony G. Basile
2015-09-25 17:21                             ` Anthony G. Basile
2015-08-12  3:50   ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGQVrL8ei1py2LW2vNnwQbCa1r4gAeB4mfWg8iLatw9_a7c3Ww@mail.gmail.com \
    --to=lenohou@gmail.com \
    --cc=blueness@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-powerpc@lists.gentoo.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox