> ./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 -- ------------------------------------------------------------------------------ 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 Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users