|
From: w112318 <w1...@ho...> - 2008-01-29 16:08:47
|
Hi,
I am trying to cross compile the valgrind for ppc-82xx target version, I got
some compile errors, please help me. Thanks.
configure like this:
CC=/opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc ../configure
--host=powerpc-linux --disable-tls
...
checking for a supported version of gcc... ok (ppc_82xx-gcc (GCC) 3.4.3
(MontaVista 3.4.3-25.0.70.0501961 2005-12-18))
checking endian.h presence... yes
configure: WARNING: endian.h: present but cannot be compiled
configure: WARNING: endian.h: check for missing prerequisite headers?
configure: WARNING: endian.h: see the Autoconf documentation
configure: WARNING: endian.h: section "Present But Cannot Be Compiled"
configure: WARNING: endian.h: proceeding with the preprocessor's result
configure: WARNING: endian.h: in the future, the compiler will take
precedence
configure: WARNING: ##
--------------------------------------------------- ##
configure: WARNING: ## Report this to
val...@li... ##
configure: WARNING: ##
--------------------------------------------------- ##
checking for endian.h... yes
checking mqueue.h usability... no
checking mqueue.h presence... yes
configure: WARNING: mqueue.h: present but cannot be compiled
configure: WARNING: mqueue.h: check for missing prerequisite headers?
configure: WARNING: mqueue.h: see the Autoconf documentation
configure: WARNING: mqueue.h: section "Present But Cannot Be Compiled"
configure: WARNING: mqueue.h: proceeding with the preprocessor's result
configure: WARNING: mqueue.h: in the future, the compiler will take
precedence
configure: WARNING: ##
--------------------------------------------------- ##
configure: WARNING: ## Report this to
val...@li... ##
configure: WARNING: ##
--------------------------------------------------- ##
checking for mqueue.h... yes
checking for uid_t in sys/types.h... yes
checking for off_t... no
checking for size_t... no
checking whether time.h and sys/time.h may both be included... no
checking for working memcmp... no
checking for stdlib.h... (cached) no
Make error:
[root@sbuild1 build]# make
/opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc -m32 -Wl,--verbose
-nostdlib 2>&1 | sed \
-e '1,/^=====\+$/d' \
-e '/^=====\+$/d' \
-e '/\. = 0x[0-9A-Fa-f]\+ +
SIZEOF_HEADERS/s/0x[0-9A-Fa-f]\+/valt_load_address/g' >
valt_load_address_ppc32_linux.lds \
|| rm -f valt_load_address_ppc32_linux.lds
make all-recursive
make[1]: Entering directory `/home/vwen/tools/valgrind-3.2.3/build'
Making all in include
make[2]: Entering directory `/home/vwen/tools/valgrind-3.2.3/build/include'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/vwen/tools/valgrind-3.2.3/build/include'
Making all in coregrind
make[2]: Entering directory
`/home/vwen/tools/valgrind-3.2.3/build/coregrind'
make all-am
make[3]: Entering directory
`/home/vwen/tools/valgrind-3.2.3/build/coregrind'
if /opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc -DHAVE_CONFIG_H -I.
-I../../coregrind -I.. -I../../coregrind -I../.. -I../../coregrind/ppc32
-I../../coregrind/linux -I../../coregrind/ppc32-linux -I../../include
-I../../VEX/pub -DVG_PLATFORM="\"ppc32-linux\"" -DVGA_ppc32=1 -DVGO_linux=1
-DVGP_ppc32_linux=1 -DVG_LIBDIR="\"/usr/local/lib/valgrind"\" -I
/opt/montavista/pro/devkit/ppc/82xx/target/usr/src/linux/include/linux -m32
-O -g -Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith
-Wstrict-prototypes -Wmissing-declarations -Wno-long-long
-Wdeclaration-after-statement -MT libcoregrind_ppc32_linux_a-m_commandline.o
-MD -MP -MF ".deps/libcoregrind_ppc32_linux_a-m_commandline.Tpo" -c -o
libcoregrind_ppc32_linux_a-m_commandline.o `test -f 'm_commandline.c' ||
echo '../../coregrind/'`m_commandline.c; \
then mv -f ".deps/libcoregrind_ppc32_linux_a-m_commandline.Tpo"
".deps/libcoregrind_ppc32_linux_a-m_commandline.Po"; else rm -f
".deps/libcoregrind_ppc32_linux_a-m_commandline.Tpo"; exit 1; fi
/opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc -I../../coregrind
-I../.. -I../../coregrind/ppc32 -I../../coregrind/linux
-I../../coregrind/ppc32-linux -I../../include -I../../VEX/pub
-DVG_PLATFORM="\"ppc32-linux\"" -DVGA_ppc32=1 -DVGO_linux=1
-DVGP_ppc32_linux=1 -Wa,-maltivec -m32 -g -Wno-long-long -c -o
libcoregrind_ppc32_linux_a-m_cpuid.o `test -f 'm_cpuid.S' || echo
'../../coregrind/'`m_cpuid.S
In file included from ../../coregrind/m_cpuid.S:31:
../../coregrind/pub_core_basics_asm.h:46:20: config.h: No such file or
directory
make[3]: *** [libcoregrind_ppc32_linux_a-m_cpuid.o] Error 1
make[3]: Leaving directory `/home/vwen/tools/valgrind-3.2.3/build/coregrind'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/vwen/tools/valgrind-3.2.3/build/coregrind'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/vwen/tools/valgrind-3.2.3/build'
make: *** [all] Error 2
--
View this message in context: http://www.nabble.com/valgrind-3.2.3-PPC-cross-compile-problem-tp15162690p15162690.html
Sent from the Valgrind - Users mailing list archive at Nabble.com.
|
|
From: Florian K. <br...@ac...> - 2008-01-31 02:23:06
|
You get compile errors because config.h is not there. Which implies that the "configure" step had errors and did not succeed. I see warnings in the output below which should not be there.. Perhaps this is a problem related to autoconf/make versions. I'm using autoconf 2.61 and automake 1.7 which work fine for me and I'm cross-compiling to, although for a different target. Florian On Tuesday 29 January 2008 11:08:45 am w112318 wrote: > Hi, > I am trying to cross compile the valgrind for ppc-82xx target version, I > got some compile errors, please help me. Thanks. > > configure like this: > > CC=/opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc ../configure > --host=powerpc-linux --disable-tls > ... > checking for a supported version of gcc... ok (ppc_82xx-gcc (GCC) 3.4.3 > (MontaVista 3.4.3-25.0.70.0501961 2005-12-18)) > > checking endian.h presence... yes > configure: WARNING: endian.h: present but cannot be compiled > configure: WARNING: endian.h: check for missing prerequisite headers? > configure: WARNING: endian.h: see the Autoconf documentation > configure: WARNING: endian.h: section "Present But Cannot Be Compiled" > configure: WARNING: endian.h: proceeding with the preprocessor's result > configure: WARNING: endian.h: in the future, the compiler will take > precedence > configure: WARNING: ## > --------------------------------------------------- ## > configure: WARNING: ## Report this to > val...@li... ## > configure: WARNING: ## > --------------------------------------------------- ## > checking for endian.h... yes > checking mqueue.h usability... no > checking mqueue.h presence... yes > configure: WARNING: mqueue.h: present but cannot be compiled > configure: WARNING: mqueue.h: check for missing prerequisite headers? > configure: WARNING: mqueue.h: see the Autoconf documentation > configure: WARNING: mqueue.h: section "Present But Cannot Be Compiled" > configure: WARNING: mqueue.h: proceeding with the preprocessor's result > configure: WARNING: mqueue.h: in the future, the compiler will take > precedence > configure: WARNING: ## > --------------------------------------------------- ## > configure: WARNING: ## Report this to > val...@li... ## > configure: WARNING: ## > --------------------------------------------------- ## > checking for mqueue.h... yes > checking for uid_t in sys/types.h... yes > checking for off_t... no > checking for size_t... no > checking whether time.h and sys/time.h may both be included... no > checking for working memcmp... no > checking for stdlib.h... (cached) no > > > Make error: > [root@sbuild1 build]# make > /opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc -m32 -Wl,--verbose > -nostdlib 2>&1 | sed \ > -e '1,/^=====\+$/d' \ > -e '/^=====\+$/d' \ > -e '/\. = 0x[0-9A-Fa-f]\+ + > SIZEOF_HEADERS/s/0x[0-9A-Fa-f]\+/valt_load_address/g' > > valt_load_address_ppc32_linux.lds \ > > || rm -f valt_load_address_ppc32_linux.lds > > make all-recursive > make[1]: Entering directory `/home/vwen/tools/valgrind-3.2.3/build' > Making all in include > make[2]: Entering directory `/home/vwen/tools/valgrind-3.2.3/build/include' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/home/vwen/tools/valgrind-3.2.3/build/include' > Making all in coregrind > make[2]: Entering directory > `/home/vwen/tools/valgrind-3.2.3/build/coregrind' > make all-am > make[3]: Entering directory > `/home/vwen/tools/valgrind-3.2.3/build/coregrind' > if /opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc -DHAVE_CONFIG_H -I. > -I../../coregrind -I.. -I../../coregrind -I../.. -I../../coregrind/ppc32 > -I../../coregrind/linux -I../../coregrind/ppc32-linux -I../../include > -I../../VEX/pub -DVG_PLATFORM="\"ppc32-linux\"" -DVGA_ppc32=1 -DVGO_linux=1 > -DVGP_ppc32_linux=1 -DVG_LIBDIR="\"/usr/local/lib/valgrind"\" -I > /opt/montavista/pro/devkit/ppc/82xx/target/usr/src/linux/include/linux > -m32 -O -g -Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith > -Wstrict-prototypes -Wmissing-declarations -Wno-long-long > -Wdeclaration-after-statement -MT > libcoregrind_ppc32_linux_a-m_commandline.o -MD -MP -MF > ".deps/libcoregrind_ppc32_linux_a-m_commandline.Tpo" -c -o > libcoregrind_ppc32_linux_a-m_commandline.o `test -f 'm_commandline.c' || > echo '../../coregrind/'`m_commandline.c; \ > then mv -f ".deps/libcoregrind_ppc32_linux_a-m_commandline.Tpo" > ".deps/libcoregrind_ppc32_linux_a-m_commandline.Po"; else rm -f > ".deps/libcoregrind_ppc32_linux_a-m_commandline.Tpo"; exit 1; fi > /opt/montavista/pro/devkit/ppc/82xx/bin/ppc_82xx-gcc -I../../coregrind > -I../.. -I../../coregrind/ppc32 -I../../coregrind/linux > -I../../coregrind/ppc32-linux -I../../include -I../../VEX/pub > -DVG_PLATFORM="\"ppc32-linux\"" -DVGA_ppc32=1 -DVGO_linux=1 > -DVGP_ppc32_linux=1 -Wa,-maltivec -m32 -g -Wno-long-long -c -o > libcoregrind_ppc32_linux_a-m_cpuid.o `test -f 'm_cpuid.S' || echo > '../../coregrind/'`m_cpuid.S > In file included from ../../coregrind/m_cpuid.S:31: > ../../coregrind/pub_core_basics_asm.h:46:20: config.h: No such file or > directory > make[3]: *** [libcoregrind_ppc32_linux_a-m_cpuid.o] Error 1 > make[3]: Leaving directory > `/home/vwen/tools/valgrind-3.2.3/build/coregrind' make[2]: *** [all] Error > 2 > make[2]: Leaving directory > `/home/vwen/tools/valgrind-3.2.3/build/coregrind' make[1]: *** > [all-recursive] Error 1 > make[1]: Leaving directory `/home/vwen/tools/valgrind-3.2.3/build' > make: *** [all] Error 2 |
|
From: w112318 <w1...@ho...> - 2008-01-31 20:01:12
|
thanks for help,now the cross compile "seems" done, the reason for this config file issue is because I make a build folder in the valgrind-3.3.0 folder and run configure and make in this build folder, when I run configure and make in the valgrind folder, it goes fine. but the valgrind doesn't work on the target baord. Any suggestion is quite appreciated. the configure like this: CC=ppc_82xx-gcc ./configure --host=powerpc-linux --disable-tls make the problem is when I run valgrind in the target board, it doesn't work, here is the log message: ==1117== Memcheck, a memory error detector. ==1117== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==1117== Using LibVEX rev 1804, a library for dynamic binary translation. ==1117== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==1117== Using valgrind-3.3.0, a dynamic binary instrumentation framework. ==1117== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==1117== For more details, rerun with: -v ==1117== ==1117== My PID = 1117, parent PID = 1068. Prog and args are: ==1117== /tmp/vgtest.exe ==1117== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld.so.1 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld.so.1 valgrind: valgrind: Possible fix: install glibc's debuginfo package on this machine. valgrind: valgrind: Cannot continue -- exiting now. Sorry. -- View this message in context: http://www.nabble.com/valgrind-3.2.3-PPC-cross-compile-problem-tp15162690p15213361.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |
|
From: Hiran <hir...@gm...> - 2008-02-02 14:20:04
|
Hi,
I think glibc on your target is stripped. Try installing
unstripped versions (if space allows) and it should pass. You may
directly copy the libraries from your build env without stripping.
Regards,
Hiran
On Feb 1, 2008 1:31 AM, w112318 <w1...@ho...> wrote:
>
> thanks for help,now the cross compile "seems" done, the reason for this
> config file issue is because I make a build folder in the valgrind-3.3.0
> folder and run configure and make in this build folder, when I run configure
> and make in the valgrind folder, it goes fine. but the valgrind doesn't work
> on the target baord.
> Any suggestion is quite appreciated.
>
> the configure like this:
> CC=ppc_82xx-gcc ./configure --host=powerpc-linux --disable-tls
> make
>
> the problem is when I run valgrind in the target board, it doesn't work,
> here is the log message:
>
> ==1117== Memcheck, a memory error detector.
> ==1117== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
> ==1117== Using LibVEX rev 1804, a library for dynamic binary translation.
> ==1117== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
> ==1117== Using valgrind-3.3.0, a dynamic binary instrumentation framework.
> ==1117== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
> ==1117== For more details, rerun with: -v
> ==1117==
> ==1117== My PID = 1117, parent PID = 1068. Prog and args are:
> ==1117== /tmp/vgtest.exe
> ==1117==
>
> valgrind: Fatal error at startup: a function redirection
> valgrind: which is mandatory for this platform-tool combination
> valgrind: cannot be set up. Details of the redirection are:
> valgrind:
> valgrind: A must-be-redirected function
> valgrind: whose name matches the pattern: strlen
> valgrind: in an object with soname matching: ld.so.1
> valgrind: was not found whilst processing
> valgrind: symbols from the object with soname: ld.so.1
> valgrind:
> valgrind: Possible fix: install glibc's debuginfo package on this machine.
> valgrind:
> valgrind: Cannot continue -- exiting now. Sorry.
> --
> View this message in context: http://www.nabble.com/valgrind-3.2.3-PPC-cross-compile-problem-tp15162690p15213361.html
>
> Sent from the Valgrind - Users mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
--
- - - - - - - - - - - - - - - - - - - - - -
Hiranjyoti Mahanta
-- + -- + -- + -- + -- + -- + -- + -- + -- + --
+-- +-- +-- +-- +-- +-- +-- +-- +-- +-- +-- +--
--o--o--o--o--o--o--o--o--o--o--o--o--o--o--o--
Linux is user friendly: No version of Linux I know ever prompted the
user to debug a crashed application.
|
|
From: Julian S. <js...@ac...> - 2008-02-04 21:59:29
|
On Monday 04 February 2008 22:52, w112318 wrote: > Hi, thanks for your information, I tried this way, the memcheck still > doesn't work, the memcheck of the V3.2.1 version works fine but it generate > 5000 lines of gabage log message, Memcheck 3.3.0 has the same problem as 3.2.1. Difference is 3.3.0 detects the problem and refuses to start, instead of continuing and producing garbage. > > I think glibc on your target is stripped. Try installing > > unstripped versions (if space allows) and it should pass. You may > > directly copy the libraries from your build env without stripping. Yes. Specifically, you need to make sure that Memcheck can see the "strlen" symbol in /lib/ld.so (or whatever ld.so you are using). Either by - installing an unstripped version of ld.so - or installing the debuginfo RPM for ld.so (perhaps for glibc?) J |
|
From: w112318 <w1...@ho...> - 2008-02-06 15:13:03
|
unstripped version of ld.so made it work, thanks! Julian Seward-2 wrote: > > On Monday 04 February 2008 22:52, w112318 wrote: >> Hi, thanks for your information, I tried this way, the memcheck still >> doesn't work, the memcheck of the V3.2.1 version works fine but it >> generate >> 5000 lines of gabage log message, > > Memcheck 3.3.0 has the same problem as 3.2.1. Difference is 3.3.0 > detects the problem and refuses to start, instead of continuing > and producing garbage. > >> > I think glibc on your target is stripped. Try installing >> > unstripped versions (if space allows) and it should pass. You may >> > directly copy the libraries from your build env without stripping. > > Yes. Specifically, you need to make sure that Memcheck can see the > "strlen" symbol in /lib/ld.so (or whatever ld.so you are using). > Either by > > - installing an unstripped version of ld.so > - or installing the debuginfo RPM for ld.so (perhaps for glibc?) > > J > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- View this message in context: http://www.nabble.com/valgrind-3.3.0-doesn%27t-work-on-the-ppc32-linux-target-board-tp15162690p15306719.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |
|
From: w112318 <w1...@ho...> - 2008-02-04 21:52:52
|
Hi, thanks for your information, I tried this way, the memcheck still doesn't work, the memcheck of the V3.2.1 version works fine but it generate 5000 lines of gabage log message, and the helgrind of the V3.3.0 works fine on the target board. Any suggestion is quite appcaited. Vincent Hiran wrote: > > Hi, > I think glibc on your target is stripped. Try installing > unstripped versions (if space allows) and it should pass. You may > directly copy the libraries from your build env without stripping. > Regards, > Hiran > > > On Feb 1, 2008 1:31 AM, w112318 <w1...@ho...> wrote: >> >> thanks for help,now the cross compile "seems" done, the reason for this >> config file issue is because I make a build folder in the valgrind-3.3.0 >> folder and run configure and make in this build folder, when I run >> configure >> and make in the valgrind folder, it goes fine. but the valgrind doesn't >> work >> on the target baord. >> Any suggestion is quite appreciated. >> >> the configure like this: >> CC=ppc_82xx-gcc ./configure --host=powerpc-linux --disable-tls >> make >> >> the problem is when I run valgrind in the target board, it doesn't work, >> here is the log message: >> >> ==1117== Memcheck, a memory error detector. >> ==1117== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. >> ==1117== Using LibVEX rev 1804, a library for dynamic binary translation. >> ==1117== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. >> ==1117== Using valgrind-3.3.0, a dynamic binary instrumentation >> framework. >> ==1117== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. >> ==1117== For more details, rerun with: -v >> ==1117== >> ==1117== My PID = 1117, parent PID = 1068. Prog and args are: >> ==1117== /tmp/vgtest.exe >> ==1117== >> >> valgrind: Fatal error at startup: a function redirection >> valgrind: which is mandatory for this platform-tool combination >> valgrind: cannot be set up. Details of the redirection are: >> valgrind: >> valgrind: A must-be-redirected function >> valgrind: whose name matches the pattern: strlen >> valgrind: in an object with soname matching: ld.so.1 >> valgrind: was not found whilst processing >> valgrind: symbols from the object with soname: ld.so.1 >> valgrind: >> valgrind: Possible fix: install glibc's debuginfo package on this >> machine. >> valgrind: >> valgrind: Cannot continue -- exiting now. Sorry. >> -- >> View this message in context: >> http://www.nabble.com/valgrind-3.2.3-PPC-cross-compile-problem-tp15162690p15213361.html >> >> Sent from the Valgrind - Users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Valgrind-users mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-users >> > > > > -- > - - - - - - - - - - - - - - - - - - - - - - > Hiranjyoti Mahanta > -- + -- + -- + -- + -- + -- + -- + -- + -- + -- > +-- +-- +-- +-- +-- +-- +-- +-- +-- +-- +-- +-- > --o--o--o--o--o--o--o--o--o--o--o--o--o--o--o-- > Linux is user friendly: No version of Linux I know ever prompted the > user to debug a crashed application. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- View this message in context: http://www.nabble.com/valgrind-3.3.0-doesn%27t-work-on-the-ppc32-linux-target-board-tp15162690p15278467.html Sent from the Valgrind - Users mailing list archive at Nabble.com. |