|
From: Pinkesh P. <pin...@li...> - 2015-07-02 12:56:20
|
Hello everyone ,
I am novice to valgrind tool . I want to configure valgrind for ARM Cortex-m4 .
My host system is x86_64 GNU/Linux ..
and cross-compile toolchain is arm-none-eabi .
Anyone ?
./configure --target=arm-none-eabi --host=x86_64-linux CC=~/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc
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/install -c
checking whether build environment is sane... yes
checking for x86_64-linux-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for x86_64-linux-gcc... /home/pinkesh/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc
checking whether the C compiler works... no
configure: error: in `/home/pinkesh/installs/valgrind-3.10.1':
configure: error: C compiler cannot create executables
See `config.log' for more details
- Pinkesh
|
|
From: Alexander P. <gl...@go...> - 2015-07-02 13:22:42
|
Apparently you're trying to use the cross-compiler targeting ARM as the host compiler. ./configure is attempting to compile a small program with that compiler and is unable to execute the resulting binary. You need to look at ./configure source or the --help output to find out how to supply different compilers for host and target. On Thu, Jul 2, 2015 at 2:56 PM, Pinkesh Pachchigar <pin...@li...> wrote: > Hello everyone , > > I am novice to valgrind tool . I want to configure valgrind for ARM > Cortex-m4 . > > My host system is x86_64 GNU/Linux .. > > and cross-compile toolchain is arm-none-eabi . > > Anyone ? > > ./configure --target=arm-none-eabi --host=x86_64-linux > CC=~/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc > > 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/install -c > checking whether build environment is sane... yes > checking for x86_64-linux-strip... no > checking for strip... strip > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking whether ln -s works... yes > checking for x86_64-linux-gcc... > /home/pinkesh/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc > checking whether the C compiler works... no > configure: error: in `/home/pinkesh/installs/valgrind-3.10.1': > configure: error: C compiler cannot create executables > See `config.log' for more details > > - Pinkesh > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- Alexander Potapenko Software Engineer Google Germany GmbH Dienerstraße 12 80331 München |
|
From: John R. <jr...@bi...> - 2015-07-02 13:40:34
|
> ./configure --target=arm-none-eabi --host=x86_64-linux CC=~/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc
> checking for x86_64-linux-gcc... /home/pinkesh/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc
> checking whether the C compiler works... no
> configure: error: in `/home/pinkesh/installs/valgrind-3.10.1':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
Well, what does config.log say?
Does running the shell command:
/home/pinkesh/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc -o hello hello.c
produce a file 'hello' which is an executable for arm-none-eabi?
If more information is needed, then diagnose with strace, such as:
strace -f -e trace=execve -v -s 300 \
./configure --target=arm-none-eabi --host=x86_64-linux \
CC=~/gcc/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc
--
|