On Fri, May 24, 2002 at 10:21:28AM -0400, Doug Dobies wrote: > I have searched the list archives, as well as google for clues to solve > this problem, hopefully, someone here may have some suggestions. > I'm attempting to build tcpdump 3.7.1 on a x86-based Linux system (using > the Embedix tools) for a MIPS-based system, mipsel-linux-gccc is my > compiler, and I return the following errors when attempting to make: > > mipsel-linux-gcc -O2 -DHAVE_CONFIG_H -I. -I../libpcap-0.7.1 -I./missing > -I/opt/Embedix/tools/include -I/usr/include -c ./addrtoname.c > /tmp/cc8jIlBi.s: Assembler messages: > /tmp/cc8jIlBi.s:28: Error: unrecognized opcode `rorw $8,$6' > /tmp/cc8jIlBi.s:28: Error: unrecognized opcode `rorl $16,$6' > /tmp/cc8jIlBi.s:28: Error: unrecognized opcode `rorw $8,$6' > /tmp/cc8jIlBi.s:789: Error: unrecognized opcode `rorw $8,$16' > /tmp/cc8jIlBi.s:1453: Error: unrecognized opcode `rorw $8,$17' > /tmp/cc8jIlBi.s:1634: Error: unrecognized opcode `rorw $8,$3' > /tmp/cc8jIlBi.s:1664: Error: unrecognized opcode `rorw $8,$2' > /tmp/cc8jIlBi.s:1798: Error: unrecognized opcode `rorw $8,$2' > make: *** [addrtoname.o] Error 1 > > I believe my environment is correct as I have been able to build other > binaries and then successfully use them on the MIPS system.
Perhaps other binaries don't happen to have code that hits that particular problem. That's a compiler problem of some sort; either it's a compiler bug, or it's a mismatch between the cross-assembler and cross-compiler (i.e., the compiler is generating code the assembler can't assemble), or somethng such as that. Try re-running that compiler command, with -v, to make the compiler driver program (gcc) print out all the subprograms it runs, and then make sure that the version of the assembler it runs is a MIPS assembler that understands those instructions. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
