app-emulation/rkt: add support for ppc64le arch

[houstar]

Issue Report

Feature Request

CoreOS Version

$ cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1248.0.0+2016-12-17-1006
VERSION_ID=1248.0.0
BUILD_ID=2016-12-17-1006
PRETTY_NAME="CoreOS 1248.0.0+2016-12-17-1006 (Ladybug)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

$ uname -a
Linux localhost 4.4.6-gentoo #1 SMP Thu Aug 4 07:38:22 2016 ppc64le POWER8E (raw), altivec supported CHRP IBM pSeries (emulated by qemu) GNU/Linux

### Environment ###
On powerpc64le platform

### Expected Behavior ###
emerge app-emulation/rkt successfully
### Actual Behavior ###
failed with emerge app-emulation/rkt

### Reproduction Steps ###

  1. emerge rkt
  2. failed with below log.
>>> Emerging (3 of 3) app-emulation/rkt-9999::coreos for /build/ppc64le-usr/
 * Running stacked hooks for pre_pkg_setup
 *    sysroot_build_bin_dir ...                                                                                                                 [ ok ]
 * Running stacked hooks for pre_src_unpack
 *    python_multilib_setup ...                                                                                                                 [ ok ]
>>> Unpacking source...
 * Cloning /mnt/host/source/src/third_party/rkt
Cloning into '/build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work/rkt-9999'...
done.
 * Copying source from /mnt/host/source/src/third_party/rkt
>>> Source unpacked in /build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work
>>> Preparing source in /build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work/rkt-9999 ...
 * Running eautoreconf in '/build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work/rkt-9999' ...
 * Running aclocal -I /build/ppc64le-usr/usr/share/aclocal ...                                                                                  [ ok ]
 * Running autoconf --force -I /build/ppc64le-usr/usr/share/aclocal ...                                                                         [ ok ]
 * Running elibtoolize in: rkt-9999/
>>> Source prepared.
>>> Configuring source in /build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work/rkt-9999 ...
>>> Working in BUILD_DIR: "/build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work/rkt-9999"
 * econf: updating rkt-9999/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating rkt-9999/config.guess with /usr/share/gnuconfig/config.guess
/build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/work/rkt-9999/configure --prefix=/usr --build=powerpc64le-unknown-linux-gnu --host=powerpc64le-unknown-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --docdir=/usr/share/doc/rkt-9999 --with-coreos-local-pxe-image-path=/build/ppc64le-usr/var/tmp/portage/app-emulation/rkt-9999/distdir/rkt-pxe-ppc64-usr-1235.0.0.img --with-coreos-local-pxe-image-systemd-version=v231 --disable-tpm --with-stage1-flavors=coreos,fly --with-stage1-default-location=/usr/lib64/rkt/stage1-images/stage1-coreos.aci
configure: loading site script /usr/share/config.site
checking for powerpc64le-unknown-linux-gnu-gcc... powerpc64le-unknown-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether powerpc64le-unknown-linux-gnu-gcc accepts -g... yes
checking for powerpc64le-unknown-linux-gnu-gcc option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether powerpc64le-unknown-linux-gnu-g++ accepts -g... yes
checking for bash... /bin/bash
checking for git... git
checking build system type... powerpc64le-unknown-linux-gnu
checking host system type... powerpc64le-unknown-linux-gnu
checking how to run the C preprocessor... powerpc64le-unknown-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for cat... cat
checking for comm... comm
checking for cpio... cpio
checking for gzip... gzip
checking for md5sum... md5sum
checking for mktemp... mktemp
checking for sort... sort
checking for touch... touch
checking for unsquashfs... unsquashfs
checking for wget... wget
configure: WARNING: * fly is an experimental stage1 implementation with almost no isolation and less features
checking for acl/libacl.h... yes
checking for dlfcn.h... yes
checking for printf in -lc... yes
checking whether C library provides setns function... yes
checking for gpg... gpg
configure: error: *** ppc64le: no arch support for stage1 flavors {coreos,kvm,src}

[houstar]

Hi @philips @marineam

Could you arrange someone to enable rkt on ppc64le platform? Thanks

-Leno Hou

[lucab]

@houstar you may try building only the fly and host flavours, which have been reported to work on ppc64le: https://github.com/coreos/rkt/pull/3315. All other flavours depend on a working coreos PXE image to build, thus the configure failure above.

[houstar]

OK. Thanks @lucab pointed out this bugs has been working on coreos/rkt#3315 and could you inform that If we have done with merge ppc64le patches in app-emulation/rkt 's master branch?