<div class="gmail_quote">On Wed, Apr 20, 2011 at 9:43 AM, David Doria <span dir="ltr"><<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Apr 20, 2011 at 9:04 AM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
> If you are setting the CXX compiler, you should also probably be setting the<br>
> C compiler.<br>
><br>
> I always use environment variables to do this:<br>
><br>
> export CC=/home/doriad/src/gcc-4.5.2/bin/gcc/gcc<br>
> export CXX=/home/doriad/src/gcc-4.5.2/bin/gcc/g++<br>
> ccmake ../../src/ITK<br>
><br>
> If that still doesn't work, then inspect the contents of the file<br>
> CMakeFiles/CMakeError.log to see what the actual errors are, and post them<br>
> here. (CMakeFiles/CMakeOutput.log may also have relevant results in it...)<br>
><br>
><br>
> HTH,<br>
> David C.<br>
<br>
</div>Hm, so there is no 'gcc' executable after I built gcc. Gcc's configure<br>
says: "The following languages will be built:<br>
c,c++,fortran,java,objc". So I'm assuming it should be there? I tried<br>
setting the ITK C compiler to g++ as well, but no dice.<br>
<br>
In CMakeFiles/CMakeError.log<br>
<br>
of course it says:<br>
<br>
CMakeCCompilerId.c:2:3: error: #error "A C++ compiler has been selected for C."<br>
<br>
The executables that were built are:<br>
<br>
[doriad@daviddesktop gcc]$ find . -executable -type f<br>
./as<br>
./cc1-dummy<br>
./jcf-dump<br>
./cc1<br>
./jvgenmain<br>
./gcj<br>
./config.status<br>
./lto-wrapper<br>
./cc1plus-dummy<br>
./cc1plus<br>
./cc1obj-dummy<br>
./gcov<br>
./nm<br>
./cpp<br>
./f951<br>
./xgcc<br>
./cc1obj<br>
./gfortran<br>
./collect2<br>
./collect-ld<br>
./jc1<br>
./g++<br>
./gcov-dump<br>
<br>
Any thoughts?<br>
<br>
Thanks,<br>
<font color="#888888"><br>
David<br>
</font></blockquote></div><br><br>Sounds like you must have gotten errors when you built gcc...<br><br>Pore through the log of what happened during the gcc build maybe?<br><br>Are you building gcc from source, or using some package manager to build it for you? (MacPorts, something else?)<br>
<br><br>