from:"Leno Hou"

[gentoo-dev] Gentoo@ppc64le docker image was hosted on Docker Hub!

2016-12-16 Thread Leno Hou

Gentoo@ppc64le docker image was hosted on Docker Hub! welcome have a try.

*1) For convenience which means you needn't to install gentoo anymore,
please use this gentoo@ppc64le docker image as follows.*

1. Pull gentoo@ppc64le docker images, you should install docker on your
ppc64le host firstly, then.
   #docker pull powerkvm/gentoo

2. Run this docker images, if you have to use some device, please use
--device to passthrough. e.g --device /dev/snd
  #docker run -it powerkvm/gentoo /bin/bash

3. Sync Portage tree
  #emerge --sync

4. Add ppc64le-overlay
 #emerge layman
 #layman -L
 #layman -a ppc64le
 # cat "source /var/lib/layman/make.conf" >> /etc/portage/make.conf

5. Then free to use this gentoo@ppc64le in docker. Thanks.

*2) I request in here to build gentoo livecd and stage3 for ppc64le that
will be hosted in Gentoo Official Website for public experimental. *

*Leno Hou*
E-mail :  leno...@gmail.com

[gentoo-dev][eselect][PATCH v1] add powerpc64le arch support * libs/package-manager.bash.in (arch()) fix can't determine architecture in powerpc64le

2016-12-11 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 libs/package-manager.bash.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libs/package-manager.bash.in b/libs/package-manager.bash.in
index aececfd..621f6ac 100644
--- a/libs/package-manager.bash.in
+++ b/libs/package-manager.bash.in
@@ -80,6 +80,7 @@ arch() {
mips*)  ret=mips;;
powerpc)ret=ppc ;;
powerpc64)  ret=ppc64   ;;
+   powerpc64le)ret=ppc64   ;;
s390*)  ret=s390;;
sh*)ret=sh  ;;
sparc)  ret=sparc   ;;
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 09/12] dev-libs/libverto: add elibtoolize w/ libverto to build for ppc64le

2016-06-28 Thread Leno Hou

This patch fixs mit-krb5 link with wrong libverto when emerge mit-krb5
Add elibtoolize will let's econf generate the configure for ppc64le
and build the correct libverto for mit-krb5 to use.

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 dev-libs/libverto/libverto-0.2.5-r1.ebuild | 3 ++-
 dev-libs/libverto/libverto-0.2.5.ebuild| 3 +++
 dev-libs/libverto/libverto-0.2.6.ebuild| 3 ++-
 3 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/dev-libs/libverto/libverto-0.2.5-r1.ebuild 
b/dev-libs/libverto/libverto-0.2.5-r1.ebuild
index cd1aecd..3d06f99 100644
--- a/dev-libs/libverto/libverto-0.2.5-r1.ebuild
+++ b/dev-libs/libverto/libverto-0.2.5-r1.ebuild
@@ -4,7 +4,7 @@
 
 EAPI=5
 
-inherit multilib-minimal
+inherit multilib-minimal libtool
 
 DESCRIPTION="Main event loop abstraction library"
 HOMEPAGE="https://fedorahosted.org/libverto/;
@@ -33,6 +33,7 @@ src_prepare() {
# callback on error, but we explicitly test for this behaviour.  Do not 
run
# tevent tests for now.
sed -i -e 's/def HAVE_TEVENT/ 0/' tests/test.h || die
+   elibtoolize
 }
 
 multilib_src_configure() {
diff --git a/dev-libs/libverto/libverto-0.2.5.ebuild 
b/dev-libs/libverto/libverto-0.2.5.ebuild
index 92642a9..9aac4aa 100644
--- a/dev-libs/libverto/libverto-0.2.5.ebuild
+++ b/dev-libs/libverto/libverto-0.2.5.ebuild
@@ -4,6 +4,8 @@
 
 EAPI=5
 
+inherit libtool
+
 DESCRIPTION="Main event loop abstraction library"
 HOMEPAGE="https://fedorahosted.org/libverto/;
 SRC_URI="https://fedorahosted.org/releases/l/i/libverto/${P}.tar.gz;
@@ -31,6 +33,7 @@ src_prepare() {
# callback on error, but we explicitly test for this behaviour.  Do not 
run
# tevent tests for now.
sed -i -e 's/def HAVE_TEVENT/ 0/' tests/test.h || die
+   elibtoolize
 }
 
 src_configure() {
diff --git a/dev-libs/libverto/libverto-0.2.6.ebuild 
b/dev-libs/libverto/libverto-0.2.6.ebuild
index 6f6eff7..fc0711a 100644
--- a/dev-libs/libverto/libverto-0.2.6.ebuild
+++ b/dev-libs/libverto/libverto-0.2.6.ebuild
@@ -4,7 +4,7 @@
 
 EAPI=5
 
-inherit multilib-minimal
+inherit multilib-minimal libtool
 
 DESCRIPTION="Main event loop abstraction library"
 HOMEPAGE="https://fedorahosted.org/libverto/;
@@ -33,6 +33,7 @@ src_prepare() {
# callback on error, but we explicitly test for this behaviour.  Do not 
run
# tevent tests for now.
sed -i -e 's/def HAVE_TEVENT/ 0/' tests/test.h || die
+   elibtoolize
 }
 
 multilib_src_configure() {
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 10/12] sys-devel/binutils: add ld BE emulations for ppc64le target #580614

2016-06-28 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 eclass/toolchain-binutils.eclass   | 10 ++
 .../binutils/files/binutils-configure-target.patch | 18 ++
 2 files changed, 28 insertions(+)
 create mode 100644 sys-devel/binutils/files/binutils-configure-target.patch

diff --git a/eclass/toolchain-binutils.eclass b/eclass/toolchain-binutils.eclass
index 34c8569..17eb5dc 100644
--- a/eclass/toolchain-binutils.eclass
+++ b/eclass/toolchain-binutils.eclass
@@ -180,6 +180,16 @@ tc-binutils_apply_patches() {
eend $?
done
fi
+
+   # fix emulations issues if possible #580614
+   if [[ -e ${FILESDIR}/binutils-configure-target.patch ]] ; then
+   einfo "Fixing emulations issues in configure target files"
+   ebegin "  Updating ld/configure.tgt"
+   patch "ld/configure.tgt" 
"${FILESDIR}"/binutils-configure-target.patch >& 
"${T}"/configure-target-patch.log \
+   || eerror "Please file a bug about this"
+   eend $?
+   fi
+
# fix conflicts with newer glibc #272594
if [[ -e libiberty/testsuite/test-demangle.c ]] ; then
sed -i 's:\<getline\>:get_line:g' 
libiberty/testsuite/test-demangle.c
diff --git a/sys-devel/binutils/files/binutils-configure-target.patch 
b/sys-devel/binutils/files/binutils-configure-target.patch
new file mode 100644
index 000..0cd8778
--- /dev/null
+++ b/sys-devel/binutils/files/binutils-configure-target.patch
@@ -0,0 +1,18 @@
+--- ld/configure.tgt.orig  2016-05-15 07:49:39.661039407 +
 ld/configure.tgt   2016-05-15 08:15:24.441045822 +
+@@ -586,10 +586,13 @@
+   esac
+   case "${targ}" in
+   powerpc*le-*)
+-  for z in targ_emul targ_extra_emuls 
targ_extra_libpath targ64_extra_emuls targ64_extra_libpath
++  for z in targ_extra_emuls targ_extra_libpath 
targ64_extra_emuls targ64_extra_libpath
+   do
+-eval ${z}=\"`eval echo \\$${z} | sed -e 
's/ppc/lppc/g'`\"
++eval ${z}+=\" `eval echo \\$${z} | sed -e 
's/ppc/lppc/g'`\"
+   done
++  eval targ_extra_emuls+=\" \$targ_emul\"
++  eval targ_emul=\"`eval echo \\$targ_emul | sed 
-e 's/ppc/lppc/g'`\"
++
+   esac ;;
+ powerpc-*-nto*) targ_emul=elf32ppcnto ;;
+ powerpcle-*-nto*)   targ_emul=elf32lppcnto ;;
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 02/12] libtool.eclass: elibtoolize: add ppc64le handling #580792

2016-06-28 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 eclass/ELT-patches/ppc64le/2.4.2 | 26 ++
 eclass/libtool.eclass|  6 +-
 2 files changed, 31 insertions(+), 1 deletion(-)
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.2

diff --git a/eclass/ELT-patches/ppc64le/2.4.2 b/eclass/ELT-patches/ppc64le/2.4.2
new file mode 100644
index 000..d61f6c3
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.2
@@ -0,0 +1,26 @@
+--- m4/libtool.m4.orig 2016-04-21 16:50:01.118444710 +
 m4/libtool.m4  2016-04-21 16:52:39.419906716 +
+@@ -1329,6 +1329,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -1345,9 +1348,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++powerpcle-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/eclass/libtool.eclass b/eclass/libtool.eclass
index 47ef812..9f56c20 100644
--- a/eclass/libtool.eclass
+++ b/eclass/libtool.eclass
@@ -144,7 +144,7 @@ elibtoolize() {
local deptoremove=
local do_shallow="no"
local force="false"
-   local elt_patches="install-sh ltmain portage relink max_cmd_len sed 
test tmp cross as-needed target-nm"
+   local elt_patches="install-sh ltmain portage relink max_cmd_len sed 
test tmp cross as-needed target-nm ppc64le"
 
for x in "$@" ; do
case ${x} in
@@ -417,6 +417,10 @@ elibtoolize() {
ELT_walk_patches "${d}/configure" "${p}"
ret=$?
;;
+   ppc64le)
+   ELT_walk_patches "${d}/configure" "${p}"
+   ret=$?
+   ;;
*)
# ltmain.sh patches are applied above
;;
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 01/12] sys-devel/libtool: add m4/libtool.m4 patch for ppc64le #581314

2016-06-28 Thread Leno Hou

Reference Bug:
Gentoo Bug: https://bugs.gentoo.org/show_bug.cgi?id=581314
GNU Bug: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348

* m4/libtool (LD=elf64lppc): add recognise definition with
CHOST=powerpc64le-unknown-linux-gnu on ppc64le platform and
CHOST=powerpc64-unknown-linux-gnu on ppc64 platform. This
patch sets $LD=elf64lppc on ppc64le and $LD=elf64ppc on ppc64.

Package-Manager: portage-2.2.26
Signed-off-by: Leno Hou <leno...@gmail.com>
---
 .../libtool-2.4.6-libtool-m4-for-ppc64le.patch | 41 ++
 sys-devel/libtool/libtool-2.4.6-r1.ebuild  |  1 +
 sys-devel/libtool/libtool-2.4.6-r2.ebuild  |  1 +
 sys-devel/libtool/libtool-2.4.6.ebuild |  1 +
 4 files changed, 44 insertions(+)
 create mode 100644 
sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch

diff --git a/sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch 
b/sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch
new file mode 100644
index 000..946c8c7
--- /dev/null
+++ b/sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch
@@ -0,0 +1,41 @@
+From a08fc6407e6bead83024668227b91556de7292eb Mon Sep 17 00:00:00 2001
+From: Leno Hou <leno...@gmail.com>
+Date: Sat, 14 May 2016 14:56:57 +
+Subject: [PATCH] m4/libtool.m4: Fix LD parameters with ppc64 & ppc64le
+ platform
+
+For v2.4.6
+Reference Bug:
+Gentoo Bug: https://bugs.gentoo.org/show_bug.cgi?id=581314
+GNU Bug: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
+
+* m4/libtool (LD=elf64lppc): add recognise definition with
+CHOST=powerpc64le-unknown-linux-gnu on ppc64le platform and
+CHOST=powerpc64-unknown-linux-gnu on ppc64 platform. This
+patch sets =elf64lppc on ppc64le and =elf64ppc on ppc64.
+
+Signed-off-by: Leno Hou <leno...@gmail.com>
+---
+ m4/libtool.m4 | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/m4/libtool.m4 b/m4/libtool.m4
+index a3bc337..91b2e01 100644
+--- a/m4/libtool.m4
 b/m4/libtool.m4
+@@ -1417,10 +1417,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux*)
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
+-- 
+2.7.3
+
diff --git a/sys-devel/libtool/libtool-2.4.6-r1.ebuild 
b/sys-devel/libtool/libtool-2.4.6-r1.ebuild
index 677db33..2038ff0 100644
--- a/sys-devel/libtool/libtool-2.4.6-r1.ebuild
+++ b/sys-devel/libtool/libtool-2.4.6-r1.ebuild
@@ -48,6 +48,7 @@ src_prepare() {
 
epatch "${FILESDIR}"/${PN}-2.4.3-use-linux-version-in-fbsd.patch #109105
epatch "${FILESDIR}"/${P}-fuse-ld.patch
+   epatch "${FILESDIR}"/${PN}-2.4.6-libtool-m4-for-ppc64le.patch #581314
pushd libltdl >/dev/null
AT_NOELIBTOOLIZE=yes eautoreconf
popd >/dev/null
diff --git a/sys-devel/libtool/libtool-2.4.6-r2.ebuild 
b/sys-devel/libtool/libtool-2.4.6-r2.ebuild
index 7e8b7ef..528ce85 100644
--- a/sys-devel/libtool/libtool-2.4.6-r2.ebuild
+++ b/sys-devel/libtool/libtool-2.4.6-r2.ebuild
@@ -53,6 +53,7 @@ src_prepare() {
epatch "${FILESDIR}"/${P}-libtoolize-slow.patch
epatch "${FILESDIR}"/${P}-libtoolize-delay-help.patch
epatch "${FILESDIR}"/${P}-sed-quote-speedup.patch #542252
+   epatch "${FILESDIR}"/${PN}-2.4.6-libtool-m4-for-ppc64le.patch #581314
pushd libltdl >/dev/null
AT_NOELIBTOOLIZE=yes eautoreconf
popd >/dev/null
diff --git a/sys-devel/libtool/libtool-2.4.6.ebuild 
b/sys-devel/libtool/libtool-2.4.6.ebuild
index 71a9b47..e7eeaed 100644
--- a/sys-devel/libtool/libtool-2.4.6.ebuild
+++ b/sys-devel/libtool/libtool-2.4.6.ebuild
@@ -47,6 +47,7 @@ src_prepare() {
use vanilla && return 0
 
epatch "${FILESDIR}"/${PN}-2.4.3-use-linux-version-in-fbsd.patch #109105
+   epatch "${FILESDIR}"/${PN}-2.4.6-libtool-m4-for-ppc64le.patch #581314
pushd libltdl >/dev/null
AT_NOELIBTOOLIZE=yes eautoreconf
popd >/dev/null
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 12/12] net-misc/gsutils: fix dev-python/oauth2client-2 dependency

2016-06-28 Thread Leno Hou

---
 net-misc/gsutil/gsutil-4.19.ebuild | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/net-misc/gsutil/gsutil-4.19.ebuild 
b/net-misc/gsutil/gsutil-4.19.ebuild
index ea1c3e1..7904721 100644
--- a/net-misc/gsutil/gsutil-4.19.ebuild
+++ b/net-misc/gsutil/gsutil-4.19.ebuild
@@ -26,8 +26,7 @@ RDEPEND="${PYTHON_DEPS}
>=dev-python/pyopenssl-0.13[${PYTHON_USEDEP}]
>=dev-python/gcs-oauth2-boto-plugin-1.12[${PYTHON_USEDEP}]
>=dev-python/google-apitools-0.5.2[${PYTHON_USEDEP}]
-   >=dev-python/oauth2client-1.5.2[${PYTHON_USEDEP}]
-   =dev-python/python-gflags-2.0[${PYTHON_USEDEP}]
>=dev-python/retry-decorator-1.0.0[${PYTHON_USEDEP}]
>=dev-python/six-1.9.0[${PYTHON_USEDEP}]
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 11/12] dev-utils/perf: add support for ppc64le #581746

2016-06-28 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 dev-util/perf/perf-4.4.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/perf/perf-4.4.4.ebuild b/dev-util/perf/perf-4.4.4.ebuild
index 18dd89e..b4fe31e 100644
--- a/dev-util/perf/perf-4.4.4.ebuild
+++ b/dev-util/perf/perf-4.4.4.ebuild
@@ -76,7 +76,7 @@ pkg_setup() {
 src_unpack() {
local paths=(
tools/arch tools/build tools/include tools/lib tools/perf 
tools/scripts
-   include lib "arch/*/lib"
+   include lib "arch/*/include" "arch/*/lib"
)
 
# We expect the tar implementation to support the -j option (both
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 08/12] sys-block/partimage: run elibtoolize #580792

2016-06-28 Thread Leno Hou

This is needed to support newer platforms (like ppc64le).
Signed-off-by: Leno Hou <leno...@gmail.com>
---
 sys-block/partimage/partimage-0.6.9.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/sys-block/partimage/partimage-0.6.9.ebuild 
b/sys-block/partimage/partimage-0.6.9.ebuild
index 10f9545..92302f2 100644
--- a/sys-block/partimage/partimage-0.6.9.ebuild
+++ b/sys-block/partimage/partimage-0.6.9.ebuild
@@ -3,7 +3,7 @@
 # $Id$
 
 EAPI=4
-inherit eutils flag-o-matic pam user
+inherit eutils libtool flag-o-matic pam user
 
 DESCRIPTION="Console-based application to efficiently save raw partition data 
to an image file"
 HOMEPAGE="http://www.partimage.org/;
@@ -34,6 +34,7 @@ pkg_setup() {
 src_prepare() {
epatch "${FILESDIR}"/${P}-zlib-1.2.5.2.patch #405323
epatch "${FILESDIR}"/${P}-minor-typo.patch #580290
+   elibtoolize
 }
 
 src_configure() {
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 07/12] app-text/opensp: autoreconf to build opensp for ppc64le #580792

2016-06-28 Thread Leno Hou

This is needed to support newer platforms (like ppc64le).
Signed-off-by: Leno Hou <leno...@gmail.com>
---
 app-text/opensp/opensp-1.5.2-r3.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/app-text/opensp/opensp-1.5.2-r3.ebuild 
b/app-text/opensp/opensp-1.5.2-r3.ebuild
index 9f97607..d60c8f6 100644
--- a/app-text/opensp/opensp-1.5.2-r3.ebuild
+++ b/app-text/opensp/opensp-1.5.2-r3.ebuild
@@ -3,7 +3,7 @@
 # $Id$
 
 EAPI=5
-inherit eutils flag-o-matic
+inherit eutils flag-o-matic autotools
 
 MY_P=${P/opensp/OpenSP}
 
@@ -34,6 +34,7 @@ src_prepare() {
epatch \
"${FILESDIR}"/${PN}-1.5-gcc34.patch \
"${FILESDIR}"/${P}-fix-segfault.patch
+   eautoreconf #580792
 }
 
 src_configure() {
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 05/12] dev-libs/libmnl: run elibtoolize #580792

2016-06-28 Thread Leno Hou

This is needed to support newer platforms (like ppc64le).
Signed-off-by: Leno Hou <leno...@gmail.com>
---
 net-libs/libmnl/libmnl-1.0.3-r1.ebuild | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/net-libs/libmnl/libmnl-1.0.3-r1.ebuild 
b/net-libs/libmnl/libmnl-1.0.3-r1.ebuild
index 4b0bbc2..bca8c8e 100644
--- a/net-libs/libmnl/libmnl-1.0.3-r1.ebuild
+++ b/net-libs/libmnl/libmnl-1.0.3-r1.ebuild
@@ -4,7 +4,7 @@
 
 EAPI=4
 
-inherit eutils toolchain-funcs
+inherit eutils libtool toolchain-funcs
 
 DESCRIPTION="Minimalistic netlink library"
 HOMEPAGE="http://netfilter.org/projects/libmnl;
@@ -15,6 +15,9 @@ SLOT="0"
 KEYWORDS="alpha amd64 arm arm64 hppa ia64 m68k ~mips ppc ppc64 s390 sh sparc 
x86 ~amd64-linux"
 IUSE="examples static-libs"
 
+src_prepare(){
+   elibtoolize #580792
+}
 src_configure() {
econf $(use_enable static-libs static)
 }
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 06/12] sys-process/procps: run elibtoolize #580792

2016-06-28 Thread Leno Hou

This is needed to support newer platforms (like ppc64le).
Signed-off-by: Leno Hou <leno...@gmail.com>
---
 sys-process/procps/procps-3.3.10-r1.ebuild | 3 ++-
 sys-process/procps/procps-3.3.9-r2.ebuild  | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/sys-process/procps/procps-3.3.10-r1.ebuild 
b/sys-process/procps/procps-3.3.10-r1.ebuild
index f254f34..d484b23 100644
--- a/sys-process/procps/procps-3.3.10-r1.ebuild
+++ b/sys-process/procps/procps-3.3.10-r1.ebuild
@@ -4,7 +4,7 @@
 
 EAPI="5"
 
-inherit eutils toolchain-funcs
+inherit eutils libtool toolchain-funcs
 
 DESCRIPTION="standard informational utilities and process-handling tools"
 # http://packages.debian.org/sid/procps
@@ -34,6 +34,7 @@ src_prepare() {
epatch "${FILESDIR}"/${PN}-3.3.8-kill-neg-pid.patch # 
http://crbug.com/255209
epatch "${FILESDIR}"/${P}-pmap-unreadable.patch #404389
epatch "${FILESDIR}"/${P}-tests-no-tty.patch #461302
+   elibtoolize #580792
sed -i -e 's:systemd-login:systemd:' configure || die #501306
 }
 
diff --git a/sys-process/procps/procps-3.3.9-r2.ebuild 
b/sys-process/procps/procps-3.3.9-r2.ebuild
index 4e8e0e6..d5c6df8 100644
--- a/sys-process/procps/procps-3.3.9-r2.ebuild
+++ b/sys-process/procps/procps-3.3.9-r2.ebuild
@@ -4,7 +4,7 @@
 
 EAPI="4"
 
-inherit eutils toolchain-funcs
+inherit eutils libtool toolchain-funcs
 
 DESCRIPTION="standard informational utilities and process-handling tools"
 # http://packages.debian.org/sid/procps
@@ -33,6 +33,7 @@ src_prepare() {
epatch \
"${FILESDIR}"/${PN}-3.3.8-kill-neg-pid.patch \
"${FILESDIR}"/${P}-sysctl-load-config-files.patch
+   elibtoolize #580792
sed -i -e 's:systemd-login:systemd:' configure || die #501306
 }
 
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 04/12] ELT-patches/ppc64le: add libtool-2.4.6 patch for ppc64le #580792

2016-06-28 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 eclass/ELT-patches/ppc64le/2.4.6 | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.6

diff --git a/eclass/ELT-patches/ppc64le/2.4.6 b/eclass/ELT-patches/ppc64le/2.4.6
new file mode 100644
index 000..711ceb2
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.6
@@ -0,0 +1,15 @@
+--- m4/libtool.m4.orig 2016-04-21 16:42:22.170586778 +
 m4/libtool.m4  2016-04-21 16:43:41.571195049 +
+@@ -1417,10 +1417,10 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
-- 
2.7.3

[gentoo-dev][ppc64le][PATCH 03/12] ELT-patches/ppc64le: add libtool-2.4.4 patch for ppc64le #580792

2016-06-28 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 eclass/ELT-patches/ppc64le/2.4.4 | 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.4

diff --git a/eclass/ELT-patches/ppc64le/2.4.4 b/eclass/ELT-patches/ppc64le/2.4.4
new file mode 100644
index 000..e3e4637
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.4
@@ -0,0 +1,15 @@
+--- m4/libtool.m4.orig 2016-04-21 16:59:06.039629474 +
 m4/libtool.m4  2016-04-21 17:00:10.564264157 +
+@@ -1386,10 +1386,10 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
-- 
2.7.3

[gentoo-dev][PATCH v1] sys-devel/libtool: add m4/libtool.m4 patch for ppc64le #581314

2016-05-14 Thread Leno Hou

Reference Bug:
Gentoo Bug: https://bugs.gentoo.org/show_bug.cgi?id=581314
GNU Bug: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348

* m4/libtool (LD=elf64lppc): add recognise definition with
CHOST=powerpc64le-unknown-linux-gnu on ppc64le platform and
CHOST=powerpc64-unknown-linux-gnu on ppc64 platform. This
patch sets $LD=elf64lppc on ppc64le and $LD=elf64ppc on ppc64.

Package-Manager: portage-2.2.26
Signed-off-by: Leno Hou <leno...@gmail.com>
---
 .../libtool-2.4.6-libtool-m4-for-ppc64le.patch | 41 ++
 sys-devel/libtool/libtool-2.4.6-r1.ebuild  |  1 +
 sys-devel/libtool/libtool-2.4.6-r2.ebuild  |  1 +
 sys-devel/libtool/libtool-2.4.6.ebuild |  1 +
 4 files changed, 44 insertions(+)
 create mode 100644 
sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch

diff --git a/sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch 
b/sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch
new file mode 100644
index 000..946c8c7
--- /dev/null
+++ b/sys-devel/libtool/files/libtool-2.4.6-libtool-m4-for-ppc64le.patch
@@ -0,0 +1,41 @@
+From a08fc6407e6bead83024668227b91556de7292eb Mon Sep 17 00:00:00 2001
+From: Leno Hou <leno...@gmail.com>
+Date: Sat, 14 May 2016 14:56:57 +
+Subject: [PATCH] m4/libtool.m4: Fix LD parameters with ppc64 & ppc64le
+ platform
+
+For v2.4.6
+Reference Bug:
+Gentoo Bug: https://bugs.gentoo.org/show_bug.cgi?id=581314
+GNU Bug: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348
+
+* m4/libtool (LD=elf64lppc): add recognise definition with
+CHOST=powerpc64le-unknown-linux-gnu on ppc64le platform and
+CHOST=powerpc64-unknown-linux-gnu on ppc64 platform. This
+patch sets =elf64lppc on ppc64le and =elf64ppc on ppc64.
+
+Signed-off-by: Leno Hou <leno...@gmail.com>
+---
+ m4/libtool.m4 | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/m4/libtool.m4 b/m4/libtool.m4
+index a3bc337..91b2e01 100644
+--- a/m4/libtool.m4
 b/m4/libtool.m4
+@@ -1417,10 +1417,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux*)
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
+-- 
+2.7.3
+
diff --git a/sys-devel/libtool/libtool-2.4.6-r1.ebuild 
b/sys-devel/libtool/libtool-2.4.6-r1.ebuild
index 677db33..2038ff0 100644
--- a/sys-devel/libtool/libtool-2.4.6-r1.ebuild
+++ b/sys-devel/libtool/libtool-2.4.6-r1.ebuild
@@ -48,6 +48,7 @@ src_prepare() {
 
epatch "${FILESDIR}"/${PN}-2.4.3-use-linux-version-in-fbsd.patch #109105
epatch "${FILESDIR}"/${P}-fuse-ld.patch
+   epatch "${FILESDIR}"/${PN}-2.4.6-libtool-m4-for-ppc64le.patch #581314
pushd libltdl >/dev/null
AT_NOELIBTOOLIZE=yes eautoreconf
popd >/dev/null
diff --git a/sys-devel/libtool/libtool-2.4.6-r2.ebuild 
b/sys-devel/libtool/libtool-2.4.6-r2.ebuild
index 7e8b7ef..528ce85 100644
--- a/sys-devel/libtool/libtool-2.4.6-r2.ebuild
+++ b/sys-devel/libtool/libtool-2.4.6-r2.ebuild
@@ -53,6 +53,7 @@ src_prepare() {
epatch "${FILESDIR}"/${P}-libtoolize-slow.patch
epatch "${FILESDIR}"/${P}-libtoolize-delay-help.patch
epatch "${FILESDIR}"/${P}-sed-quote-speedup.patch #542252
+   epatch "${FILESDIR}"/${PN}-2.4.6-libtool-m4-for-ppc64le.patch #581314
pushd libltdl >/dev/null
AT_NOELIBTOOLIZE=yes eautoreconf
popd >/dev/null
diff --git a/sys-devel/libtool/libtool-2.4.6.ebuild 
b/sys-devel/libtool/libtool-2.4.6.ebuild
index 71a9b47..e7eeaed 100644
--- a/sys-devel/libtool/libtool-2.4.6.ebuild
+++ b/sys-devel/libtool/libtool-2.4.6.ebuild
@@ -47,6 +47,7 @@ src_prepare() {
use vanilla && return 0
 
epatch "${FILESDIR}"/${PN}-2.4.3-use-linux-version-in-fbsd.patch #109105
+   epatch "${FILESDIR}"/${PN}-2.4.6-libtool-m4-for-ppc64le.patch #581314
pushd libltdl >/dev/null
AT_NOELIBTOOLIZE=yes eautoreconf
popd >/dev/null
-- 
2.7.3

[gentoo-dev][PATCH] dev-lang/go-1.6.2: enable go-bootstrap tarball for ppc64le #581278

2016-04-28 Thread Leno Hou

There is a bootstrap tarball for ppc64le now, and  we have bi-arch
support for ppc64 platform. It's means that we can build go-1.6.2
without gccgo

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 dev-lang/go/go-1.6.2.ebuild | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/dev-lang/go/go-1.6.2.ebuild b/dev-lang/go/go-1.6.2.ebuild
index 57ca2c7..7408cd2 100644
--- a/dev-lang/go/go-1.6.2.ebuild
+++ b/dev-lang/go/go-1.6.2.ebuild
@@ -88,6 +88,16 @@ go_arch()
case "${portage_arch}" in
x86)echo 386;;
x64-*)  echo amd64;;
+   ppc64)
+   case "$(tc-endian $@)" in
+   little)
+   echo ppc64le
+   ;;
+   big)
+   echo ppc64
+   ;;
+   esac
+   ;;
*)  echo "${portage_arch}";;
esac
 }
-- 
2.7.3

[gentoo-dev][PATCH V3] dev-lang/go-1.6.2: enable go-bootstrap tarball for ppc64le #581278

2016-04-28 Thread Leno Hou

There is a bootstrap tarball for ppc64le now, and  we have bi-arch
support for ppc64 platform. It's means that we can build go-1.6.2
without gccgo

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 dev-lang/go/go-1.6.2.ebuild | 5 +
 1 file changed, 5 insertions(+)

diff --git a/dev-lang/go/go-1.6.2.ebuild b/dev-lang/go/go-1.6.2.ebuild
index 57ca2c7..ba61397 100644
--- a/dev-lang/go/go-1.6.2.ebuild
+++ b/dev-lang/go/go-1.6.2.ebuild
@@ -88,6 +88,11 @@ go_arch()
case "${portage_arch}" in
x86)echo 386;;
x64-*)  echo amd64;;
+   ppc64)  if [[ "$(tc-endian $@)" == "big" ]]; then
+   echo ppc64
+   else
+   echo ppc64le
+   fi;;
*)  echo "${portage_arch}";;
esac
 }
-- 
2.7.3

Re: [gentoo-dev][PATCH V2] dev-lang/go-1.6.2: enable go-bootstrap tarball for ppc64le #581278

2016-04-28 Thread Leno Hou

On Thu, Apr 28, 2016 at 4:14 PM, Michał Górny <mgo...@gentoo.org> wrote:

> On Thu, 28 Apr 2016 05:59:14 +0000
> Leno Hou <leno...@gmail.com> wrote:
>
> > There is a bootstrap tarball for ppc64le now, and  we have bi-arch
> > support for ppc64 platform. It's means that we can build go-1.6.2
> > without gccgo.
> >
> > Signed-off-by: Leno Hou <leno...@gmail.com>
> > CC: William Hubbs <willi...@gentoo.org>
> > ---
> >  dev-lang/go/go-1.6.2.ebuild | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/dev-lang/go/go-1.6.2.ebuild b/dev-lang/go/go-1.6.2.ebuild
> > index 57ca2c7..049973a 100644
> > --- a/dev-lang/go/go-1.6.2.ebuild
> > +++ b/dev-lang/go/go-1.6.2.ebuild
> > @@ -88,6 +88,7 @@ go_arch()
> >   case "${portage_arch}" in
> >   x86)echo 386;;
> >   x64-*)  echo amd64;;
> > + ppc64)  [[ "$(tc-endian $@)" == "big" ]] || echo ppc64le;;
>
> Shouldn't this also have '&& echo ppc64'? Otherwise, on BE ppc64 there
> will be no output.
>

That's true. You're right.  So the next PATCH v3 will be sent.
-Leno Hou

[gentoo-dev][PATCH V2] dev-lang/go-1.6.2: enable go-bootstrap tarball for ppc64le #581278

2016-04-27 Thread Leno Hou

There is a bootstrap tarball for ppc64le now, and  we have bi-arch
support for ppc64 platform. It's means that we can build go-1.6.2
without gccgo.

Signed-off-by: Leno Hou <leno...@gmail.com>
CC: William Hubbs <willi...@gentoo.org>
---
 dev-lang/go/go-1.6.2.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-lang/go/go-1.6.2.ebuild b/dev-lang/go/go-1.6.2.ebuild
index 57ca2c7..049973a 100644
--- a/dev-lang/go/go-1.6.2.ebuild
+++ b/dev-lang/go/go-1.6.2.ebuild
@@ -88,6 +88,7 @@ go_arch()
case "${portage_arch}" in
x86)echo 386;;
x64-*)  echo amd64;;
+   ppc64)  [[ "$(tc-endian $@)" == "big" ]] || echo ppc64le;;
*)  echo "${portage_arch}";;
esac
 }
-- 
2.7.3

Re: [gentoo-dev][PATCH V1] dev-lang/go-1.6.2: enable go-bootstrap tarball for ppc64le #581278

2016-04-27 Thread Leno Hou

Please ignore this due to the logic and See PATCH V2

On Thu, Apr 28, 2016 at 1:42 PM, Leno Hou <leno...@gmail.com> wrote:

> There is a bootstrap tarball for ppc64le now, and  we have bi-arch
> support for ppc64 platform. It's means that we can build go-1.6.2
> without gccgo.
>
> Signed-off-by: Leno Hou <leno...@gmail.com>
> CC: William Hubbs <willi...@gentoo.org>
> ---
>  dev-lang/go/go-1.6.2.ebuild | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/dev-lang/go/go-1.6.2.ebuild b/dev-lang/go/go-1.6.2.ebuild
> index 57ca2c7..4babafe 100644
> --- a/dev-lang/go/go-1.6.2.ebuild
> +++ b/dev-lang/go/go-1.6.2.ebuild
> @@ -88,6 +88,7 @@ go_arch()
> case "${portage_arch}" in
> x86)echo 386;;
> x64-*)  echo amd64;;
> +   ppc64)  [[ "$(tc-endian $@)" == "little" ]] && echo
> ppc64le;;
> *)  echo "${portage_arch}";;
> esac
>  }
> --
> 2.7.3
>
>

[gentoo-dev][PATCH V1] dev-lang/go-1.6.2: enable go-bootstrap tarball for ppc64le #581278

2016-04-27 Thread Leno Hou

There is a bootstrap tarball for ppc64le now, and  we have bi-arch
support for ppc64 platform. It's means that we can build go-1.6.2
without gccgo.

Signed-off-by: Leno Hou <leno...@gmail.com>
CC: William Hubbs <willi...@gentoo.org>
---
 dev-lang/go/go-1.6.2.ebuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-lang/go/go-1.6.2.ebuild b/dev-lang/go/go-1.6.2.ebuild
index 57ca2c7..4babafe 100644
--- a/dev-lang/go/go-1.6.2.ebuild
+++ b/dev-lang/go/go-1.6.2.ebuild
@@ -88,6 +88,7 @@ go_arch()
case "${portage_arch}" in
x86)echo 386;;
x64-*)  echo amd64;;
+   ppc64)  [[ "$(tc-endian $@)" == "little" ]] && echo ppc64le;;
*)  echo "${portage_arch}";;
esac
 }
-- 
2.7.3

Re: [gentoo-dev] Last rites: dev-lang/go-bootstrap

2016-04-26 Thread Leno Hou

On Sun, Apr 3, 2016 at 2:53 AM, William Hubbs <willi...@gentoo.org> wrote:

> # William Hubbs <willi...@gentoo.org> (02 Apr 2016)
> # Stable dev-lang/go no longer needs this; end users should have never
> # installed it on their own.
> # Masked for removal on 20160409
> dev-lang/go-bootstrap
>

1) Thanks William. You have integrated with go-bootstrap in build process.

2) I've reported dev-lang/go bug on ppc64le platform, Could you have a look
?
This bug may happens in run go-ppc64-bootstrap.tbz
https://bugs.gentoo.org/show_bug.cgi?id=581278

3) We've successfully use gccgo to compile GO-1.6.1 on ppc64le. So go may
have LE port.

-Leno Hou

Re: [gentoo-dev][PATCH v2 1/2] eclass/libtool: fix unable read SONAME for ppc64le #580792

2016-04-24 Thread Leno Hou

On Sat, Apr 23, 2016 at 2:16 PM, Mike Frysinger <vap...@gentoo.org> wrote:

> On 22 Apr 2016 03:44, Leno Hou wrote:
> >  2) The problem is due to the wrong $LD="ld -m elf64ppc" when link.
> >   This patch sets $LD="ld -m elf64lppc" in m4/libtool.m4 on ppc64le.
>
> i'm looking at the upstream libtool project and i'm not seeing
> these changes in there.  have you sent patches to them to update
> libtool ?  otherwise, all packages will continue to be created
> with bad versions in them ...
>
>
1) I have reported the libtool in upstream. See here
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348

2) The new PATCH V3 which called
 [gentoo-dev][PATCH V3] libtool.eclass:elibtoolize: add ppc64le handling
#580792
was sent to mailing list and cc'ed you
has update libtool-2.4.6

what upstream has right now is:
>   if AC_TRY_EVAL(ac_compile); then
> case `/usr/bin/file conftest.o` in
>   *32-bit*)
> case $host in
> ...
>   powerpc64le-*linux*)
> LD="${LD-ld} -m elf32lppclinux"
> ;;
>   powerpc64-*linux*)
> LD="${LD-ld} -m elf32ppclinux"
> ;;
> ...
>   *64-bit*)
> case $host in
> ...
>   powerpcle-*linux*)
> LD="${LD-ld} -m elf64lppc"
> ;;
>   powerpc-*linux*)
> LD="${LD-ld} -m elf64ppc"
> ;;
> ...
>
> your 2.4.2 patch makes sense in that it had no LE support, so you
> need to add the tuple matching.  however, the 2.4.4 & 2.4.6 patches
> are applying to libtool versions that know how to handle LE.
>

3) The 2.4.4 and 2.4.6 are applied correct lib tool version that know how
to handle LE


> keep in mind that the logic here is just for handling mismatch in
> the expected bitness and the tuple.  i.e. when you're using a tuple
> like powerpc-linux-gnu (which is normally 32bit) but you're actually
> producing 64-bit code.
>

4)  Is  tuple
 
powerpcle-*linux*)
LD="${LD-ld} -m elf64lppc"

should be changed to
 
powerpcle-*linux*)
   LD="${LD-ld} -m elf32lppc"

to producing 32-bit code?

If yes, I'll send new PATCH to cover this.

-Leno Hou

[gentoo-dev][PATCH V3 ] libtool.eclass: elibtoolize: add ppc64le handling #580792

2016-04-23 Thread Leno Hou

1) We faced unable read SONAME from ${lib} when emerge below packages
   platform   pacakge elibtoolized
   ppc64leapp-text/opensp no
   ppc64ledev-libs/expat  yes
   ppc64lenet-firewall/iptables   yes
   ppc64lenet-libs/libmnl no
   ppc64lesys-apps/aclyes
   ppc64lesys-apps/attr   yes
   ppc64lesys-libs/gdbm   yes
   ppc64lesys-process/procps  no

 2) The problem is due to the wrong $LD="ld -m elf64ppc" when link.
  This patch sets $LD="ld -m elf64lppc" in m4/libtool.m4 on ppc64le.

 3) Also patched m4/libtool.m4 in libtool-2.4.6. Reported the bug[1] in
libtool upstream, Once the upstream fixed the libtool problem for
ppc64le, we can pull back from the upstream.

[1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348

Signed-off-by: Leno Hou <leno...@gmail.com>
CC: Mike Frysinger <vap...@gentoo.org>
---
 eclass/ELT-patches/ppc64le/2.4.2   | 26 ++
 eclass/ELT-patches/ppc64le/2.4.4   | 15 +
 eclass/ELT-patches/ppc64le/2.4.6   | 15 +
 eclass/libtool.eclass  |  6 -
 .../files/libtool-2.4.6-link-with-ppc64le.patch| 15 +
 sys-devel/libtool/libtool-2.4.6-r1.ebuild  |  1 +
 sys-devel/libtool/libtool-2.4.6-r2.ebuild  |  1 +
 sys-devel/libtool/libtool-2.4.6.ebuild |  1 +
 8 files changed, 79 insertions(+), 1 deletion(-)
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.2
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.4
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.6
 create mode 100644 
sys-devel/libtool/files/libtool-2.4.6-link-with-ppc64le.patch

diff --git a/eclass/ELT-patches/ppc64le/2.4.2 b/eclass/ELT-patches/ppc64le/2.4.2
new file mode 100644
index 000..d61f6c3
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.2
@@ -0,0 +1,26 @@
+--- m4/libtool.m4.orig 2016-04-21 16:50:01.118444710 +
 m4/libtool.m4  2016-04-21 16:52:39.419906716 +
+@@ -1329,6 +1329,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -1345,9 +1348,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++powerpcle-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/eclass/ELT-patches/ppc64le/2.4.4 b/eclass/ELT-patches/ppc64le/2.4.4
new file mode 100644
index 000..e3e4637
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.4
@@ -0,0 +1,15 @@
+--- m4/libtool.m4.orig 2016-04-21 16:59:06.039629474 +
 m4/libtool.m4  2016-04-21 17:00:10.564264157 +
+@@ -1386,10 +1386,10 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
diff --git a/eclass/ELT-patches/ppc64le/2.4.6 b/eclass/ELT-patches/ppc64le/2.4.6
new file mode 100644
index 000..711ceb2
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.6
@@ -0,0 +1,15 @@
+--- m4/libtool.m4.orig 2016-04-21 16:42:22.170586778 +
 m4/libtool.m4  2016-04-21 16:43:41.571195049 +
+@@ -1417,10 +1417,10 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
diff --git a/eclass/libtool.eclass b/eclass/libtool.eclass
index 47ef812..9f56c20 100644
--- a/eclass/libtool.eclass
+++ b/eclass/libtool.eclass
@@ -144,7 +144,7 @@ elibtoolize() {
local deptoremove=
local do_shallow="no"
local force="false"
-   local elt_patches="install-sh ltmain portage relink max_cmd_len sed 
test tmp cross as-needed target-nm"
+   local elt_p

[gentoo-dev][PATCH v1 ] sys-fs/hfsplusutils with gcc-5: blockiter.c:148:8: error: redefinition of blockiter_curr #580620

2016-04-22 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 .../files/hfsplusutils-1.0.4-gcc5.patch| 98 ++
 sys-fs/hfsplusutils/hfsplusutils-1.0.4-r1.ebuild   |  1 +
 2 files changed, 99 insertions(+)
 create mode 100644 sys-fs/hfsplusutils/files/hfsplusutils-1.0.4-gcc5.patch

diff --git a/sys-fs/hfsplusutils/files/hfsplusutils-1.0.4-gcc5.patch 
b/sys-fs/hfsplusutils/files/hfsplusutils-1.0.4-gcc5.patch
new file mode 100644
index 000..3dacd57
--- /dev/null
+++ b/sys-fs/hfsplusutils/files/hfsplusutils-1.0.4-gcc5.patch
@@ -0,0 +1,98 @@
+--- libhfsp/src/blockiter.h.orig   2016-04-15 16:32:04.548299500 +
 libhfsp/src/blockiter.h2016-04-15 16:32:24.920515955 +
+@@ -52,9 +52,4 @@
+ extern int blockiter_skip(blockiter *b, UInt32 skip);
+ 
+ /* return current block */
+-extern inline UInt32 blockiter_curr(blockiter *b)
+-{
+-return b->e->start_block + b->block;
+-}
+-
+-
++extern inline UInt32 blockiter_curr(blockiter *b);
+--- libhfsp/src/libhfsp.h.orig 2016-04-15 16:32:45.888738808 +
 libhfsp/src/libhfsp.h  2016-04-15 16:33:12.809024783 +
+@@ -90,15 +90,7 @@
+ 
+ 
+ /** helper function to create those Apple 4 byte Signatures */
+-extern inline UInt32 sig(char c0, char c1, char c2, char c3)
+-{
+-UInt32 sig;
+-((char*))[0] = c0;
+-((char*))[1] = c1;
+-((char*))[2] = c2;
+-((char*))[3] = c3;
+-return sig;
+-}
++extern inline UInt32 sig(char c0, char c1, char c2, char c3);
+ 
+ 
+ 
+--- libhfsp/src/volume.h.orig  2016-04-15 16:34:29.641839177 +
 libhfsp/src/volume.h   2016-04-15 16:35:03.154194245 +
+@@ -75,12 +75,7 @@
+ extern void volume_create_extents_tree(volume* vol);
+ 
+ /* accessor for entends btree, is created on demand */
+-extern inline btree* volume_get_extents_tree(volume* vol) 
+-{
+-if (!vol->extents)
+-  volume_create_extents_tree(vol);
+-return vol->extents;
+-}
++extern inline btree* volume_get_extents_tree(volume* vol);
+ 
+ /* return new Id for files/folder and check for overflow.
+  *
+--- src/dstring.h.orig 2016-04-15 16:38:14.404216390 +
 src/dstring.h  2016-04-15 16:38:45.344543346 +
+@@ -42,13 +42,6 @@
+ extern void   dstring_shrink(dstring *, size_t);
+ extern void   dstring_free(dstring *);
+ 
+-extern inline char*dstring_string(dstring *string)
+-{
+-return string->str;
+-}
+-
+-extern inline int dstring_length(dstring *string)
+-{
+-return string->len;
+-}  
++extern inline char*dstring_string(dstring *string);
++extern inline int dstring_length(dstring *string);
+ 
+--- src/dlist.h.orig   2016-04-15 16:39:16.336870099 +
 src/dlist.h2016-04-15 16:39:55.697284793 +
+@@ -36,14 +36,5 @@
+ extern intdlist_append(dlist *, const char *);
+ 
+ /* return the array of strings in a list; can dispose with free() */
+-extern inline char **dlist_array(dlist *list)
+-{
+-return (char **) list->mem;
+-} 
+-
+-/* return the number of strings in a list */
+-extern inline int dlist_size(dlist *list)
+-{
+-  return list->eltend - (char **) list->mem;
+-}
+-
++extern inline char **dlist_array(dlist *list);
++extern inline int dlist_size(dlist *list);
+--- src/darray.h.orig  2016-04-15 16:43:23.775481365 +
 src/darray.h   2016-04-15 16:43:41.807671388 +
+@@ -40,9 +40,4 @@
+ externvoiddarray_sort(darray *, int (*)(const void *, const 
void *));
+ 
+ /* return the array as an indexable block */
+-extern inline void *darray_array(darray *array)
+-{
+-  return (void *) array->mem;
+-}
+-
+-
++extern inline void *darray_array(darray *array);
diff --git a/sys-fs/hfsplusutils/hfsplusutils-1.0.4-r1.ebuild 
b/sys-fs/hfsplusutils/hfsplusutils-1.0.4-r1.ebuild
index aa6fe7c..e673c04 100644
--- a/sys-fs/hfsplusutils/hfsplusutils-1.0.4-r1.ebuild
+++ b/sys-fs/hfsplusutils/hfsplusutils-1.0.4-r1.ebuild
@@ -26,6 +26,7 @@ src_unpack() {
epatch "${FILESDIR}/${P}-errno.patch"
epatch "${FILESDIR}/${P}-gcc4.patch"
epatch "${FILESDIR}/${P}-string.patch"
+   epatch "${FILESDIR}/${P}-gcc5.patch"
#let's avoid the Makefile.cvs since isn't working for us
eautoreconf
 }
-- 
2.1.4

Re: [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem

2016-04-22 Thread Leno Hou

On Wed, Apr 20, 2016 at 10:33 AM, Mike Frysinger <vap...@gentoo.org> wrote:

> On 19 Apr 2016 22:12, Leno Hou wrote:
> > --- /dev/null
> > +++ b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > @@ -0,0 +1,26 @@
> > +--- configure.orig   2016-04-09 16:24:17.507053635 +
> >  configure2016-04-09 16:25:41.851918142 +
> > +@@ -4947,6 +4947,9 @@
> > + ppc64-*linux*|powerpc64-*linux*)
> > +   LD="${LD-ld} -m elf32ppclinux"
> > +   ;;
> > ++ppc64le-*linux*|powerpc64le-*linux*)
> > ++  LD="${LD-ld} -m elf32lppclinux"
> > ++  ;;
>
> you appear to be patching libtool code.  this should be in libtool
> itself. if it's a common issue, we'll want to leverage elibtoolize
> here.  make a patch and stick it in eclass/ELT-patches/ppc64le/,
> and then update the libtool.eclass file to apply those.  then update
> opensp to call the elibtoolize function in src_prepare.
> -mike
>

Thanks Mike, I've sent the patch in mailing list and cc'ed you. Could you
help me to review and merge?

-Leno Hou

[gentoo-dev][PATCH v2 2/2] ERROR: sys-apps/attr: unable to read SONAME from libattr.so #580792

2016-04-22 Thread Leno Hou

Signed-off-by: Leno Hou <leno...@gmail.com>
CC: Mike Frysinger <vap...@gentoo.org>
---
 sys-apps/attr/attr-2.4.47-r2.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/sys-apps/attr/attr-2.4.47-r2.ebuild 
b/sys-apps/attr/attr-2.4.47-r2.ebuild
index 11a6bda..aa62248 100644
--- a/sys-apps/attr/attr-2.4.47-r2.ebuild
+++ b/sys-apps/attr/attr-2.4.47-r2.ebuild
@@ -4,7 +4,7 @@
 
 EAPI="4"
 
-inherit eutils toolchain-funcs multilib-minimal
+inherit eutils libtool toolchain-funcs multilib-minimal
 
 DESCRIPTION="Extended attributes tools"
 HOMEPAGE="http://savannah.nongnu.org/projects/attr;
@@ -29,6 +29,7 @@ src_prepare() {
include/builddefs.in \
|| die
strip-linguas -u po
+   elibtoolize
multilib_copy_sources # https://savannah.nongnu.org/bugs/index.php?39736
 }
 
-- 
2.7.3

[gentoo-dev][PATCH v2 1/2] eclass/libtool: fix unable read SONAME for ppc64le #580792

2016-04-22 Thread Leno Hou

1) We faced unable read SONAME from ${lib} when emerge below pacakges
   platform  pacakge
   ppc64le   app-text/opensp
   ppc64le   dev-libs/expat
   ppc64le   net-firewall/iptables
   ppc64le   net-libs/libmnl
   ppc64le   sys-apps/acl
   ppc64le   sys-apps/attr
   ppc64le   sys-libs/gdbm
   ppc64le   sys-process/procps

 2) The problem is due to the wrong $LD="ld -m elf64ppc" when link.
  This patch sets $LD="ld -m elf64lppc" in m4/libtool.m4 on ppc64le.

Signed-off-by: Leno Hou <leno...@gmail.com>
CC: Mike Frysinger <vap...@gentoo.org>
---
 eclass/ELT-patches/ppc64le/2.4.2 | 26 ++
 eclass/ELT-patches/ppc64le/2.4.4 | 15 +++
 eclass/ELT-patches/ppc64le/2.4.6 | 15 +++
 eclass/libtool.eclass|  6 +-
 4 files changed, 61 insertions(+), 1 deletion(-)
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.2
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.4
 create mode 100644 eclass/ELT-patches/ppc64le/2.4.6

diff --git a/eclass/ELT-patches/ppc64le/2.4.2 b/eclass/ELT-patches/ppc64le/2.4.2
new file mode 100644
index 000..1a22432
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.2
@@ -0,0 +1,26 @@
+--- m4/libtool.m4.orig 2016-04-21 16:50:01.118444710 +
 m4/libtool.m4  2016-04-21 16:52:39.419906716 +
+@@ -1329,6 +1329,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -1345,9 +1348,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/eclass/ELT-patches/ppc64le/2.4.4 b/eclass/ELT-patches/ppc64le/2.4.4
new file mode 100644
index 000..e3e4637
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.4
@@ -0,0 +1,15 @@
+--- m4/libtool.m4.orig 2016-04-21 16:59:06.039629474 +
 m4/libtool.m4  2016-04-21 17:00:10.564264157 +
+@@ -1386,10 +1386,10 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
diff --git a/eclass/ELT-patches/ppc64le/2.4.6 b/eclass/ELT-patches/ppc64le/2.4.6
new file mode 100644
index 000..711ceb2
--- /dev/null
+++ b/eclass/ELT-patches/ppc64le/2.4.6
@@ -0,0 +1,15 @@
+--- m4/libtool.m4.orig 2016-04-21 16:42:22.170586778 +
 m4/libtool.m4  2016-04-21 16:43:41.571195049 +
+@@ -1417,10 +1417,10 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-powerpcle-*linux*)
++powerpcle-*linux*|powerpc64le-*linux*)
+   LD="${LD-ld} -m elf64lppc"
+   ;;
+-powerpc-*linux*)
++powerpc-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
+ s390*-*linux*|s390*-*tpf*)
diff --git a/eclass/libtool.eclass b/eclass/libtool.eclass
index 47ef812..9f56c20 100644
--- a/eclass/libtool.eclass
+++ b/eclass/libtool.eclass
@@ -144,7 +144,7 @@ elibtoolize() {
local deptoremove=
local do_shallow="no"
local force="false"
-   local elt_patches="install-sh ltmain portage relink max_cmd_len sed 
test tmp cross as-needed target-nm"
+   local elt_patches="install-sh ltmain portage relink max_cmd_len sed 
test tmp cross as-needed target-nm ppc64le"
 
for x in "$@" ; do
case ${x} in
@@ -417,6 +417,10 @@ elibtoolize() {
ELT_walk_patches "${d}/configure" "${p}"
ret=$?
;;
+   ppc64le)
+   ELT_walk_patches "${d}/configure" "${p}"
+   ret=$?
+   ;;
*)
# ltmain.sh patches are applied above
;;
-- 
2.7.3

Re: [gentoo-dev] [PATCH v1] eclass/toolchain-bintuils: enable targets powerpc-linux-gnu for ppc64

2016-04-20 Thread Leno Hou

On Wed, Apr 20, 2016 at 11:07 PM, Mike Frysinger <vap...@gentoo.org> wrote:

> On 20 Apr 2016 13:52, Leno Hou wrote:
> > Authored-by: Linda Jiang <linda.q...@gmail.com>
> > ---
> >  eclass/toolchain-binutils.eclass | 1 +
> >  1 file changed, 1 insertion(+)
>
> when you submit a patch that is not extremely obvious, you must provide
> details/justification in the commit message.  otherwise we're forced to
> try and guess what/why it is you want to do things, and ultimately we
> tend to start of just saying "no".
>

Sorry, We describes details/justification in  Gentoo Bugzilla#580614
<https://bugs.gentoo.org/show_bug.cgi?id=580614>. Explain here again.

1) When use CHOST="powerpc64le-unknown-linux-gnu" (active host?) to build
binutils. there is no birch support.
See current supported emulations#powerpc64le-unknown-linux-gnu-ld -V

leno@localhost ~ $ powerpc64le-unknown-linux-gnu-ld -V

GNU ld (Gentoo 2.25.1 p1.1) 2.25.1

  Supported emulations:

   elf64lppc

   elf32lppc

   elf32lppclinux

   elf32lppcsim

   But we want elf64ppc for building grub2. If we there is no elf64ppc
emulation, we can't compiling grub2 and grub2-install
for ppc64le platform.

2) Following are the emulations what we want

leno@localhost ~ $ powerpc64le-unknown-linux-gnu-ld -V

GNU ld (Gentoo 2.25.1 p1.1) 2.25.1

  Supported emulations:

   elf64lppc

   elf32lppc

   elf32lppclinux

   elf32lppcsim

   elf32ppclinux

   elf32ppc

   elf32ppcsim

   elf64ppc

3) Linda Jiang found that *--enable-targets=all *make on sense to build the
above emulations what we want.
But *--enable-targets="powerpc-linux-gnu" *built the targets we want.
If there is no other arch-specific
handled like this, Is there another can handle this case? where is the
file you attached ?

and indeed, when i query a default ppc64 linker, it says it already
> supports both 32bit & 64bit targets:
> $ powerpc64-unknown-linux-gnu-ld --help | grep supported
> powerpc64-unknown-linux-gnu-ld: supported targets: elf64-powerpc
> elf64-powerpcle elf32-powerpc elf32-powerpcle aixcoff-rs6000
> aixcoff64-rs6000 aix5coff64-rs6000 elf64-little elf64-big elf32-little
> elf32-big plugin srec symbolsrec verilog tekhex binary ihex
> powerpc64-unknown-linux-gnu-ld: supported emulations: elf64ppc elf32ppc
> elf32ppclinux elf32ppcsim
>
> it would have to of course in order for biarch support (which works)
> which is how we build 64-bit kernels in a 32-bit userland.
> -mike
>

[gentoo-dev] [PATCH v1] eclass/toolchain-bintuils: enable targets powerpc-linux-gnu for ppc64

2016-04-19 Thread Leno Hou

Authored-by: Linda Jiang 
---
 eclass/toolchain-binutils.eclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/eclass/toolchain-binutils.eclass b/eclass/toolchain-binutils.eclass
index a23300f..6d2dde8 100644
--- a/eclass/toolchain-binutils.eclass
+++ b/eclass/toolchain-binutils.eclass
@@ -271,6 +271,7 @@ toolchain-binutils_src_configure() {
# We used to do it for everyone, but it's slow on 32bit arches. #438522
case $(tc-arch) in
ppc|sparc|x86) myconf+=( --enable-64-bit-bfd ) ;;
+   ppc64) myconf+=( --enable-targets="powerpc-linux-gnu" ) ;;
esac
 
use multitarget && myconf+=( --enable-targets=all --enable-64-bit-bfd )
-- 
1.9.1

Re: [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

On Tue, Apr 19, 2016 at 10:51 PM, Leno Hou <leno...@gmail.com> wrote:

> On Tue, Apr 19, 2016 at 10:36 PM, Michał Górny <mgo...@gentoo.org> wrote:
>
>> On Tue, 19 Apr 2016 22:32:51 +0800
>> Leno Hou <leno...@gmail.com> wrote:
>>
>> > On Tue, Apr 19, 2016 at 10:20 PM, Michał Górny <mgo...@gentoo.org>
>> wrote:
>> >
>> > > On Tue, 19 Apr 2016 22:12:59 +0800
>> > > Leno Hou <leno...@gmail.com> wrote:
>> > >
>> > > > ---
>> > > >  .../opensp-1.5.2-configure-with-ppc64le.patch  | 26
>> > > ++
>> > > >  app-text/opensp/opensp-1.5.2-r3.ebuild |  3 ++-
>> > > >  app-text/opensp/opensp-1.5.2-r4.ebuild |  1 +
>> > > >  3 files changed, 29 insertions(+), 1 deletion(-)
>> > > >  create mode 100644
>> > > app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
>> > > >
>> > > > diff --git
>> > > a/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
>> > > b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
>> > > > new file mode 100644
>> > > > index 000..e1c8bef
>> > > > --- /dev/null
>> > > > +++
>> b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
>> > > > @@ -0,0 +1,26 @@
>> > > > +--- configure.orig   2016-04-09 16:24:17.507053635 +
>> > > >  configure2016-04-09 16:25:41.851918142 +
>> > > > +@@ -4947,6 +4947,9 @@
>> > > > + ppc64-*linux*|powerpc64-*linux*)
>> > > > +   LD="${LD-ld} -m elf32ppclinux"
>> > > > +   ;;
>> > > > ++ppc64le-*linux*|powerpc64le-*linux*)
>> > > > ++  LD="${LD-ld} -m elf32lppclinux"
>> > > > ++  ;;
>> > > > + s390x-*linux*)
>> > > > +   LD="${LD-ld} -m elf_s390"
>> > > > +   ;;
>> > > > +@@ -4960,9 +4963,12 @@
>> > > > + x86_64-*linux*)
>> > > > +   LD="${LD-ld} -m elf_x86_64"
>> > > > +   ;;
>> > > > +-ppc*-*linux*|powerpc*-*linux*)
>> > > > ++ppc64-*linux*|powerpc64-*linux*)
>> > > > +   LD="${LD-ld} -m elf64ppc"
>> > > > +   ;;
>> > > > ++ppc64le-*linux*|powerpc64le-*linux*)
>> > > > ++  LD="${LD-ld} -m elf64lppc"
>> > > > ++  ;;
>> > > > + s390*-*linux*)
>> > > > +   LD="${LD-ld} -m elf64_s390"
>> > > > +   ;;
>> > >
>> > > Isn't that the generic kind of problem usually fixed via elibtoolize?
>> > >
>> >
>> >  How to fix it via elibtoolize ? Thanks if you give me in detail ;-)
>>
>> I don't know the details, I just know it does some random common
>> patching to configure files. Take a look at libtool.eclass and
>> ELT-patches.
>
>
> Seems can't  fix this in libtool.eclass and ELT-patches.
>
>

How goes today ? I've got strict on some metadata.xml stuffs with github PRs
QA check
<https://qa-reports.gentoo.org/output/gentoo-ci/dfdf38e/output.html> ..

-Leno Hou

Re: [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

On Tue, Apr 19, 2016 at 10:36 PM, Michał Górny <mgo...@gentoo.org> wrote:

> On Tue, 19 Apr 2016 22:32:51 +0800
> Leno Hou <leno...@gmail.com> wrote:
>
> > On Tue, Apr 19, 2016 at 10:20 PM, Michał Górny <mgo...@gentoo.org>
> wrote:
> >
> > > On Tue, 19 Apr 2016 22:12:59 +0800
> > > Leno Hou <leno...@gmail.com> wrote:
> > >
> > > > ---
> > > >  .../opensp-1.5.2-configure-with-ppc64le.patch  | 26
> > > ++
> > > >  app-text/opensp/opensp-1.5.2-r3.ebuild |  3 ++-
> > > >  app-text/opensp/opensp-1.5.2-r4.ebuild |  1 +
> > > >  3 files changed, 29 insertions(+), 1 deletion(-)
> > > >  create mode 100644
> > > app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > > >
> > > > diff --git
> > > a/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > > b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > > > new file mode 100644
> > > > index 000..e1c8bef
> > > > --- /dev/null
> > > > +++ b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > > > @@ -0,0 +1,26 @@
> > > > +--- configure.orig   2016-04-09 16:24:17.507053635 +
> > > >  configure2016-04-09 16:25:41.851918142 +
> > > > +@@ -4947,6 +4947,9 @@
> > > > + ppc64-*linux*|powerpc64-*linux*)
> > > > +   LD="${LD-ld} -m elf32ppclinux"
> > > > +   ;;
> > > > ++ppc64le-*linux*|powerpc64le-*linux*)
> > > > ++  LD="${LD-ld} -m elf32lppclinux"
> > > > ++  ;;
> > > > + s390x-*linux*)
> > > > +   LD="${LD-ld} -m elf_s390"
> > > > +   ;;
> > > > +@@ -4960,9 +4963,12 @@
> > > > + x86_64-*linux*)
> > > > +   LD="${LD-ld} -m elf_x86_64"
> > > > +   ;;
> > > > +-ppc*-*linux*|powerpc*-*linux*)
> > > > ++ppc64-*linux*|powerpc64-*linux*)
> > > > +   LD="${LD-ld} -m elf64ppc"
> > > > +   ;;
> > > > ++ppc64le-*linux*|powerpc64le-*linux*)
> > > > ++  LD="${LD-ld} -m elf64lppc"
> > > > ++  ;;
> > > > + s390*-*linux*)
> > > > +   LD="${LD-ld} -m elf64_s390"
> > > > +   ;;
> > >
> > > Isn't that the generic kind of problem usually fixed via elibtoolize?
> > >
> >
> >  How to fix it via elibtoolize ? Thanks if you give me in detail ;-)
>
> I don't know the details, I just know it does some random common
> patching to configure files. Take a look at libtool.eclass and
> ELT-patches.


Seems can't  fix this in libtool.eclass and ELT-patches.

-Leno Hou

Re: [gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

On Tue, Apr 19, 2016 at 10:20 PM, Michał Górny <mgo...@gentoo.org> wrote:

> On Tue, 19 Apr 2016 22:12:59 +0800
> Leno Hou <leno...@gmail.com> wrote:
>
> > ---
> >  .../opensp-1.5.2-configure-with-ppc64le.patch  | 26
> ++
> >  app-text/opensp/opensp-1.5.2-r3.ebuild |  3 ++-
> >  app-text/opensp/opensp-1.5.2-r4.ebuild |  1 +
> >  3 files changed, 29 insertions(+), 1 deletion(-)
> >  create mode 100644
> app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> >
> > diff --git
> a/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > new file mode 100644
> > index 000..e1c8bef
> > --- /dev/null
> > +++ b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
> > @@ -0,0 +1,26 @@
> > +--- configure.orig   2016-04-09 16:24:17.507053635 +
> >  configure2016-04-09 16:25:41.851918142 +
> > +@@ -4947,6 +4947,9 @@
> > + ppc64-*linux*|powerpc64-*linux*)
> > +   LD="${LD-ld} -m elf32ppclinux"
> > +   ;;
> > ++ppc64le-*linux*|powerpc64le-*linux*)
> > ++  LD="${LD-ld} -m elf32lppclinux"
> > ++  ;;
> > + s390x-*linux*)
> > +   LD="${LD-ld} -m elf_s390"
> > +   ;;
> > +@@ -4960,9 +4963,12 @@
> > + x86_64-*linux*)
> > +   LD="${LD-ld} -m elf_x86_64"
> > +   ;;
> > +-ppc*-*linux*|powerpc*-*linux*)
> > ++ppc64-*linux*|powerpc64-*linux*)
> > +   LD="${LD-ld} -m elf64ppc"
> > +   ;;
> > ++ppc64le-*linux*|powerpc64le-*linux*)
> > ++  LD="${LD-ld} -m elf64lppc"
> > ++  ;;
> > + s390*-*linux*)
> > +   LD="${LD-ld} -m elf64_s390"
> > +   ;;
>
> Isn't that the generic kind of problem usually fixed via elibtoolize?
>

 How to fix it via elibtoolize ? Thanks if you give me in detail ;-)

--
> Best regards,
> Michał Górny
> <http://dev.gentoo.org/~mgorny/>
>

[gentoo-dev] [PATCH v1][ 7/8] sys-libs/gdbm: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 .../files/gdbm-1.11-configure-with-ppc64le.patch   | 26 ++
 sys-libs/gdbm/gdbm-1.11.ebuild |  1 +
 2 files changed, 27 insertions(+)
 create mode 100644 sys-libs/gdbm/files/gdbm-1.11-configure-with-ppc64le.patch

diff --git a/sys-libs/gdbm/files/gdbm-1.11-configure-with-ppc64le.patch 
b/sys-libs/gdbm/files/gdbm-1.11-configure-with-ppc64le.patch
new file mode 100644
index 000..2bdba70
--- /dev/null
+++ b/sys-libs/gdbm/files/gdbm-1.11-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-09 17:02:36.818123640 +
 configure  2016-04-09 17:04:09.407071685 +
+@@ -6898,6 +6898,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -6914,9 +6917,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/sys-libs/gdbm/gdbm-1.11.ebuild b/sys-libs/gdbm/gdbm-1.11.ebuild
index 06ebd03..aa9d6cf 100644
--- a/sys-libs/gdbm/gdbm-1.11.ebuild
+++ b/sys-libs/gdbm/gdbm-1.11.ebuild
@@ -26,6 +26,7 @@ RDEPEND="
 EX_S="${WORKDIR}"/${EX_P}
 
 src_prepare() {
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
elibtoolize
 }
 
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 8/8] sys-process/procps: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 .../procps-3.3.10-configure-with-ppc64le.patch | 26 ++
 sys-process/procps/procps-3.3.10-r1.ebuild |  1 +
 2 files changed, 27 insertions(+)
 create mode 100644 
sys-process/procps/files/procps-3.3.10-configure-with-ppc64le.patch

diff --git 
a/sys-process/procps/files/procps-3.3.10-configure-with-ppc64le.patch 
b/sys-process/procps/files/procps-3.3.10-configure-with-ppc64le.patch
new file mode 100644
index 000..9251a09
--- /dev/null
+++ b/sys-process/procps/files/procps-3.3.10-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-09 00:44:30.728256474 +
 configure  2016-04-09 00:47:52.098589452 +
+@@ -9367,6 +9367,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -9383,9 +9386,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/sys-process/procps/procps-3.3.10-r1.ebuild 
b/sys-process/procps/procps-3.3.10-r1.ebuild
index f254f34..237ebda 100644
--- a/sys-process/procps/procps-3.3.10-r1.ebuild
+++ b/sys-process/procps/procps-3.3.10-r1.ebuild
@@ -34,6 +34,7 @@ src_prepare() {
epatch "${FILESDIR}"/${PN}-3.3.8-kill-neg-pid.patch # 
http://crbug.com/255209
epatch "${FILESDIR}"/${P}-pmap-unreadable.patch #404389
epatch "${FILESDIR}"/${P}-tests-no-tty.patch #461302
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
sed -i -e 's:systemd-login:systemd:' configure || die #501306
 }
 
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 5/8] sys-apps/acl: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 sys-apps/acl/acl-2.2.52-r1.ebuild  |  2 ++
 .../files/acl-2.2.52-configure-with-ppc64le.patch  | 26 ++
 2 files changed, 28 insertions(+)
 create mode 100644 sys-apps/acl/files/acl-2.2.52-configure-with-ppc64le.patch

diff --git a/sys-apps/acl/acl-2.2.52-r1.ebuild 
b/sys-apps/acl/acl-2.2.52-r1.ebuild
index d1d2169..e2112b3 100644
--- a/sys-apps/acl/acl-2.2.52-r1.ebuild
+++ b/sys-apps/acl/acl-2.2.52-r1.ebuild
@@ -31,6 +31,8 @@ src_prepare() {
|| die
strip-linguas po
 
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
+
# same as https://savannah.nongnu.org/bugs/index.php?39736
multilib_copy_sources
 }
diff --git a/sys-apps/acl/files/acl-2.2.52-configure-with-ppc64le.patch 
b/sys-apps/acl/files/acl-2.2.52-configure-with-ppc64le.patch
new file mode 100644
index 000..52fc63c
--- /dev/null
+++ b/sys-apps/acl/files/acl-2.2.52-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-09 08:34:52.432446384 +
 configure  2016-04-09 08:36:45.785578064 +
+@@ -5487,6 +5487,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -5503,9 +5506,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 6/8] sys-apps/attr: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 sys-apps/attr/attr-2.4.47-r2.ebuild|  1 +
 .../files/attr-2.4.47-configure-with-ppc64le.patch | 26 ++
 2 files changed, 27 insertions(+)
 create mode 100644 sys-apps/attr/files/attr-2.4.47-configure-with-ppc64le.patch

diff --git a/sys-apps/attr/attr-2.4.47-r2.ebuild 
b/sys-apps/attr/attr-2.4.47-r2.ebuild
index 11a6bda..2803514 100644
--- a/sys-apps/attr/attr-2.4.47-r2.ebuild
+++ b/sys-apps/attr/attr-2.4.47-r2.ebuild
@@ -29,6 +29,7 @@ src_prepare() {
include/builddefs.in \
|| die
strip-linguas -u po
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
multilib_copy_sources # https://savannah.nongnu.org/bugs/index.php?39736
 }
 
diff --git a/sys-apps/attr/files/attr-2.4.47-configure-with-ppc64le.patch 
b/sys-apps/attr/files/attr-2.4.47-configure-with-ppc64le.patch
new file mode 100644
index 000..13e8dfc
--- /dev/null
+++ b/sys-apps/attr/files/attr-2.4.47-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-09 01:41:18.087752381 +
 configure  2016-04-09 01:43:29.129086786 +
+@@ -5454,6 +5454,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -5470,9 +5473,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 4/8] net-libs/libmnl: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 .../libmnl-1.0.3-configure-with-ppc64le.patch  | 26 ++
 net-libs/libmnl/libmnl-1.0.3-r1.ebuild |  4 
 2 files changed, 30 insertions(+)
 create mode 100644 
net-libs/libmnl/files/libmnl-1.0.3-configure-with-ppc64le.patch

diff --git a/net-libs/libmnl/files/libmnl-1.0.3-configure-with-ppc64le.patch 
b/net-libs/libmnl/files/libmnl-1.0.3-configure-with-ppc64le.patch
new file mode 100644
index 000..d46bcc9
--- /dev/null
+++ b/net-libs/libmnl/files/libmnl-1.0.3-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-08 16:30:09.521850897 +
 configure  2016-04-08 16:34:25.932337241 +
+@@ -6309,6 +6309,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -6325,9 +6328,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/net-libs/libmnl/libmnl-1.0.3-r1.ebuild 
b/net-libs/libmnl/libmnl-1.0.3-r1.ebuild
index 4b0bbc2..aa57068 100644
--- a/net-libs/libmnl/libmnl-1.0.3-r1.ebuild
+++ b/net-libs/libmnl/libmnl-1.0.3-r1.ebuild
@@ -15,6 +15,10 @@ SLOT="0"
 KEYWORDS="alpha amd64 arm arm64 hppa ia64 m68k ~mips ppc ppc64 s390 sh sparc 
x86 ~amd64-linux"
 IUSE="examples static-libs"
 
+src_prepare() {
+epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
+}
+
 src_configure() {
econf $(use_enable static-libs static)
 }
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 3/8] net-firewall/iptables: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 .../iptables-1.4.21-configure-with-ppc64le.patch   | 26 ++
 net-firewall/iptables/iptables-1.4.21-r1.ebuild|  3 +++
 net-firewall/iptables/iptables-1.4.21-r2.ebuild|  2 ++
 net-firewall/iptables/iptables-1.4.21-r3.ebuild|  2 ++
 net-firewall/iptables/iptables-1.4.21-r4.ebuild|  1 +
 5 files changed, 34 insertions(+)
 create mode 100644 
net-firewall/iptables/files/iptables-1.4.21-configure-with-ppc64le.patch

diff --git 
a/net-firewall/iptables/files/iptables-1.4.21-configure-with-ppc64le.patch 
b/net-firewall/iptables/files/iptables-1.4.21-configure-with-ppc64le.patch
new file mode 100644
index 000..58ebb6a
--- /dev/null
+++ b/net-firewall/iptables/files/iptables-1.4.21-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-08 14:03:11.035208027 -0400
 configure  2016-04-08 14:05:22.270056952 -0400
+@@ -6707,6 +6707,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -6723,9 +6726,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/net-firewall/iptables/iptables-1.4.21-r1.ebuild 
b/net-firewall/iptables/iptables-1.4.21-r1.ebuild
index 056b1b4..288f2da 100644
--- a/net-firewall/iptables/iptables-1.4.21-r1.ebuild
+++ b/net-firewall/iptables/iptables-1.4.21-r1.ebuild
@@ -31,6 +31,9 @@ src_prepare() {
# use the saner headers from the kernel
rm -f include/linux/{kernel,types}.h
 
+   # fix the configure problem for ppc64le
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
+
# Only run autotools if user patched something
epatch_user && eautoreconf || elibtoolize
 }
diff --git a/net-firewall/iptables/iptables-1.4.21-r2.ebuild 
b/net-firewall/iptables/iptables-1.4.21-r2.ebuild
index e87e4ed..1baaf2d 100644
--- a/net-firewall/iptables/iptables-1.4.21-r2.ebuild
+++ b/net-firewall/iptables/iptables-1.4.21-r2.ebuild
@@ -35,6 +35,8 @@ src_prepare() {
rm -f include/linux/{kernel,types}.h
 
epatch "${FILESDIR}"/${P}-configure.patch #557586
+   # fix the configure problem for ppc64le
+epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
 
# Only run autotools if user patched something
epatch_user && eautoreconf || elibtoolize
diff --git a/net-firewall/iptables/iptables-1.4.21-r3.ebuild 
b/net-firewall/iptables/iptables-1.4.21-r3.ebuild
index ef4eb78..7eb801f 100644
--- a/net-firewall/iptables/iptables-1.4.21-r3.ebuild
+++ b/net-firewall/iptables/iptables-1.4.21-r3.ebuild
@@ -36,6 +36,8 @@ src_prepare() {
 
epatch "${FILESDIR}"/${P}-configure.patch #557586
epatch "${FILESDIR}"/${P}-static-connlabel-config.patch #558234
+epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
+
 
# Only run autotools if user patched something
epatch_user && eautoreconf || elibtoolize
diff --git a/net-firewall/iptables/iptables-1.4.21-r4.ebuild 
b/net-firewall/iptables/iptables-1.4.21-r4.ebuild
index 49b9bd8..27c89fe 100644
--- a/net-firewall/iptables/iptables-1.4.21-r4.ebuild
+++ b/net-firewall/iptables/iptables-1.4.21-r4.ebuild
@@ -36,6 +36,7 @@ src_prepare() {
 
epatch "${FILESDIR}"/${P}-configure.patch #557586
epatch "${FILESDIR}"/${P}-static-connlabel-config.patch #558234
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
 
# Only run autotools if user patched something
epatch_user && eautoreconf || elibtoolize
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 1/8] app-text/opensp: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 .../opensp-1.5.2-configure-with-ppc64le.patch  | 26 ++
 app-text/opensp/opensp-1.5.2-r3.ebuild |  3 ++-
 app-text/opensp/opensp-1.5.2-r4.ebuild |  1 +
 3 files changed, 29 insertions(+), 1 deletion(-)
 create mode 100644 
app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch

diff --git a/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch 
b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
new file mode 100644
index 000..e1c8bef
--- /dev/null
+++ b/app-text/opensp/files/opensp-1.5.2-configure-with-ppc64le.patch
@@ -0,0 +1,26 @@
+--- configure.orig 2016-04-09 16:24:17.507053635 +
 configure  2016-04-09 16:25:41.851918142 +
+@@ -4947,6 +4947,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -4960,9 +4963,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
diff --git a/app-text/opensp/opensp-1.5.2-r3.ebuild 
b/app-text/opensp/opensp-1.5.2-r3.ebuild
index 9f97607..28c32fc 100644
--- a/app-text/opensp/opensp-1.5.2-r3.ebuild
+++ b/app-text/opensp/opensp-1.5.2-r3.ebuild
@@ -33,7 +33,8 @@ S=${WORKDIR}/${MY_P}
 src_prepare() {
epatch \
"${FILESDIR}"/${PN}-1.5-gcc34.patch \
-   "${FILESDIR}"/${P}-fix-segfault.patch
+   "${FILESDIR}"/${P}-fix-segfault.patch \
+   "${FILESDIR}"/${P}-configure-with-ppc64le.patch
 }
 
 src_configure() {
diff --git a/app-text/opensp/opensp-1.5.2-r4.ebuild 
b/app-text/opensp/opensp-1.5.2-r4.ebuild
index 2abcab3..0851155 100644
--- a/app-text/opensp/opensp-1.5.2-r4.ebuild
+++ b/app-text/opensp/opensp-1.5.2-r4.ebuild
@@ -33,6 +33,7 @@ S=${WORKDIR}/${MY_P}
 
 src_prepare() {
epatch "${FILESDIR}"/${P}-fix-segfault.patch
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
use prefix && eautoreconf
 }
 
-- 
1.9.1

[gentoo-dev] [PATCH v1][ 2/8] dev-libs/expat: Fix ppc64le configure problem

2016-04-19 Thread Leno Hou

---
 dev-libs/expat/expat-2.1.0-r5.ebuild   |  1 +
 .../files/expat-2.1.0-configure-with-ppc64le.patch | 78 ++
 2 files changed, 79 insertions(+)
 create mode 100644 
dev-libs/expat/files/expat-2.1.0-configure-with-ppc64le.patch

diff --git a/dev-libs/expat/expat-2.1.0-r5.ebuild 
b/dev-libs/expat/expat-2.1.0-r5.ebuild
index c0aca16..bb3d559 100644
--- a/dev-libs/expat/expat-2.1.0-r5.ebuild
+++ b/dev-libs/expat/expat-2.1.0-r5.ebuild
@@ -19,6 +19,7 @@ RDEPEND="abi_x86_32? ( 
!<=app-emulation/emul-linux-x86-baselibs-20130224-r6
 src_prepare() {
epatch "${FILESDIR}"/${P}-xmlwfargs.patch
epatch "${FILESDIR}"/${P}-mozilla-sanity-check-size.patch #555642
+   epatch "${FILESDIR}"/${P}-configure-with-ppc64le.patch
elibtoolize
 }
 
diff --git a/dev-libs/expat/files/expat-2.1.0-configure-with-ppc64le.patch 
b/dev-libs/expat/files/expat-2.1.0-configure-with-ppc64le.patch
new file mode 100644
index 000..2d7f01e
--- /dev/null
+++ b/dev-libs/expat/files/expat-2.1.0-configure-with-ppc64le.patch
@@ -0,0 +1,78 @@
+--- configure.orig 2016-04-13 16:49:24.906810546 +
 configure  2016-04-13 16:52:37.792699936 +
+@@ -5932,6 +5932,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -5948,9 +5951,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
+--- aclocal.m4.orig2016-04-13 16:53:39.097309462 +
 aclocal.m4 2016-04-13 16:55:33.502456982 +
+@@ -1292,6 +1292,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -1308,9 +1311,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
+--- m4/libtool.m4.org  2016-04-13 16:58:32.884276527 +
 m4/libtool.m4  2016-04-13 16:59:47.713041421 +
+@@ -1285,6 +1285,9 @@
+ ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf32ppclinux"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf32lppclinux"
++  ;;
+ s390x-*linux*)
+   LD="${LD-ld} -m elf_s390"
+   ;;
+@@ -1301,9 +1304,12 @@
+ x86_64-*linux*)
+   LD="${LD-ld} -m elf_x86_64"
+   ;;
+-ppc*-*linux*|powerpc*-*linux*)
++ppc64-*linux*|powerpc64-*linux*)
+   LD="${LD-ld} -m elf64ppc"
+   ;;
++ppc64le-*linux*|powerpc64le-*linux*)
++  LD="${LD-ld} -m elf64lppc"
++  ;;
+ s390*-*linux*|s390*-*tpf*)
+   LD="${LD-ld} -m elf64_s390"
+   ;;
-- 
1.9.1

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-03 Thread Leno Hou

On Tue, Nov 3, 2015 at 3:45 PM, Justin (jlec) <j...@gentoo.org> wrote:

> On 02/11/15 23:38, William Hubbs wrote:
> Hi William,
>
> but instead of adding
>
> DEPEND="||·(
> >=dev-lang/go-1.4
> >=sys-devel/gcc-5.1.0:=[go]
>
> to ebuilds, you could create a virtual/go with that dependency and make all
> packages depend on that instead of this || (). Maybe in future clang gets
> also
> support for go, then you would need to edit again all ebuilds. Having a
> virtual
> for that case is much simpler. This is how we are doing it for fortran.
>
> Another problem which you have with these split deps is the following.
> Imagine
> the user has gcc-5[go] installed, which fullfills the dependency
> requirement.
> But she selected gcc-4.9 as the active compiler, which doesn't have go
> support.
>
The build will fail. For fortran we test in pkg_setup if we have a working
> fortran compiler present. You would need to do the same for go compiler.
>
> Justin
>
>
Pretty good ! I'll take it.  thanks.

-Leno Hou

[gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread Leno Hou

1. go compiler only support x86 platform
2. gcc 5 includes go command to build go apps
3. for coreos enablement, it's use gcc 5 to build go apps

Signed-off-by: Leno Hou <leno...@gmail.com>
---
 app-admin/consul-template/consul-template-0.9.0-r1.ebuild   | 5 -
 app-admin/consul-template/consul-template-0.9.0.ebuild  | 5 -
 app-admin/consul-template/consul-template-.ebuild   | 5 -
 app-admin/consul/consul-0.5.2-r1.ebuild | 5 -
 app-admin/consul/consul-0.5.2.ebuild| 5 -
 app-admin/consul/consul-.ebuild | 5 -
 app-admin/fleet/fleet-0.11.0-r1.ebuild  | 5 -
 app-admin/fleet/fleet-0.11.1.ebuild | 5 -
 app-admin/fleet/fleet-0.11.5.ebuild | 5 -
 app-admin/fleet/fleet-.ebuild   | 5 -
 app-admin/logstash-forwarder/logstash-forwarder-0.4.0-r1.ebuild | 2 +-
 app-admin/mongo-tools/mongo-tools-3.0.5.ebuild  | 5 -
 app-admin/mongo-tools/mongo-tools-3.0.6.ebuild  | 5 -
 app-admin/mongo-tools/mongo-tools-3.0.7.ebuild  | 5 -
 app-crypt/etcd-ca/etcd-ca-0_p20140903.ebuild| 2 +-
 app-crypt/etcd-ca/etcd-ca-0_p20150423-r1.ebuild | 2 +-
 app-crypt/etcd-ca/etcd-ca-0_p20150423.ebuild| 2 +-
 app-emulation/docker/docker-1.6.1.ebuild| 5 -
 app-emulation/docker/docker-1.6.2.ebuild| 5 -
 app-emulation/docker/docker-1.7.1.ebuild| 6 +-
 app-emulation/flannel/flannel-0.5.4.ebuild  | 2 +-
 app-emulation/lxd/lxd-0.16.ebuild   | 5 -
 app-emulation/lxd/lxd-0.18.ebuild   | 5 -
 app-emulation/lxd/lxd-0.20.ebuild   | 5 -
 app-emulation/rkt/rkt-0.8.0.ebuild  | 5 -
 app-emulation/rkt/rkt-.ebuild   | 5 -
 app-emulation/runc/runc-0.0.2.ebuild| 2 +-
 dev-db/etcd/etcd-2.0.10-r1.ebuild   | 2 +-
 dev-db/etcd/etcd-2.2.1.ebuild   | 2 +-
 dev-db/etcdctl/etcdctl-0.4.6-r1.ebuild  | 2 +-
 dev-db/etcdctl/etcdctl-0.4.6.ebuild | 2 +-
 dev-db/go-etcd/go-etcd-0_p20141013-r1.ebuild| 2 +-
 dev-db/go-etcd/go-etcd-2.0.0-r1.ebuild  | 2 +-
 dev-db/go-etcd/go-etcd-2.0.0.ebuild | 2 +-
 dev-libs/go-fuse/go-fuse-0_p20140812-r1.ebuild  | 2 +-
 dev-libs/go-fuse/go-fuse-0_p20150422.ebuild | 2 +-
 dev-libs/go-fuse/go-fuse-.ebuild| 2 +-
 dev-libs/go-usb/go-usb-.ebuild  | 2 +-
 dev-vcs/hub/hub-2.2.0-r1.ebuild | 2 +-
 eclass/golang-base.eclass   | 2 +-
 sys-apps/lmctfy/lmctfy-0.5.0-r1.ebuild  | 5 -
 sys-apps/lmctfy/lmctfy-0.5.0.ebuild | 5 -
 sys-fs/etcd-fs/etcd-fs-0_p20140620.ebuild   | 5 -
 sys-fs/go-mtpfs/go-mtpfs-.ebuild| 5 -
 44 files changed, 120 insertions(+), 44 deletions(-)

diff --git a/app-admin/consul-template/consul-template-0.9.0-r1.ebuild 
b/app-admin/consul-template/consul-template-0.9.0-r1.ebuild
index cbc1059..a24ec80 100644
--- a/app-admin/consul-template/consul-template-0.9.0-r1.ebuild
+++ b/app-admin/consul-template/consul-template-0.9.0-r1.ebuild
@@ -14,7 +14,10 @@ LICENSE="MPL-2.0"
 SLOT="0"
 IUSE="test"
 
-DEPEND=">=dev-lang/go-1.4:=
+DEPEND="|| (
+   >=dev-lang/go-1.4:=
+   >=sys-devel/gcc-5.1.0:=[go]
+   )
test? ( dev-go/go-tools )
app-admin/consul
app-admin/vault"
diff --git a/app-admin/consul-template/consul-template-0.9.0.ebuild 
b/app-admin/consul-template/consul-template-0.9.0.ebuild
index 80a3de8..c35ed0a 100644
--- a/app-admin/consul-template/consul-template-0.9.0.ebuild
+++ b/app-admin/consul-template/consul-template-0.9.0.ebuild
@@ -14,7 +14,10 @@ LICENSE="MPL-2.0"
 SLOT="0"
 IUSE="test"
 
-DEPEND=">=dev-lang/go-1.4
+DEPEND="|| (
+   >=dev-lang/go-1.4
+   >=sys-devel/gcc-5.1.0:=[go]
+   )
test? ( dev-go/go-tools )
app-admin/consul
app-admin/vault"
diff --git a/app-admin/consul-template/consul-template-.ebuild 
b/app-admin/consul-template/consul-template-.ebuild
index 0dcf7f1..e43a1fd 100644
--- a/app-admin/consul-template/consul-template-.ebuild
+++ b/app-admin/consul-template/consul-templ

Re: [gentoo-dev] [PATCH v1] enable gccgo for all platform

2015-11-02 Thread Leno Hou

On Tue, Nov 3, 2015 at 6:38 AM, William Hubbs <willi...@gentoo.org> wrote:

> On Mon, Nov 02, 2015 at 09:12:30PM +0100, Justin Lecher (jlec) wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > How about a virtual here?
>
> I don't see that working out to well because the compilers are
> completely different from each other. As I said, the reference
> implementation of the go language is dev-lang/go and the other one, that
> is part of gcc, as I understand it, is not quite as fully developed as
> dev-lang/go.
>
>
As you said, I want to build packages use `go build` command.
1. The GCC 5 releases include a complete implementation of the Go 1.4 user
libraries. [1]
2. The Go 1.4 runtime is not fully merged, but that should not be visible
to Go programs.
3.  The GCC 5 includes go command like dev-lang/go
4.  Now I've successfully compiled docker on gentoo ppc64le by gcc5, see [2]
5.  So I think there're the same. but i'm not sure, Is dev/go-1.5  support
ppc64, s390 platform ?
 If not support,  DEPEND=" || ( >=dev-lang/go-1.4:=
>sys-devel/gcc-5.1.0:=[go] ) " would be better.

Links
[1] https://golang.org/doc/install/gccgo
[2] https://bpaste.net/show/e4c68cfec77c

-Leno Hou

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-09-25 Thread Leno Hou

On Fri, Sep 25, 2015 at 3:34 PM, Anthony G. Basile <bluen...@gentoo.org>
wrote:

> On 9/25/15 1:05 AM, Mike Frysinger wrote:
>
>> On 25 Sep 2015 10:32, Leno Hou wrote:
>>
>>> On Thu, Sep 24, 2015 at 11:07 PM, Mike Frysinger wrote:
>>>
>>>> On 14 Aug 2015 15:52, Leno Hou wrote:
>>>>
>>>>> On Wed, Aug 12, 2015 at 3:47 PM, Mike Frysinger wrote:
>>>>>
>>>>>> On 12 Aug 2015 15:20, Leno Hou wrote:
>>>>>>
>>>>>>> **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 ?
>>>>>
>>>> KVM is fine.  i'm assuming you can't boot a ppc64le vm when the host is
>>>> ppc64be ?
>>>>
>>> We can boot ppc64le by KVM on POWER7  (abbrev. PowerKVM)
>>> and KVM on Power7 is big endian. If you have real POWER7 hardware,
>>>
>> we have a Gentoo box running on a POWER7 from IBM:
>> IBM,8231-E2B POWER7 32 x 3.5GHz
>>
>> it has KVM enabled in it.  so i guess we should be able to start a LE
>> instance in KVM there.
>>
>> you can install Ubuntu or RedHat ( integrated with KVM by default) on
>>> POWER7.
>>>
>> are you really making this suggestion on a Gentoo list ? ;)
>> booting other distros isn't generally interesting to us.
>> don't you already have a Gentoo instance booting ?
>> -mike
>>
>
> @Leno, can you give me a url where i can download the stage3 and i'll try
> to set up a development environment on our power7.
>
> --
> Anthony G. Basile, Ph.D.
>

Download ppc64le seed stage3 here. http://pan.baidu.com/s/1uiVtc

-Leno Hou

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-09-24 Thread Leno Hou

On Fri, Sep 11, 2015 at 8:01 PM, Leno Hou <leno...@gmail.com> wrote:

>
> 2. We believe to make Gentoo support ppc64le, we still need to compile
> kernel and bootloader
>
>- Which version of kernel provided by Gentoo would you suggest us to
>use?
>
>   As to Ubuntu, there will be many patches to make the kernel
> workable, so how to patch
>   our Gentoo kernel  to make it work for ppc64le?
>

Upstream's 4.2.1 is OK  :-)
I've compiled sys-kernel/gentoo-sources-4.2.1 on Ubuntu and
successfully booted  Ubuntu as following.
root@ppc64le:~# uname -a
Linux ppc64le 4.2.1-gentoo #1 SMP Wed Sep 23 19:28:17 PDT 2015
ppc64le ppc64le ppc64le GNU/Linux


>- Which version of grub suitable for ppc64le ?  Is there any patches
>to ppc64le grub ?
>
> 3. When the gentoo we make out workable on ppc64le, we would like to know
> the process of
> making it officially supported by Gentoo community
>
>- For each arch, do we have a subteam to verify the packages? If so,
>how to reach these guys?
>- For hardware environment, does anyone have Power8 systems ?
>
>  Again, please apply POWER8 Systems and join our work  :-)
 [1]: https://www.runabove.com/instances/ibm-power8.xml
 [2]: https://ptopenlab.com/cloudlabconsole/#/
     [3]: http://osuosl.org/services/powerdev/request_hosting


> -Leno Hou
>

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-09-24 Thread Leno Hou

On Thu, Sep 24, 2015 at 11:07 PM, Mike Frysinger <vap...@gentoo.org> wrote:

> On 14 Aug 2015 15:52, Leno Hou wrote:
> > On Wed, Aug 12, 2015 at 3:47 PM, Mike Frysinger wrote:
> > > On 12 Aug 2015 15:20, Leno Hou wrote:
> > > > **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 ?
>
> KVM is fine.  i'm assuming you can't boot a ppc64le vm when the host is
> ppc64be ?

We can boot ppc64le by KVM on POWER7  (abbrev. PowerKVM)
and KVM on Power7 is big endian. If you have real POWER7 hardware,
you can install Ubuntu or RedHat ( integrated with KVM by default) on
POWER7.

> i don't think any Gentoo dev has access to ppc64le hardware,
> so we'd rely on ibm to fix bugs and such.
>

As above, we can boot ppc64le by KVM on POWER7. Is not mean that we can
booting/filing/fixing by KVM? If so, i'll try to get some KVM virtual
machines :-)

-mike
>

-Leno Hou

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-09-17 Thread Leno Hou

On Wed, Aug 12, 2015 at 4:30 PM, Anthony G. Basile <bluen...@gentoo.org>
wrote:

> On 8/12/15 3:47 AM, Mike Frysinger wrote:
>
>>
>> 4.  I would like become a developer of porting gentoo on ppc64le.  Anyone
>>> could help/mentor me to join this project ?
>>>
>> ideally someone on the ppc side would pick you up, but i think they've
>> been
>> a bit of a skeleton team of late.  so if need be, i can help you here.
>>
>
> I can help out here.

Great pleasure that you can pick me up. It would be nice that you can
tell me how
to reach guys ?  Now we have some ppc64le profile & patches needs to be
upload.

>
>
> **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 :).
>> -mike
>>
> We should also start building stage3s.

   stage3s for ppc64, or ppc64le ?  If its stage3s for ppc64le, that's
perfect to work together.

>
>
> --
> Anthony G. Basile, Ph.D.
> Gentoo Linux Developer [Hardened]
> E-Mail: bluen...@gentoo.org
> GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
> GnuPG ID  : F52D4BBA
>
>
>
Leno Hou
E-Mail: leno...@gmail.com

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-09-17 Thread Leno Hou

*Leno Hou*
E-mail :  leno...@gmail.com
Phone : 185-0093-5995

On Fri, Sep 11, 2015 at 8:01 PM, Leno Hou <leno...@gmail.com> wrote:
>
> This is a great pleasure to announce that we've made ppc64le stage 3.
>
> 1.  We've successfully compiled stage 3 for  ppc64le. The stage 3 covers
> most useful functionalities:
>
>- GNU tool chains. e.g. automake, autoconf, gcc & glibc.
>- Normally use Portage, e.g. emerge, ebuild & python
>- Normally chroot in this stage 3.
>- Not included linux kernel & bootloader yet.
>
> 2. We believe to make Gentoo support ppc64le, we still need to compile
> kernel and bootloader
>
>- Which version of kernel provided by Gentoo would you suggest us to
>use?
>
>   As to Ubuntu, there will be many patches to make the kernel
> workable, so how to patch
>   our Gentoo kernel  to make it work for ppc64le?
>
>- Which version of grub suitable for ppc64le ?  Is there any patches
>to ppc64le grub ?
>
>   When I building grub, it happens
https://bpaste.net/show/732172bfe927 .
  CC:  grub-dev community  , could you give me a hand with ppc64le
grub ?
  Or the latest grub  merged ppc64le patches ?


> 3. When the gentoo we make out workable on ppc64le, we would like to know
> the process of
> making it officially supported by Gentoo community
>
>- For each arch, do we have a subteam to verify the packages? If so,
>how to reach these guys?
>
>ppc64le are inherit from ppc64 profile.  Is that say we should
push this portage contains ppc64le
   profile. And provides this stage 3 made by catalyst ?
  What my mean is, I known arm64 ( aarch64 ?)  was merged to
portage, Could you let me know the
  process of ppc64le as same as arm64 supported by Gentoo community
?

>
>- For hardware environment, does anyone have Power8 systems ?
>
>   If someone have POWER8 OR POWER 7 systems,  it would be nice If
you'll  join this project.

-Leno Hou
>
E-mail: ho...@linux.vnet.ibm.com
E-mail: leno...@gmail.com

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-09-11 Thread Leno Hou

On Wed, Aug 12, 2015 at 4:30 PM, Anthony G. Basile <bluen...@gentoo.org>
wrote:

> On 8/12/15 3:47 AM, Mike Frysinger wrote:
>
>>
>> 4.  I would like become a developer of porting gentoo on ppc64le.  Anyone
>>> could help/mentor me to join this project ?
>>>
>> ideally someone on the ppc side would pick you up, but i think they've
>> been
>> a bit of a skeleton team of late.  so if need be, i can help you here.
>>
>
> I can help out here.

See in my 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 :).
>> -mike
>>
> We should also start building stage3s.
>
>
> --
> Anthony G. Basile, Ph.D.
> Gentoo Linux Developer [Hardened]
> E-Mail: bluen...@gentoo.org
> GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
> GnuPG ID  : F52D4BBA
>
>
>
Appreciated your efforts and comments.

1.  We've successfully compiled stage 3 for  ppc64le. The stage 3 covers
most useful functionalities:

   - GNU tool chains. e.g. automake, autoconf, gcc & glibc.
   - Normally use Portage, e.g. emerge, ebuild & python
   - Normally chroot in this stage 3.
   - Not included linux kernel & bootloader yet.

2. We believe to make Gentoo support ppc64le, we still need to compile
kernel and bootloader

   - Which version of kernel provided by Gentoo would you suggest us to use?

  As to Ubuntu, there will be many patches to make the kernel
workable, so how to patch
  our Gentoo kernel  to make it work for ppc64le?

   - Which version of grub suitable for ppc64le ?  Is there any patches to
   ppc64le grub ?

3. When the gentoo we make out workable on ppc64le, we would like to know
the process of
making it officially supported by Gentoo community

   - For each arch, do we have a subteam to verify the packages? If so, how
   to reach these guys?
   - For hardware environment, does anyone have Power8 systems ?


-Leno Hou

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-08-14 Thread Leno Hou

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

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-08-12 Thread Leno Hou

On Wed, Aug 12, 2015 at 11:50 AM, Mike Frysinger vap...@gentoo.org 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: leno...@gmail.com

Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-08-11 Thread Leno Hou

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.


*Leno Hou*
E-mail :  leno...@gmail.com

On Tue, Aug 11, 2015 at 5:49 PM, James Le Cuirot ch...@gentoo.org wrote:

 On Tue, 11 Aug 2015 17:22:21 +0800
 Leno Hou leno...@gmail.com wrote:

  Please let me know forward/steps to port gentoo on ppc64le.

 I'm not on the ppc team but I do some ppc(64) testing for Java
 packages. Although these are relatively well-maintained keywords
 overall, I think the team would struggle to cope with an additional
 one. It's also important to note that while ppc and ppc64 can be tested
 on the same hardware, I think ppc64le would require different hardware?
 If ppc64le does become popular then I would suggest that we drop 32-bit
 ppc first. Others may disagree though. :)

 --
 James Le Cuirot (chewi)
 Gentoo Linux Developer

[gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments

2015-08-11 Thread Leno Hou

Greetings ! Any Ideas/steps of how to  porting gentoo on  ppc64le
architecture?

Is it that we should add 'ppc64le' keyword to portage ?


As some of you might know,  Ubuntu has been introduced in support of
ppc64le. http://www.ubuntu.com/download/server/power8 ! It's just as it
 sounds  ppc64( 64bit only ) but little endian. I've been made basic chroot
environment  in my
Ubuntu 14.04 ppc64le manually, the packages was built  and you can see here
for detail:
https://bpaste.net/show/e99035777057

And another way how to porting is: https://wiki.gentoo.org/wiki/Porting

Please let me know forward/steps to port gentoo on ppc64le.

Appreciated your thoughts, comments and efforts on it ~~~

Leno Hou
E-mail: leno...@gmail.com

54 matches

Mail list logo