Hi Brad,<br> Thanks for the help. I uninstalled my older CMAKE 2.8.7 ans installed the latest CMAKE which is 2.8.10.2.<br><br>I am still getting the same error. I think the executable is not being generated as shown by the below lines<br>
<br><i>-- Detecting C compiler ABI info<br>CMake Error at /net/dslabfs/dsl01/users/nmahabaleshwar/NewDataBaseStuff/cmake/cmake-2.8.10.2-Linux-i386/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:31 (try_compile):<br>
<br><b>Cannot copy output executable</b><br> ''<br> to destination specified by COPY_FILE:<br>.<br>.<br>.<br></i>Below is the line where the problem occurs in the file CMakeDetermineCompilerABI.cmake line 31<br>
<br><b>try_compile(CMAKE_${lang}_ABI_COMPILED</b> <b> --> ERROR</b><br> ${CMAKE_BINARY_DIR} ${src}<br> CMAKE_FLAGS "${CMAKE_FLAGS}"<br> "-DCMAKE_${lang}_STANDARD_LIBRARIES="<br>
# We need ignore these warnings because some platforms need<br> # CMAKE_${lang}_STANDARD_LIBRARIES to link properly and we<br> # don't care when we are just determining the ABI.<br>
"--no-warn-unused-cli"<br> OUTPUT_VARIABLE OUTPUT<br> COPY_FILE "${BIN}"<br> )<br><br>Does it mean the file is not being compiled. I checked in a couple of other posts and found that if a custom compiler is used <i>try_compile</i> uses information provided in CMakePlatformTests.txt file to get more information about the custom compiler to generate the executable. Should I provide additional information ? When I setup my tool chain the compiler is available at shell (ppc_4xx-gcc and ppc_4xx-g++). This problem is specific to my tool chain, cmake works fine for gcc and g++ in my environment.<br>
<br>Another thing to note is that the problem is only for <b>ppc_4xx-gcc</b> which is my C compiler, I am not getting similar problem for <b>ppc_4xx-g++</b> which is my C++ compiler.<br><br>I am attaching the new build file.<br>
<br>With Regards,<br>Niranjan<br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 1:24 PM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com" target="_blank">brad.king@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 3/19/2013 5:51 PM, Niranjan M wrote:<br>
> --debug-trycompile<br>
...<br>
<div class="im">> -- Detecting C compiler ABI info<br>
</div><div class="im">> Unable to find the executable at any of:<br>
><br>
> DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/cmTryCompileExec<br>
> DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec<br>
> DIR/mysql-connector-c-6.0.2/CMakeFiles/CMakeTmp/Development/cmTryCompileExec<br>
<br>
</div>This means CMake cannot find any executable produced by the<br>
compiler after building a small test project. CMake wants<br>
to find the executable to read information about its ABI as<br>
produced by the compiler toolchain.<br>
<br>
The problem is either that the executable really isn't being<br>
produced or that the toolchain names it something other than<br>
what CMake thinks. Before we spend too much time on this<br>
please test with a more recent CMake version.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Brad<br>
</font></span></blockquote></div><br>