Hi,
> I found a big problem. I started again to build the toolchain, > with a powerpc as host, and uclibc-i386 and uclibc-powerpc as > targets. I'm at the step 4, the bootstrap compiler. > > Here my command: > [EMAIL PROTECTED]:~/tmp/gcc-3.4-3.4.4$ env LANG=C LC_LANG=C > GCC_TARGET=uclibc-i386 DEB_CROSS_BOOTSTRAP=yes > dpkg-buildpackage -uc -us -rfakeroot -d -b > &>../gcc-cross-target-uclibc-i386-host-powerpc-full > 2>../gcc-cross-target-uclibc-i386-host-powerpc-errors > > The most interesting messages were in full log: > /home/jujux/tmp/gcc-3.4-3.4.4/build/gcc/xgcc > -B/home/jujux/tmp/gcc-3.4-3.4.4/build/gcc/ > -B/usr/i486-linux-uclibc/bin/ -B/usr/i486-linux-uclibc/lib/ > -isystem /usr/i486-linux-uclibc/include -isystem > /usr/i486-linux-uclibc/sys-include -O2 -DIN_GCC > -DCROSS_COMPILE -DUSE_UCLIBC -W -Wall -Wwrite-strings > -Wstrict-prototypes -Wmissing-prototypes > -Wold-style-definition -isystem ./include -I. -I. > -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/../include > -g0 -finhibit-size-directive -fno-inline-functions > -fno-exceptions -fno-zero-initialized-in-bss > -fno-unit-at-a-time -fno-omit-frame-pointer \ > -Dinhibit_libc -c ../../src/gcc/crtstuff.c -DCRT_BEGIN \ > -o crtbegin.o > /tmp/ccKRTz7l.s: Assembler messages: > /tmp/ccKRTz7l.s:33: Warning: alignment too large: 15 assumed > /tmp/ccKRTz7l.s:36: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:37: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:38: Error: Unrecognized opcode: `subl' > /tmp/ccKRTz7l.s:39: Error: Unrecognized opcode: `cmpb' > /tmp/ccKRTz7l.s:40: Error: Unrecognized opcode: `je' > /tmp/ccKRTz7l.s:41: Error: Unrecognized opcode: `jmp' > /tmp/ccKRTz7l.s:42: Warning: alignment too large: 15 assumed > /tmp/ccKRTz7l.s:44: Error: Unrecognized opcode: `addl' > /tmp/ccKRTz7l.s:45: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:46: Error: Unrecognized opcode: `call' > /tmp/ccKRTz7l.s:48: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:49: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:50: Error: Unrecognized opcode: `testl' > /tmp/ccKRTz7l.s:51: Error: Unrecognized opcode: `jne' > /tmp/ccKRTz7l.s:52: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:53: Error: Unrecognized opcode: `testl' > /tmp/ccKRTz7l.s:54: Error: Unrecognized opcode: `je' > /tmp/ccKRTz7l.s:55: Error: Unrecognized opcode: `subl' > /tmp/ccKRTz7l.s:56: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:57: Error: Unrecognized opcode: `call' > /tmp/ccKRTz7l.s:58: Error: Unrecognized opcode: `addl' > /tmp/ccKRTz7l.s:60: Error: Unrecognized opcode: `movb' > /tmp/ccKRTz7l.s:62: Error: Unrecognized opcode: `leave' > /tmp/ccKRTz7l.s:63: Error: Unrecognized opcode: `ret' > /tmp/ccKRTz7l.s:66: Error: Unrecognized opcode: `call' > /tmp/ccKRTz7l.s:71: Warning: alignment too large: 15 assumed > /tmp/ccKRTz7l.s:74: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:75: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:76: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:78: Error: Unrecognized opcode: `call' > /tmp/ccKRTz7l.s:80: Error: Unrecognized opcode: `popl' > /tmp/ccKRTz7l.s:81: Error: Unrecognized opcode: `addl' > /tmp/ccKRTz7l.s:83: Error: Unrecognized opcode: `subl' > /tmp/ccKRTz7l.s:84: Error: Unrecognized opcode: `testl' > /tmp/ccKRTz7l.s:85: Error: Unrecognized opcode: `je' > /tmp/ccKRTz7l.s:86: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:87: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:88: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:89: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:90: Error: Unrecognized opcode: `call' > /tmp/ccKRTz7l.s:91: Error: Unrecognized opcode: `addl' > /tmp/ccKRTz7l.s:93: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:94: Error: Unrecognized opcode: `testl' > /tmp/ccKRTz7l.s:95: Error: Unrecognized opcode: `je' > /tmp/ccKRTz7l.s:96: Error: Unrecognized opcode: `movl' > /tmp/ccKRTz7l.s:97: Error: Unrecognized opcode: `testl' > /tmp/ccKRTz7l.s:98: Error: Unrecognized opcode: `je' > /tmp/ccKRTz7l.s:99: Error: Unrecognized opcode: `subl' > /tmp/ccKRTz7l.s:100: Error: Unrecognized opcode: `pushl' > /tmp/ccKRTz7l.s:101: Error: Unrecognized opcode: `call' > /tmp/ccKRTz7l.s:102: Error: Unrecognized opcode: `addl' > /tmp/ccKRTz7l.s:103: Warning: alignment too large: 15 assumed > /tmp/ccKRTz7l.s:105: Error: Unrecognized opcode: `leave' > /tmp/ccKRTz7l.s:106: Error: Unrecognized opcode: `ret' > /tmp/ccKRTz7l.s:109: Error: Unrecognized opcode: `call' > make[3]: *** [crtbegin.o] Error 1 > make[3]: Leaving directory > `/home/jujux/tmp/gcc-3.4-3.4.4/build/gcc' > make[2]: *** [all-gcc] Error 2 > make[2]: Leaving directory `/home/jujux/tmp/gcc-3.4-3.4.4/build' > s=`cat status`; rm -f status; test $s -eq 0 > > Maybe do I need to increase the errors number for gcc. If > someone think so too, can he explain me how to do so ? > After some search on the gcc list, I found that most of opcode problems came from binutils version, so I don't think that's the problem here. Finally, I recalled me that I had a strange warning during linux and c headers building: sh: line 1: i486-linux-uclibc-gcc: command not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) I didn't think that was a problem the first time, because the uclibc-powerpc was build, at least it with the option -auclibc-powerpc. But that's sure, trying to compile some x86 codes on powerpc, that's a bit dumb... I copy here, a part of the step 2, Linux kernel headers, log, created with the command env LANG=C LC_LANG=C dpkg-buildpackage -uc -us -rfakeroot -auclibc-i386 -b -d &> ../linux-kernel-headers.log : # Make a testsuite only if we're not cross-compiling. dh_installdirs -plinux-kernel-headers dh_installdocs -plinux-kernel-headers dh_installexamples -plinux-kernel-headers dh_installman -plinux-kernel-headers dh_installinfo -plinux-kernel-headers dh_installmenu -plinux-kernel-headers dh_installcron -plinux-kernel-headers dh_installinit -plinux-kernel-headers dh_installdebconf -plinux-kernel-headers dh_installemacsen -plinux-kernel-headers dh_installpam -plinux-kernel-headers dh_installlogrotate -plinux-kernel-headers if test -x /usr/bin/dh_installlogcheck; then dh_installlogcheck -plinux-kernel-headers ; fi dh_installchangelogs -plinux-kernel-headers dh_install -plinux-kernel-headers dh_link -plinux-kernel-headers if test ""; then :; else dh_strip -plinux-kernel-headers ; fi dh_compress -plinux-kernel-headers dh_fixperms -plinux-kernel-headers if test ""; then :; else dh_makeshlibs -plinux-kernel-headers ; fi dh_installdeb -plinux-kernel-headers dh_perl -plinux-kernel-headers dh_shlibdeps -plinux-kernel-headers dh_gencontrol -plinux-kernel-headers sh: line 1: i486-linux-uclibc-gcc: command not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) sh: line 1: i486-linux-uclibc-gcc: command not found dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation) dh_md5sums -plinux-kernel-headers dh_builddeb -plinux-kernel-headers dpkg-deb: building package `linux-kernel-headers' in `../linux-kernel-headers_2.6.12.0-1.slind1_uclibc-i386.deb'. make: Leaving directory `/home/jujux/tmp/linux-kernel-headers-2.6.12.0' dpkg-genchanges -b dpkg-genchanges: binary-only upload - not including any source code dpkg-buildpackage: binary only upload (no source included) I'm not sure, if I was clear enough. During the uclibc-powerpc toolchain building, I had the same error. Yes, I installed dpkg, dpkg-dev and dpkg-cross: [EMAIL PROTECTED]:~$ dpkg -l | grep "^ii" | grep slind ii binutils-i386-linux-uclibc 2.16.1-2.slind1 The GNU binary utilities, for i386-linux-ucl ii dpkg 1.13.10.slind1 Package maintenance system for Debian, with ii dpkg-cross 1.25.slind1 tools for cross compiling Debian packages ii dpkg-dev 1.13.10.slind1 Package building tools for Debian I didn't see an error during binutils building. Best regards Julien Accédez au courrier électronique de La Poste : www.laposte.net 3615 LAPOSTENET (0,34 /mn)
