On Tue, Apr 19, 2016 at 6:33 PM, Anthony G. Basile <blueness@gentoo.org>
wrote:

>
> >> @everyone else on the list, i've been moving slowly on this because of
> >> time constraints.  i hope in may-ish once the semester is over to
> >> provide a working ppc64le to the community.
> >
> >
> >
> > Hi all,
> >
> >     To speed up the progress of provide a working ppc64le to the Gentoo
> > Community.
> >
> >     We're planning to make gentoo ppc64le to be merged in Q2 due to the
> > following reason.
> >
> > 1. We're successfully made gentoo stage3 and livecd for ppc64le platform,
> > please download in below
> >     [1]  stage3 for ppc64le
> > <
> https://drive.google.com/folderview?id=0B8O8TRm4UoiqMC03cVd6NGdnbHc&usp=sharing
> >
> >  , *already done*
> >     [2]  livecd for ppc64le
> > <
> https://drive.google.com/folderview?id=0B8O8TRm4UoiqMC03cVd6NGdnbHc&usp=sharing
> >,
> > ready for this Weekend( *April 22th*)
> > 2. We've opened  bug#580512 <
> https://bugs.gentoo.org/show_bug.cgi?id=580512> to
> > request and track some questions/problems related with ppc64le platform
> > 3. We've opened github PRs#1304 <
> https://github.com/gentoo/gentoo/pull/1304> to
> > merge the portage tree changes which is related to ppc64le platform
> > 4. We've pushed the portage tree changes in github repo named
> linux-on-power
> > <https://github.com/linux-on-power/gentoo>
> >
> > @Anthony, Could you help me to review and merge the patches ?
> >
> > Thanks in advance and any comments would be appreciated.
> >
>
>
> The osuosl power8 openstack is hard to work with.  right now i'm
> struggling with why networking doesn't work in a chroot, crippling wget
> and curl while ping works.  otherwise i'd probably have stage3 ppc64le's
> out already.  admittedly until the semester ends, i jsut don't have time.
>
> i did review those patches.  there are problems.
> 1) putting all these changes in one commit makes it impossible to
> selectively commit or revert changes to different packages.
>

Fixed ppc64le configure problem and split into 8 patches. These will be
find in github PRs#1304 <https://github.com/gentoo/gentoo/pull/1304> or in
gentoo-dev mail list.

2) the changes to config.sub need to go upstream
>

The package sys-devel/gnuconfig-9999999::gentoo from
https://savanah.gnu.org/projects/config has already fixed the problem with
./config.sub powerpc64le-unknown-linux-gnu problem

3) package.accept_keywords is not allowed in a profile. it short circuits
> arch testing for keywords and stablereq
>

So currently I'll put the package.accept_keywords into /etc/portage. How to
arch testing for keywords and stablereq?
Did we have auto test framework for arch testing in Gentoo Community?  For
example, Linux Test Project <https://linux-test-project.github.io>( abbrev.
LTP)
If we have some test strategy, anything could I help for this ?

4) you have numerous QA issues. there are still other problems. i would
> start by getting the changes to config.sub upstream to gnuconfig. See
> http://savannah.gnu.org/projects/config
>

For QA issues, *monsieur*  said that "Disregard errors. Stricter QA checks
have been turned on."
For config.sub, also we can change the app-crypt/shash/shash-0.2.6-r2
depends on sys-devel/gnuconfig package

src_prepare() {

+       rm config.sub

+ [ -f "EPREFIX/usr/share/gnuconfig/config.sub]" && \

+       ln -s "${EPREFIX}"/usr/share/gnuconfig/config.sub config.sub || die

  epatch "${FILESDIR}"/${PV}-manpage-fixes.patch

  epatch "${FILESDIR}"/${P}-binary-files.patch

 }

-Leno Hou