|
From: xavier.vvv <xav...@gm...> - 2009-02-12 16:00:08
|
Hi all, I want to install valgrind on linux 2.6 embedded in xupv2p board (ppc405 procesor + 256MB DDR). The error is: make[4]: Leaving directory `/root/valgrind-3.4.0/VEX' gcc -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement -fno-stack-protector -o memcheck-ppc32-linux -static -Wl,-defsym,valt_load_address=0x3 /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divsf3.o): In function `__divsf3': (.text+0x88): undefined reference to `abort' /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divdf3.o): In function `__divdf3': (.text+0x118): undefined reference to `abort' /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(muldf3.o): In function `__muldf3': (.text+0x11c): undefined reference to `abort' collect2: ld returned 1 exit status make[3]: *** [memcheck-ppc32-linux] Error 1 make[3]: Leaving directory `/root/valgrind-3.4.0/memcheck' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/valgrind-3.4.0/memcheck' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/valgrind-3.4.0' make: *** [all] Error 2 ************************************* Can someone help me please? Thanks Xavier -- View this message in context: http://www.nabble.com/valgring-3.4-compiling-problem-under-ppc405-and-gcc4.2.2-tp21978916p21978916.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |
|
From: Bart V. A. <bar...@gm...> - 2009-02-12 16:11:50
|
On Thu, Feb 12, 2009 at 5:00 PM, xavier.vvv <xav...@gm...> wrote: > > Hi all, > I want to install valgrind on linux 2.6 embedded in xupv2p board (ppc405 > procesor + 256MB DDR). > The error is: > > make[4]: Leaving directory `/root/valgrind-3.4.0/VEX' > gcc -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement > -fno-stack-protector -o memcheck-ppc32-linux -static > -Wl,-defsym,valt_load_address=0x3 > /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divsf3.o): In function `__divsf3': > (.text+0x88): undefined reference to `abort' > /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divdf3.o): In function `__divdf3': > (.text+0x118): undefined reference to `abort' > /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(muldf3.o): In function `__muldf3': > (.text+0x11c): undefined reference to `abort' > collect2: ld returned 1 exit status > make[3]: *** [memcheck-ppc32-linux] Error 1 > make[3]: Leaving directory `/root/valgrind-3.4.0/memcheck' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/root/valgrind-3.4.0/memcheck' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/valgrind-3.4.0' > make: *** [all] Error 2 > ************************************* Which options did you pass to configure ? And which gcc version did you use ? The output of gcc -v would be helpful. Bart. |
|
From: xavier.vvv <xav...@gm...> - 2009-02-12 16:30:45
|
I have made: ./configure --prefix=/root/opt/ And I use gcc 4.2.2 version Bugzilla from bar...@gm... wrote: > > On Thu, Feb 12, 2009 at 5:00 PM, xavier.vvv <xav...@gm...> wrote: >> >> Hi all, >> I want to install valgrind on linux 2.6 embedded in xupv2p board (ppc405 >> procesor + 256MB DDR). >> The error is: >> >> make[4]: Leaving directory `/root/valgrind-3.4.0/VEX' >> gcc -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement >> -fno-stack-protector -o memcheck-ppc32-linux -static >> -Wl,-defsym,valt_load_address=0x3 >> /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divsf3.o): In function `__divsf3': >> (.text+0x88): undefined reference to `abort' >> /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divdf3.o): In function `__divdf3': >> (.text+0x118): undefined reference to `abort' >> /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(muldf3.o): In function `__muldf3': >> (.text+0x11c): undefined reference to `abort' >> collect2: ld returned 1 exit status >> make[3]: *** [memcheck-ppc32-linux] Error 1 >> make[3]: Leaving directory `/root/valgrind-3.4.0/memcheck' >> make[2]: *** [all-recursive] Error 1 >> make[2]: Leaving directory `/root/valgrind-3.4.0/memcheck' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/root/valgrind-3.4.0' >> make: *** [all] Error 2 >> ************************************* > > Which options did you pass to configure ? And which gcc version did > you use ? The output of gcc -v would be helpful. > > Bart. > > ------------------------------------------------------------------------------ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- View this message in context: http://www.nabble.com/valgring-3.4-compiling-problem-under-ppc405-and-gcc4.2.2-tp21978916p21979546.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |
|
From: Bart V. A. <bar...@gm...> - 2009-02-12 17:52:45
|
On Thu, Feb 12, 2009 at 5:00 PM, xavier.vvv <xav...@gm...> wrote: > > Hi all, > I want to install valgrind on linux 2.6 embedded in xupv2p board (ppc405 > procesor + 256MB DDR). > The error is: > > make[4]: Leaving directory `/root/valgrind-3.4.0/VEX' > gcc -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement > -fno-stack-protector -o memcheck-ppc32-linux -static > -Wl,-defsym,valt_load_address=0x3 > /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divsf3.o): In function `__divsf3': > (.text+0x88): undefined reference to `abort' > /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divdf3.o): In function `__divdf3': > (.text+0x118): undefined reference to `abort' > /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(muldf3.o): In function `__muldf3': > (.text+0x11c): undefined reference to `abort' > collect2: ld returned 1 exit status > make[3]: *** [memcheck-ppc32-linux] Error 1 > make[3]: Leaving directory `/root/valgrind-3.4.0/memcheck' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/root/valgrind-3.4.0/memcheck' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/valgrind-3.4.0' > make: *** [all] Error 2 > ************************************* The following can be concluded from the above output: - The gcc compiler you are using has been configured to use soft float (see also http://gcc.gnu.org/onlinedocs/gccint/Soft-float-library-routines.html). - The soft float functions in the libgcc.a library contain calls to abort(). - There is no function with the name "abort" in Valgrind itself. Does adding the following code near the end of e.g. coregrind/m_main.c help ? void abort (void) { vg_assert(0); } Bart. |
|
From: xavier.vvv <xav...@gm...> - 2009-02-13 09:05:35
|
Hi Bart, Thanks a lot for the answer. This solution fixed the errors. But I have another question, when I cross-compiled valgrind for ppc405, then I copied all the generated file (in prefix dir) to the target platform, I have always an error when running valgrind: valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No such file or directory Here are the steps of the cross compilation: $CC=powerpc-linux-gcc LD=powerpc-linux-ld ./configure --host=powerpc-linux --target=powerpc-unknown-linux --prefix=/home/tools/valgrind_ppc_4 --build=i486-cross-linux-gnu $make $make install Then I copied the /home/tools/valgrind_ppc_4 directory to the target system. And I run valgrind from valgrind_ppc_4/bin directory. -- Xavier Bugzilla from bar...@gm... wrote: > > On Thu, Feb 12, 2009 at 5:00 PM, xavier.vvv <xav...@gm...> wrote: >> >> Hi all, >> I want to install valgrind on linux 2.6 embedded in xupv2p board (ppc405 >> procesor + 256MB DDR). >> The error is: >> >> make[4]: Leaving directory `/root/valgrind-3.4.0/VEX' >> gcc -Wno-long-long -Wno-pointer-sign -Wdeclaration-after-statement >> -fno-stack-protector -o memcheck-ppc32-linux -static >> -Wl,-defsym,valt_load_address=0x3 >> /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divsf3.o): In function `__divsf3': >> (.text+0x88): undefined reference to `abort' >> /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(divdf3.o): In function `__divdf3': >> (.text+0x118): undefined reference to `abort' >> /usr/lib/gcc/ppc-linux/4.2.2/libgcc.a(muldf3.o): In function `__muldf3': >> (.text+0x11c): undefined reference to `abort' >> collect2: ld returned 1 exit status >> make[3]: *** [memcheck-ppc32-linux] Error 1 >> make[3]: Leaving directory `/root/valgrind-3.4.0/memcheck' >> make[2]: *** [all-recursive] Error 1 >> make[2]: Leaving directory `/root/valgrind-3.4.0/memcheck' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/root/valgrind-3.4.0' >> make: *** [all] Error 2 >> ************************************* > > The following can be concluded from the above output: > - The gcc compiler you are using has been configured to use soft float > (see also > http://gcc.gnu.org/onlinedocs/gccint/Soft-float-library-routines.html). > - The soft float functions in the libgcc.a library contain calls to > abort(). > - There is no function with the name "abort" in Valgrind itself. > > Does adding the following code near the end of e.g. coregrind/m_main.c > help ? > > void abort (void) { vg_assert(0); } > > Bart. > > ------------------------------------------------------------------------------ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- View this message in context: http://www.nabble.com/valgring-3.4-compiling-problem-under-ppc405-and-gcc4.2.2-tp21978916p21992603.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |
|
From: Bart V. A. <bar...@gm...> - 2009-02-13 09:32:31
|
On Fri, Feb 13, 2009 at 10:05 AM, xavier.vvv <xav...@gm...> wrote: > > Hi Bart, > Thanks a lot for the answer. This solution fixed the errors. > But I have another question, when I cross-compiled valgrind for ppc405, > then I copied all the generated file (in prefix dir) to the target > platform, > I have always an error when running valgrind: > valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No > such file or directory > > Here are the steps of the cross compilation: > > $CC=powerpc-linux-gcc LD=powerpc-linux-ld ./configure --host=powerpc-linux > --target=powerpc-unknown-linux --prefix=/home/tools/valgrind_ppc_4 > --build=i486-cross-linux-gnu > $make > $make install > > Then I copied the /home/tools/valgrind_ppc_4 directory to the target > system. > And I run valgrind from valgrind_ppc_4/bin directory. > You have to specify the directory where Valgrind will be installed on the target via the --prefix option of the configure script. This issue has already been discussed before -- see also http://thread.gmane.org/gmane.comp.debugging.valgrind/8203/focus=8212. Bart. |