|
From: Stephen W. <st...@ic...> - 2010-02-10 23:05:44
|
I'm on an x86_64 workstation (Linux 2.6) trying to cross compile
for ppc (Linux 2.4). I can't even get past the configure, it fails
with the error:
checking for /proc/self/fd... configure: error: cannot check for file
existence when cross compiling
The complete configure output is as follows:
% ./configure --prefix=/valgrind CC=ppc_4xx-gcc --host=ppc-linux
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /usr/bin/X11/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for ppc-linux-strip... ppc-linux-strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for ppc-linux-gcc... ppc_4xx-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether ppc_4xx-gcc accepts -g... yes
checking for ppc_4xx-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of ppc_4xx-gcc... gcc3
checking whether ppc_4xx-gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... ppc_4xx-gcc -E
checking for ppc-linux-g++... ppc-linux-g++
checking whether we are using the GNU C++ compiler... yes
checking whether ppc-linux-g++ accepts -g... yes
checking dependency style of ppc-linux-g++... gcc3
checking for ppc-linux-ranlib... ppc-linux-ranlib
checking for ar... /usr/bin/X11/ar
checking for perl... /usr/bin/X11/perl
checking for gdb... /usr/bin/X11/gdb
checking for diff -u... yes
checking for a supported version of gcc... ok (4)
checking build system type... x86_64-suse-linux
checking host system type... powerpc-unknown-linux
checking for a supported CPU... ok (powerpc)
checking for a 64-bit only build... no
checking for a 32-bit only build... no
checking for a supported OS... ok (linux)
checking for the kernel version... 2.6 family (2.6.22.19-0.4-default)
checking for a supported CPU/OS combination... ok (ppc32-linux)
checking for use as an inner Valgrind... no
checking for egrep... grep -E
checking the GLIBC_VERSION version... 2.3 family
checking for CLOCK_MONOTONIC... no
checking for PTHREAD_MUTEX_ADAPTIVE_NP... yes
checking for PTHREAD_MUTEX_ERRORCHECK_NP... yes
checking for PTHREAD_MUTEX_RECURSIVE_NP... yes
checking for PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP... yes
checking for pthread_mutex_t::__m_kind... yes
checking for pthread_mutex_t::__data.__kind... no
checking for Altivec... yes
checking for pthread_create@GLIBC2.0()... no
checking for eventfd()... no
checking if gcc accepts -m32... no
checking if gcc accepts -maix32... no
checking if gcc accepts -m64... no
checking if gcc accepts -maix64... no
checking if gcc accepts -mmmx... no
checking if gcc accepts -msse... no
checking if gcc accepts -mpreferred-stack-boundary... no
checking if gcc accepts -Wno-pointer-sign... no
checking if gcc accepts -Wdeclaration-after-statement... no
checking if gcc accepts -Wno-empty-body... no
checking if gcc accepts -Wno-format-zero-length... yes
checking if gcc accepts -Wno-uninitialized... yes
checking if gcc accepts -Wextra or -W... -W
checking if gcc accepts -fno-stack-protector... no
checking if gcc accepts --param inline-unit-growth... no
checking if gcc supports __builtin_expect... yes
checking if ppc32/64 as supports mtocrf/mfocrf... no
checking if x86/amd64 assembler speaks SSE3... no
checking if x86/amd64 assembler speaks SSSE3... no
checking for TLS support... no
checking for /proc/self/fd... configure: error: cannot check for file
existence when cross compiling
--
Steve Williams "The woods are lovely, dark and deep.
steve at icarus.com But I have promises to keep,
http://www.icarus.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
|
|
From: Saranya P. L <sar...@ar...> - 2010-06-10 16:30:18
|
Hi, When I try to cross compile valgrind-3.5.0 for ppc and my host is x86 Linux , I am getting the following error checking for /proc/self/fd... configure: error: cannot check for file existence when cross compiling I heard that this bug is already raised for 3.5.0 and the bugId is #204843 and it is reported that this bug has been fixed on the trunk and on the 3.5 branch. Can you please confirm the same and if this has been fixed,Can I know the svn version of the fix Regards, Saranya P.L ________________________________ "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." |
|
From: Bart V. A. <bva...@ac...> - 2010-06-10 16:38:45
|
On Thu, Jun 10, 2010 at 5:37 PM, Saranya P. L <sar...@ar...> wrote: > > When I try to cross compile valgrind-3.5.0 for ppc and my host is x86 Linux , I am getting the following error > checking for /proc/self/fd... configure: error: cannot check for file existence when cross compiling > > I heard that this bug is already raised for 3.5.0 and the bugId is #204843 and it is reported that this bug has been fixed on > the trunk and on the 3.5 branch. The source code on the 3.5 branch should build and run fine (the trunk doesn't cross-compile at this time). You can check out the source code on the 3.5 branch as follows: svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH Bart. |
|
From: Robert B. <gm...@re...> - 2010-06-13 11:51:56
Attachments:
abort.diff
altivec.diff
|
On 06/10/2010 07:38 PM, Bart Van Assche wrote: Hi, I'm using ELDK 4.2 on an AMCC kilauea board: All on the host: svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH VALGRIND_PATH="VALGRIND_3_5_BRANCH" The patches are attached as well. This patch is to remove the altivec instructions patch -p1 < patches/altivec.diff This patch is to make the linker happy. 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' patch -p1 < patches/abort.diff cd $VALGRIND_PATH source ../../../env.sh make distclean echo "autogen" ./autogen.sh --host=powerpc-linux --target=powerpc-linux --disable-tls --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx echo "configure" ./configure --host=powerpc-linux --target=powerpc-linux --disable-tls --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx echo "make" make So far so bad. With make install on the host we fail here: win.h' '/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/include/valgrind/vki/vki-scnums-darwin.h' make[3]: Leaving directory `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/include' make[2]: Leaving directory `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/include' Making install in VEX make[2]: Entering directory `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/VEX' make install-am make[3]: Entering directory `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/VEX' make[4]: Entering directory `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/VEX' test -z "/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind" || /bin/mkdir -p "/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind" /usr/bin/install -c -m 644 'libvex-ppc32-linux.a' '/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind/libvex-ppc32-linux.a' powerpc-linux-ranlib '/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind/libvex-ppc32-linux.a' /bin/sh: line 4: powerpc-linux-ranlib: command not found Which is strange, since powerpc-linux-ranlib is definitely on the patch. Please advise. Regards, Robert -- Robert Berger Embedded Software Specialist Reliable Embedded Systems Consulting Training Engineering Tel.: (+30) 697 593 3428 Fax.:(+30) 210 684 7881 URL: http://www.reliableembeddedsystems.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- ..."Beware of bugs in the above code; I have only proved it correct, not tried it." - Donald Knuth, in a memo to Peter Van Emde Boas titled "Notes on the van Emde Boas construction of priority deques: An instructive use of recursion" My public pgp key is available at: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1 |
|
From: Bart V. A. <bva...@ac...> - 2010-06-13 14:53:58
|
On Sun, Jun 13, 2010 at 1:51 PM, Robert Berger <gm...@re...> wrote: > On 06/10/2010 07:38 PM, Bart Van Assche wrote: > I'm using ELDK 4.2 on an AMCC kilauea board: > > All on the host: > > svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH > > VALGRIND_PATH="VALGRIND_3_5_BRANCH" > > The patches are attached as well. > > This patch is to remove the altivec instructions > > patch -p1 < patches/altivec.diff > > This patch is to make the linker happy. > > 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' > > patch -p1 < patches/abort.diff > > cd $VALGRIND_PATH > > source ../../../env.sh > > make distclean > > echo "autogen" > ./autogen.sh --host=powerpc-linux --target=powerpc-linux --disable-tls > --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx > > echo "configure" > ./configure --host=powerpc-linux --target=powerpc-linux --disable-tls > --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx > > echo "make" > make > > So far so bad. > > With make install on the host we fail here: > > win.h' > '/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/include/valgrind/vki/vki-scnums-darwin.h' > make[3]: Leaving directory > `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/include' > make[2]: Leaving directory > `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/include' > Making install in VEX > make[2]: Entering directory > `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/VEX' > make install-am > make[3]: Entering directory > `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/VEX' > make[4]: Entering directory > `/home/rber/projects/ldd/ldd_for_trainer/src/31_valgrind/VALGRIND_3_5_BRANCH/VEX' > test -z "/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind" || /bin/mkdir > -p "/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind" > /usr/bin/install -c -m 644 'libvex-ppc32-linux.a' > '/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind/libvex-ppc32-linux.a' > powerpc-linux-ranlib > '/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind/libvex-ppc32-linux.a' > /bin/sh: line 4: powerpc-linux-ranlib: command not found > > Which is strange, since powerpc-linux-ranlib is definitely on the patch. The first and second issue should now be fixed on the trunk (r11172 and r11173 respectively). Not sure why powerpc-linux-ranlib could not be found - I have never seen this before. Maybe this is a local issue ? Note: cross-compilation will work soon again on the trunk - a patch has already been posted by Julian on the valgrind-developers mailinglist. Bart. |
|
From: Bart V. A. <bva...@ac...> - 2010-06-15 15:10:47
|
On Mon, Jun 14, 2010 at 5:28 PM, Robert Berger <rob...@gm...> wrote: > > It looks like last time this mail did not make it to the list. > Here I try again. Hi Robert, Does the current Valgrind trunk build and install fine on your setup ? Cross-compilation should work again with the current trunk. Bart. |
|
From: Robert B. <gm...@re...> - 2010-06-15 16:00:59
|
Hi Bart, On 06/15/2010 06:10 PM, Bart Van Assche wrote: > > > > Hi Robert, > > > > Does the current Valgrind trunk build and install fine on your setup ? > > Cross-compilation should work again with the current trunk. It looks like cross compilation is up and running again. Cool! svn co svn://svn.valgrind.org/valgrind/trunk valgrind cd valgrind source ../../../env.sh ./autogen.sh --host=powerpc-linux --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx ./configure --host=powerpc-linux --prefix=$ELDK_PREFIX/eldk-4.2-ppc_4xx/ppc_4xx make make install seem to be happy. Now I'm at the same stage as before with the 3.5 trunk and some hacks here and there. That's what my target says: -bash-3.2# valgrind valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No such file or directory -bash-3.2# Where does valgrind expect to find memcheck on my target? I do have under /lib/valgrind this: -rwxr-xr-x 1 1001 1001 5591541 Jun 15 2010 cachegrind-ppc32-linux -rwxr-xr-x 1 1001 1001 5863593 Jun 15 2010 callgrind-ppc32-linux -rw-r--r-- 1 1001 1001 29789 Jun 15 2010 default.supp -rwxr-xr-x 1 1001 1001 5859015 Jun 15 2010 drd-ppc32-linux -rwxr-xr-x 1 1001 1001 5477994 Jun 15 2010 exp-bbv-ppc32-linux -rwxr-xr-x 1 1001 1001 5713694 Jun 15 2010 exp-ptrcheck-ppc32-linux -rwxr-xr-x 1 1001 1001 5854195 Jun 15 2010 helgrind-ppc32-linux -rwxr-xr-x 1 1001 1001 5488678 Jun 15 2010 lackey-ppc32-linux -rw-r--r-- 1 1001 1001 4065720 Jun 15 2010 libcoregrind-ppc32-linux.a -rw-r--r-- 1 1001 1001 51258 Jun 15 2010 libreplacemalloc_toolpreload-ppc32-linux.a -rw-r--r-- 1 1001 1001 4157614 Jun 15 2010 libvex-ppc32-linux.a -rwxr-xr-x 1 1001 1001 5553083 Jun 15 2010 massif-ppc32-linux -rwxr-xr-x 1 1001 1001 6054208 Jun 15 2010 memcheck-ppc32-linux -rwxr-xr-x 1 1001 1001 5466099 Jun 15 2010 none-ppc32-linux -rwxr-xr-x 1 1001 1001 14978 Jun 15 2010 vgpreload_core-ppc32-linux.so -rwxr-xr-x 1 1001 1001 235699 Jun 15 2010 vgpreload_drd-ppc32-linux.so -rwxr-xr-x 1 1001 1001 63804 Jun 15 2010 vgpreload_exp-ptrcheck-ppc32-linux.so -rwxr-xr-x 1 1001 1001 132807 Jun 15 2010 vgpreload_helgrind-ppc32-linux.so -rwxr-xr-x 1 1001 1001 49269 Jun 15 2010 vgpreload_massif-ppc32-linux.so -rwxr-xr-x 1 1001 1001 95557 Jun 15 2010 vgpreload_memcheck-ppc32-linux.so Regards, Robert > > > > Bart. -- Robert Berger Embedded Software Specialist Reliable Embedded Systems Consulting Training Engineering Tel.: (+30) 697 593 3428 Fax.:(+30) 210 684 7881 URL: http://www.reliableembeddedsystems.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- ..."Stroustroup writes in the ARM: C programmers think that memory allocation is too important to be left to the computer, Lisp programmers think that memory allocation is too important to be left to the programmer." My public pgp key is available at: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1 |
|
From: Bart V. A. <bva...@ac...> - 2010-06-15 16:05:32
|
On Tue, Jun 15, 2010 at 5:55 PM, Robert Berger <rob...@gm...> wrote: > > [ ... ] > > That's what my target says: > > -bash-3.2# valgrind > valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No > such file or directory > -bash-3.2# You can analyze what went wrong by analyzing the output of the following command: valgrind -v -d /bin/date Bart. |
|
From: Robert B. <gm...@re...> - 2010-06-15 19:12:21
|
On 06/15/2010 07:05 PM, Bart Van Assche wrote:
> On Tue, Jun 15, 2010 at 5:55 PM, Robert Berger
> <rob...@gm...> wrote:
>>
>> [ ... ]
>>
>> That's what my target says:
>>
>> -bash-3.2# valgrind
>> valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No
>> such file or directory
>> -bash-3.2#
>
> You can analyze what went wrong by analyzing the output of the
> following command:
>
> valgrind -v -d /bin/date
-bash-3.2# valgrind -v -d /bin/date
--1059:1:debuglog DebugLog system started by Stage 1, level 1 logging
requested
--1059:1:launcher no tool requested, defaulting to 'memcheck'
--1059:1:launcher selected platform 'ppc32-linux'
--1059:1:launcher launching
/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind/memcheck-ppc32-linux
valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No
such file or directory
The install path on my host is /work/rber/eldk-4.2-ppc_4xx/ppc_4xx
On my target this is /
I hacked this by:
mkdir -p /work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib
ln -sf /lib/valgrind /work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind
I guess this should be fixed for cross debugging, or maybe I should use
some additional --{?} in configure to tell valgrind where the find the
stuff on the target.
Followed by:
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 fixes: (1, short term): install glibc's debuginfo
valgrind: package on this machine. (2, longer term): ask the packagers
valgrind: for your Linux distribution to please in future ship a non-
valgrind: stripped ld.so (or whatever the dynamic linker .so is called)
valgrind: that exports the above-named function using the standard
valgrind: calling conventions for this platform.
valgrind:
valgrind: Cannot continue -- exiting now. Sorry.
I'll try to install the glibc with debuginfo as indicated here:
http://lists.denx.de/pipermail/eldk/2010-June/001505.html
.. but so far without much success.
In worst case I will need to rebuild the glibc with an unstripped ld.
Regards,
Robert
>
> Bart.
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
|
|
From: Mogens L. L. <ML...@ba...> - 2010-06-15 20:41:43
|
I've had the same problem, but saw a colleague using "DESTDIR" when
building some other project (See the make install command). This also
works with valgrind. I build valgrind with this script:
******************************
export location=$(pwd)
#Path to compiler:
export
TARGET_TOOL_BASE=/opt/wrsysroot/x86-linux2/powerpc-wrs-linux-gnu-ppc_603e-glibc_small-
export CC=${TARGET_TOOL_BASE}gcc
export CXX=${TARGET_TOOL_BASE}g++
export LD=${TARGET_TOOL_BASE}ld
install_dir=${location}/install_svn_debug
rm -rf ${install_dir}
rm -rf valgrind
svn co svn://svn.valgrind.org/valgrind/trunk valgrind
cd valgrind
./autogen.sh
./configure --enable-shared --host=ppc-linux --target=ppc-linux
--enable-debug || exit 1
make || exit 1
make install DESTDIR=${install_dir} || exit 1
*******************************
In the "install_dir" you will now get a "usr" directory which you can copy
directly to your targets rootfs.
I don't really know if I myself prefer this.... It might be nice to have
tools separated from the OS release. (I kind of prefer to have all my
code/tools in my home dir on target).
-Mogens
Robert Berger <gm...@re...>
15-06-2010 21:13
Please respond to
gm...@re...
To
val...@li...
cc
val...@li...
Subject
Re: [Valgrind-users] Cross compiling valgrind 3.5.0 for ppc
On 06/15/2010 07:05 PM, Bart Van Assche wrote:
> On Tue, Jun 15, 2010 at 5:55 PM, Robert Berger
> <rob...@gm...> wrote:
>>
>> [ ... ]
>>
>> That's what my target says:
>>
>> -bash-3.2# valgrind
>> valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux':
No
>> such file or directory
>> -bash-3.2#
>
> You can analyze what went wrong by analyzing the output of the
> following command:
>
> valgrind -v -d /bin/date
-bash-3.2# valgrind -v -d /bin/date
--1059:1:debuglog DebugLog system started by Stage 1, level 1 logging
requested
--1059:1:launcher no tool requested, defaulting to 'memcheck'
--1059:1:launcher selected platform 'ppc32-linux'
--1059:1:launcher launching
/work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind/memcheck-ppc32-linux
valgrind: failed to start tool 'memcheck' for platform 'ppc32-linux': No
such file or directory
The install path on my host is /work/rber/eldk-4.2-ppc_4xx/ppc_4xx
On my target this is /
I hacked this by:
mkdir -p /work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib
ln -sf /lib/valgrind /work/rber/eldk-4.2-ppc_4xx/ppc_4xx/lib/valgrind
I guess this should be fixed for cross debugging, or maybe I should use
some additional --{?} in configure to tell valgrind where the find the
stuff on the target.
Followed by:
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 fixes: (1, short term): install glibc's debuginfo
valgrind: package on this machine. (2, longer term): ask the packagers
valgrind: for your Linux distribution to please in future ship a non-
valgrind: stripped ld.so (or whatever the dynamic linker .so is called)
valgrind: that exports the above-named function using the standard
valgrind: calling conventions for this platform.
valgrind:
valgrind: Cannot continue -- exiting now. Sorry.
I'll try to install the glibc with debuginfo as indicated here:
http://lists.denx.de/pipermail/eldk/2010-June/001505.html
.. but so far without much success.
In worst case I will need to rebuild the glibc with an unstripped ld.
Regards,
Robert
>
> Bart.
>
>
------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users
|
|
From: Felix S. <sch...@go...> - 2010-07-14 18:09:58
|
Hi folks, I know that Valgrind is a analyze tool for binary code but is it possible to use Valgrind especially Cachegrind with a Java application? Does anybody has any experiences with Valgrind and Java? Thanks a lot Felix |
|
From: Bart V. A. <bva...@ac...> - 2010-02-11 07:11:09
|
On Wed, Feb 10, 2010 at 11:27 PM, Stephen Williams <st...@ic...> wrote: > > I'm on an x86_64 workstation (Linux 2.6) trying to cross compile > for ppc (Linux 2.4). I can't even get past the configure, it fails > with the error: > > checking for /proc/self/fd... configure: error: cannot check for file > existence when cross compiling This has been reported some time ago as bug #204843 (https://bugs.kde.org/show_bug.cgi?id=204843) and has been fixed on the trunk and on the 3.5 branch. Bart. |