|
From: Gary Y. <gar...@ya...> - 2010-05-26 21:41:47
|
Hi Mogens, I removed --disable-tls from the configure command. The config.log shows that the Altivec is supported. ./configure --host=powerpc-linux --target=powerpc-linux --prefix=/myhome/download/valgrind config.log: ...... configure:6942: checking for Altivec configure:6973: ppc_4xx-gcc -c -maltivec conftest.c >&5 configure:6979: $? = 0 configure:6986: result: yes ...... Maximum build arch: ppc32 Primary build arch: ppc32 Secondary build arch: Build OS: linux Primary build target: PPC32_LINUX Secondary build target: Default supp files: exp-ptrcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp glibc-2.6.supp However, I still got the error, ": undefined reference to `abort'". Any idea? make ...... ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_ppc32_linux-mc_errors.o -MD -MP -MF .deps/memcheck_ppc32_linux-mc_errors.Tpo -c -o memcheck_ppc32_linux-mc_errors.o `test -f 'mc_errors.c' || echo './'`mc_errors.c mv -f .deps/memcheck_ppc32_linux-mc_errors.Tpo .deps/memcheck_ppc32_linux-mc_errors.Po ppc_4xx-gcc -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -static -Wl,-defsym,valt_load_address=0x38000000 -nodefaultlibs -nostartfiles -u _start -m32 -Wl,-T,../valt_load_address_ppc32_linux.lds -o memcheck-ppc32-linux memcheck_ppc32_linux-mc_leakcheck.o memcheck_ppc32_linux-mc_malloc_wrappers.o memcheck_ppc32_linux-mc_main.o memcheck_ppc32_linux-mc_translate.o memcheck_ppc32_linux-mc_machine.o memcheck_ppc32_linux-mc_errors.o ../coregrind/libcoregrind-ppc32-linux.a ../VEX/libvex-ppc32-linux.a -lgcc /.automount/tools/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/m403/libgcc.a(divsf3.o): In function `__divsf3': /opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/gcc/config/soft-fp/divsf3.c:44: undefined reference to `abort' /.automount/tools/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/m403/libgcc.a(divdf3.o): In function `__divdf3': /opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/gcc/config/soft-fp/divdf3.c:44: undefined reference to `abort' /.automount/tools/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/m403/libgcc.a(muldf3.o): In function `__muldf3': /opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/gcc/config/soft-fp/muldf3.c:44: undefined reference to `abort' collect2: ld returned 1 exit status make[4]: *** [memcheck-ppc32-linux] Error 1 make[4]: Leaving directory `download/try/tmp/valgrind/memcheck' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `download/try/tmp/valgrind/memcheck' make[2]: *** [all] Error 2 make[2]: Leaving directory `download/try/tmp/valgrind/memcheck' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `download/try/tmp/valgrind' make: *** [all] Error 2 Gary --- On Wed, 5/26/10, Mogens Lindholdt Lauridsen <ML...@ba...> wrote: From: Mogens Lindholdt Lauridsen <ML...@ba...> Subject: Re: [Valgrind-users] [Valgrind-developers] Valgrind cross compilation error for PPC32_LINUX To: "Gary Yang" <gar...@ya...> Cc: val...@li..., val...@li... Date: Wednesday, May 26, 2010, 2:02 PM Hi, I don't know if this helps you, but what is the output from configure? configure checks for altivec support, and it seems to me like this isn't supported by your compiler. I run valgrind on a ppc. The (cross)compiler (4.1.2) supports altivec, but the CPU doesn't. And valgrind builds and runs fine for me using similar build method as you describe. When I run configure it says that altivec is supported (by the compiler). It would be interesting to see what happens if you hack configure to believe altivec isn't supported. If this doesn't help you, you can hack the: "checking for /proc/self/fd... configure: error: cannot check for file problem in 3.5.0. (I did that locally). BTW: There is one more case in configure just like the fd problem, which also can be hacked... -Mogens Gary Yang <gar...@ya...> 26-05-2010 22:35 To Bart Van Assche <bva...@ac...> cc val...@li..., val...@li... Subject Re: [Valgrind-users] [Valgrind-developers] Valgrind cross compilation error for PPC32_LINUX I meant, I commented out those Unrecognized opcode in the file, m_dispatch/dispatch-ppc32-linux.S. But, I other error. Can someone please help. Thanks. --- On Wed, 5/26/10, Gary Yang <gar...@ya...> wrote: From: Gary Yang <gar...@ya...> Subject: Re: [Valgrind-developers] Valgrind cross compilation error for PPC32_LINUX To: "Bart Van Assche" <bva...@ac...> Cc: val...@li..., val...@li... Date: Wednesday, May 26, 2010, 1:31 PM Hi, I commented out those stvx, vand and vspltw etc. But, I got anther error. Can someone help? ...... ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT memcheck_ppc32_linux-mc_errors.o -MD -MP -MF .deps/memcheck_ppc32_linux-mc_errors.Tpo -c -o memcheck_ppc32_linux-mc_errors.o `test -f 'mc_errors.c' || echo './'`mc_errors.c mv -f .deps/memcheck_ppc32_linux-mc_errors.Tpo .deps/memcheck_ppc32_linux-mc_errors.Po ppc_4xx-gcc -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -O2 -Wno-long-long -Wno-pointer-sign -fno-stack-protector -static -Wl,-defsym,valt_load_address=0x38000000 -nodefaultlibs -nostartfiles -u _start -m32 -Wl,-T,../valt_load_address_ppc32_linux.lds -o memcheck-ppc32-linux memcheck_ppc32_linux-mc_leakcheck.o memcheck_ppc32_linux-mc_malloc_wrappers.o memcheck_ppc32_linux-mc_main.o memcheck_ppc32_linux-mc_translate.o memcheck_ppc32_linux-mc_machine.o memcheck_ppc32_linux-mc_errors.o ../coregrind/libcoregrind-ppc32-linux.a ../VEX/libvex-ppc32-linux.a -lgcc /.automount/tools/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/m403/libgcc.a(divsf3.o): In function `__divsf3': /opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/gcc/config/soft-fp/divsf3.c:44: undefined reference to `abort' /.automount/tools/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/m403/libgcc.a(divdf3.o): In function `__divdf3': /opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/gcc/config/soft-fp/divdf3.c:44: undefined reference to `abort' /.automount/tools/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/m403/libgcc.a(muldf3.o): In function `__muldf3': /opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/gcc/config/soft-fp/muldf3.c:44: undefined reference to `abort' collect2: ld returned 1 exit status make[4]: *** [memcheck-ppc32-linux] Error 1 make[4]: Leaving directory `download/try/valgrind/memcheck' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `download/try/valgrind/memcheck' make[2]: *** [all] Error 2 make[2]: Leaving directory `download/try/valgrind/memcheck' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `download/try/valgrind' make: *** [all] Error 2 --- On Wed, 5/26/10, Gary Yang <gar...@ya...> wrote: From: Gary Yang <gar...@ya...> Subject: Re: [Valgrind-developers] Valgrind cross compilation error for PPC32_LINUX To: "Bart Van Assche" <bva...@ac...> Cc: val...@li..., val...@li... Date: Wednesday, May 26, 2010, 12:37 PM Hi Bart, Thanks for your reply. I read https://bugs.kde.org/show_bug.cgi?id=238745. However, I did not find a solution. I added --disable-tls for configure. I still got the error. Any idea? ./configure --host=powerpc-linux --target=powerpc-linux --disable-tls --prefix=/myhome/download/valgrind ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -m32 -O2 -g -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -Wno-format-zero-length -fno-strict-aliasing -Wno-long-long -Wno-pointer-sign -fno-stack-protector -MT libcoregrind_ppc32_linux_a-safe-ctype.o -MD -MP -MF .deps/libcoregrind_ppc32_linux_a-safe-ctype.Tpo -c -o libcoregrind_ppc32_linux_a-safe-ctype.o `test -f 'm_demangle/safe-ctype.c' || echo './'`m_demangle/safe-ctype.c mv -f .deps/libcoregrind_ppc32_linux_a-safe-ctype.Tpo .deps/libcoregrind_ppc32_linux_a-safe-ctype.Po ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -m32 -g -Wno-long-long -MT libcoregrind_ppc32_linux_a-dispatch-x86-linux.o -MD -MP -MF .deps/libcoregrind_ppc32_linux_a-dispatch-x86-linux.Tpo -c -o libcoregrind_ppc32_linux_a-dispatch-x86-linux.o `test -f 'm_dispatch/dispatch-x86-linux.S' || echo './'`m_dispatch/dispatch-x86-linux.S mv -f .deps/libcoregrind_ppc32_linux_a-dispatch-x86-linux.Tpo .deps/libcoregrind_ppc32_linux_a-dispatch-x86-linux.Po ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -m32 -g -Wno-long-long -MT libcoregrind_ppc32_linux_a-dispatch-amd64-linux.o -MD -MP -MF .deps/libcoregrind_ppc32_linux_a-dispatch-amd64-linux.Tpo -c -o libcoregrind_ppc32_linux_a-dispatch-amd64-linux.o `test -f 'm_dispatch/dispatch-amd64-linux.S' || echo './'`m_dispatch/dispatch-amd64-linux.S mv -f .deps/libcoregrind_ppc32_linux_a-dispatch-amd64-linux.Tpo .deps/libcoregrind_ppc32_linux_a-dispatch-amd64-linux.Po ppc_4xx-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -I.. -I../include -I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -I../coregrind -DVG_LIBDIR="\"/projects/svdc/P4wsIPCSW/download/valgrind/lib/valgrind"\" -DVG_PLATFORM="\"ppc32-linux\"" -m32 -g -Wno-long-long -MT libcoregrind_ppc32_linux_a-dispatch-ppc32-linux.o -MD -MP -MF .deps/libcoregrind_ppc32_linux_a-dispatch-ppc32-linux.Tpo -c -o libcoregrind_ppc32_linux_a-dispatch-ppc32-linux.o `test -f 'm_dispatch/dispatch-ppc32-linux.S' || echo './'`m_dispatch/dispatch-ppc32-linux.S m_dispatch/dispatch-ppc32-linux.S: Assembler messages: m_dispatch/dispatch-ppc32-linux.S:142: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:144: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:146: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:148: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:150: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:152: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:154: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:156: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:158: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:160: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:162: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:164: Error: Unrecognized opcode: `stvx' m_dispatch/dispatch-ppc32-linux.S:221: Error: Unrecognized opcode: `vspltisw' m_dispatch/dispatch-ppc32-linux.S:222: Error: Unrecognized opcode: `mtvscr' m_dispatch/dispatch-ppc32-linux.S:420: Error: Unrecognized opcode: `vspltisw' m_dispatch/dispatch-ppc32-linux.S:421: Error: Unrecognized opcode: `vspltisw' m_dispatch/dispatch-ppc32-linux.S:422: Error: Unrecognized opcode: `vsldoi' m_dispatch/dispatch-ppc32-linux.S:424: Error: Unrecognized opcode: `mfvscr' m_dispatch/dispatch-ppc32-linux.S:425: Error: Unrecognized opcode: `vand' m_dispatch/dispatch-ppc32-linux.S:426: Error: Unrecognized opcode: `vspltw' m_dispatch/dispatch-ppc32-linux.S:427: Error: Unrecognized opcode: `vcmpequw.' m_dispatch/dispatch-ppc32-linux.S:511: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:513: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:515: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:517: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:519: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:521: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:523: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:525: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:527: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:529: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:531: Error: Unrecognized opcode: `lvx' m_dispatch/dispatch-ppc32-linux.S:533: Error: Unrecognized opcode: `lvx' make[3]: *** [libcoregrind_ppc32_linux_a-dispatch-ppc32-linux.o] Error 1 make[3]: Leaving directory `download/try/valgrind/coregrind' make[2]: *** [all] Error 2 make[2]: Leaving directory `download/try/valgrind/coregrind' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `download/try/valgrind' make: *** [all] Error 2 Thanks, Gary --- On Wed, 5/26/10, Bart Van Assche <bva...@ac...> wrote: From: Bart Van Assche <bva...@ac...> Subject: Re: [Valgrind-developers] Valgrind cross compilation error for PPC32_LINUX To: "Gary Yang" <gar...@ya...> Cc: val...@li..., val...@li... Date: Wednesday, May 26, 2010, 12:08 PM On Wed, May 26, 2010 at 9:04 PM, Gary Yang <gar...@ya...> wrote: [ ... ] m_dispatch/dispatch-ppc32-linux.S:142: Error: Unrecognized opcode: `stvx' [ ... ] See also https://bugs.kde.org/show_bug.cgi?id=238745. Bart. -----Inline Attachment Follows----- ------------------------------------------------------------------------------ -----Inline Attachment Follows----- _______________________________________________ Valgrind-developers mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-developers -----Inline Attachment Follows----- ------------------------------------------------------------------------------ -----Inline Attachment Follows----- _______________________________________________ Valgrind-developers mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-developers ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |