On my stable ppc-system gmp fails to build:
m4 -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_submul_1 -DPIC submul_1.asm >tmp-submul_1.s
../mpn/m4-ccas --m4=m4 powerpc-unknown-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_mul_1 -O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe mul_1.asm -o mul_1.o >/dev/null 2>&1
tmp-addmul_1.s: Assembler messages:
tmp-addmul_1.s:50: Error: operand out of range (5 is not between 0 and 1)
tmp-addmul_1.s:50: Error: missing operand
make[2]: *** [addmul_1.lo] Error 1
make[2]: *** Waiting for unfinished jobs....
powerpc-unknown-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_submul_1 -O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe tmp-submul_1.s -fPIC -DPIC -o .libs/submul_1.o
tmp-submul_1.s: Assembler messages:
tmp-submul_1.s:50: Error: operand out of range (5 is not between 0 and 1)
tmp-submul_1.s:50: Error: missing operand
make[2]: *** [submul_1.lo] Error 1
../mpn/m4-ccas --m4=m4 powerpc-unknown-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_lshift -O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe lshift.asm -fPIC -DPIC -o .libs/lshift.o
m4 -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_lshift -DPIC lshift.asm >tmp-lshift.s
powerpc-unknown-linux-gnu-gcc -c -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_lshift -O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe tmp-lshift.s -fPIC -DPIC -o .libs/lshift.o
tmp-lshift.s: Assembler messages:
tmp-lshift.s:54: Error: operand out of range (5 is not between 0 and 1)
tmp-lshift.s:54: Error: missing operand
make[2]: *** [lshift.lo] Error 1
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/gmp-4.1.4/work/gmp-4.1.4'
make: *** [all] Error 2
orophin root # emerge --info
Portage 2.0.51.19 (default-linux/ppc/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.10-gentoo-r6-orophin ppc)
=================================================================
System uname: 2.6.10-gentoo-r6-orophin ppc 7400, altivec supported
Gentoo Base System version 1.4.16
Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 8 2005, 01:04:38)]
distcc 2.16 powerpc-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
dev-lang/python: 2.3.5
sys-apps/sandbox: [Not Present]
sys-devel/autoconf: 2.59-r6, 2.13
sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5
sys-devel/binutils: 2.15.92.0.2-r8
sys-devel/libtool: 1.5.16
virtual/os-headers: 2.6.8.1-r4
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms strict userpriv usersandbox"
GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://elrohir/gentoo-portage"
USE="ppc X alsa berkdb bitmap-fonts crypt cups dvd emboss esd fam fortran gif gnome gpm gtk gtk2 imlib ipv6 jpeg kde libwww motif mp3 mpeg ncurses nls oggvorbis opengl pam pdflib perl png python qt readline spell ssl tcpd tiff truetype truetype-fonts type1-fonts unicode xml2 xprint xv zlib userland_GNU kernel_linux elibc_glibc"
Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Jacub, very nice. ppc is already in Cc and I assigned the bug to
bug-wranglers, as I don't know the maintainer of the package. And finding out
somebody who could handle this bug should be the task of the bug-wranglers.
Reassigning back to bug-wranglers. If somebody of the ppc-team has a clue, he
would raise word.
This doesn't seem to be a problem with the package, I can't reproduce it here
on my stable chroot. The only obvious difference between our configurations is
distcc. Does the error happen with distcc off as well?
