This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Fail to build Frysk on PPC64:undefined reference to `print_insn_i386_intel'
- From: Yao Qi <qiyaoltc at cn dot ibm dot com>
- To: frysk <frysk at sourceware dot org>
- Date: Fri, 19 May 2006 13:58:59 +0800
- Subject: Fail to build Frysk on PPC64:undefined reference to `print_insn_i386_intel'
Hi, everyone,
I failed to build frysk on PPC64, and here is the output,
[qiyao@plinuxt18 build-frysk]$ ../frysk/autogen.sh
[qiyao@plinuxt18 build-frysk]$ CC='gcc -m64' GCJ='gcj -m64' CXX='g++ -m64' ../frysk/configure
[qiyao@plinuxt18 build-frysk]$ make
.......
ranlib libfrysk-imports.a
soname=`basename libfrysk-imports.so` ; \
gcc -m64 -g -O -shared -o libfrysk-imports.so.tmp \
-Wl,--whole-archive,libfrysk-imports.a,--no-whole-archive \
-Wl,--soname,$soname,-z,-defs
if readelf -d libfrysk-imports.so.tmp | fgrep -q TEXTREL; then exit 1; fi
mv libfrysk-imports.so.tmp libfrysk-imports.so
gcj -m64 -I../../frysk/frysk-imports -I. -Ijargs.jar -Ijunit.jar -Werror -Wall -fPIC -g -O -o fryski -lgij -Wl,-rpath,./:/home/qiyao/build-frysk/frysk-imports -L./ -lfrysk-imports -L./ -lfrysk-jargs -L./ -lfrysk-junit -Lelfutils/libelf/ -lelf -lopcodes libfrysk-imports.so libfrysk-jargs.so libfrysk-junit.so libfrysk-imports.a libfrysk-jargs.a libfrysk-junit.a elfutils/libelf/libelf.a -lopcodes
.//libfrysk-imports.so: undefined reference to `print_insn_i386_intel'
collect2: ld returned 1 exit status
make[3]: *** [fryski] Error 1
I greped `print_insn_i386_intel' in source code tree, and found it only in
frysk/frysk-imports/lib/opcodes/cni/Disassembler.cxx, line 92,
89 bfd_vma current_address = (bfd_vma) address;
90 for(int i = 0; i < instructions; i++){
91 this->setCurrentAddress(current_address);
92 current_address += ::print_insn_i386_intel(current_address, &disasm_info);
93 this->moveToNext();
94 }
95 }
A target-independent function, such as 'print_insn', is needed here,
and implement target-specific functions somewhere else, or later.
Any comments are greatly appreciated! Thanks!
--
Yao Qi